Rolling Forecasts vs the Annual Budget
A virtual CFO's case for the rolling forecast: why the annual budget goes stale, what a rolling 12-month cadence changes, and what to keep from budgeting.
The annual budget is usually wrong by March and quietly ignored by June. It was built on assumptions that started ageing the day it was locked, and the business it describes no longer exists a quarter in. A rolling forecast fixes the decay by never letting the view go stale. This is a virtual CFO's case for the rolling cadence, argued with mechanics rather than attitude, and with a clear account of what the annual budget is still good for.
Published: July 2026
The annual budget has one structural flaw: it is a fixed picture of a moving business. It is built once, before the year starts, on the best assumptions available at that moment, and then it stays still while the world does not. A big customer leaves in February, a new product lands ahead of plan, costs rise faster than assumed, and the budget, unchanged, drifts further from reality with each passing month.
By the second quarter, most founders are managing against a document they no longer believe. The budget still exists, it still gets reported against, but the variance columns have become an exercise in explaining why reality diverged from a guess made months ago, rather than a tool for deciding what to do next. That is not a failure of discipline; it is the inevitable result of anchoring a full year to a single stale view. This is the planning-cadence companion to the weekly cash meeting, and it is often part of a 90-Day Number reporting build.
A rolling forecast replaces the fixed year with a continuously updated horizon. Instead of budgeting January to December and then living with it, you always hold a forward view of the next twelve months, and each month you drop the month just finished and add a new month at the far end. The horizon rolls forward, so you always have four quarters of forward visibility rather than a shrinking remainder of a stale year.
Twelve months is the standard horizon for the $2M to $15M band, usually with monthly detail for the next two quarters and quarterly buckets beyond, since precision at month eleven is theatre. Businesses raising capital or carrying long build cycles sometimes extend to eighteen. Either way, the faster the business moves month to month, the stronger the case: SaaS businesses with live churn and pipeline feel budget decay first.
The practical change is that the forecast stays current. When the big customer leaves in February, the March re-forecast absorbs it, and the forward view reflects the business as it actually is, not as it was assumed to be in October. Decisions get made against a live picture. The variance conversation shifts from explaining the past to adjusting the future, which is the conversation that actually helps.
The objection founders raise first is effort: if the annual budget took two weeks, surely a monthly forecast takes two weeks every month. It does not, and understanding why is the key to the whole approach. The heavy lifting is building the model once. After that, the monthly re-forecast is an update, not a rebuild: refresh the actuals for the month just closed, adjust the forward assumptions that have changed, and extend the horizon by one month. Done well, on a model built for it, this is a couple of hours a month, not a couple of weeks.
The discipline is in the rhythm, not the labour. A fixed monthly slot, the same few drivers reviewed each time, and a willingness to change the forward numbers when the evidence changes. The model does the arithmetic; the founder supplies the judgement about what has shifted. That cadence is what keeps the forecast alive rather than letting it decay into another document nobody opens.
The couple-of-hours claim only holds if the model is built the right way. A budget is typically a schedule of two hundred GL lines, each one a number somebody typed. A rolling forecast should be driver-based: revenue expressed as the handful of operational drivers that produce it (pipeline times conversion, customers times price, billable days times rate), headcount as its own block because it is most of the cost base at this size, and everything else grouped into a dozen cost lines that move with revenue, headcount, or time.
Then a re-forecast means touching five or six assumptions, not two hundred cells. If churn moved, change churn and let it flow through. If the model cannot do that, the problem is the model, not the cadence, and it is worth rebuilding before committing to the rhythm.
The rolling forecast does not make budgeting worthless, and pretending it does is where the argument usually overreaches. Two things from the budgeting world are worth keeping, and most businesses that adopt the rolling cadence run both instruments in parallel.
The first is the annual target. A board, investors, or the founder's own ambition often needs a fixed goal for the year, a line in the ground to be measured against. That is a legitimate use, and it survives. The second is cost discipline: the budgeting exercise of deciding, deliberately, what the business will and will not spend on, which imposes a useful constraint that a forecast alone does not.
The clean way to hold both is to treat the annual target as a contract and the rolling forecast as a forecast. The target is what you committed to; the forecast is your current honest expectation of where you will land. They are different instruments for different purposes, and a mature finance rhythm runs both. The rolling forecast tells you the truth; the annual target holds you to account.
Here is what the rhythm looks like in practice. At the start of the year, you set an annual target (the contract) and build the rolling 12-month forecast (the forward view), and they agree, because at that moment they should. Each month, within a few days of close, you spend a couple of hours updating the forecast: actuals in, forward assumptions adjusted, horizon extended. Quarterly, you review the forecast against the annual target and report both to the board, one as the commitment, one as the current expectation, with the gap between them as the real subject of the conversation. By year end, the target tells you whether you delivered what you promised, and the forecast has been useful every single month along the way. The two coexist without conflict, which is the point.
The most common institutional objection is that the board wants a budget. Give them one. The annual target serves exactly that need, as the contract the business is measured against. What the rolling forecast adds, alongside it, is an honest forward view that updates as the year unfolds, so board conversations rest on the current reality rather than on variance to a stale plan. A board that sees both, the commitment and the live expectation, makes better decisions than one staring at a budget everyone privately knows is out of date. For the reporting that carries both to the board, see designing a KPI tree and the three-way forecast and when you need one.
Setting this up is a build, not a subscription. The board reporting pack in the 90-Day Number delivers the rolling model, the annual target sitting alongside it as the contract, and the monthly cadence documented, fixed at $17,850 plus GST. Most virtual CFO engagements in Australia are open-ended retainers; this one ends on day 90 with the rhythm running and the model yours.
Why does the annual budget stop being useful?
Because it is a fixed picture of a moving business. Built once on pre-year assumptions, it drifts from reality as customers, costs, and conditions change, and by the second quarter most founders are managing against a document they no longer believe. The variance columns end up explaining the past rather than guiding the future.
What exactly is a rolling forecast?
A continuously updated twelve-month forward view. Each month you drop the month just finished and add a new one at the far end, so you always hold four quarters of forward visibility rather than a shrinking remainder of a stale year. It stays current because it is refreshed monthly against actuals and changed assumptions.
How long a horizon should a rolling forecast cover?
Twelve months is the standard for a $2M to $15M business, with monthly detail over the next two quarters and quarterly buckets beyond that, because month-eleven precision is false precision. Extend to eighteen months if you are raising capital or carrying long build or inventory cycles that need the longer view.
Doesn't a monthly forecast take far more work than an annual budget?
No, once the model is built. The heavy lifting is the initial build; after that, the monthly re-forecast is an update, refresh actuals, adjust forward assumptions, extend the horizon, which is a couple of hours a month on a model designed for it, not a couple of weeks. The discipline is the rhythm, not the labour.
Do I have to abandon budgeting entirely?
No. Keep the annual target as a contract, the fixed goal the business is measured against, and keep the cost discipline that budgeting imposes. Run the rolling forecast alongside as your live expectation. The target holds you to account; the forecast tells you the truth. A mature rhythm uses both.
My board wants a budget. How does this work?
Give them the annual target as the budget-equivalent contract, and present the rolling forecast alongside it as the current forward view. The board sees both the commitment and the honest expectation, and the gap between them becomes the useful conversation, rather than reviewing variance against a plan everyone knows is stale.
Is a rolling forecast just a fad?
No. It is a mechanics-driven improvement, not a fashion. The annual budget's staleness is structural, not a discipline problem, and the rolling cadence fixes it by keeping the view current. The argument is not that budgets are bad but that a fixed annual view alone is insufficient for decisions in a business that changes month to month.
Can a virtual CFO set up a rolling forecast for me?
Yes. The board reporting pack in the 90-Day Number covers exactly this: the rolling model built, the annual target set alongside it as the contract, and the monthly cadence documented so you can run it yourself in a couple of hours a month after day 90.
Sydney Virtual CFO is a Sydney-based virtual CFO service for founders running $2M to $15M businesses across SaaS, ecommerce, professional services, construction, and other low-volume, high-value industries. We deliver fixed-scope CFO engagements with a named deliverable on day 90: a 13-week cashflow forecast, a fundraise-ready financial model, a unit economics build, or a board reporting pack you can run on your own.
Our front-door product, the 90-Day Number, is fixed scope at $17,850 plus GST. We are one of the few project-based virtual CFOs in Australia, in a market built almost entirely on monthly retainers. No retainers without a deliverable. No 80-page reports. No theatre.
This content is general information only, written for Australian founders running businesses in the $2M to $15M revenue range. It does not constitute tax, financial product, investment, or legal advice and should not be relied on as such. The work referenced is led by a Chartered Accountant (CA ANZ), but Sydney Virtual CFO is not a licensed tax agent, not a licensed financial adviser, and not authorised to provide personal financial advice. Tax obligations, accounting treatments, fundraise terms, and statutory requirements depend on your individual circumstances. For advice specific to your business, contact the team directly or consult a registered tax agent, licensed financial adviser, or qualified lawyer. Information was current at the time of publication and may change without notice. We review and update guides periodically.
