FinOps Pilote by AB Conseil
Guide · FinOps for AI

FinOps for AI: managing generative AI costs in the cloud

AI has become FinOps teams' priority: its bill is counted in tokens and GPUs, it can double in a week, and its value is hard to measure. Here is how to keep it under control.

By Aymeric Boucher · 20 October 2026 · 3 min read

Why AI shakes up FinOps

According to State of FinOps 2026, 98% of FinOps teams now manage AI spend, up from 31% two years earlier. And Flexera links the first rise in cloud waste in five years to AI usage. Three reasons:

  • New billing: per token, input and output, with very different prices from one model to another.
  • Unpredictable consumption: a new use case, an agent loop or an overly long prompt can multiply the bill within days.
  • Value that is hard to measure: without a cost per use, you can't tell whether a use case pays off.

Payment modes

ModePrincipleWhen to choose it
Pay-as-you-go (per token)Price per million input and output tokensGetting started, variable load
Provisioned capacityThroughput reserved by the hour or month (PTUs on Azure OpenAI, provisioned throughput on Bedrock)Heavy, steady load, guaranteed latency needed
BatchAsynchronous processing, about 50% cheaper than real time on eligible modelsAnything that doesn't need an immediate answer: classification, summaries, extraction

Optimization levers

  1. The right model for each task. A small model is often enough to classify, extract or route; keep large models for the tasks that need them.
  2. Bounded answers. Limit answer length and clean up prompts: every token counts, input and output.
  3. Prompt caching. When a long context comes back with every call, caching it sharply cuts the cost of input tokens.
  4. Batch for non-urgent bulk processing.
  5. Provisioned capacity only when the load is steady and measured, like a reservation.
  6. GPUs: automatic shutdown of training and test machines, Spot for interruptible jobs, scale to zero for lightly used endpoints.

Guardrails to set from day one

  • One tag or deployment per use case, to know who consumes what.
  • Quotas and rate limits per application.
  • Daily budget alerts on AI resources: a monthly alert arrives too late.
  • A cost per use tracked in the dashboard: cost per conversation, per document, per active user.

It is the same logic as for the rest of the cloud: understand, optimize, operate, stay in control. At a much faster pace.

FAQ

How do you cut the Azure OpenAI bill?

Choose the smallest model that does the job for each task, bound answer length, use prompt caching and batch, and only move to PTUs for a steady, measured load.

Should you reserve capacity for AI?

Only when the load is heavy, steady and measured. Otherwise, pay-as-you-go remains cheaper, as for a VM.

How do you measure the profitability of an AI use case?

By tracking a cost per use (per conversation, per document processed) and comparing it with the value produced or the cost of manual processing.

Aymeric Boucher has been a FinOps consultant for 8 years and is the founder of FinOps Pilote. He works with large international enterprises and SMEs on Azure and AWS, and has delivered more than €20M in cloud savings. Learn more →

First conversation

How much are you losing every month on a poorly optimized cloud?

SMEs: we are paid 20% of the annual savings achieved. Large enterprises: day-rate engagement. A first 30-minute conversation, no commitment.