Twenty years of enterprise technology transformation across EMEA produces a clear pattern library: the process failures that repeat regardless of the technology chosen, the people dynamics that defeat even well-resourced programmes, and the leadership behaviours that determine outcome more than the technology does.
Cloud-native infrastructure was the last major infrastructure paradigm shift. AI workloads are forcing the next one. Understanding what is changing, and what is not, is the architectural judgment that will define enterprise infrastructure strategy for the coming decade.
Multi-agent workflows multiply token consumption non-linearly — agents calling agents, re-planning, retrying. Without observability and governance in place first, scaling agentic AI is scaling an unmetered cost problem.
IT owns the bill, business owns the usage — a split that breaks down for token spend specifically. Chargeback and showback models adapted from cloud FinOps, and what accountability actually needs to look like.
Model right-sizing, prompt and context engineering, caching, and retrieval design are cost levers as much as performance levers. Optimization has to be owned at design time, not applied after a bill shocks someone.
Most enterprises cannot answer what they spent in tokens this week, on what, and whether it was worth it. Real-time token metering is an architecture decision made at design time, not a reporting problem solved after the fact.
Token cost is becoming the defining AI cost-control problem for enterprises, the way cloud spend was a decade ago. Most organisations have neither the real-time visibility nor the operating model to manage it. This is the conversation that needs to start now.
AI is a powerful execution engine. But the expertise required to know whether its output is right, where it will fail, and what to do about it remains irreducibly human. Domain knowledge is not a legacy requirement in the age of AI. It is the foundation that makes AI work.
AI is becoming the execution layer for an expanding range of work. But the architectural function, defining what should be built and why, remains irreducibly human. The enterprises that understand this distinction will deploy AI far better than those still debating job displacement.
DORA compliance is routinely justified on regulatory grounds — the cost of non-compliance exceeds the cost of the programme. This is a sufficient justification but not the strongest one. The operational resilience capability that DORA requires has business value well beyond avoiding fines.
