In May 2026, Microsoft’s Experiences + Devices division quietly pulled Claude Code licenses from its engineers. The reason wasn’t performance. Token billing had reportedly climbed to roughly $2,000 per engineer per month, and nobody inside the division had seen it coming until the invoice did. Weeks earlier, Uber had burned through its entire 2026 AI coding budget in four months flat, after adoption across its 5,000-engineer org surged from 32% to 84% almost overnight, with its heaviest users individually costing the company $2,000 a month. Both stories made headlines for the same reason: the bill was a surprise. Neither company lacked data from its AI coding vendors. Each had a perfectly good dashboard — for one tool.
That’s the part that should worry every VP of Engineering reading this. Uber and Microsoft aren’t outliers because they use AI coding tools aggressively. They’re outliers because their overruns became public. Jellyfish’s 2026 AI Engineering Trends report, which analyzed more than 20 million pull requests across 700+ companies and 200,000+ engineers, found that Claude Code, Gemini Code Assist, and GitHub Copilot now cluster within nine points of each other at the top of enterprise adoption, with twelve more tools trailing close behind. A year earlier, Copilot alone held a commanding 42% share. That era is over. The modern engineering org doesn’t pick a coding assistant. It accumulates several, one team at a time, until nobody in leadership can name all the tools running against the company’s codebase — let alone say what each one costs, who’s actually using it, or whether it’s paying for itself.
Sprawl is the default, not the exception
It’s tempting to treat “which AI coding tool should we standardize on” as the strategic question. It isn’t, anymore. Claude Code lands with one team because a senior engineer swears by its planning mode. Cursor spreads through another because it’s the fastest way to onboard a new hire onto an unfamiliar repo. GitHub Copilot ships by default because it’s bundled into the existing GitHub Enterprise contract. Codex creeps in through a few engineers experimenting on side projects. Gemini Code Assist arrives bundled with a Google Workspace renewal nobody scrutinized closely. None of these adoptions individually looks like a decision worth escalating. Collectively, they add up to an organization running four or five AI coding vendors with zero shared measurement layer between them — which is precisely the fragmentation problem we’ve written about at the platform level in what agentic AI actually means for the enterprise, and precisely the gap Olakai was built to close.
We’ve written before about the harder problem of proving that any single AI coding tool is generating value rather than just generating code, and about why acceptance rate is the wrong metric to chase when you’re evaluating one vendor in isolation — see Your AI Coding Tools Are Generating Code. Are They Generating Value? and AI Coding Tool ROI: Why Acceptance Rate Is the Wrong Metric. Those posts assumed a single tool as the unit of analysis. This one doesn’t. The question enterprises are actually facing in mid-2026 isn’t “is Copilot worth it” — it’s “we run five of these, and I have five different answers to that question, none of which use the same metric, currency, or time window.” That’s a portfolio problem, and native vendor dashboards were never built to solve it. Copilot’s dashboard sees Copilot. Cursor’s admin panel sees Cursor. Neither will ever tell you which tool your best engineers are quietly switching away from, or which team is paying triple the per-seat cost of another team doing comparable work.
Nobody is actually measuring this — even one tool at a time
Before an organization can worry about comparing five AI coding tools, it has to be tracking metrics on any of them, and most aren’t. Jellyfish’s same report found that only 46% of organizations are actively tracking AI-specific metrics at all — adoption, acceptance rate, model usage, anything. That’s not 46% tracking consistently across every vendor in use. That’s 46% tracking anything, from any vendor, in any form. The other 54% are running a multi-vendor AI coding program on instinct: a sense that “the team seems to like Cursor” or “we haven’t heard complaints about Copilot,” with no underlying data to confirm or contradict it.
Layer cost onto that visibility gap and the picture gets worse. Research from DX covering more than 400 organizations found blended per-developer spend across tiers and tools now running $200 to $600 a month, with agentic token consumption alone sometimes reaching $200 to $2,000-plus per engineer per month depending on usage intensity — the same range that blindsided Microsoft’s E+D division. And forecasting that spend is failing broadly, not just at the companies that make the news: a Mavvrik/Benchmarkit survey of 372 enterprises found only 15% forecast AI costs within 10% of actual, while nearly one in four miss by more than 50%. Multiply that forecasting failure across four or five tools running in parallel, each billed differently, each reported through a different console, and “surprise” stops being a risk and starts being the expected outcome.
What a unified view actually requires
Solving this isn’t a matter of asking engineering managers to check five dashboards instead of one and mentally reconcile the numbers. It requires a measurement layer that sits above every vendor and normalizes what each one reports into a single, comparable view. That’s the specific gap Olakai Agentic is built to close: a vendor-neutral analytics and governance layer across Claude Code, Cursor, GitHub Copilot, Codex, Gemini Code Assist, and whatever the team adopts next, without requiring the organization to standardize on one vendor first.
Concretely, that means three things a single-vendor dashboard structurally cannot give you. First, cost-per-PR comparison across tools on common ground — not Cursor’s definition of a productive session next to Copilot’s definition of an accepted suggestion, but one measurement standard applied consistently, so a VP of Engineering can see that Team A’s tool costs three times what Team B’s does for comparable throughput and ask why. Second, adoption cohorts that span vendors, showing who’s actually using what — the power users worth studying, the licenses sitting idle regardless of which tool issued them, and the teams quietly switching tools without anyone approving the shift. Third, budget forecasting that aggregates spend across every provider into one number the CFO can trust, with alerts before a team’s token usage on any single tool turns into the kind of invoice that ends a pilot. This is the same measurement-layer thinking behind our Analytics & Custom KPIs capability, applied specifically to the vendor sprawl that now defines every engineering org’s AI coding stack.
For a VP of Engineering, the practical shift is to stop evaluating AI coding tools one procurement cycle at a time and start treating the portfolio itself as the thing to manage. That means asking which teams are using which tools before the next contract renewal, not after a token bill forces the conversation; it means comparing cost-per-outcome across vendors on the same axis instead of trusting each tool’s self-reported acceptance rate; and it means building budget alerts before adoption surges the way Uber’s did, not after. Olakai Agentic is purpose-built for exactly that workflow, and it’s the specific reason we built a dedicated page for engineering leadership — see Olakai for VPs of Engineering for how the cross-tool view maps to the decisions this role actually has to make.
None of this requires an organization to consolidate down to one AI coding tool, and for most engineering teams that wouldn’t even be the right call — different tools genuinely suit different workflows, and forcing a single vendor sacrifices real productivity gains for the sake of simpler reporting. The fix isn’t fewer tools. It’s a unified measurement layer across every coding tool the organization already runs, so the next $2,000-a-month surprise shows up on a dashboard weeks before it shows up on an invoice.
If your engineering org is running three, four, or five AI coding tools right now with no shared view across them, that’s not a future governance project — it’s the state of your AI spend today, and it’s already accumulating risk you can’t see. Talk to an Expert to see how Olakai Agentic brings every AI coding vendor into one measurement and governance layer.