Zero-Based Budgeting

Every budgeting methodology carries an implicit question. Line-item budgeting asks: what did we spend last year? Driver-based budgeting asks: what does the business need to do, and what does that cost? Zero-based budgeting asks something more uncomfortable: if we were building this cost base from scratch today, would we build it this way?

That question is powerful in the right context. In the wrong context, it is an expensive distraction that consumes the finance team’s capacity for months and produces recommendations the organisation was never going to act on.

I introduced ZBB briefly in Driver-Based Budgeting: Moving Beyond Line-Item Extrapolation, where I noted that it solves a cost structure problem rather than a cost visibility problem. This article goes deeper: when the clean-sheet approach earns its complexity, when it does not, how to run the process without destroying your team, and how ZBB fits alongside the driver-based and rolling forecast infrastructure I covered in the earlier articles.

What Zero-Based Budgeting Actually Means

ZBB requires every cost to be justified from zero for the upcoming period. There is no inherited baseline. Last year’s spend is not a starting point. Every function, every cost centre, and every activity must make a fresh case for why it should exist and at what funding level.

The original concept, developed by Peter Pyhrr at Texas Instruments in the 1970s, required managers to build “decision packages” for each activity: a minimum level of funding, an incremental level, and the business case for each tier. Leadership would then rank these packages across the organisation and fund them in priority order until the budget was fully allocated.

In practice, most modern implementations are less dogmatic. Full ZBB (every cost from zero, every year) is rare outside of private equity portfolio companies and businesses in financial distress. What most finance teams run is a targeted ZBB exercise: selecting specific cost categories or business units for the clean-sheet treatment while leaving the rest of the budget on a driver-based or incremental approach.

The distinction matters because the resource cost of ZBB scales directly with scope. A targeted exercise on indirect costs for three cost centres is a two-month project. A full enterprise-wide ZBB is a six-month transformation programme that touches every function and requires executive sponsorship to survive.

When ZBB Earns Its Complexity

I have seen ZBB produce genuinely valuable outcomes in four specific situations.

Cost structures that have accumulated without scrutiny. Businesses that have grown rapidly over several years often carry cost layers that made sense at an earlier stage but no longer match the current operating model. The subscription stack grows by addition and almost never by subtraction. Headcount follows the same pattern: roles created for a specific initiative remain after the initiative ends. Incremental budgeting perpetuates these costs because nobody has a reason to question them. ZBB forces the question.

Post-acquisition integration. After a merger or acquisition, the combined entity almost always has duplicate functions, overlapping vendor contracts, and conflicting cost structures. A clean-sheet exercise on the combined cost base is one of the few ways to make integration savings real rather than theoretical. The alternative (asking each legacy entity to find savings within their own structure) preserves the boundaries that the acquisition was supposed to eliminate.

Restructuring under margin pressure. When a business needs to materially reduce its cost base (not trim 5%, but restructure 15-20%), incremental approaches are structurally inadequate. Asking each function to cut proportionally produces a smaller version of the same cost structure, which is rarely the right answer. ZBB forces a prioritisation exercise that incremental cuts avoid: which activities are essential, which are valuable but not essential, and which no longer justify their cost?

New business units or product lines. When a cost base is being built for the first time, ZBB is not really a methodology. It is the natural state. There is no prior-year base to increment from. Building the cost plan from first principles (what activities are needed, what resources do those activities require, what does that cost) is simply good planning. The ZBB framing helps because it provides a structured approach to the decision-package logic that new ventures need.

When ZBB Does Not Make Sense

The honest assessment is that ZBB is wrong for most businesses in most years. Three conditions make the exercise counterproductive.

Stable operations with well-understood cost drivers. If the cost structure reflects the current operating model, and the finance team already has visibility into what drives each cost line (through a driver-based model), the marginal benefit of starting from zero is low. The driver-based approach already makes costs traceable to operational decisions. ZBB adds process cost without adding proportional insight.

Small teams without dedicated planning capacity. A ZBB exercise requires significant analytical bandwidth: building decision packages, facilitating prioritisation workshops, iterating through multiple rounds of review. A finance team of three that also handles monthly close, reporting, and ad hoc analysis cannot absorb this workload without something else breaking. I have seen small teams attempt ZBB and abandon it halfway through the cycle, which is worse than not starting because it leaves the budget process incomplete.

Organisations without executive sponsorship. ZBB surfaces uncomfortable truths about cost priorities. A function that has been funded at a certain level for years may find its activity ranked below the funding line. If the CFO and CEO are not willing to act on those findings, the exercise generates frustration without generating change. The finance team spends months building a prioritised view of costs, leadership declines to make the hard calls, and the result is an incremental budget with extra steps and damaged credibility for the planning process.

The ZBB Process: Building from Zero

A well-run targeted ZBB exercise follows a consistent sequence. The specifics vary by organisation, but the logic is the same.

Step 1: Define the scope. Select the cost categories or business units that will undergo the clean-sheet exercise. The selection should be driven by where the cost structure is most likely to contain legacy inefficiency, not by where it is easiest to cut. Indirect costs (SaaS subscriptions, professional services, travel and entertainment, facilities) are common starting points because they accumulate incrementally and are rarely tied to a specific driver in the operating model.

Step 2: Build decision packages. For each activity within scope, the responsible manager builds a decision package that answers three questions. What does this activity do? What is the minimum funding level at which it can function? What incremental value does each additional tier of funding provide? The discipline here is that “we have always done this” is not a justification. The case must be made as if the activity were being proposed for the first time.

