“An operating Group CTO on why enterprise AI autonomy fails for arithmetic reasons, not technical ones — and what to measure before you buy”
His work sits at the point where enterprise architecture meets financial accountability. That covers SAP S/4HANA modernisation under RAP and Clean Core principles, AI systems designed to be governable rather than merely capable, and the operational reality of India's DPDP framework alongside ISO 27001 controls. He writes about a problem most enterprise AI programmes discover late. Automation business cases are built on the process as documented, but the process as executed carries far more variance, and that variance was historically absorbed by people rather than by systems. He describes this as the Variant Coverage Ratio: the share of real process variants an automation actually handles, against the number the business case assumed. The gap between those two figures is where pilots quietly fail. The same reasoning produces his four-factor readiness test. Autonomy Readiness = Specification x Exception Coverage x Observability x Reversibility. The relationship is multiplicative rather than additive, because a zero on any single factor does not make autonomy imperfect. It makes it unsafe. He holds an M.Tech in Artificial Intelligence from IIT Patna. That background anchors a view of technology investment that is simultaneously engineering and economics: architecture decisions are capital allocation decisions, and they should be defended as such.
Digital transformation and AI governance advisory. Frameworks and analysis on enterprise AI architecture, technology governance, and SAP S/4HANA.
