FinOps grew up managing one kind of cost: cloud infrastructure. Instances, storage, data transfer, the stuff on your AWS or GCP or Azure bill. That scope is now too narrow, because a new operational cost has shown up that behaves differently from everything FinOps was built for, and most teams have no idea how big it is: AI token spend.
The industry conversation this year has been blunt about it. Token usage has become a major operational expense, and organizations still lack a good way to connect that spend to developer productivity or business outcomes. That gap is the whole problem. Let me lay out why AI spend breaks the old FinOps model and what tracking it actually looks like.
Why token spend is not just another line item
You might think, it is on the cloud bill (Bedrock, Vertex) or an API invoice (OpenAI, Anthropic), so treat it like any other cost. It is not that simple, for three reasons:
1. It is usage-metered at a granularity nothing else is. An EC2 instance costs the same whether it does important work or spins idle. A token costs the same either way too, but the volume is driven by application behavior in a way instance-hours are not. One inefficient prompt, one chatty agent, one retry loop, and volume explodes. The cost is coupled to code behavior, not provisioned capacity.
