Zero-Based Budgeting: When It Works and When It Creates Overhead

Zero-based budgeting (ZBB) is a planning method where every expense must be justified from scratch each budget cycle, rather than starting from last year's numbers and adjusting incrementally. It forces departments to build their budgets from a zero base, documenting the business need and expected return for every dollar requested. The approach gained mainstream corporate attention when 3G Capital used it aggressively during the Kraft Heinz merger in 2015, and it remains popular in private equity-backed companies focused on cost discipline.

How ZBB differs from traditional budgeting

Traditional incremental budgeting starts with last year's actual spending and adjusts — typically by applying a percentage increase for inflation or growth, then negotiating line-item changes with department heads. The implicit assumption is that last year's spending was justified, and only the changes need scrutiny. This is efficient but creates a ratchet effect: once a budget line exists, it rarely disappears. Departments learn to spend their full allocation each year to protect next year's baseline, regardless of whether the spending is still valuable.

Zero-based budgeting eliminates this assumption entirely. Every department starts at zero and must justify each budget request with a documented purpose, expected outcome, and prioritization rank. If a marketing team spent $200,000 on trade shows last year, they cannot simply request $210,000 this year. They must explain why trade shows are the best use of $200,000, what the expected return is, how that return compares to alternative uses of the same dollars, and whether the full $200,000 is necessary or whether $150,000 would achieve 80 percent of the value.

The 5-step ZBB process

Step 1: Define decision units

A decision unit is the organizational level at which budgets are built and approved — typically a department, function, or cost center. The decision unit owner is responsible for constructing the zero-based budget for their area. Defining decision units correctly is critical: too broad and the analysis lacks actionable detail; too narrow and the process becomes impossibly time-consuming. Most implementations use functional departments or cost centers with annual budgets above $100,000 as the primary decision units.

Step 2: Build decision packages

Each decision unit creates decision packages — documented budget requests that describe a specific activity or expenditure, its purpose, expected outcomes, and cost at different funding levels. A typical decision package includes a base level (minimum viable funding to maintain essential operations), a current level (funding needed to maintain existing service quality), and an enhancement level (additional funding for growth or improvement). This tiered approach forces managers to distinguish between essential and discretionary spending.

Step 3: Rank decision packages

Department heads rank their own decision packages from highest to lowest priority. Then senior leadership ranks packages across departments, creating a company-wide priority list. This cross-functional ranking is the most powerful part of ZBB — it makes explicit trade-offs that incremental budgeting hides. Should the company fund a $150,000 marketing hire or a $150,000 engineering contractor? Traditional budgeting answers this implicitly through historical precedent. ZBB forces an explicit comparison of expected value.

Step 4: Allocate resources

With all packages ranked, leadership draws a funding line at the available budget. Everything above the line gets funded. Everything below does not. The ranking makes the trade-offs visible and defensible — departments whose packages are cut can see exactly what was prioritized above their request and why. This transparency is one of ZBB's greatest strengths for organizations with political budgeting cultures where allocation is determined by who negotiates hardest rather than what generates the most value.

Step 5: Monitor and adjust

Throughout the fiscal year, actual spending is tracked against the zero-based budget. Variance analysis focuses not just on whether departments stayed within budget, but on whether the expected outcomes documented in the decision packages are being achieved. If a funded initiative is not delivering its projected return, the budget can be reallocated to higher-value packages that were below the funding line. This ongoing accountability loop is what distinguishes disciplined ZBB from a one-time cost-cutting exercise.

Pros and cons of zero-based budgeting

Which companies benefit most from ZBB

ZBB delivers the highest return for organizations with large, mature cost structures where historical spending patterns have calcified over time. Private equity-backed companies undergoing operational improvement are the most common adopters — the PE sponsor wants to identify and eliminate spending that does not drive EBITDA growth, and ZBB provides the analytical framework to do it rigorously. Companies that have grown through acquisition and accumulated redundant functions and vendors also benefit significantly because ZBB forces a rationalization of overlapping spending.

Government agencies and large nonprofits use ZBB to counter the institutional tendency toward budget expansion. The approach is also effective at companies experiencing a strategic pivot, where last year's spending priorities may be completely misaligned with next year's direction. In these contexts, the high effort of ZBB is justified because the alternative — incremental budgeting based on an irrelevant baseline — would perpetuate misallocation.

When ZBB creates unnecessary overhead

ZBB is the wrong approach for early-stage startups where the budget changes quarterly, for small teams where the budget owner is also the executor and does not have time for extensive documentation, and for organizations where the majority of costs are truly fixed (rent, committed salaries, contracted services) and the discretionary spending that ZBB examines represents less than 15 to 20 percent of total cost. In these cases, the effort of building and ranking decision packages exceeds the value of the insights generated.

Even for organizations where ZBB fits, running a full zero-based process every year is often too much. Many companies adopt a rotational approach — conducting full ZBB for one-third of the organization each year on a 3-year cycle, with incremental budgeting for the departments not in the ZBB rotation. This captures most of the benefits while reducing the annual process burden by two-thirds. Kraft Heinz, which popularized modern corporate ZBB, eventually moderated its approach after finding that annual full-company ZBB contributed to underinvestment in brand building.

Software that supports zero-based budgeting

Most FP&A and budgeting tools can be configured to support ZBB workflows, even if they do not market themselves specifically as ZBB platforms. Anaplan and Pigment offer the model flexibility to build decision packages, create ranking frameworks, and run scenario analysis comparing different funding levels. Planful and Vena provide template-driven budgeting workflows that can be adapted for ZBB input collection. SAP's dedicated Analytics Cloud ZBB module is purpose-built for the methodology but is typically only cost-effective for large enterprise deployments.

The software requirement for ZBB is mainly a structured input collection and prioritization engine — not fundamentally different from what good FP&A software provides for any planning process. The differentiator is whether the tool can handle the volume of decision packages (often 200 to 500 for a mid-market company), support tiered funding levels within each package, and produce the ranking and allocation output that leadership needs to make decisions. Spreadsheets can handle ZBB for a single department but break down when the process scales across the organization.