Cloud FinOps became a discipline because infrastructure spend outgrew what a single line item on an invoice could explain. AI spend is following the same trajectory, faster — and the organizations handling it well are the ones applying the same discipline: granular visibility, shared accountability, and forecasting, instead of reacting to the bill after the fact.
Start with attribution, not restriction
The instinct when AI spend gets attention is to cap it. The more useful first step is attribution: knowing exactly which team, which use case, and which model is driving spend before deciding what — if anything — needs to change. A 30% spend increase from a team that just launched a high-value new use case is a very different conversation than the same increase from unexplained usage drift.
Showback before chargeback
Most organizations aren't ready to charge AI costs back to departmental budgets on day one, and don't need to be. Showback — giving every team visibility into their own spend, without moving money between budgets — builds the habit of cost-awareness first. Chargeback can follow once teams are used to seeing and managing their own numbers.
The three numbers that matter most
Attributed automatically via SSO group, not self-reported
Spend divided by tickets resolved, documents drafted, or another real business unit
What routing and caching actually avoided, shown separately from raw spend
Forecasting, not just reporting
A monthly spend report tells finance what already happened. A useful FinOps practice adds a forecast: given current usage growth per team, what will next quarter cost, and does that match planned budget? Catching a trajectory problem three months out is a budget conversation; catching it after the invoice arrives is a budget crisis.
Make the drill-down available, not just the total
When a number looks wrong, the question is always "wrong because of who, or because of what." A team-level dashboard that only shows a monthly total forces someone to go digging manually. A dashboard that lets you click from a team's total down to individual member-level spend turns a multi-day investigation into a two-minute check.
Putting it together
- checkAttribute spend automatically by team and model before deciding on any spend controls.
- checkStart with showback; move to chargeback only once teams are already managing their own numbers.
- checkTrack cost per business outcome, not just raw dollars, so growth in spend can be evaluated against growth in value.
- checkForecast quarterly, and revisit budgets before they're blown, not after.