Picture this: a department rolls out a chat assistant on a Friday. By Monday a few power users have pasted whole contracts into it, an overnight agent loop is retrying failed calls, and a seat add-on nobody budgeted for has lit up on the invoice. That is not a horror story from a vendor deck. It is the shape of the 2014 cloud-bill surprise all over again, except now any employee or agent can create spend with a single prompt. IT leaders already know how to track seats. Usage-based token costs are a different animal, and the AI spending budget is the place that pain shows up first. The job is to forecast, cap, and charge them back before finance has to reverse-engineer the bill.
I am deliberately not calling that “impossible.” That word is editorial heat, not a finding. What the sources do say is that AI costs are harder to forecast and allocate than the flat software licenses most of us grew up on, and that quotas, budgets and hard spend ceilings are the controls practitioners and vendors are actually recommending.
Why AI Spending Budgets Struggle With Token Costs
The FinOps Foundation’s FinOps for AI guidance puts the problem in operator language. Forecasting for new AI work is “much more challenging,” with more forecast variance and a need for shorter forecasting windows. On budgeting, it says top-down dollar budgets are limited by heterogeneous vendor pricing, bottom-up budgets are overloaded with per-component estimates, and for pilots “consumption volumes are virtually impossible to predict,” so budgets need more frequent revision. Tokens are one of the primary cost meters, but the guidance also flags non-token costs and the harder problem of tying spend to an outcome.
The Wall Street Journal reported in June 2026 that CFOs are finding usage-based, token-priced AI “more unpredictable and harder to model,” and that only 26% of companies in a survey the paper cited said they had a comprehensive view of their AI costs. The Journal’s free summary does not name the survey firm or sample size, so treat that number as directional rather than definitive. The Journal’s CIO coverage the same season made a similar point from the other side: AI is putting pressure on corporate IT budgets, and leaders are already worrying about rising token costs past the pilot phase.
Token Quotas and Spend Ceilings Are Real Controls
This is the part of the sheet headline that holds up. FinOps for AI calls for “much more wide implementation of multiple limits such as quotas, use of reserved capacity, throttles, etc.” It also notes you may relax some rules for pilots, which is not the same as having no ceiling at all.
The vendors have shipped matching knobs. OpenAI’s own spend-limits documentation describes monthly organization and project spend limits, spend alerts that notify without stopping traffic, and hard spend limits that return HTTP 429 errors with organization_spend_limit_exceeded or project_spend_limit_exceeded once tracked spend hits the cap. Alerts and hard limits are meant to be used together: warn first, then stop. Microsoft’s Azure guidance for Foundry and Azure OpenAI costs is blunter about the gap: create budgets and alerts in Cost Management, but “While OpenAI has an option for hard limits that prevent you from going over your budget, Azure OpenAI doesn’t currently provide this functionality.” Enforcement there needs custom automation off action groups. So “set a quota” is not one checkbox across every provider.
What I Would Put in Place This Quarter
Opinion: treat AI usage the way we eventually learned to treat cloud: owner, meter, ceiling, showback. In practice that means:
- Name an owner. Someone in IT or FinOps owns the AI spend number the way someone owns the AWS bill. FinOps explicitly calls for clearer persona coverage because non-traditional “engineers” can now spin up AI projects.
- Meter by use case, not just by vendor. FinOps argues for unit economics such as cost per inference or cost per outcome, not only total tokens. A chat pilot and a production agent will not share a sensible average.
- Set alerts and, where the platform allows, hard caps. Use OpenAI’s project and org spend limits where you are on that API. On Azure, set Cost Management budgets and decide in advance what the action group does at 80% and 100%.
- Charge back or at least show back. Tag or project-map usage to a cost center before the invoice lands. If you cannot allocate it, you cannot explain it.
- Revisit the forecast on a short cycle. FinOps’s own advice is more frequent budget revision while the work is still experimental. Annual AI line items written in January will be fiction by April.
None of that needs a new platform purchase. It needs the same discipline we built for cloud, applied to a meter that moves every time someone hits Enter.
The CFO Invoice Is a Symptom
If the first time IT hears about token burn is a forwarded invoice, the control plane failed earlier. Quotas and spend ceilings will not make AI cheap. They will make the surprise smaller, the owner clearer, and the conversation with finance about tradeoffs instead of forensics. That is the bar.