Zero-based budgeting: why your company should consider (and when not).

"Let's do zero-based budgeting" became corporate jargon in recent years. Almost always said without understanding what the method actually is, or when it adds — and when it destroys value. This article is the honest defense of zero-based budgeting (ZBB), with the caveats that usually get left out of the famous cases.

What zero-based budgeting actually is, in practice

Traditional budgeting starts from prior year. You take each category's expense, adjust for inflation, add margin for new projects, and close the budget. It's fast, simple, and has one defect: it perpetuates everything that exists, efficient or not.

ZBB is the opposite. Every cent of the budget starts at zero. To be approved, any cost needs to be justified by the value it delivers. It doesn't matter if the expense existed before — it only survives if defended in current context.

The classic example: company spends R$ 200k/year on software subscriptions. In traditional budgeting, this becomes "IT: R$ 220k (inflation adjustment)". In ZBB, each license is evaluated individually. Who uses it? How frequently? What value does it deliver? The final number could be R$ 130k, R$ 200k or R$ 280k — but it's defended.

Why it became famous

3G Capital bought large companies (Anheuser-Busch, Heinz, Burger King, Kraft) and applied ZBB systematically. Results were drastic: EBITDA margins rose double digits in few years, administrative expenses fell 30-40%, cash generation exploded.

The method became benchmark. Consulting firms started selling it. Companies started applying it. And here begins the problem.

Why many implementations fail

ZBB applied with wrong metric becomes value destruction. The three most common errors:

1. Confusing ZBB with "cut everything"

The method doesn't say to cut. It says to justify. If an expense delivers real value (sales, retention, operational efficiency), it passes. Cutting expense without understanding consequence is the opposite of ZBB — it's just blind economy.

Companies that drastically reduced marketing, R&D or training investment "because of ZBB" generally paid dearly 18-24 months later. ZBB demands analysis, not shortcut.

2. Applying every year

ZBB is expensive in management time. Justifying every cent from scratch yearly consumes 3-5x more hours than traditional budgeting. Yearly application creates organizational fatigue, generates superficial re-approvals and loses effect.

Correct model: deep ZBB every 2-3 years, with annual reviews on approved numbers. 3G applies intensely in first 12-18 months post-acquisition, then maintains discipline without redoing everything.

3. Applying only to expense, not revenue

Famous ZBB is known as cost-cutting tool, but the method applies equally to revenue. Each revenue line deserves questioning: is this product/service still strategic? Is this customer profitable? Does this sales channel generate the right ROI?

Companies applying ZBB only on expense side optimize cost of an operation that might need strategic rethinking. It's possible to have best-possible cost for a product that shouldn't exist anymore.

Well-applied ZBB is a strategic clarity exercise disguised as budgetary exercise. Poorly applied, it's just dumb expense compression.

When ZBB makes sense for your company

These are contexts where we seriously recommend it:

• Company in transformation or turnaround. When there's clarity that status quo must change, ZBB forces the strategic conversation.
• Leadership change or shareholder control change. New CEO or new investor needs to understand the company from zero — ZBB accelerates that process.
• Intense competitive pressure compressing margin. When maintaining "the way we always did" isn't viable anymore, ZBB helps identify where money can be reallocated.
• Company in fast growth where expense grows more than revenue. Sign that operation accumulated inefficiencies during the rush.
• Preparation for fundraising or sale. Investors value companies with audited and justified cost structure.

When ZBB does NOT make sense

Equally important to know when to avoid:

• Company in explosive revenue growth phase, where priority is capturing market, not optimizing expense. Applying ZBB in middle of expansion can pull fuel from the engine.
• Companies with still-immature management culture. ZBB demands analytical discipline. If company doesn't even have reliable expense data by category, ZBB becomes bureaucratic theater.
• Operations with high seasonality or volatility. When comparison base changes too much year-to-year, "starting from zero" loses useful reference.
• Small teams with managers stacked across multiple functions. ZBB consumes a lot of management time. In SMEs without dedicated CFO or Controller, better to start with well-done traditional revision.

How to apply ZBB in an SME — practical version

Full ZBB like 3G Capital's takes months of work and dedicated team. For SMEs, there's a simplified version that works:

Phase 1 — Mapping (4-6 weeks)

List ALL expense from past 12 months, categorize by area and type. Required detail level is granular: not enough to know "marketing R$ 480k", need to know each campaign, each agency, each tool, each freelancer. This is where most companies discover they don't have data — and work begins with the basics.

Phase 2 — Justification (6-8 weeks)

For each significant expense (rule of thumb: top 80% of total), responsible manager needs to answer three questions: what value does this expense deliver? How would you measure that value? What would happen if expense were cut in half?

This phase generates most of the real value. Answers reveal invisible inefficiencies in traditional budgeting.

Phase 3 — Approval by tier (2-4 weeks)

Each expense classified in three tiers: essential (keeps), discretionary (cuts 20-30%), questionable (eliminates or substitutes). Leadership decides case by case, based on justifications.

Phase 4 — Monitoring (continuous)

Approved budget becomes living tool. Monthly comparisons between budgeted and actual on automated dashboard, alerts for significant deviations, lightweight quarterly review.

Typical result

In ZBB projects we conducted, average operational expense reduction is 12-22%. Not homogeneous compression — redistribution. Some categories rise (because they deliver more value than imagined), others fall drastically (because they were inertial).

But the most valuable effect is usually cultural. Team that went through the process starts thinking differently about expense. "Why this?" becomes default question. Financial discipline stops being CFO's theme and becomes distributed asset.

One last caveat

ZBB isn't a miracle recipe. Applied with discipline and context, it's powerful. Applied by fashion or pressure without preparation, it's destructive. The question shouldn't be "should we apply ZBB?" — should be "what strategic problem would ZBB solve, and are we ready for that conversation?".

If the answer is "we have out-of-control expense and want to see where money goes", ZBB serves. If it's "we want to look modern to the board", there are cheaper tools.