Does the forecast cover the rest of this month or next month?

Next month. CostCompass projects the full next calendar month at your current pace, not the remainder of the month you're in. Late in a month there are too few days left for a current-month projection to mean much, and the question that actually drives a budget is "if this pace holds, what does a whole month at it cost?" The month-to-date figure already tells you where this month stands. The forecast tells you what the next one is shaping up to be.

How is the forecast calculated?

It takes your spending over the last seven days, divides by seven to get a daily rate, multiplies that by the number of days in next month, and adds next month's fixed subscriptions in full. Only metered usage gets extended from the seven-day rate — tokens, GPU-hours, characters, requests. Flat subscriptions are a known monthly charge, so they're added at their actual next-month cost rather than guessed from a few days of usage.

Why a seven-day window instead of the whole month?

Seven days is a middle ground. A single day swings too much to trust — one heavy batch job or one quiet weekend would throw the projection off. Averaging the whole month so far reacts too slowly, dragging an old, cheaper pace into the number long after your usage has changed. A trailing week smooths out day-to-day noise while still turning quickly when your real pace shifts, so a genuine change in spending shows up within days rather than weeks.

Why might the forecast differ from my eventual invoice?

A forecast is an estimate of a future month built from a recent rate, so it moves as your usage moves. A new model, a launch, or a quiet stretch all change it. It also assumes your next-month pace resembles this week's, which won't hold if you already know a big change is coming. And like any rate-based projection it can't see discounts that aren't in the raw usage, such as batch pricing, prompt caching, or promotional credits. Treat it as a well-grounded heading rather than a contract.

Do I have to change my code to forecast AI spend?

No. CostCompass reads each provider's own usage or billing API directly and computes the projection from that. There's no SDK to install and no gateway in your request path — your application runs exactly as it did before. The forecast is built entirely from records the providers already keep, so the only thing you do is connect each provider once.

Can you show the forecast math with an example?

Say your metered usage over the last seven days came to $1,050. Divide by seven and the daily burn rate is $150. If next month has 30 days, the metered part of the forecast is $150 × 30, or $4,500. Add a $200 flat subscription at its real next-month cost and the forecast reads $4,700. The subscription is counted once, never run through the daily rate.

Why use CostCompass to forecast instead of doing it myself?

Forecasting it by hand means logging into every provider, reading each one's after-the-fact usage in its own units, converting to money, averaging a recent window, and projecting it across next month. Then you redo the whole thing every time you want a current number, still separately per provider with no combined view. CostCompass pulls every connected provider's usage with one click and turns it into a single forward projection across all of them — your trailing burn rate extended into next month, beside the month-to-date total and a per-provider breakdown, with nothing wired into your code. You read one number instead of rebuilding it by hand.

Forecast AI spend

See your AI bill before it arrives

Every provider console shows what you've already spent, but none of them tell you where the month is heading. A forecast reads your recent pace and projects it forward, so a climbing bill becomes a number you can act on before the invoice lands.

See your own forecast — start free

By Joubert Berger Published June 6, 2026

A provider dashboard is a record of the past. It tells you precisely what you've already spent, and nothing about what you're about to spend. By the time a bill surprises you, the month is over and the money is gone. The question worth asking is where the spend is heading, and whether there's still time to do something about it.

That's what a forecast is for. Take the pace you've been spending at and project it forward, and a rear-view number becomes a heading you can steer by. This guide covers what an AI spend forecast actually is, why provider consoles can't give you one, and the exact way CostCompass builds it.

An antique almanac engraving: a sundial whose gnomon casts a shadow across the hour marks, the shadow continuing past the final mark as a fine dotted line projected onto open ground beyond the dial face. — The dial reads the hours already passed; the projected line reads where the shadow is headed next.

What is an AI spend forecast?

A forecast is a forward number: what you’re on track to spend, as opposed to what you’ve already spent. Three things tend to get blurred together, so it’s worth separating them. Usage is the raw meter — tokens, GPU-seconds, characters, requests. A running total prices that usage into money and adds it up to the moment, giving you what the month has cost so far. A forecast takes the rate underneath that total and projects it ahead to estimate what a full month at this pace will cost.

