
About
I own technology and product strategy end to end — and I have spent 28+ years doing it on both sides of a line most careers stay on one side of.
Most technology leaders come from software or from industry. I came from both. I started in civil and plant engineering, spent years turning drawings into models and plants into data, and now run product and platform strategy for enterprise SaaS. That is an unusual seam to sit on, and it is the reason I am useful: I have stood on the shop floor whose problem the software is supposed to solve, and I have owned the P&L consequences of solving it badly.
The arc
1997 – 2005
Drawing boards, then satellites
I trained in civil engineering and started on plant layouts and structural drawings — the least glamorous, most unforgiving end of the discipline, where a misaligned foundation is discovered in concrete. That grounding is why I have never treated software as separable from the physical thing it describes. By the early 2000s I was leading a 30-person photogrammetry team at Cadworld, building an early pipeline that combined satellite imagery with aerial photography for 3D modelling — work delivered with OSIG in Canada that fed Google's 3D mapping data pipeline. Nobody had a workflow for combining those two sources; we wrote one, and productivity rose 50%.
2005 – 2018
Making 50-year-old engineering firms digital
At M. N. Dastur I took an organisation with half a century of 2D drafting practice and moved 32 engineering disciplines onto BIM-based virtual engineering. The technology was the easy half. The hard half was persuading engineers with thirty years of judgement in their hands that a model could hold what a drawing held. At Tata Steel I introduced drone survey, LiDAR and digital twins across 800+ acres of live plant — the first such deployment in that setting — which recovered roughly 30% of revenue leakage and cut engineering rework by a fifth.
2019 – 2022
A steelmaker going public
Gunung Raja Paksi is Indonesia's largest private steelmaker, and it was becoming a public company. I owned the digital and data agenda through that transition: ERP across 25+ departments, a consolidated reporting layer that gave the board one set of numbers instead of several, and predictive models for scrap price and FX that turned procurement from a months-long cycle into a days-long one and saved over $1M a year. Working inside an IPO teaches you quickly which numbers survive scrutiny and which merely sound good.
2022 – present
Rebuilding a SaaS platform, and the business model under it
I own product and technology strategy for a global enterprise SaaS platform — the roadmap I report weekly to the CEO and founders, the commercial model beneath it, the organisation that builds it, and the infrastructure it runs on. In practice that has meant a monolith re-architected into container-native microservices, release cadence from twice a year to daily, infrastructure cost down 70%, and an engineering organisation grown from 3 people to 85+ across 4 squads. It has equally meant replacing flat-fee licensing with consumption-based pricing and moving the customer segment from SMB to enterprise, which took average customer renewal from $2–5K to $35K+.
How I work
Technology investment is a business argument
Every programme I have run had its ROI model agreed with Finance before it started, and reported quarterly after. Not because it is good governance theatre, but because a number nobody agreed to in advance is a number nobody believes afterwards.
Execution beats architecture
I have seen more value destroyed by elegant designs that shipped late than by pragmatic ones that shipped. I bias toward the version that reaches production, then improves.
Build the organisation, not just the system
Platforms outlive the people who build them only if the operating model does too. Hiring, squad structure, on-call, and how decisions get made are architecture by another name.
Stay close to the floor
The reason I can translate between a plant manager and a product team is that I have done work on both sides. I still read the shop-floor problem before I read the dashboard describing it.
Outside the day job
I wrote Mastering 3D Plant Engineering, Digitalisation & Automation because the field guide I wanted did not exist — something that treated photogrammetry, BIM, LiDAR and CAD automation as things you actually deploy in a working plant rather than as a technology survey.
I also founded Imotara, a privacy-first emotional wellness companion, as a philanthropic initiative. It exists because I think we are building a generation of technology that is very good at capturing attention and very poor at supporting the people giving it. No ads, no paywall on the core, data local by default, and 22 languages including nine Indian regional ones.
Education & credentials
- Master’s in Computer Applications
- Post Graduate Diploma in Information Technology
- Diplomas in Civil Engineering and Transport Management
- PMP · Six Sigma Green Belt
- Certifications across AI/ML, business intelligence and RPA
Based in Kolkata, India. Work has spanned India, Indonesia, Canada, the US, Europe and Japan.