Your Budget Shouldn't Drive Your Business Plan

Most businesses build the budget and then work backwards to an operating plan. The businesses that plan well do it the other way around. Most annual budget processes are political theatre. Departments pad their asks knowing they'll be cut. Leadership cuts by an arbitrary percentage, expecting the padding. Everyone ends up with a number nobody believes in by February.

The bigger problem is that many businesses start in the wrong place. They start with the financial outcome they want (20% growth, another 3% of margin, a headcount target) and then work backwards to create a business plan capable of delivering it. That's the wrong way around.

Start with the operating plan: what are we actually going to do, what resources will we need, and what should happen as a result? The operating plan creates the budget. Then the budget challenges the operating plan.

Driver-based budgeting with zero-based challenge

At Rhomu, we think about this as driver-based budgeting with zero-based challenge. Driver-based means building the numbers from what actually drives the business - customers, volumes, pricing, people, capacity, investment and new initiatives. Zero-based challenge means last year's spend doesn't automatically earn the right to exist again this year. Instead of asking "What did we spend last year?", ask: "Given what we're actually planning to do, what should this cost?"

What I learned about planning at Amazon

One of the most important things I learned during my time at Amazon was that the budget wasn't the starting point. The operating plan was. The process ran for almost six months.

June - the Three-Year Plan

The longer-term plan was continuously updated for what we'd learned, where assumptions had changed and where the business had pivoted. It wasn't a separate strategy exercise. The longer-term plan, annual operating plan and budget were connected.

August/September - OP1

OP1 was the first full operating plan for the following year. The business set out what it intended to do - priorities, initiatives, investment, resources and headcount. If you wanted investment, you needed to explain what you were going to do with it. If you expected growth, you needed to explain what would operationally create it. Then those decisions were translated into financial numbers.

Then the numbers fought back

Once the operating plan had been translated into a budget, the numbers challenged it. Maybe the business couldn't afford to do everything being proposed. Maybe several initiatives all generated a good return, but one generated a better return than another. Maybe the headcount ask was too aggressive. Maybe the revenue assumptions didn't support the investment being requested. The challenge wasn't usually finding bad ideas. There were always more good ideas than there were resources to execute them. Planning forced the business to choose which opportunities deserved those resources most.

That's the important distinction: good budgeting is about capital and resource allocation, rather than cost cutting. The question isn't simply "Where can we spend less?" It's: "Given the people, cash and capacity we have, where will they create the greatest return?" The process therefore became: Operating Plan → Budget → Challenge → Revised Operating Plan → Revised Budget. The plan created the numbers. Then the numbers challenged the plan.

December - OP2

By OP2, initiatives had been accepted or rejected, assumptions refined, resource asks challenged and priorities agreed. OP2 wasn't supposed to be a completely different plan. It was the refined, financially grounded version of OP1. By December, the operating plan and budget could be signed off together because they had been built together.

The real output wasn't the budget

There was another consequence of spending almost six months building and challenging the plan. On Day One, everyone knew the plan inside out. The priorities were understood. Resource decisions had already been debated. Teams knew what had been approved and what hadn't. The difficult conversations happened before the year started. There wasn't a strategy in one document, a three-year plan somewhere else and a budget sitting with Finance. They were different views of the same plan.

You don't need to be Amazon

A growing SME doesn't need a six-month planning process. But the discipline scales remarkably well. Start with what the business intends to do. Translate that into people, investment, capacity and financial outcomes. Let the numbers challenge the plan. Prioritise the opportunities that create the greatest return. Keep going until you have something the business can both afford and actually deliver.

Closing

A budget built without an operating plan is just a spreadsheet full of assumptions.

Start with the plan. Let the plan create the budget. Then let the budget challenge the plan.

And if you've done it properly, Day One isn't when people discover the plan. It's when they start executing a plan they already know inside out.

Does your budget describe how your business is actually going to operate next year? If the plan and the numbers were built separately, that's probably the place to start.