One architect. Full accountability.
Twenty-one years directing enterprise technology — now advising boards, governing vendors, and delivering full-stack outcomes under engineering governance.
The situation you're probably in
You don't need this page to tell you what's wrong. One of these is why you're here.
- No one senior owns your technology risk. Decisions get made by whoever is loudest in the room.
- Your systems aren't documented, and the people who built them hold the only copy of the source.
- Something critical is fragile. Or it's already down.
- You need to modernise, and you can't justify hiring a technology leader full-time.
The record
- 21 years
- Enterprise technology leadership
- 13,000+
- Users in the enterprise I ran
- ~BDT 8 crore
- Annual technology investment directed
- 6 days
- To move a university to fully remote operations, no disruption to teaching
- 13 days
- To recover a failed production platform, working alone
- 17
- Engineering documents handed to the client at the end of it
Four ways to engage. Nine services inside them.
Standing advisory
A retainer relationship where I sit inside your governance rather than beside it.
Recovery and reconstruction
The crisis door. Stabilise, preserve, document, rebuild.
Transformation and architecture
Modernisation, ERP, enterprise architecture, automation.
Security, cloud and continuity
Posture, policy, hybrid cloud, disaster recovery.
What you keep
Every engagement ends with documentation you own. Versioned systems, decision logs, continuity plans, source code in your custody. You should finish an engagement with Hikvara less dependent on outside help than when you started — including less dependent on me.
That's not a nice sentiment. It's the deliverable.
Technology, governed.