BusinessExpert5 min read
Part V. Quantified impact analysis
What a blind spot costs: the speed at which the loss builds up multiplied by the time it takes to notice. The model, a worked example, the calculator and a matrix to choose what to watch first.
For: architects · finance, risk and compliance · executives and CIOsPrerequisites: Have read part I (the silent failure model).
An illustrative scenario. The CFO receives the model provider’s invoice. It has gone up every month since spring, while the number of assistant users has not moved. She asks the team two questions: where does the gap come from? How much would we have saved by spotting it earlier? This part gives the method for answering the second one.
18. The cost model of not monitoring
Section titled “18. The cost model of not monitoring”Think of a leak under a sink. What it costs depends on two things: the flow of the leak and the time that passes before someone opens the cupboard. An observability blind spot works the same way. Its cost is an accumulation rate (how much you lose per day) multiplied by a detection delay (how many days before you notice).
Without a signal, you find the loss through an outside channel: the monthly invoice, a customer complaint. The method assumes one billing cycle, that is 30 days. With the signal, the delay drops to minutes or hours. The value of a signal is therefore roughly what you lose per day multiplied by the days you win back.
signal_value ~= accumulation_rate x (delay_without_signal - delay_with_signal)Notation
Section titled “Notation”To put figures on this, start from the cost of one model call. V is the number of requests or tasks per day. t_in and t_out are the average number of tokens sent to the model and received from it. p_in and p_out are the matching prices per token, found in the provider’s contract. For an agent, cost_per_step is the cost of one step of the loop: one step is one model call, so cost_per_step equals cost_per_call, unless you measure the actual cost of steps, which often send more context than average.
cost_per_call = t_in * p_in + t_out * p_outbase_monthly_cost = V * cost_per_call * 30cost_per_step = cost_per_call (by default, without a finer measurement)What each blind spot costs
Section titled “What each blind spot costs”An agent loop is like a taxi that circles the block three times before dropping you off. A normal task takes K steps. A share r of tasks loops and takes L steps instead of K. The monthly overspend is = V * r * (L - K) * cost_per_step * 30. The extreme case is the overnight runaway: a stuck agent sending R requests per minute for H hours costs R * 60 * H * cost_per_call.
Prompt bloat is sneakier. Every month someone adds an instruction, an example or a paragraph of context; the text sent to the model grows by a fraction g. Nobody notices for M months. The cumulative overspend is roughly base_monthly_cost_in * g * M * (M + 1) / 2, where base_monthly_cost_in = V * t_in * p_in * 30.
An unexploited response cache means paying every time for a question you have already answered. If a share h of calls could be served from the cache, the foregone saving is = h * base_monthly_cost. This formula holds for a response cache, where a hit (a question found in the cache) avoids the whole call. A prompt cache only lowers the price of input tokens read back from cache; the saving is then smaller.
Finally, hallucination has an expected cost = P_hallucination * N_exposed_incidents * cost_per_incident. The cost per incident covers remediation, reputational harm and regulatory exposure. It is the hardest item to estimate.
19. Worked example
Section titled “19. Worked example”Prices change fast and vary by contract: this guide gives none. Use your provider’s dated price list. The example therefore sizes the blind spots in tokens and calls. To get euros, multiply input tokens by p_in and output tokens by p_out (annex D explains how to build your table).
The parameters are illustrative. The application receives V = 50,000 calls per day, with on average t_in = 1,500 input tokens and t_out = 400 output tokens. That makes 50,000 x 1,500 = 75 million input tokens and 50,000 x 400 = 20 million output tokens each day. Over a month, the cost base is 2,250 million input tokens and 600 million output tokens, so base_monthly_cost = 2,250 M x p_in + 600 M x p_out.
Now apply the three blind spots to these same parameters.
A prompt that swells by g = 8 percent per month with nobody noticing for M = 4 months produces cumulative overconsumption on the order of 2,250 M x 0.08 x 4 x 5 / 2 = 1,800 million input tokens over four months. Multiply by p_in. No alert ever fires.
A response cache that could serve h = 30 percent of calls but goes unused lets through 0.30 x 50,000 x 30 = 450,000 calls per month that could have been avoided. That is 675 million input tokens and 180 million output tokens, or 30 percent of the base cost.
A single agent running away for one night, at R = 20 requests per minute for 8 hours, sends 20 x 60 x 8 = 9,600 calls. That is 14.4 million input tokens and 3.84 million output tokens, to multiply by how often such incidents happen.
None of these losses triggers a latency or error alert. They are textbook cases of the silent failure model. In my view, this is the kind of figure that justifies an observability investment in front of leadership: euros, once your prices are applied, rather than curves.
20. Tool: the economic exposure calculator
Section titled “20. Tool: the economic exposure calculator”The model is put into practice in an interactive calculator, designed for a conversation with finance or a risk committee. You enter volume, tokens, prices, the agent profile and drift assumptions. It returns the base cost, the exposure of each blind spot and the total exposure over twelve months, meaning the loss observability can prevent. The calculator simplifies the model on some items; its page details each gap.
21. Prioritization matrix
Section titled “21. Prioritization matrix”You cannot watch everything in the first month. To choose, the method places each blind spot on two axes: is it loud (it ends up raising a visible error) or silent? How severe is it? The top right corner, silent and severe, is priority 1. It holds hallucination, cost drift and MCP tool poisoning. Loud failures such as a server 500 error are already covered by classical monitoring.
quadrantChart title Prioritization of blind spots x-axis "Loud" --> "Silent" y-axis "Low severity" --> "Critical severity" quadrant-1 "Priority 1: monitor first" quadrant-2 "Covered by classical monitoring" quadrant-3 "Low stakes" quadrant-4 "Instrument next" "Hallucination": [0.85, 0.9] "Cost drift": [0.9, 0.7] "MCP tool poisoning": [0.8, 0.95] "Agent loop": [0.75, 0.65] "Quality drift": [0.88, 0.6] "Provider rate-limit": [0.25, 0.55] "Server 500 error": [0.15, 0.5] "One-off latency": [0.3, 0.25]
For Monday morning
Section titled “For Monday morning”Take your own volume and token figures and compute the monthly base cost with your contract prices. Then apply the assumption of a prompt that swells by a few percent per month. If the one-year result surprises you, open the calculator and prepare the conversation with finance.
Revised on 2 October 2026: prices removed; the worked example is expressed in tokens and calls.
Revised on 25 October 2026: page rewritten for a wider audience (opening scenario, images, example written as prose), with no change of substance.