Sharoze Iftikhar
RevOps Solutions Architect and Developer
Many solutions architects hand off to a developer. Many developers are not responsible for the architecture.
RevOps requires deep domain knowledge (attribution models, lifecycle stage logic, pipeline mechanics, CRM internals) and production code skills. Many practitioners lean toward one or the other.
When those roles are separate, the gap between strategy and execution can slow delivery, create misalignment, and produce implementations that work technically but miss the operational intent.
What I believe
Architecture-led delivery.
Scope the system design before touching the tooling.
Data precedes integrations.
Most RevOps problems are data problems first, integration problems second.
Code unlocks scale.
Configuration is not a substitute for code. Workflow logic has limits; custom code does not.
Results over concepts.
I ship working systems, not slide decks.
Years active
6+
years across commercial, operations, and revenue systems work, now focused on RevOps.
Capabilities
- HubSpot architecture and custom development
- CRM migrations
- Attribution model implementation
- Data pipelines
- Custom integrations
- HubSpot app development
Tech Stack
- HubSpot
- Python, FastAPI, SQLite
- Docker, Hetzner, Hostinger, Cloudflare
- n8n, Workato
- NetSuite integrations
- Stripe integrations
Also ships products
I also build and operate the Business Days Calculator, a HubSpot workflow app for business day calculations, available at networkdays.io.