Top-Down vs. Bottom-Up Budgeting: Which One Should Finance Trust?

Budget season brings out two very different personalities. Leadership arrives with a spending ceiling. Department managers arrive with carefully considered requests, every one of which is apparently essential to the survival of civilization. Then finance gets invited to make the numbers agree.

I don’t think top-down or bottom-up budgeting wins that argument by itself. One tells us what the business can afford. The other tells us what it may actually take to operate. I’d rather reconcile those two realities than pretend one of them is inconvenient background noise.

What the two approaches mean

Top-down budgeting begins with company targets and financial constraints. Leadership sets expectations for revenue, profit, investment and spending. Bottom-up budgeting starts with the activities and resources individual teams expect to need, then adds them into a company plan.

Top-down can keep the organization financially disciplined. Bottom-up can capture the messy details leadership may not see. Both have blind spots. A target that ignores staffing requirements is wishful thinking; a department request without a business case is also wishful thinking, just with more line items.

Let’s work through a $500,000 disagreement

Suppose a hypothetical company expects $12 million in revenue. Leadership sets a $4 million operating expense ceiling, but department submissions total $4.5 million. We’re $500,000 apart.

Someone will inevitably suggest cutting every department by about 11.1%. It’s wonderfully simple, assuming every expense behaves the same way. By that logic, we could save money on a house by removing 11% of the roof.

I’d sort the requests into contractual commitments, costs driven by volume, optional projects and investments intended to increase capacity. Suppose we can defer $120,000 of software, shift hiring dates to save $180,000 and renegotiate $50,000 in services. We’ve identified $350,000 in possible reductions. The remaining $150,000 is a decision leadership must make, not a discrepancy finance should hide.

Where top-down budgeting helps

When cash is tight or the company needs to protect a margin target, I want leadership to set clear boundaries. Otherwise departments can create individually sensible plans that add up to an unaffordable company plan.

But I’d challenge a top-down revenue target that requires more output while simultaneously removing the labor needed to deliver it. We can ask people to work smarter. We cannot budget our way into infinite Tuesdays.

Where bottom-up budgeting helps

Managers know about supplier quotes, staffing coverage, project timing and operational constraints. I’d ask them to tie every major request to a driver and explain the consequence of delaying it.

I’m not looking for a speech about how every request is urgent. I’d like to know what changes if the new hire starts in July instead of April, or if a project moves to next year. That’s where the useful trade-offs live.

How I’d bring the two plans together

First, I’d give everyone the same assumptions about pricing, wages and demand. Then I’d collect bottom-up plans, compare them with leadership’s constraints and build a bridge showing the differences. We’d resolve the largest gaps through explicit choices, document owners and keep a record of what would trigger a reforecast.

Top-down and bottom-up describe where planning begins. They don’t determine whether an expense must be justified from zero. That’s a separate budgeting choice, and I’d keep the terminology straight before someone creates a 40-slide presentation to settle it.

My preferred outcome isn’t a number everyone has been pressured to accept. It’s a plan where people understand what we’re funding, what we’re postponing and what we’re risking. That makes the next conversation much easier, even if nobody gets everything on the wish list.

Related reading: budget vs. forecast and headcount planning.

Financial examples are hypothetical.