Before Uber capped anything, it did the opposite. The company encouraged employees to use AI coding tools “as much as possible” and put usage on internal leaderboards — a competitive, public ranking of who was generating the most AI activity, with no ceiling attached. Four months later, Uber’s CTO told the company it had blown through its entire annual AI budget. Not a quarter’s worth. Not a soft warning at 80%. The whole year, gone in a third of it, discovered only after the money was already spent.
The fix Uber built next is real infrastructure, not a memo. According to TechCrunch’s reporting, Uber now caps AI spending at $1,500 per employee, per month, per agentic coding tool — a separate limit for each of Claude Code and Cursor, so maxing out one doesn’t touch the budget for the other. Employees can track their own usage against the cap through an internal dashboard, and the limit can be exceeded with permission when the work genuinely calls for it. That’s a legitimate governance mechanism, built under real pressure, by a company that clearly has engineers capable of shipping it fast. It’s also the second half of a story worth sitting with: the guardrail arrived after the crash, not before it.
A flat cap catches the symptom, not the trajectory
A per-employee, per-tool monthly ceiling is a real control, and it’s a meaningfully better position than the leaderboard-driven free-for-all that came before it. But it’s also a blunt instrument compared to what a purpose-built AI spend governance system actually does. A flat cap tells an employee “no” at $1,500 with no earlier signal along the way. It doesn’t distinguish between a team burning through budget in the first ten days of the month versus one pacing evenly across thirty. It has no program-level ceiling sitting above the per-tool one, and no way to see a provider-wide spend trend across every developer at once — just individual caps, checked individually, after the spend has already happened.
Compare that to what a real budget mechanism looks like when it’s built to catch the problem before month-end rather than cap it after the fact. Olakai’s own AI Spend Governance runs a daily run-rate forecast against every budget — program-wide, per-provider, per-developer — and fires two different kinds of alerts: one when actual spend crosses a threshold (50%, 80%, 100% of the limit), and a second, more useful one, when the trajectory alone is on pace to blow through the budget by month-end, even while spend is technically still under the line today. That second alert is the exact warning Uber didn’t have in month three, when the company was still four to six weeks from finding out the hard way.
The other half of the problem: nobody could say what the spend bought
Spend control is only half of what went wrong at Uber, and arguably the easier half to fix. The harder admission came from COO Andrew Macdonald, who said on a podcast that “it’s very hard to draw a line” between the company’s AI usage and the new consumer features it had shipped. That’s a striking thing for a public company’s COO to say on the record — not “AI isn’t working,” but “we genuinely can’t tell.” A company that spent a full year’s AI budget in four months, driven by a leaderboard that rewarded activity over outcome, and then couldn’t connect that activity to a specific shipped result, wasn’t missing a budget cap. It was missing a way to measure value at all.
That’s the pattern that should worry a CFO more than the overspend itself. A budget overrun is a one-time, fixable embarrassment. A COO unable to say whether a year of AI spend produced anything measurable is a standing problem that a hard cap doesn’t touch — Uber can enforce $1,500 per employee per tool forever and still not know if that $1,500 is buying real developer output or just more prompts on a leaderboard. Spend control and value measurement are usually treated as two separate initiatives, owned by two different teams, on two different timelines. They’re actually the same problem: you can’t govern spend you can’t see clearly, and you can’t prove ROI on spend you’re not governing.
What the next version of this story should look like
Uber isn’t unusual for having gone through this — it’s unusual for having said so publicly. Most companies encouraging “use AI as much as possible” this year, with no program-wide budget ceiling and no forecast catching the trajectory early, are somewhere on the same four-month timeline Uber already lived through; they just haven’t hit the wall yet, or haven’t been reported on when they did. The version of this story worth aiming for isn’t “we built a cap after the crisis.” It’s a unified view of AI coding spend and AI coding value from day one — budgets that alert before the month closes, not after, and a productivity signal sitting right next to the cost one, so nobody’s COO has to say “it’s very hard to draw a line” on a podcast eighteen months in.
If your organization is somewhere on that same trajectory — multiple AI coding tools, growing spend, and no clear answer yet to “what did this actually buy us” — the better time to build the guardrail is before the invoice, not after. Talk to an Expert about what proactive AI spend governance looks like against your own provider data.