From Tokenmaxing to Tokenomics
Enterprises spent the last two years getting everyone into the AI tent. Now the bill has started to land and the conversation has shifted from "are your employees using AI?" to a much harder question: "what is the ROI of the AI spend?"
This is not a story about AI hype fading. I am an AI believer, AI is working and the adoption is real. The problem is that the way enterprises adopted it, by treating unlimited consumption as a virtue, has created a spending crisis that most organizations were not prepared for. The first phase was enablement. The next phase is governance.
The transition has a name. Let's call it Tokenomics.
First, Let's Talk About Tokenmaxing
Before you can govern AI spend, you have to understand how it got out of control. The answer is a behavior called tokenmaxxing (source). The practice has "turned token usage into a benchmark for productivity and a competitive measure of who is most AI-native."
The trigger was internal leaderboards. Inside Meta, an employee built a ranking system called "Claudeonomics" that scored all 85,000+ employees by token consumption and gave titles like "Session Immortal" and "Token Legend" to the top users (source). The result? Meta's engineers burned through 60.2 trillion tokens in a single month. At Anthropic's API prices, that would cost $900 million. Even at enterprise discounts, the bill likely landed above $100 million. For a month of token consumption.
Microsoft ran the same playbook. An internal token dashboard, live since January 2026, ranked employees by usage across the whole company. Distinguished-level engineers, the most senior individual contributors, landed in the top five. VP-level leaders made the top ten and twenty, despite spending most of their days in meetings. The number had become the signal of being "AI-native," so people optimized for the number.
The one counterexample worth naming is Shopify. The company built the first internal token usage dashboard, then renamed it from "leaderboard" to "usage dashboard" when they saw where the competitive framing was going. They added circuit breakers that automatically cut off access when personal spend spiked in a single day, which caught runaway agents and surfaced infrastructure bugs. And the head of engineering personally reviews what top-spending engineers are actually building (source). The result is high usage that connects to real work. That is the standard every org should be building toward.
Why did tokenmaxxing take hold so widely? Because in the enablement phase, consumption was the metric. Adoption dashboards tracked active users, message volume, and seats deployed. More tokens meant more engagement, and more engagement meant the rollout was working. The behavior the org rewarded was the behavior it got. And now it is the source of the problem.
The Budget Wall
The bill is no longer theoretical. Enterprises are hitting it in real time, and some of the most sophisticated technology companies in the world are among the first to feel it.
Uber rolled Claude Code out to its roughly 5,000 engineers in December 2025 and, to drive adoption, built an internal leaderboard ranking teams by AI usage. It worked spectacularly. By March, 84% of engineers were classified as agentic coding users, and 70% of new code traced back to AI assistance (source).
It also burned through Uber's entire 2026 AI tools budget in four months, at per-engineer monthly costs of $500 to $2,000 (source). COO Andrew Macdonald called it a "head-exploding moment" and admitted, publicly, that the connection between all that spend and customer value "is not there yet" (source). Uber has since capped per-employee AI spend at $1,500 a month and built a request process for engineers who need to go higher (source).
Microsoft followed a similar arc. In December, it gave thousands of engineers Claude Code on the company's dime. Six months later, it cancelled those licenses across its Experiences and Devices division, the group that builds Windows, Microsoft 365, Teams, and Surface, and migrated engineers to GitHub Copilot CLI by June 30 (source). Part of that decision is about platform control, Microsoft owns GitHub and sells Copilot to the world. But cost is also named plainly. Claude Code's consumption-based pricing scales exactly the way that just broke Uber's budget.
The pattern is not limited to tech giants. Just recently, I was talking to a friend who works at a leading financial institution. He told me they had been struggling with their Claude API spend to the point where they had to make a hard call: pull all employee access to Claude Opus and downgrade everyone to Sonnet and Haiku. Not because the Opus outputs weren't good. Because the budget was gone. An entire tier of model capability, taken off the table, not for performance reasons but for cost ones.
The ROI Question Is Not Going Away
Here is the data that should make every executive uncomfortable. MIT research found that 95% of generative AI pilots delivered no measurable profit-and-loss impact despite billions invested (source). Enterprise AI token consumption has increased 13x since January 2025 (source). And 73% of enterprises reported their AI costs exceeded original projections, even as the blended cost per million tokens dropped 67% year-over-year (source).
Read that last one carefully. Prices are falling. Spend is rising faster. Total cost equals price per unit multiplied by volume consumed. The first variable is moving in your favor. The second is moving against you, faster.
Average enterprise AI spend is projected to jump roughly 65%, from $7 million in 2025 to $11.6 million in 2026 (source). For companies that built no governance layer during the enablement phase, that number can arrive as a surprise.
The conversation in every CFO and CIO meeting right now is the same: we are spending more than we budgeted. We cannot point to the return. And we cannot get in front of the finance team with nothing but a usage dashboard.
Enterprises Need Tokenomics
Tokenomics is not cost-cutting. It is not a mandate to do less with AI. It is a discipline: the principles and practices for matching AI spend to AI value, at the organizational level.
Think of what cloud FinOps did for infrastructure spend. Before FinOps, cloud bills were treated like electricity, a utility cost you paid and moved on. FinOps brought attribution, allocation, tagging, anomaly detection, and optimization into the operating model. It did not reduce usage. It made usage visible, accountable, and sustainable. That is what Tokenomics does for AI.
Here are some ideas:
Route to the right model. Not every task requires your most capable model. A JSON formatting check, a label classification, a two-line summary: these are not frontier tasks. They are clerical tasks, and smaller models handle them well at a fraction of the cost. The gap between frontier and budget-tier models can be 10 to 30 times in cost per token for comparable routine work (source). Researchers at UC Berkeley built RouteLLM, an open-source routing framework that sends everyday queries to cheaper models while preserving 95% of GPT-4-level quality. Cost reduction on standard benchmarks: over 85% (source). Teams that route consistently report 60% to 80% cost reduction with no meaningful quality loss (source).
Implement role-based model access. Not everyone in an organization needs the same model tier. A data scientist building complex multi-step reasoning pipelines has different needs than a customer service rep drafting email responses. Define model tiers by role. Give your power users access to the frontier. Give everyone else the model that matches the complexity of their actual work. This is not about restricting access for its own sake. It is about allocating the right capability to the right job, the same way you think about software licenses or cloud instance types.
Set token quotas for roles and business functions. Token budgets work exactly the way cloud resource budgets work. Define an expected monthly allocation per role, per team, per use case. Build alerts that fire at 70% consumption so you are never surprised at month-end. Build a request process for exceptions, the way Uber eventually did, but proactively rather than reactively. The organizations that will manage this best are the ones that treat token budgets as a first-class planning artifact, not a dashboard you check after the fact.
Renegotiate your AI contracts. Most enterprise AI contracts were signed during the enablement phase, when the primary goal was access, and the pricing was frontier-model-first, volume-light. That was the right deal for year one. It is not the right deal for year three. Go back to your AI vendors with actual consumption data, tiered usage patterns, and a conversation about committed spend versus on-demand. AI labs are competing aggressively for enterprise contracts right now, and you have more leverage than you did eighteen months ago.
Explore cloud-hosted open source models. The open-source model ecosystem has matured considerably. Meta's Llama family, Mistral, Qwen, and a growing roster of specialized models are now available through AWS Bedrock, Azure AI, and Google Vertex, alongside proprietary options. For workloads where the task is well-defined, a cloud-hosted open-source model can deliver strong results at meaningfully lower cost than frontier proprietary APIs, without the operational overhead of running your own infrastructure.
Consider self-hosted open source for high-volume, constrained workloads. For organizations with the engineering capacity to support it, self-hosted open-source models change the economics entirely. No per-token billing. Predictable infrastructure costs. Full control over the data. This is not the right answer for all workloads, and it is not free to operate. But for the right use cases, specifically high-volume, well-scoped tasks where a smaller model clearly fits, the cost differential versus a frontier API is substantial. It is worth putting into the conversation.
OpenAI May Be Doing the Math as well
There is news worth watching here. The Wall Street Journal reported in June 2026 that OpenAI is mulling sharp cuts to what it charges for tokens, in anticipation of similar moves from Anthropic, as both companies compete aggressively for enterprise market share (source).
This is not entirely surprising. API prices across the major providers have already dropped roughly 80% since early 2025, driven by hardware improvements, model efficiency gains, and intensifying competition (source). OpenAI CFO Sarah Friar put the cost drop from GPT-4 to GPT-4o alone at 97% over roughly two years (source). The direction of travel on unit economics is clear.
The strategic logic behind this price reduction is clear: it is undercutting Anthropic's lead with Claude Code and Opus-class models. OpenAI is not optimizing for this month's revenue. They are optimizing for the enterprise footprint and long term value, when AI spend is embedded into operating models and switching costs are real. Lower token costs today buy stickiness. That is a lifetime value calculation, not a margin one.
If the rumors are right and prices do fall significantly, it will provide some relief to budgets under pressure. But it will not solve the governance problem. If you have no routing layer, no quota system, and no attribution model today, lower token prices will simply mean the same ungoverned consumption at a lower unit rate. Governance is not a response to high prices. It is how you run a mature AI program.
Tokenomics Is Not What the AI Labs Want
Here is the uncomfortable truth: Tokenomics is not in the interest of the companies selling tokens. AI labs are consumption businesses. Their revenue model runs on volume. Every routing decision that sends a task to a cheaper model instead of a frontier one, every quota that limits agent loops, every self-hosted deployment that replaces an API call, is margin they do not collect.
The incentive to build you a great cost control layer is not aligned with the incentive to grow your spend. This is where the opportunity lies. For startups, building the governance and FinOps layer for enterprise AI is a real market, and it is early. Companies like Kion are already moving into AI token spend management the way cloud cost management tools did a decade ago (source). There is a generation of tooling to be built: token routers, quota managers, attribution dashboards, cost anomaly detectors, ROI calculators that connect spend to business outcomes.
For enterprises, the leverage is real too. You have consumption data. You have contract renewal cycles. You have the ability to move workloads. Demand better governance primitives from your AI vendors natively, not just through third-party wrappers. Ask for cost attribution by team and use case, anomaly alerting, and tiered access controls as first-class platform features, not add-ons.
The labs will follow the enterprise money. They will have to do it.
The enablement phase built the capability. The Tokenomics phase is where you build the discipline to sustain it.
Written in a personal capacity. I spent years at Microsoft building AI tools for Copilot Studio, and I now work at Audible. This piece draws on public reporting only and these are my own observations unrelated to my employer.