Budgets, Forecasts & Run Rate
The plan, the updated guess, and the simple math that turns one month into a full year.
What you'll learn
- Tell a budget apart from a forecast
- Calculate a run rate from a single period
- Follow planning-season conversations with confidence
When your company starts talking about “the plan,” “where we’ll land,” and “annualizing,” it is really talking about three close cousins: the budget, the forecast, and the run rate. They all describe the same money, just from different angles and at different moments. Once you can tell them apart, planning season stops sounding like a foreign language and starts sounding like common sense.
Budget and forecast: the plan vs. the honest update
The budget is the plan you commit to before the year begins. It is set during planning season, usually a few months early, and it says something like “this team will spend $240k and bring in $1M.” Once approved, it barely moves. That is on purpose: the budget is the fixed yardstick you measure everything else against, so it has to stay still.
The forecast is your latest honest guess about where you will actually end up. Three months into the year you know things the budget never did — a hire slipped, a deal closed early, a price went up. The forecast folds all of that in: “we budgeted $240k, but realistically we’ll spend $228k.” Forecasts are supposed to change every month. A forecast that never moves usually means nobody is updating it.
Run rate annualizes a single period; compare it to the budget to see if you are on track.
Run rate: stretching one period across a year
A run rate takes what happened in one short period and projects it across a full year, as if that pace continued unchanged. The math is deliberately simple. If your team spent $20k last month, the monthly run rate is $20k × 12 = $240k a year. If a product earned $50k in a quarter, the revenue run rate is $50k × 4 = $200k a year.
The point of a run rate is speed. You do not have to wait for twelve months of data to sense whether you are on track — you take the most recent, most relevant period and annualize it. In the diagram, a $20k month implies a $240k yearly run rate, which is running a little hot against a $228k budget. That gap is your early warning.
Why a run rate can mislead
A run rate assumes the future looks exactly like the period you measured, and that is rarely true. If last month included a one-off software purchase, annualizing it pretends you will buy that software twelve times. If your best sales month was December, multiplying it by twelve invents a fantasy year. Always ask whether the period you are stretching is typical before you trust the number it produces.
Rule of thumb: a run rate is a fast estimate, not a forecast. Use it to spot a trend early, then build a real forecast that accounts for the bumps a run rate ignores.
Putting the three together
Think of it as a timeline. The budget is the promise made early. The forecast is the careful update made later, with real information. The run rate is the quick-and-dirty shortcut that turns “this month” into “this year” so you can react before the quarter closes. The budget tells you the goal, the run rate tells you the current pace, and the forecast reconciles the two into your best honest guess.
When the pace and the plan disagree, that is the conversation worth having. A run rate that is above budget is not automatically bad and below budget is not automatically good — it depends on whether you are looking at costs or revenue, and on what one-off events sit inside the period you measured.
Spot the moment
Read each scenario and decide what number it is — budget, forecast, or run rate? Tap a card to flip it and check your answer.
Sort the statements
Drag each item into the bucket it belongs to — or tap an item, then tap a bucket. Hit Check placement when you’re done.
Here's where each one goes:
- Set in planning season before the year starts → Budget — it's the committed plan locked in early.
- Updated every month with new information → Forecast — you revise it as reality becomes clearer.
- Takes one period and multiplies it by 12 (or 4) → Run rate — simple annualization math.
- The fixed yardstick you measure against → Budget — the budget stays still so you can benchmark everything else.
- Your latest honest guess at where you'll end up → Forecast — this is the update that folds in what you've learned.
- $15k × 12 = $180k annual pace → Run rate — stretching one month into a year.
Tip: drag with a mouse, or tap an item then tap a bucket on touch screens. Get one wrong and the answer key appears.
How to use it
In a planning meeting, quietly tag each number with its moment in time. Is this the budget (the plan), the forecast (the latest guess), or a run rate (one period stretched out)? When someone says “we’re running at $240k a year,” ask what period that came from and whether it was a normal one. When a forecast drifts away from the budget, treat it as new information, not a failure — then ask what changed. Useful phrases: “What’s our run rate based on?” “Is that month typical, or did it include anything one-off?” “How does the latest forecast compare to the budget?” Saying those out loud makes you sound like someone who plans, not someone who panics.
Quick check
1. A team spends $15k in one month. Its annual run rate is…
2. Which number is the plan committed to before the year starts?
3. The biggest risk when using a run rate is that…