The first two look backward. The third looks forward, and it’s the one a budget actually turns on. Knowing you’ve spent a certain amount so far this month doesn’t tell you whether you’re about to blow past the figure you had in mind. For that you need the pace, extended far enough ahead to be worth reacting to. Measure the recent rate, multiply it across a month, and read the result before the month happens.

Why can’t provider dashboards forecast for you?

Because a dashboard is built to report, not to project. Every provider gives you a usage page, and for looking backward it’s fine: it shows what you’ve spent and lets you export it. But it’s a rear-view mirror by design, showing the road behind you and never the road ahead.

Two limits make this worse the moment you run on more than one provider. Each console sees only its own slice, in its own unit — tokens here, GPU-hours there, characters somewhere else — so there’s no single pace to project from in the first place. And none of them extend the line forward. To build a forecast yourself you’d log into every provider, read each one’s recent usage, convert it to money, average a trailing window, and project that across next month, then repeat the whole exercise every time you wanted a current figure. It’s enough work that almost nobody does it, which is why a rising bill so often arrives as a surprise. For the broader picture of pulling those scattered consoles into one running total in the first place, see how to track AI costs across providers.

How does CostCompass forecast your spend?

It reads your recent pace and extends it into next month. Concretely, the projection is built like this:

Take a trailing seven-day burn rate. CostCompass sums your metered usage over the last seven days and divides by seven to get a daily rate. Seven days is long enough to smooth out the swing between a heavy day and a quiet one, and short enough that a real change in pace shows up within days instead of being averaged away over weeks.
Multiply it across next month. That daily usage rate is extended over the number of days in next month, whether that’s 28, 30, or 31, to project what a full month at this pace would cost.
Add next month’s fixed subscriptions in full. Flat subscriptions are a known monthly charge, so they’re added at their actual next-month cost rather than extrapolated from a few days of usage.

So the forecast is your recent usage rate, projected across next month, plus next month’s subscriptions. It carries no month-to-date term, so it isn’t “what you’ve spent plus a bit more.” It answers a cleaner question: at this pace, what does next month cost?

The CostCompass dashboard card showing a month-to-date total of $5,127.30, a FORECAST of $6,512.00 for next month picked out in copper, a burn rate of $221.40 per day, and 9 days remaining in the current month. — The forward number sits right beside the running total — month-to-date for where this month stands, forecast for what next month costs at your current burn rate.

The burn rate shown on the card is the everyday pace: your recent spend per day, subscriptions included. The forecast is the same idea aimed a month ahead, with one careful distinction. It extends only your metered usage from that seven-day rate and adds subscriptions separately, so a flat monthly charge gets counted once at its real value instead of being inflated by the daily rate.

Here’s the same calculation worked through with round numbers, for a next month of 30 days:

Step	Value
Metered spend, last 7 days	$1,050
Daily burn rate ($1,050 ÷ 7)	$150/day
Metered projection ($150 × 30)	$4,500
Fixed subscription (added in full)	$200
Forecast for next month	$4,700

One thing here is intentional: you pull the data, not a background timer. The forecast recomputes from each provider’s latest usage the moment you click Refresh. It stays quiet until you look. One click then brings every connected provider’s latest usage in at once and rebuilds the projection from it. Because each refresh reads a fresh seven days, a developing spike works its way into the forecast the next time you pull it in, while there are still days left to act on it.

A 30-day line chart of daily AI spend across all connected providers, climbing steadily — the recent slope the seven-day burn rate is measured from. — The forecast reads the pace off the recent slope. A climbing trend pulls the forward number up days before the same rise would reach an invoice.

It also doesn’t stop at model APIs. The same projection rolls Claude and OpenAI up next to the GPU box, the hosting bill, and the voice service — the compute spend most token-only tools leave out — so the forward number covers your whole AI bill. Your keys stay encrypted in your browser before they’re ever stored, so the figure is built without the server ever holding a usable credential.

