A static budget is a 12-month financial plan prepared once a year and left unchanged; a rolling forecast is a projection updated monthly or quarterly that always looks a fixed horizon, typically 12 months, ahead. For most startups and SMBs the answer is to use both: the annual budget for targets, accountability, and incentives, and the rolling forecast for operational decisions and cash flow visibility. Neither requires enterprise software; Excel or Google Sheets is sufficient through Series A.
Every September, thousands of finance teams around the world go through a ritual that most of them privately acknowledge is at least partially pointless. They build an annual budget — a detailed, line-by-line projection of the next 12 months — that by March will have been rendered largely irrelevant by things that nobody predicted in September: a customer who churned unexpectedly, a hire who didn't join, a market that moved faster or slower than anyone modelled.
The annual budget isn't useless. But treating it as the primary tool for navigating a fast-moving business is a bit like planning a road trip with a map printed six months ago and refusing to use GPS.
The rolling forecast is the GPS. This guide explains what it is, how it compares to the static budget, and — critically — how startups and SMBs can implement one without an enterprise FP&A team or expensive software.
The static budget problem: why annual plans break by Q2
A static (or annual) budget is a financial plan prepared once a year that covers the full 12-month period ahead. Once approved, it typically doesn't change — actuals are compared against it monthly, variances are explained, and the exercise repeats.
The structural problem is straightforward: the assumptions baked into a September budget are based on what you knew in September. A startup's environment in March — competitive dynamics, hiring market, sales cycle length, customer churn behaviour — is routinely different from what was knowable six months earlier. A budget prepared in those conditions will generate variances that are informative (you learn something about your business) but progressively less useful as a forward-looking guide (the projection is too stale to trust for decisions).
This creates a frustrating dynamic where finance spends significant energy explaining why actuals diverged from a plan that everyone knows is outdated, rather than focusing on what comes next and what to do about it.
The other limitation of a static budget is psychological. Once a budget is approved, it becomes a target that shapes behaviour — often in ways that don't serve the business. Departments defend budget allocations they don't need because surrendering them might result in smaller allocations next year. Managers underspend in Q4 to hit a budget line while a competitor is moving fast. The budget becomes an end in itself rather than a tool for better business outcomes.
What a rolling forecast is (and what it isn't)
A rolling forecast is a continuously updated forward projection that maintains a consistent time horizon — typically 12 months — regardless of where you are in the calendar year.
Instead of preparing one annual plan in September that governs the full year, you update the forecast monthly (or quarterly). As January closes, you roll the forecast forward and now have a 12-month view from February. The projection is always current, always forward-looking, and always reflects what you've actually learned about the business.
What a rolling forecast is:
- A forward-looking projection updated regularly (monthly or quarterly)
- A management and decision-support tool
- A living document that reflects current business conditions
- The basis for near-term operational decisions
What a rolling forecast is not:
- A replacement for variance analysis (you still need to compare actuals to a prior plan)
- An excuse to avoid accountability (the act of updating the forecast should include honest explanation of why the business is where it is)
- A tool that requires a dedicated FP&A team or enterprise software to maintain
- A goal-setting or incentive framework (for those purposes, a fixed target — the budget — is typically more appropriate)
That last distinction matters. The rolling forecast and the annual budget serve different purposes, and understanding that distinction is the key to implementing a hybrid approach that actually works.
Side-by-side comparison: rolling forecast vs. static budget
| Dimension | Static budget | Rolling forecast |
|---|---|---|
| Update frequency | Once a year | Monthly or quarterly |
| Forward horizon | Fixed (e.g., Jan–Dec) | Rolling (e.g., always 12 months ahead) |
| Primary purpose | Performance management, accountability | Decision support, forward planning |
| Accuracy over time | Degrades significantly by Q3–Q4 | Maintained (always recently updated) |
| Best for | Setting annual targets, incentive alignment | Operational decisions, resource allocation |
| Effort to maintain | Low (built once, reported against) | Moderate (requires regular update discipline) |
| Typical users | Finance, department heads, board | Finance, leadership team, operational managers |
| Software requirements | Excel/Google Sheets | Excel/Google Sheets (no enterprise software needed) |
The conclusion from the comparison is not that rolling forecasts are better than static budgets — it's that they serve different purposes and work best together. The annual budget sets the targets that everyone is accountable to. The rolling forecast tells you where you're actually going and what decisions you need to make to get there.
The hybrid model: how startups can use both effectively
The most practical approach for startups and SMBs is a lightweight hybrid:
Annual budget (set once, at the start of the year):
- Used for performance management — are we hitting the targets we committed to?
- Used for board and investor reporting — where are we vs. the annual plan?
- Used for incentive alignment — sales targets, team OKRs, and bonus structures are set against the budget
Rolling forecast (updated monthly):
- Used for operational decisions — hiring, spending, resource allocation
- Used for cash flow visibility — the rolling forecast feeds directly into the cash flow model
- Used for investor narrative — "we're tracking 8% below budget on ARR, here's why, and here's what the next 12 months look like on current trends"
In practice, this means the finance function maintains two documents: the locked annual budget, which changes only if there is a genuine need for a formal reforecast (material business model change, significant acquisition, board-approved revision), and the rolling forecast, which is updated every month as part of the standard close process.
How to build a Minimum Viable Rolling Forecast in 4 weeks
The biggest barrier to rolling forecasting in small businesses is perceived complexity. In reality, a Minimum Viable Rolling Forecast (MVRF) for a startup or SMB is not a sophisticated enterprise planning exercise. It's a structured update to a relatively simple financial model, performed monthly.
Week 1: Structure the model correctly Your rolling forecast needs to be built in a structure that allows monthly actuals to replace projected figures and the horizon to roll forward. This means: one row per month (at minimum), a clear demarcation between actuals (closed months) and forecast (open months), and assumptions that live in a separate, clearly labelled section.
Week 2: Define the key business drivers For each major line item, identify the 1–3 business drivers that actually determine the outcome. Revenue is not "revenue grows 10% per month" — it's new customer signings × average contract value × churn rate. Headcount costs are not a lump sum — they're a list of people with start dates, salaries, and employer cost percentages. Build the forecast from these drivers, not from top-down growth assumptions.
Week 3: Establish the update process Agree on the monthly update protocol: who pulls the actuals from the accounting system, who updates the key assumptions based on current trading conditions, who reviews the output before distribution, and who receives the final forecast. This process should take no more than half a day per month once it's established.
Week 4: Connect the forecast to decisions Review the rolling forecast output and identify what it tells you about the next 90 days. Are you on track to meet the board's expectations? Are there cash flow pinch points visible in weeks 8–10? Do you need to accelerate or delay a hire? The forecast's purpose is to inform these decisions — if it's not doing that, the process isn't working yet.
Lightweight tools that won't break your budget
You do not need Adaptive Insights, Anaplan, or Pigment to run a rolling forecast. Those tools are genuinely powerful at scale, but they add complexity and cost that most startups cannot justify until they have a dedicated FP&A resource.
Excel or Google Sheets is sufficient for the rolling forecast through Series A for most businesses. The key is model discipline — version control, clear assumption architecture, and a consistent monthly update process. A well-built Excel rolling forecast maintained properly is more useful than a poorly maintained enterprise tool.
Google Sheets has specific advantages for collaborative environments: real-time collaboration, built-in version history, and accessibility from any device. The tradeoff is performance (large models run slowly) and some formula limitations vs. Excel.
Consider a lightweight FP&A tool (Causal, Jirav, Mosaic) at Series A if the number of users who need to interact with the model makes Excel collaboration unwieldy, or if you want automated actuals integration from your accounting system. But solve the process first; the tool is an accelerant, not a foundation.
When to bring in a fractional CFO for forecasting
The rolling forecast is a powerful tool, but it requires consistent discipline and financial modelling skill to maintain properly. If the forecast isn't being updated monthly, if it's drifting significantly from actuals without clear explanation, or if it's not informing decisions — the tool is failing.
A fractional CFO typically owns the rolling forecast as part of the FP&A function. They update it monthly, present the findings to the leadership team, and use it as the basis for strategic financial recommendations. For businesses that want the benefit of a rolling forecast without the overhead of building and maintaining it in-house, a fractional engagement is usually the most cost-effective path.
FAQs
How often should a rolling forecast be updated? Monthly is the standard for most businesses — it aligns with the monthly close cycle and ensures the forecast is always current. Quarterly updates are acceptable for smaller, more stable businesses, but any less frequent than that and the rolling forecast starts to lose its value over the static budget.
What's a reforecast, and how is it different from a rolling forecast? A reforecast is a formal revision to the annual budget — typically triggered by a material change to the business (a significant acquisition, a major customer loss, a strategic pivot). A rolling forecast is an ongoing operational tool that runs alongside the annual budget. They serve different purposes and are not substitutes.
Can we use a rolling forecast for board reporting? Yes, and it's often the most useful format for board reporting — showing the board not just where you are vs. the annual plan, but where you're actually headed over the next 12 months on current trends. The combination of budget vs. actuals and rolling forecast vs. prior rolling forecast gives the board the full picture.
BB Financial Services Kft designs and maintains rolling forecast frameworks for startups and SMBs across Europe. Get in touch if you want to replace your annual budget with a planning process that actually stays relevant.