How to Control AI Spend: a FinOps Playbook
A capability of the Behest AI Token FinOps platform.
Last updated:
A practical, finance-toned playbook for platform and finance owners: six steps to make enterprise AI spend visible, attributable, and capped — before the provider invoice arrives, and without standing up a dedicated FinOps team.
The short version
How do I control AI spend, step by step?
Behest meters every model call, attributes cost to a team, project, or user, and enforces per-unit token and dollar budgets on the request path, blocking overruns before the invoice arrives. It's self-serve: a platform or finance owner gets control without a dedicated FinOps team — all in your own cloud.
Why AI spend runs away
AI cost climbs quietly because the bill is aggregate and the usage is not. Retries, agentic loops, and reasoning-model token bloat inflate consumption; without per-unit attribution, no team owns the number; and shadow AI adds calls IT never sanctioned. The invoice is the first time anyone sees the total — by then the money is spent.
Published research frames the scale: the FinOps Foundation's State of FinOps 2026 reports that roughly 73% of organizations run over their cloud and AI budgets, and the FinOps Foundation and DoiT estimate 30–50% AI-budget overruns as agentic and reasoning models scale. Separately, 2026 research puts shadow-AI use — employees using AI tools IT has not sanctioned — above 80%. The fix is the same discipline finance already applies to cloud: attribution, budgets, and enforcement, brought down to every model call.
The six-step AI spend playbook
Each step maps to a control Behest runs on the request path — self-serve, in your own cloud.
- 1
Meter every model call on the request path
Capture the model, token counts, and dollar cost of every completion as it happens — on the request path, not from a monthly provider export — so AI spend is visible in real time instead of after the invoice posts.
- 2
Attribute each call to a user, team, project, and session
Tag every model call with the user, team, project, and session that triggered it, so spend rolls up to the cost centers finance already owns instead of arriving as one opaque provider bill.
- 3
Set per-team and per-project token and dollar budgets
Give each team, project, or user a token and dollar budget with warning thresholds, so every unit has a ceiling that maps to how your organization already plans and approves spend.
- 4
Enforce hard caps on the request path
Evaluate budgets on the request path and block or throttle calls when a cap is hit — stopping runaway agents and overruns before the model runs and before the provider invoice arrives.
- 5
Chargeback and showback to finance
Export attributed cost per team and project so AI spend flows into chargeback, showback, and P&L reporting instead of living in an engineering dashboard.
- 6
Forecast and review spend trends
Review attributed spend over time to forecast the next period, catch drift early, and adjust budgets before a single model or feature quietly moves the quarterly number.
Frequently asked questions
- How long does it take to set up AI spend controls?
- Hours, not a quarter-long program. You point your apps at Behest, tag calls with a team, project, or user, and turn on budgets. Attribution and enforcement run on the request path immediately — there is no data warehouse to build or monthly reconciliation pipeline to stand up before you get control.
- Do I have to change my application code?
- Minimally. Behest exposes an OpenAI-compatible endpoint, so most apps change a base URL and pass an identity header — the team, project, or user — so spend attributes to the right unit. You do not rewrite your app or hand-instrument every call; metering, budgets, and enforcement happen in the request path.
- What if my teams use different LLM providers?
- Behest meters and attributes spend across providers — OpenAI, Anthropic, Google, and others — through one control center. Budgets and enforcement apply uniformly no matter which model a team calls, and when you bring your own provider keys Behest meters usage without marking up tokens, so chargeback stays pass-through.
See your AI spend before the invoice does
Estimate your exposure, then put every model call under budget and enforcement.