Article 2 of 8 · Financial Intelligence · 9 min read
Why Your Budget Is Already Wrong
Most budgets are obsolete before they're approved. Not because the numbers are wrong — but because the process that builds them is designed for a world that no longer exists by the time the document is finished.
November. The management team spends six weeks building the budget for next year. Revenue targets are negotiated. Cost envelopes are defined. Headcount plans are approved. The document is finalised in mid-December and presented to the board. By the first week of February, a major client has given notice, a key supplier has increased prices by 12%, and the interest rate environment has shifted the cost of the company's revolving credit facility. The budget is eleven weeks old and already materially wrong. The team will spend the rest of the year explaining the variances.
The scenario above isn't a failure of planning — it's the predictable result of how most organisations approach budgeting. The annual budget cycle produces a document that is precise, detailed, and backward-looking. It captures the world as it was understood in October and November. It says almost nothing useful about the world as it actually unfolds in the following twelve months.
This is not an argument against budgeting. It's an argument for understanding what a budget can and cannot do — and building a planning system that compensates for its structural limitations.
A budget is a plan for a world that will not exist. The question is what you do when reality diverges.
The five reasons your budget is already wrong
- It was built on last year's assumptions — The most common budgeting method takes last year's actuals and applies adjustments: grow revenue by X%, hold costs at Y%. This anchors the entire document to a baseline that may no longer be relevant. The mix of products, customers, and costs changes every year. A budget built on last year's structure systematically misrepresents next year's reality.
- It was negotiated, not calculated — In most organisations, the budget process is fundamentally political. Revenue targets are set by what management wants, not what the sales pipeline supports. Cost budgets are set by what departments can negotiate, not what the work actually requires. The resulting numbers satisfy organisational dynamics — but they don't accurately represent the financial future of the business.
- It assumes linearity in a non-linear world — Most budgets spread annual numbers evenly across twelve months — or apply a simple seasonal pattern based on prior years. Real businesses don't work this way. Revenue is lumpy. Costs spike at project starts. Cash timing is irregular. A budget that doesn't model the actual timing of cash flows and costs will produce misleading monthly variance reports, even when the full-year number is roughly right.
- It ignores the things most likely to change — Budget assumptions typically cover the predictable and ignore the probable. Exchange rate movements, key customer concentration risk, supplier price escalations, regulatory changes, team departures — these are the variables that most frequently derail budgets. Because they are uncertain, they are excluded. Because they are excluded, the organisation has no framework for responding when they materialise.
- It is measured against itself, not against reality — Budget variance analysis compares actual results to the original budget. When both are wrong in the same direction — when the budget overestimated revenue and you also underperformed — the variance looks better than the true picture. The budget becomes the benchmark for success, which means the benchmark moves as reality changes. This is not accountability. It is a sophisticated way of avoiding it.
Budget vs. plan vs. forecast — three things most companies confuse
Much of the confusion around budgeting comes from treating these three tools as the same thing. They are not. Each serves a different purpose and should be managed differently.
| What most companies do | What high-performing companies do |
|---|
| One document does all three jobs | Budget: annual commitment to stakeholders |
| Budget = target = forecast = plan | Forecast: rolling best estimate, updated monthly |
| Updated once a year, maybe twice | Plan: operational roadmap with milestones |
| Variances explained after the fact | Each owned by a different person |
| Nobody quite sure what it's for | Gaps between them treated as information |
The budget is a commitment — to the board, to investors, to the management team. It sets expectations and defines accountability. It should be ambitious but credible, and once set, it should not move. It is the stake in the ground.
The forecast is a prediction — the finance team's best current estimate of where the business will actually land, given current information. It should be honest, not optimistic. It should update every month as new information arrives. The gap between the budget and the forecast is a signal — when it widens, it demands attention and a response.
The plan is a roadmap — the operational actions that will close the gap between where you are and where the budget says you need to be. It changes as circumstances change. It is owned by the people doing the work, not just the finance team.
What a better budgeting process looks like
- Start from strategy, not from last year — Before opening last year's numbers, define what the business is trying to achieve next year — which markets, which customers, which products, which capabilities. Build the budget from those strategic choices. Last year's actuals are inputs, not the framework.
- Build from drivers, not from line items — Revenue should be the product of pipeline conversion assumptions, average deal sizes, and retention rates — not a single growth percentage. Costs should be driven by headcount plans, project volumes, and supplier contracts — not a percentage of last year. Driver-based budgets are easier to update and easier to understand when they're wrong.
- Build at least two scenarios — A base case and a downside case, at minimum. The downside case should reflect genuinely plausible adverse conditions — not catastrophic ones. What happens if your two largest customers reduce spend by 20%? What if a key hire doesn't close? Scenario budgets don't make the bad outcomes more likely — they make the organisation more capable of responding when they occur.
- Separate the budget from the forecast immediately — From January 1, maintain a rolling forecast alongside the budget. They will start identical. By March they will have diverged. That divergence is information. Review the gap monthly, not to update the budget but to decide what to do about it.
- Shorten the budget cycle — Most organisations spend ten to twelve weeks on the annual budget. For most of that time, they are refining precision that will be irrelevant by February. A six-week budget cycle — focused on strategic assumptions and key drivers rather than granular line items — produces a document that is equally useful and significantly less expensive to produce.
A budget that updates when your business does.
BudgetAI connects your financial plan to your operational data — so when reality diverges from the plan, you see it immediately, not at the end of the quarter.
Cash Flow vs. Profit: The Confusion That Kills Growing Companies · Working Capital: The Cash Trapped in Your Own Business