Step 3: Rank and prioritise. Leadership reviews the decision packages across functions and ranks them by strategic value. This is the step where ZBB becomes genuinely difficult because it requires comparing unlike things: is an additional analyst in FP&A more valuable than a second content marketing specialist? There is no formula for that comparison. It requires business judgement, and it requires people in the room who are willing to make trade-offs rather than protect their territory.

Step 4: Set the funding line. Based on the total budget envelope and the prioritised ranking, leadership draws a line. Activities above the line are funded. Activities below the line are not, or are funded at a reduced tier. The funded packages become the budget for those cost centres.

Step 5: Integrate with the operating budget. The ZBB outputs for the targeted categories merge with the driver-based budget for the remaining categories. The combined plan becomes the operating budget for the period.

How ZBB Complements Driver-Based Budgeting and Rolling Forecasts

ZBB is not an alternative to the planning infrastructure I described in the driver-based budgeting and rolling forecast articles. It is a different tool that solves a different problem.

Driver-based budgeting connects costs to operational decisions. It answers the question: given what the business plans to do, what should this cost? That is a visibility and traceability problem. The driver tree makes every cost line explainable in terms of the business activity that generates it.

ZBB challenges whether the activity itself should exist. It answers a prior question: should the business plan to do this at all, and at this scale? That is a prioritisation problem. The decision package forces a justification that the driver tree does not require.

Rolling forecasts keep the plan current as conditions change. They answer the question: given what we now know, what does the forward view look like? That is a currency problem. The rolling horizon prevents the plan from going stale.

The three tools work together rather than competing. A practical integration looks like this: run a targeted ZBB exercise every two to three years on selected cost categories to reset the base. Build the annual operating budget on driver-based logic, using the ZBB outputs as the starting cost structure for the relevant categories. Maintain a rolling forecast on the driver model to keep the plan connected to business reality throughout the year.

The ZBB resets the base. The driver model connects costs to activity. The rolling forecast keeps everything current. Each tool has a job, and none of them replaces the others.

Common Failure Modes

ZBB implementations fail more often than they succeed. The failures follow predictable patterns.

The exercise is too broad. Attempting full enterprise ZBB in the first year overwhelms both the finance team and the business. The analytical workload is enormous, the prioritisation conversations are politically exhausting, and the organisation runs out of energy before the process completes. Start targeted. Prove the value on a defined scope before expanding.

Decision packages lack rigour. When managers treat the decision package as a bureaucratic exercise rather than a genuine justification, the packages become descriptions of current spending dressed in ZBB language. “We need three analysts because we have always had three analysts” is not a decision package. It is incrementalism in a clean-sheet format. The finance team must challenge weak packages before they reach the ranking stage.

Leadership avoids the hard trade-offs. The ranking and funding-line step is where ZBB creates value. If leadership funds everything above a trivially low threshold, the exercise produces the same budget as an incremental approach. The willingness to defund activities that are valuable but not essential is what separates a genuine ZBB from a performance.

No follow-through on implementation. A ZBB exercise that produces a prioritised cost plan but does not result in actual cost changes (cancelled contracts, reassigned headcount, closed programmes) has consumed months of planning capacity for zero operational impact. Implementation tracking must be built into the process from the start, with named owners and deadlines for each cost action.

Doing it every year. Full ZBB every annual cycle is not sustainable for most organisations. The process cost is too high, and the incremental insight from the second consecutive clean-sheet exercise on the same cost base is minimal. The right cadence for most businesses is a targeted ZBB every two to three years, or triggered by a specific event (acquisition, restructuring, strategic pivot), with driver-based budgeting handling the years between.

Realistic Implementation Timelines

For finance teams considering a ZBB exercise, here is what the timeline actually looks like.

A targeted ZBB on indirect costs (SaaS, professional services, facilities, T&E) for a mid-sized business typically takes eight to twelve weeks from scoping to funded packages. Allow two additional weeks for integration with the broader operating budget.

A broader ZBB covering multiple cost centres and some headcount categories takes twelve to sixteen weeks and requires a dedicated project lead within the finance team. This person cannot be running the monthly close simultaneously.

A full enterprise ZBB is a five to seven month programme that requires external support (consultants or dedicated internal project team), executive sponsorship at the CEO level, and a clear mandate that the organisation will act on the findings. Attempting this without those conditions is not advisable.

In all cases, the timeline assumes that the organisation has a functioning driver-based model for the cost categories not in ZBB scope. If the underlying budgeting infrastructure does not exist, building that foundation comes first. ZBB on top of a weak planning process produces a prioritised view of costs that nobody can maintain once the exercise ends.

The Question Before the Question

Before committing to a ZBB exercise, the question worth sitting with is whether the problem you are trying to solve is a cost structure problem or a cost visibility problem.

If the business knows what it spends and why, but suspects that the cost structure no longer matches the operating model, ZBB is the right tool. The clean-sheet approach forces a conversation that incremental budgeting actively avoids.

If the business does not have clear visibility into what drives its costs, or the budget is built on historical line items without operational logic, the first step is building a driver-based model. The driver-based budgeting article covers how to construct the driver tree that makes costs traceable to decisions. Without that foundation, ZBB produces a one-time prioritisation that cannot be sustained, because there is no model infrastructure to maintain the disciplined cost base after the exercise ends.

Most businesses I have worked with need the visibility before they need the reset. Get the drivers right first. Then, when the structure genuinely needs challenging, the clean sheet has something solid to build on.

If you are weighing a ZBB exercise against other planning improvements, or thinking about how to sequence these capabilities within your finance team, I would welcome that conversation. Let’s connect.