CostCompass An Almanac Beta
Managing AI spend

Get ahead of the AI bill, not just even with it

A running total tells you what you've already spent. Managing spend is the forward problem — seeing where the month is heading and having levers to change it before the invoice arrives.

By Joubert Berger Published July 9, 2026

An antique almanac engraving: a hand grips one spoke of a ship's helm mounted before a compass rose, a sight-line running forward from the wheel to a distant horizon — steering the spend rather than watching it.
A running total is the wake behind you; managing spend is a hand on the wheel.

Most cost tools are rear-view mirrors. They tell you, accurately, what you have already spent — which is useful for the accounting and useless for the decision, because by the time a number is final the money is gone.

Managing AI spend is the forward-looking half. It starts with a forecast: take the burn rate you're on, extend it across the rest of the month and into the next, and add the fixed subscriptions you know are coming. That turns a total into a trajectory, and a trajectory is something you can act on — a spike shows up as a line heading the wrong way days before it reaches a bill.

The other half is having levers once you see the trajectory. Model spend responds to specific, unglamorous choices: routing routine work to a cheaper model, caching the context you'd otherwise re-send every call, trimming the input an agent has to read, setting a default that isn't your most expensive option. None of these require using AI less. They require knowing which part of the spend is elastic and pulling on that part deliberately.

The guides below cover both — how to forecast where your AI spend is going, and how to manage what your models cost once you can see it coming.

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.

A forecast, not just a tally

CostCompass takes your recent burn rate, extends it across the month, and folds in your fixed subscriptions — so a developing spike shows up while you can still act on it.