BusinessPractitioner4 min read
How much does an unmonitored AI cost?
Put a figure in tokens, then in euros with your prices, on what a GenAI service nobody watches can cost over twelve months: swelling prompts, unexploited response cache, agent loops, hallucinations.
For: finance, risk and compliance · executives and CIOsPrerequisites: Have read part V of the method and have your provider's price list at hand.
You are preparing a budget committee and need to defend an “AI observability” line. The question you will get is simple: what do we lose if we do nothing? This tool gives an order of magnitude, over twelve months, for your own service.
It rests on the idea from Part V, the leak under the sink: the cost of a blind spot is an accumulation rate (how much you lose per day) multiplied by a detection delay (how long before you notice). Without a signal, the loss shows up on the invoice or in a customer complaint. The calculator puts a figure on what that lack of monitoring costs over a year, hence on the value observability can prevent. It is designed for a conversation with finance or a risk committee.
Prices change fast and vary by contract; this guide gives none. Use your provider’s dated price list. The price fields therefore start empty. As long as they stay empty, the token-related items (tokens being the units of text the provider bills) show in tokens and calls. Enter your input and output prices to get them in euros.
Parameters
Exposure
Illustrative parameters, to replace with your own values. No price is provided: without prices, the token-related items are shown in tokens; enter the input and output prices from your provider's dated price list to get them in euros. The base cost is the legitimate spend of the service; the exposure is the avoidable or at-risk amount that observability makes visible. Every item covers twelve months: prompt bloat counts one episode per year, undetected for M months then fixed. The hallucination defaults are arbitrary: replace them with your own estimates. Working document, not financial advice.
Formulas
Section titled “Formulas”They simplify the model in Part V. Every item covers the same period, twelve months. V is the number of calls per day, t_in and t_out the average input and output tokens, p_in and p_out their prices.
| Item | Calculation |
|---|---|
| Cost per call | t_in x p_in + t_out x p_out |
| Monthly base cost | V x cost_per_call x 30 |
| Annual base cost | monthly_base_cost x 12 |
| Prompt bloat | monthly_input_base_cost x g x M x (M + 1) / 2, one episode per year, M at most 12 |
| Unexploited response cache | h x annual_base_cost |
| Agent loop | wasted_share x annual_base_cost |
| Hallucination | expected_incidents_per_month x cost_per_incident x 12 |
Without prices, the calculator applies the same formulas to volumes: t_in and t_out multiplied by V x 30 give the month’s base tokens. Every token-related item is then expressed in input and output tokens instead of euros.
How this differs from Part V
Section titled “How this differs from Part V”For prompt bloat, the formula is the same as in Part V. To stay within twelve months, the calculator assumes a single episode per year: the prompt swells unnoticed for M months (12 at most), then gets fixed.
The cache item assumes a response cache, where a hit (a question already seen) avoids the whole call. A prompt cache only lowers the price of input tokens read back from cache. If that is your case, this item overstates the saving.
For the agent loop, Part V computes V x r x (L - K) x cost_per_step x 30 per month. The calculator sums it up as a share of wasted calls, equal to r x (L - K) / K when each step costs one average call and the V of Part V counts tasks of K steps, that is K calls each.
For hallucination, Part V writes P_hallucination x N_exposed_incidents x cost_per_incident. The calculator directly asks for the expected number of incidents per month (the product P x N) and multiplies it by twelve.
What the default values give
Section titled “What the default values give”The defaults are 50,000 calls per day, 1,500 input tokens and 400 output tokens. Without prices, the base volume is 2.25 billion input tokens and 600 million output tokens per month, or 27 and 7.2 billion per year.
The calculator then shows about 14.11 billion avoidable tokens over twelve months, or 41% of the annual volume. The breakdown: 1.8 billion input tokens for prompt bloat (four months undetected), 10.26 billion tokens for the unexploited response cache (5.4 million calls) and 2.05 billion tokens for agent loops (1.08 million calls). Hallucination is shown separately, in euros: 288,000 euros.
To turn tokens into euros, multiply input tokens by p_in and output tokens by p_out, or enter those prices in the calculator.
Before you present the result
Section titled “Before you present the result”Before walking into the committee, check that your prices come from a dated price list and that the hallucination assumptions are yours rather than the defaults. Be ready to say which kind of cache your provider offers. A figure you can defend line by line convinces more than a big figure.
Revised on 2 October 2026: prices removed; token-related items show in tokens and calls, in euros only with your prices.
Revised on 25 October 2026: page text rewritten for a wider audience (opening situation, differences written as prose), with no change to the formulas or the calculator.