# Forecasting LLM cost per customer, not just in total > An aggregate forecast can be right while every customer inside it moves the wrong way. Forecasting per customer turns a projection into a decision. URL: https://getculpa.com/per-customer-llm-cost-forecast Last reviewed: 2026-08-03 Rates effective: 2026-07-02 ## Answer A per-customer LLM cost forecast projects each account's spend from its own history rather than projecting one company-wide total. The aggregate can land perfectly while the customers inside it move in opposite directions. Culpa, a local-first LLM cost, margin, and forecast ledger, forecasts at the level it attributes, so a projection names an account. ## Why this happens Almost every cost forecast in this category is a single line for the whole company, and a single line has a specific failure mode: it can be accurate and useless at the same time. If one customer doubles while another halves, the total is unchanged and both facts that matter are invisible. The reason forecasts are aggregate is rarely a modelling choice. It's that the underlying data was aggregated first, so nothing finer remains to project. Datadog's Cloud Cost Management forecasts spend built from an ingested vendor invoice, which is the coarsest object in the stack and contains no customer at all. Dynatrace says it can predict cost increases, which tells you a number is trending up rather than where any account lands. Across the twelve LLM-native tools checked on 2026-08-03, none publishes a spend forecast of any kind. So the forecast ceiling sits at or above the attribution ceiling in every case, which follows necessarily: you can't project a thing you never recorded separately. ## What this usually looks like - Your forecast was accurate last month and two accounts still surprised you. - A customer's usage tripled and the company total absorbed it. - You can't tell a renewal conversation what that account will cost next quarter. - Growth and churn cancel out in the total and nobody sees either. - A forecast exists and no account manager has ever been shown one. ## Common mistakes - Forecasting one line for the whole company. Why it hurts: Opposing movements cancel, so the total can be right while every component is wrong. Do instead: Forecast each account separately and let the total be the sum, not the input. - Projecting from an ingested vendor invoice. Why it hurts: An invoice has no customer, feature or prompt version in it, so no breakdown can come out of it. Do instead: Project from your own per-call ledger, where the attribution already exists. - Treating a cost-increase alert as a per-account forecast. Why it hurts: It tells you something rose, after it rose. It doesn't tell you which account or where it lands. Do instead: Keep the alert and add a projection per account, with a range. - Forecasting spend without the revenue beside it. Why it hurts: A customer growing fast is good news or bad news depending entirely on what they pay you. Do instead: Forecast margin per account, which means forecasting cost and holding revenue in the same place. ## Self-check - Take your three largest accounts and write down what each will cost next month. - Check whether any system could have produced those three numbers for you. - Find an account whose usage moved sharply and see whether the company total shows it. - Ask what your fastest-growing account's margin looks like at next quarter's volume. ## An aggregate forecast, exactly right and completely useless Three modelled accounts across two months, priced on Claude Haiku 4.5 at real rates of $1.00 and $5.00 per million from the price book effective 2026-07-02. The company total is flat across both months, so an aggregate forecast projecting no change would score perfectly. Account volumes are modelled. month 1: A $400.00, B $300.00, C $200.00, total $900.00 month 2: A $700.00, B $150.00, C $50.00, total $900.00 the aggregate forecast said $900.00 and was exactly right account A grew 75%, account C fell 75%, and neither appears in the total A forecast that scores perfectly and misses a customer tripling toward unprofitability is the clearest argument for forecasting where you attribute. The accuracy was real. The usefulness was zero. ## Cost figures Every figure carries its confidence and its source. No figure on this page is provider-reported. - $900.00, modelled company total, identical across two months while one account grew 75% and another fell 75% [calculated] Source: Three modelled accounts priced on Claude Haiku 4.5 at real rates of $1.00 and $5.00 per million from the price book effective 2026-07-02. Month 1: $400.00 + $300.00 + $200.00 = $900.00. Month 2: $700.00 + $150.00 + $50.00 = $900.00. Account volumes are modelled and chosen so the total is flat, which is the entire point of the figure. ## FAQ Q: Why forecast per customer rather than in total? A: Because opposing movements cancel in a total. One account tripling while another collapses leaves the company figure unchanged, so an aggregate forecast can score perfectly while missing both events. The total is worth having as a sum of the parts rather than as the thing you project. Q: Why don't other tools forecast per customer? A: Mostly because their data was aggregated before it reached the forecast. Datadog's Cloud Cost Management projects spend built from an ingested vendor invoice, which contains no customer. Across the twelve LLM-native tools checked on 2026-08-03, none publishes a spend forecast at all. Q: How much history does a per-account forecast need? A: More than most retention tiers hold, which is the practical catch. Free tiers in this category run from 24 hours to 90 days, and a seasonal read on one account needs a year. Keeping the ledger on storage you own is what makes the lookback a disk decision rather than a plan tier. Q: What makes a per-account forecast trustworthy? A: Publishing it as a range rather than a point, and scoring it afterwards. A projection nobody compares to the actual is an opinion. Culpa persists every forecast so accuracy can be measured against what happened rather than asserted in a sales page. ## Sources - Anthropic pricing: https://platform.claude.com/docs/en/docs/about-claude/pricing - Datadog LLM Observability: https://www.datadoghq.com/product/llm-observability/ Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=per-customer-llm-cost-forecast&cluster=problem Machine-readable index of every guide: https://getculpa.com/api/pages Human-readable index of every guide: https://getculpa.com/guides Site overview: https://app.getculpa.com/llms.txt Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.