Budgets, Forecasts and Run Rate

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. We’ll use Foundry — the parts maker running through this course, with its $10M of annual revenue — to keep them straight. 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. Foundry’s budget says something like “we’ll bring in $10.0M of revenue and spend $3.0M on operating costs, landing about $1.0M of operating profit.” 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. A few months into the year you know things the budget never did — a hire slipped, a big order closed early, steel got pricier. The forecast folds all of that in. Forecasts are supposed to change every month. A forecast that never moves usually means nobody is updating it.

A budget decision: hiring 10 people

Watch how a single plan choice ripples through Foundry’s numbers. Suppose Foundry’s budget includes hiring 10 people — machinists, a couple of engineers, sales support — at a fully-loaded cost of $80,000 each. Fully-loaded means salary plus payroll taxes, benefits, equipment and space, not just the headline wage. Ten roles at $80k is +$800,000 of operating cost.

That lifts budgeted operating expenses from $3.0M to $3.8M, and — with revenue unchanged at $10.0M and product costs at $6.0M — pushes budgeted operating profit from $1.0M all the way down to $0.2M. Same revenue, one hiring plan, and four-fifths of the profit is gone. This is why people say headcount is the currency of a budget: in most companies people are the largest, and most controllable, line in the plan.

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 Foundry booked $2.6M of revenue last quarter, the revenue run rate is $2.6M × 4 = $10.4M a year. If a single product line earned $850k in a month, its run rate is $850k × 12 = $10.2M 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 $2.6M quarter implies a $10.4M yearly run rate, which is running a little hot against Foundry’s $10.0M 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 quarter included a one-off equipment sale, annualizing it pretends Foundry will make that sale four times. If Foundry’s best quarter was the holiday build-out, multiplying it by four 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 — Foundry’s $10.0M revenue and $1.0M profit plan. The forecast is the careful update made later, with real information — for instance, once those 10 hires are confirmed and OpEx is heading to $3.8M. The run rate is the quick-and-dirty shortcut that turns “this quarter” into “this year” so you can react before the period 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 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.

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 $10.4M a year,” ask what period that came from and whether it was a normal one. When a forecast drifts away from the budget — say, because a hiring plan added $800k of cost — treat it as new information, not a failure, then ask what changed. Useful phrases: “What’s our run rate based on?” “Is that quarter 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.