A pattern from 1865 is playing out in 2026 enterprise AI — and most companies never saw it coming.

Start Here: What Is Jevons Paradox?

In 1865, British economist William Stanley Jevons publishedThe Coal Question, a book with a deeply counterintuitive thesis. He argued that improvements to the efficiency of steam engines — making them burn coal far more economically — would not reduce Britain’s total coal consumption. It would increase it dramatically.

His logic was simple: when a resource becomes cheaper to use, people usemore of it. Lower cost per unit lowers the barrier to adoption. More use cases become viable. More industries lean in. The aggregate demand grows far beyond what the efficiency gains saved. You don’t consume less of the thing; you find a hundred new reasons to consume it.

He was right. This effect became known asJevons Paradox — the uncomfortable truth that technological efficiency gains often increase resource consumption rather than reduce it.

It has been observed in energy, transportation, computing, and bandwidth. And right now, in May 2026, it is playing out in real time across enterprise AI.

What Just Happened

Two stories broke in mid-May 2026 that crystallised what many in the industry had been quietly sensing for months.

Microsoft began winding down internal access to Anthropic’s Claude Code for thousands of its own engineers — specifically across the Experiences + Devices division covering Windows, Microsoft 365, and Teams. By end of June 2026, those engineers will be redirected to GitHub Copilot CLI instead. This is the same Microsoft that has invested over $13 billion into OpenAI and hosts Anthropic’s workloads on Azure. The signal is unmistakable: even with deep infrastructure ownership, third-party token costs at scale become painful.

Uber reportedly exhausted its entire 2026 AI budget by April — four months into the year. With somewhere between 84 and 95 percent of engineers using AI coding tools monthly and a large and growing share of production code being AI-generated, token consumption blew past every internal forecast. The technology had worked exactly as intended. The economics had not been modelled for it.

These are not isolated incidents. They are the visible edge of a broader reckoning.

Why Jevons Paradox Explains Everything

The enterprises that adopted Claude Code, Copilot, and similar agentic tools in 2024 and early 2025 did so during a period of heavy subsidisation. AI labs — under competitive pressure and racing for market share — kept pricing low, sometimes below cost, to build usage and lock in developer workflows.

Companies responded rationally. They adopted aggressively. They built workflows around these tools. And crucially, they budgeted for AI as if it were traditional SaaS: a predictable per-seat or flat-rate line item that finance could model cleanly.

What they got instead was usage-based token billing — where highly capable tools get used constantly, and where the most valuable agentic workflows (multi-step code generation, automated testing, long-context reasoning) consume far more tokens per session than a simple chat query ever would.

Jevons Paradox kicked in hard. As the tools became genuinely useful, engineers reached for them constantly. The efficiency gain per task was real — but the total volume of tasks AI was applied to grew faster. The unit cost came down; the aggregate spend exploded.

No one was being reckless. They were just behaving exactly as users of a useful technology always do.

The Forces That Collided

Several things happened simultaneously to create this crunch.

Pricing shifted. Through 2025 and into 2026, AI labs moved from promotional and flat-rate models toward honest usage-based billing. Prices for frontier model inference rose 20 to 37 percent in some tiers. The subsidised introductory phase of the enterprise AI market was closing.

Consumption was underestimated everywhere. Most enterprises based their token usage forecasts on early-adopter pilots and simple query patterns. They did not anticipate what agentic workflows would look like at scale — long context windows, iterative back-and-forth with code environments, parallel agent runs. The consumption profile of a developer genuinely integrating AI into their daily workflow is an order of magnitude heavier than the pilot suggested.

Infrastructure reality reasserted itself. Running frontier models is genuinely expensive. The economics that make it cheap at a promotional level do not hold at enterprise scale without subsidy. Even the largest cloud operators, with the most favourable unit economics in the industry, are finding that third-party token costs sit uncomfortably on the balance sheet.

The Fork in the Road

This creates a structural tension that neither enterprises nor AI labs can easily resolve.

If enterprises cut back usage to manage costs, AI labs face slower revenue growth at exactly the moment they need strong numbers — several are eyeing IPO windows or need to justify valuations to investors. That is a problem.

If labs cut prices significantly to retain volume, their own unit economics deteriorate at a time when they are still burning enormous sums on training runs and infrastructure. That is also a problem.

The most likely path is not a neat resolution but a market forcing function: enterprise buyers will become far more disciplined about where AI spend is justified, which will accelerate optimisation rather than retreat.

Expect to see model routing mature quickly — the practice of directing simple queries to cheaper, smaller models and reserving frontier inference for genuinely hard tasks. Expect caching, fine-tuning on domain-specific data, and distillation to become standard parts of the enterprise AI stack rather than advanced techniques used by a few. And expect a meaningful shift toward strong open-weight models — DeepSeek, Qwen, Llama derivatives — running on-premises or via lower-cost inference providers, particularly for workloads where data residency and predictable cost matter more than peak capability.

The “vibe coding” era — where engineers use AI tools liberally and broadly without much thought to token spend — is likely to give way to something more deliberate. Finance teams now have the data to ask the hard questions, and they will.

What This Means in Practice

For anyone operating at the intersection of enterprise technology and AI — which, if you work in digital workplace, infrastructure, or IT strategy, is increasingly all of us — a few things are worth watching.

The ROI conversation is now unavoidable. The magic-feeling phase of enterprise AI, where adoption was justified by enthusiasm and competitive pressure alone, is giving way to measurement. Real productivity gains against actual token burn. That is a healthy shift, but it requires instrumentation most organisations have not yet built.

Build vs. buy calculus is shifting. Microsoft’s decision to push engineers toward its own tooling rather than pay Anthropic’s rates is a preview of how large enterprises with engineering capacity will respond. Owning the stack — or at least the inference layer — becomes strategically valuable.

Budget modelling for AI needs to look different from SaaS modelling. Usage-based costs with high variance require different financial governance than per-seat licensing. Teams that have not updated their procurement and budgeting frameworks for token economics will keep running into Uber-style surprises.

The technology is not in retreat. The hype phase is ending, which is actually good for the technology’s long-term credibility. What emerges from this price discovery period will be a more durable foundation: AI spend tied to measurable outcomes, workflows optimised for real-world economics, and organisations that understand what they are actually buying.

The Bottom Line

Jevons was writing about coal. But he was really writing about human behaviour in the presence of efficiency. We do not save what we make cheaper — we find more things to do with it.

Enterprise AI is at that inflection point now. The easy, subsidised phase is ending. The economics are catching up to the technology. That is not a sign that AI has failed to deliver — in many cases, the tools have worked remarkably well. It is simply the normal lifecycle of a technology maturing from hype into infrastructure.

The companies that navigate this well will treat AI spend like any other major operational cost: measuring it, routing it intelligently, and connecting it to outcomes. That is less exciting than the story of magic tools that write code overnight. But it is how useful technologies actually get embedded into how organisations work.