In June 2026, Uber’s CTO told employees that the company’s annual AI budget was gone, four months into the year. The fix that followed was a flat cap of $1,500 a month per employee for each agentic coding tool, with exceptions by approval. When a reporter asked what the spend had bought, the COO said it was “very hard to draw a line” from the tokens to the features they produced. We wrote about the cap at the time, but the more interesting fact is the one underneath it: Uber has one of the most mature cloud cost practices in the industry, and that practice did not see this coming.
That is the FinOps for AI problem in one company. The discipline is not missing. The FinOps Foundation‘s State of FinOps 2026 survey, drawn from 1,192 practitioners responsible for more than $83 billion in cloud spend, found that 98% of them now manage AI spend, up from 31% two years earlier, and that “FinOps for AI” is the top forward-looking priority on their list. The 2026 edition of the FinOps Framework added it as a dedicated technology category. Finance teams are not ignoring the AI bill. They are applying a playbook written for cloud to a cost that does not behave like cloud, and the playbook is failing in specific, predictable places.
What carries over from cloud FinOps
Most of the framework survives the move. The three-phase lifecycle of Inform, Optimize, and Operate is exactly the right shape for token spend, and the principles hold up better than their critics expect. Teams still need to collaborate, business value still drives technology decisions, and everyone still owns their own usage. The Foundation has even rewritten its sixth principle, which used to be about taking advantage of the variable cost model of the cloud; it now says “the cloud and other technologies with similar consumption models,” which is as close as a standards body gets to admitting that tokens are the new unit of variable cost.
What also carries over is the thing cloud FinOps got right first: cost is an engineering decision made thousands of times a day by people who never see the invoice, so the feedback has to reach them while they can still change the decision. That instinct is correct for AI. The problem is that four assumptions underneath the cloud version of it are wrong for tokens, and each one breaks a different phase of the lifecycle.
Inform breaks first: there is no single bill
Cloud FinOps rests on one authoritative artifact, the billing export. It is late by a few hours, but it is complete, it is tagged, and everything reconciles to it. AI spend has no such artifact. In practice a finance team is looking at three different numbers that describe the same usage. There is an estimated figure, tokens multiplied by a list price, which is the only number available in real time. There is the provider’s billed figure, which arrives later and does not always match the estimate, because cached reads and batch discounts are priced differently from fresh input. And there is an allocated figure, the share of the real bill attributed to a team or a person, which is an estimate weighted against the invoice. We built Olakai Agentic to keep those three apart on purpose, because adding them together, or quoting one as if it were another, produces a number that describes nothing.
Timeliness is the second casualty. Google Vertex AI‘s billing export to BigQuery typically runs 24 to 48 hours behind usage, which we documented in detail when we built the reconciliation for it. AWS cost reports carry a comparable lag. The FinOps principle that data should be “accessible, timely, and accurate” is intact; what changed is that for AI you have to choose two of the three and say which two you chose.
Allocation breaks next: tags attach to keys, not people
The cloud allocation model is tag discipline. Every resource carries a cost center, and showback follows. Token spend arrives, in the Foundation’s own words, as “aggregate consumption by API key at best.” A shared service key for a team of forty developers is one line on the invoice, with nothing on it that says who used it. Gartner analyst Marco Meinardi put the problem plainly at FinOps X in June: “The metadata is not there. We have to build it into the application.” Finance cannot build it into the application, which is why 36% of the finance leaders in a February 2026 survey of 500 companies named “lack of financial attribution” as the reason they could not measure AI return.
Two things follow for the practice. The first is that attribution coverage becomes the leading KPI, ahead of total spend: the share of the bill that sits in a named cost center, with the biggest unassigned keys listed next to it so that each one is a single assignment away from being attributed. A project breakdown on 9% coverage describes 9% of the bill, and a dashboard that hides that fact is lying with a pie chart. The second is that AI allocation is not a partition. The same developer’s spend legitimately belongs to their department’s headcount plan, their manager’s benchmarking, the vendor renewal, and the project that consumed it, four questions about the same dollar. Olakai’s budgets are therefore overlapping lenses rather than buckets, and the per-team totals are not supposed to sum to the program total. A CFO who expects cloud-style reconciliation needs to hear that before the meeting, not during it.
The hybrids make it worse. Seat-licensed tools such as GitHub Copilot have nothing for a per-token budget to measure, so they fall out of usage-based reporting entirely and belong with license utilization instead, where the question is how many seats are idle. Cursor moved from a flat subscription to a dollar credit pool tied to API cost in June 2025 and had to refund customers whose bills multiplied; Anthropic moved enterprise customers to a seat fee plus pre-committed token consumption in April 2026. A single engineering org can now be paying three pricing models for the same category of tool, and a chargeback built on any one of them is wrong for the other two.
Optimize breaks in the middle: the rate levers are smaller and the usage levers are larger
Cloud optimization is mostly a rate exercise. Reserved instances, savings plans, and committed-use discounts can take a third off a bill without anyone changing a line of code. The token equivalents exist but are narrower: Anthropic and OpenAI both discount batch workloads by half, cached prompt reads cost roughly a tenth of fresh input on most Anthropic models, and provisioned throughput on Azure is the closest thing to a reservation. None of them is a one-time procurement decision. Caching has to be designed into the prompt, and as we found when DeepSeek raised its cache prices, the discount itself is a variable the provider can move.
Meanwhile the usage side is doing something cloud never did. Gartner expects the cost of running a trillion-parameter model to fall by more than 90% between 2025 and 2030, and in the same breath says agentic queries consume five to thirty times the tokens of a simple prompt, so “those applications are going to be more expensive, not less.” That is the arithmetic behind the pattern we described in Your AI Got Cheaper. Your Bill Didn’t. Rate optimization in AI is worth doing, but the money is in the usage: model right-sizing, which the Foundation’s tokenomics working group puts at 60% to 90% savings on the affected calls, and the discipline of not running a reasoning model with three tool calls where a direct prompt would do. Gartner’s forecast for the end state is blunt. By 2028 it expects AI coding token costs to match the average developer salary, and it already counts 6% of organizations spending more than $2,000 per developer per month. Its own conclusion is that “token discipline will not emerge through developer choice alone.”
Operate breaks last: a budget alerts, it does not cap
In cloud, a budget is a soft control backed by hard ones. Quotas, service limits, and autoscaling ceilings mean overspend has a physical boundary. Token spend has almost none. An API key with a card behind it will keep answering requests until the card declines, and a retry loop in an agent will happily spend a week’s budget in an afternoon. Uber’s response was the cloud reflex, a hard cap, and it arrived after the money was gone. The practice that works instead is a forecast alert: a run-rate projection of month-end spend, recomputed daily as provider data lands, that fires when the trajectory will exceed the limit even though today’s total is still under it. That is how Olakai evaluates every budget, at the program, provider, department, persona, developer, and project level, and it is worth being precise about what it does. It changes who gets told, early enough to change the trajectory. Nothing in it throttles a request, and a finance team that wants a hard stop should run a gateway underneath it, not instead of it.
The piece cloud FinOps never had to solve
Every break above is fixable inside the framework. The one that is not is the denominator. Cloud FinOps could stop at cost per unit of infrastructure because the business value of the infrastructure was somebody else’s problem. AI does not allow that separation, because the unit of cost and the unit of work are the same token. Forrester’s read of FinOps X this year was that “AI economics must evolve from a cost-based discipline to a value-based one,” and the numbers explain why: McKinsey finds only 39% of companies report any EBIT impact from AI, and in the DoiT survey 15% of finance leaders could calculate AI return without major bottlenecks. A cost dashboard with no value column cannot tell whether a team spending $40,000 a month on coding agents is the best or the worst investment in the company.
This is where we think the discipline is heading, and where we built. Olakai Agentic measures spend and return in the same system: coding tool return as AI Equivalent Engineers against a fully loaded engineer cost, agent return as value created over execution cost, with the assumptions configurable by finance rather than inherited from a vendor. The metric a CFO should be watching is cost per outcome, with cost per token as its input, not its conclusion. That is the version of FinOps for AI that survives a board meeting, and it is the one that makes AI ROI measurement and spend governance a single problem rather than two adjacent ones.
Where to start
Keep the lifecycle and the principles; they are right. Then run the four checks in order. Count attribution coverage before you quote a total. Decide which of estimated, billed, and allocated you are showing, and label it. Move optimization effort from rate to usage, starting with the agentic workloads where token volume is growing fastest. And replace the cap you would reach for after the next overrun with a forecast alert you set before it. If your AI spend practice is a cloud FinOps tool, a provider console, and a spreadsheet that reconciles them a week late, talk to an expert and we will walk through what the same bill looks like with a denominator, in the form a CFO reviewing AI spend can act on.