For how each provider meters the usage the forecast is built from, the per-provider guides go deeper — Claude, OpenAI, and Gemini, with the full set on the providers page and a wider overview of tracking AI costs across providers.

Getting a forecast in front of you takes three steps:

Connect a provider — paste the usage or admin key it gives you. It’s encrypted in your browser before it’s stored, so the server only ever holds ciphertext.
Click Refresh to pull recent usage; the seven-day burn rate and next-month forecast appear beside the month-to-date total.
Add the rest. Each provider folds into the same forward number, so the forecast covers everything at once, and a click on Refresh rebuilds it from the latest usage whenever you want it.

Frequently asked questions

What is an AI spend forecast?: It's a forward number — what you're on track to spend rather than what you've already spent. A running total is a rear-view figure. A forecast takes your recent rate of spending and projects it into the future, so you can see where the trend lands. That turns "we'll find out when the invoice arrives" into a figure you can read today and act on while there's still time.
Does the forecast cover the rest of this month or next month?: Next month. CostCompass projects the full next calendar month at your current pace, not the remainder of the month you're in. Late in a month there are too few days left for a current-month projection to mean much, and the question that actually drives a budget is "if this pace holds, what does a whole month at it cost?" The month-to-date figure already tells you where this month stands. The forecast tells you what the next one is shaping up to be.
How is the forecast calculated?: It takes your spending over the last seven days, divides by seven to get a daily rate, multiplies that by the number of days in next month, and adds next month's fixed subscriptions in full. Only metered usage gets extended from the seven-day rate — tokens, GPU-hours, characters, requests. Flat subscriptions are a known monthly charge, so they're added at their actual next-month cost rather than guessed from a few days of usage.
Why a seven-day window instead of the whole month?: Seven days is a middle ground. A single day swings too much to trust — one heavy batch job or one quiet weekend would throw the projection off. Averaging the whole month so far reacts too slowly, dragging an old, cheaper pace into the number long after your usage has changed. A trailing week smooths out day-to-day noise while still turning quickly when your real pace shifts, so a genuine change in spending shows up within days rather than weeks.
Why might the forecast differ from my eventual invoice?: A forecast is an estimate of a future month built from a recent rate, so it moves as your usage moves. A new model, a launch, or a quiet stretch all change it. It also assumes your next-month pace resembles this week's, which won't hold if you already know a big change is coming. And like any rate-based projection it can't see discounts that aren't in the raw usage, such as batch pricing, prompt caching, or promotional credits. Treat it as a well-grounded heading rather than a contract.
Do I have to change my code to forecast AI spend?: No. CostCompass reads each provider's own usage or billing API directly and computes the projection from that. There's no SDK to install and no gateway in your request path — your application runs exactly as it did before. The forecast is built entirely from records the providers already keep, so the only thing you do is connect each provider once.
Can you show the forecast math with an example?: Say your metered usage over the last seven days came to $1,050. Divide by seven and the daily burn rate is $150. If next month has 30 days, the metered part of the forecast is $150 × 30, or $4,500. Add a $200 flat subscription at its real next-month cost and the forecast reads $4,700. The subscription is counted once, never run through the daily rate.
Why use CostCompass to forecast instead of doing it myself?: Forecasting it by hand means logging into every provider, reading each one's after-the-fact usage in its own units, converting to money, averaging a recent window, and projecting it across next month. Then you redo the whole thing every time you want a current number, still separately per provider with no combined view. CostCompass pulls every connected provider's usage with one click and turns it into a single forward projection across all of them — your trailing burn rate extended into next month, beside the month-to-date total and a per-provider breakdown, with nothing wired into your code. You read one number instead of rebuilding it by hand.

About the author

Joubert Berger builds CostCompass, a spend-intelligence dashboard that pulls usage from AI and compute providers into one month-to-date total, a forecast, and a per-provider breakdown. This guide reflects how CostCompass reads each provider's own usage API — see the security model for how your keys are handled.

Know what next month costs at today's pace

Connect each provider once and pull a forward projection across all of them on demand — your recent burn rate extended into next month, with nothing wired into your code.

Start free