The free-spending era of enterprise AI is over. CFOs across the Global 2000 are no longer asking "How do we adopt AI?" They're asking something far more uncomfortable: "What exactly did we spend, and what did we get for it?" The companies that survive the coming budget reckoning will be the ones that built measurement into the foundation — not bolted it on after the fact.
A new KPMG Global AI Pulse survey released June 24, 2026, covering more than 2,145 C-suite and senior business leaders across 20 countries at organizations with annual revenues exceeding $50 million, laid out the numbers plainly. Only 7 percent of leaders report establishing AI ROI. Nearly one in four — 24 percent — face active investor pressure to prove value. And 42 percent have only partial visibility into how their AI spending accumulates.
This is not a technology problem. It is a governance and accountability problem, and CFOs are now the ones being asked to solve it.
The Signal Everyone Missed
For most of 2024 and into 2025, enterprise AI spending followed a recognizable pattern: centralize the budget, lower the friction, encourage experimentation. The logic was sound. If you make AI tools easy to access and absorb the cost centrally, adoption accelerates and you learn faster.
The problem is that it created a textbook spending dynamic — teams consumed the tool while another budget paid the bill. Usage expanded faster than outcomes could be documented. And unlike traditional software licenses with predictable monthly fees, AI runs on token economics: small charges per query, per output, per agent action, per tool call, per retry. One employee using AI to draft a document is trivial to price. Ten thousand employees using AI agents that touch customer data, contract repositories, CRM systems, and internal knowledge bases — each agent potentially calling dozens of tools per task — is not.
A Forbes analysis published June 22, 2026, captured the moment precisely. Uber, a company with deep technical sophistication, set a monthly token cap per user after AI spending ran ahead of plan. Amazon, Walmart, Cisco, and Meta all moved to rein in AI tool use as costs strained budgets. These are not companies that lack engineering capability. They are companies that discovered token economics at scale behaves more like cloud compute than software licenses — and treated it accordingly.
Gartner's Warning Proved Right (Twice)
Gartner flagged the coming rationalization in stages. The initial warning: at least 30 percent of generative AI projects would be abandoned after proof of concept by the end of 2025. The sharpened update: at least 50 percent of generative AI projects had been abandoned after proof of concept by the end of 2025, citing poor data quality, weak risk controls, rising costs, and unclear business value.
That 50 percent figure deserves careful reading. These were not failed experiments from naive companies. Many were well-resourced pilots at sophisticated enterprises that simply could not answer the question: What is this worth? Not in vision. Not in potential. In dollars this quarter.
The KPMG data confirms where the gaps remain. Only 22 percent of organizations have reached a stage where AI is "part of everyday work" — that number is actually up dramatically from 13 percent in Q1 2026, the largest single shift on the AI maturity curve. The momentum is real. But turning momentum into documented financial returns is where most organizations stall. 33 percent of leaders cite limited understanding of usage costs as a key deployment challenge specifically for AI agents.
What Vendors Are Reading
Enterprise AI vendors are not waiting for their customers to figure this out. The vendors that thrive through the budget reckoning will be the ones that give procurement and finance teams a reason to defend the spend.
OpenAI added ChatGPT Enterprise tools that give administrators credit usage analytics, consumption tracking by team, adoption pattern visibility, and cost exposure reporting. Microsoft built a comparable management layer around Copilot — admin dashboards for prompt activity, agent engagement, and business impact analysis. AWS added cost allocation tools for Amazon Bedrock, letting engineering teams tag and track model usage by application or business unit. Databricks is adding AI spend limits, safeguards against runaway agent costs, and cross-provider recommendations.
The pattern is not accidental. These companies are betting that the next enterprise sale will be won not only on model quality, but on controllability. "Production systems need receipts" is the clearest framing I have heard from a vendor in this space. The era of performance benchmarks as the primary sales motion is giving way to an era of cost dashboards and chargeback reports.
The CFO Conversation Is Now Technical
This shift puts CIOs and CTOs in an unfamiliar position. The CFO conversation used to be strategic and relatively abstract: AI will unlock efficiency, transform operations, drive competitive advantage. That conversation is being replaced by a much more specific one.
How much did the AI workflow cost last month? Which team used it most? Did it reduce headcount pressure, accelerate revenue, or improve customer outcomes? Did we pay for the same capability through two different vendors? Which model handled the task — and could a smaller, cheaper model have done it just as well?
These are not questions that can be answered with a vision deck. They require infrastructure: cost allocation by business unit, usage tracking at the team and workflow level, model-level attribution, and some framework for calculating cost per outcome — cost per resolved support ticket, cost per reviewed contract, cost per qualified sales lead, cost per shipped feature.
The good news from the KPMG data: leaders who built that infrastructure are seeing dramatically different results. Organizations with strong cost visibility are five times more likely to report established ROI — 15 percent versus 3 percent. That is not a marginal difference. That is a structural advantage.
Accountability Changes Everything
The KPMG finding that may matter most sits at the leadership accountability layer. In most organizations, AI ownership is murky. Only 24 percent of leaders say the CEO is accountable for AI-driven business outcomes. Another 29 percent point to the "broader C-suite" — which, in practice, often means the accountability diffuses and no single leader owns the outcome.
The data on what happens when that changes is striking. Organizations where the CEO is explicitly accountable for decisions based on AI outputs report:
- 60 percent confidence in their AI strategy (versus 22 percent)
- 57 percent meaningful business value realization (versus 21 percent)
- 14 percent established ROI (versus 4 percent)
Clear accountability is not a bureaucratic exercise. It is a forcing function. When a CEO owns the outcome, the questions get sharper, the governance gets real, and the measurement gets built in from the start rather than requested after the fact.
The Budget Center Migration Coming in H2
Finance leaders will push AI costs back to business units. This migration is already underway at early-moving companies, and the KPMG data suggests it will accelerate. When a sales team sees its own AI bill in its monthly operating review, the question shifts from "Can we use AI?" to "Is this the cheapest reliable way to get the work done?"
That question — which feels like a constraint — is actually what produces the right decisions. Teams start to optimize. They distinguish between workflows where AI adds clear, measurable value and workflows where it adds cost without proportionate benefit. They push back on vendors who can not explain pricing or demonstrate outcomes. They start to think about AI the way engineering teams eventually thought about cloud compute: not as a magic unlimited resource, but as a cost center requiring capacity planning, optimization, and periodic cleanup.
For platform vendors, this moment is an opportunity. For point solutions with weak usage data and broad productivity claims, it is a serious threat. Procurement teams will ask the simple question: How many AI subscriptions does this organization actually need? Vendors that can not answer with hard numbers will be the first line items cut.
What Survives the Budget Reckoning
Not every AI investment is in danger. The KPMG data, the Forbes analysis, and observations from enterprise conversations point to a consistent pattern of what holds up under CFO scrutiny.
Workflows with a measurable cost-per-outcome. Contract review AI that reduces legal review time from four hours to forty minutes, with a clear cost per contract reviewed, survives. Broad "AI-powered productivity" that cannot be connected to a specific metric does not.
Platforms with granular usage reporting. Tools that give administrators visibility into who is using what, at what cost, with what outcomes, will be defended by the teams that own them. Tools that produce only aggregate claims will be difficult to protect.
Agents with defined scope and cost guardrails. The fear among finance teams about AI agents is real: always-on agents that call tools repeatedly, retry tasks, and hand work between models can generate far larger bills than anyone anticipated. Agents with configurable cost caps, usage monitoring, and clearly scoped permissions are fundable. Agents running without those controls are a CFO's nightmare scenario.
The Parallel That Keeps Coming Up
Everyone in technology who has been around long enough has seen this pattern before. Cloud computing had its own free-spending period. Usage expanded rapidly, bills arrived that surprised the CFO, and an entire discipline emerged: FinOps, reserved instances, rightsizing, chargeback models, idle capacity cleanup. The companies that moved fast on cloud governance came out ahead. The ones that waited paid for the same infrastructure at higher cost for longer before getting around to optimization.
AI is walking the same road, only faster and with a harder-to-measure outcome. The infrastructure layer is already moving in the right direction — the vendor dashboards, the cost controls, the token analytics. The organizational layer is catching up. The question for every enterprise leader reading this is which side of that gap you want to be on when the H2 budget reviews hit.
Decision Framework
For CFOs: Build cost visibility infrastructure now, before Q3 reviews. Require any AI project above $250K annually to have a defined cost-per-outcome metric at approval. Move AI costs to business units for anything in production; keep centralized budgets only for active pilots. Set a policy on token caps for agent-driven workflows before the first runaway bill arrives.
For CIOs and CTOs: The conversation with your CFO in Q3 will be different from Q1. Come in with usage data by team and workflow, model attribution, and cost trend analysis. Identify the 20 percent of AI investments producing 80 percent of measurable value and be ready to defend them specifically. Flag the 30 percent that cannot be connected to a business outcome — better to surface them now than to have finance discover them first.
For business unit leaders: When your IT department starts charging AI costs back to your budget this fall, that is not a tax. It is an accountability mechanism. Use it to sharpen your own portfolio. The AI tools that make your team more effective will survive the scrutiny. The ones that generate impressive demos will not.
The productivity promise of enterprise AI is real. The execution gap between promise and documented outcome is also real — and CFOs across the Global 2000 are running out of patience for it.
Continue Reading
Sources:
- KPMG Global AI Pulse Q2 2026, June 24, 2026 — 2,145 C-suite and senior leaders across 20 countries: kpmg.com
- Forbes / Ron Schmelzer, "CFOs Are Coming For The Enterprise AI Budget," June 22, 2026: forbes.com
- Gartner Forecast, 2026 — at least 50% of generative AI projects abandoned after PoC by end of 2025
