Zero-based Budgeting

1. What Is Zero-based Budgeting?

Zero-based Budgeting (ZBB) is a budgeting approach that starts from a “clean sheet” each cycle—every dollar of spend must be justified from zero against strategic priorities, service levels, and the most efficient way to deliver them. Unlike traditional incremental budgeting (“last year plus/minus X%”), ZBB rebuilds the budget from activities and needs, not history, using transparent cost drivers and explicit choices on service levels and standards.

In plain terms: ZBB forces you to ask “If we were starting today, what would we spend—and why?” It makes costs visible at a granular level (e.g., per user, per trip, per campaign, per facility square foot), links them to purpose and outcomes, and empowers leaders to reallocate from low-value activities to the highest-impact priorities. Done well, ZBB is not a blunt cost-cut—it is a value and growth reallocation engine.

Executives and consultants use ZBB to reset structural costs, fund growth, standardize service levels, and install continuous cost governance. It is especially effective when paired with category management, should-cost/clean-sheeting, and digital spend analytics.

2. Origin and Background

ZBB was introduced in the public sector in the 1970s (notably by Texas Instruments’ Peter Pyhrr) and adopted by corporations in later decades, with periodic waves of interest during cost cycles. Many firms now use “ZBB 2.0” or “ZBx” (zero-based everything)—an evolved, digital form that embeds driver-based costs, standard service tiers, and ongoing governance rather than a one-off reset.

Why it was created: incremental budgets entrench legacy spend, duplicate activities across silos, and underfund new priorities. ZBB addressed this by tying spend to current strategy and service needs, and by using activity/volume × unit-cost math to challenge the baseline.

How it became known: through corporate transformations, private equity playbooks, and consumer/industrial case examples showing substantial SG&A savings and reinvestment. Recent practice combines ZBB with procurement category management, shared services, and automation.

3. How Zero-based Budgeting Works

ZBB replaces “last year’s baseline” with a structured rebuild anchored in activities, service levels, and cost drivers.

Core elements

• Spend taxonomy and owners: A common set of categories (e.g., marketing, travel, facilities, IT, professional services, fleet, logistics, maintenance) with accountable “cost category owners.”
• Activity-based baselines: Define what the budget buys (e.g., “number of events,” “users supported,” “ad impressions,” “square feet maintained,” “tickets resolved,” “miles driven”). Build baseline = volume × unit cost for each activity.
• Service levels & standards: Explicit tiers (e.g., travel class rules, facility cleaning frequencies, IT device standards, customer support SLAs) with cost/experience trade-offs visible.
• Challenge process: Cross-functional reviews test necessity (“stop”), efficiency (“do cheaper”), and effectiveness (“do differently”) using benchmarks, should-costs, automation, and make/buy choices.
• Decision packs (“decision packages”): Each category presents options—e.g., Bronze/Silver/Gold service—with costs, risks, and benefits. Leaders choose the target tier and approve initiatives to reach it.
• Reallocation: A portion of released funds is redirected to growth, capability, or resilience investments, not just to the bottom line.
• Governance and cadence: Monthly spend reviews, variance analysis vs. drivers, and a quarterly refresh of volumes and unit costs keep ZBB alive (ZBx).

Math that underpins ZBB

• Baseline from zero: Demand (volumes) × standard (service level) × unit cost (best source) = justified spend.
• Savings sources: Demand management (fewer units), spec simplification (lower standard), sourcing (lower unit cost), process/automation (fewer hours), organization design (spans/layers), footprint (facilities/transport).
• Reinvestment logic: Pre-agreed share (e.g., 40–60%) of sustainable savings funds priority growth or capability initiatives.

What changes in “ZBB 2.0”

• Digital spend towers, near-real-time dashboards, and benchmarks (internal/external).
• Driver-based budgets integrated with FP&A (not Excel-only campaigns).
• Category owner roles, playbooks, and “control towers” for ongoing governance.
• Integration with procurement, shared services, and automation to lock in run-rate benefits.

4. When to Use Zero-based Budgeting

Most helpful for:

• Structural cost reset: SG&A has crept up; inflation and complexity outpaced productivity.
• Funding growth: Need to self-fund digital, data, product, or go-to-market investments.
• Post-merger integration: Normalize service levels and eliminate duplicate activities.
• Operating model shifts: Move to shared services, standardize tooling, rationalize vendor/asset footprints.

Especially powerful when:

• Leadership commits to reinvest a share of savings; not just cost cutting.
• Data exists to build drivers (volumes, unit costs) and link spend to service levels.
• Procurement, FP&A, and business owners are aligned around category ownership.

Less effective or potentially misleading when:

• Run as a one-off “slash and burn” without service-level clarity—quality and growth suffer.
• Applied mechanically where outputs are highly uncertain (e.g., innovation portfolios) without outcome-based guardrails.
• Done on spreadsheets in isolation from FP&A systems—benefits fade.

Practice evolution: Many organizations treat ZBB as a standing capability (ZBx), embedded in FP&A, procurement, and operating reviews, often combined with OKRs and value driver trees.

5. How to Apply Zero-based Budgeting: Step-by-Step

1. Set ambition, scope, and guardrails

   Define targeted run-rate impact (e.g., 10–20% addressable SG&A), reinvestment share (e.g., 40–60%), scope (corporate, functions, business units), and exclusions (e.g., regulatory, safety). Align on principles (customer experience must not degrade; savings must be sustainable).

2. Create the spend taxonomy and assign owners

   Agree “spend towers” (e.g., Marketing, T&E, Facilities, IT, Logistics, Professional Services, HR, Finance, Legal, Fleet, Real Estate). Appoint accountable category owners (business leaders, not just procurement). Establish a program “control tower.”

3. Build a driver-based baseline from zero

   For each tower, document activities, volumes, unit costs, and service levels. Examples:

   • Facilities: square feet × cleaning frequency × $ per clean; utilities by kWh × rate; security posts × $ per post.
   • Marketing: planned impressions/campaigns/events × $ per unit; agency FTEs × rate; production units × $/asset.
   • IT: devices × $ per device (lifecycle), licenses × $ per seat, tickets × $ per ticket (by severity), environments × $/month.
   • T&E: trips × route class policy × $ per trip; hotel nights × caps; per diem.

   Validate with invoices, contracts, GL, and operational systems; reconcile to financials.

4. Define service tiers and decision packages

   Propose Bronze/Silver/Gold service levels with quantified cost/benefit (e.g., device refresh every 5 vs. 3 years; cleaning 3× vs. 5× weekly; in-house vs. agency mix). Prepare “stop/shift/simplify” options and risk notes.

5. Challenge and choose

   Run cross-functional challenge sessions. Use benchmarks (internal/external), should-cost/clean-sheet models, and automation potential (RPA, AI) to pressure-test. Executive committee selects target service levels and approves initiatives with owners and timelines.

6. Translate into initiatives and a funded plan

   Convert choices into initiatives: policy changes (e.g., travel class < 6 hours = economy), vendor RFPs, consolidation (facilities, tools), process redesign (shared services), automation, org changes (spans/layers). Sequence in waves (0–3, 3–9, 9–18 months). Fund growth with the reinvestment share.

7. Embed governance and tracking

   Stand up monthly “tower reviews” (owner, FP&A, procurement) to track KPIs: spend vs. driver-based budget, initiative delivery, unit costs, service levels (SLAs), and realized P&L impact. Use a benefits-realization tracker with finance sign-off.

8. Integrate with FP&A and operating rhythms

   Load driver-based budgets into planning tools; refresh volumes quarterly; lock standard service levels as policy. Tie OKRs and incentives of tower owners to sustainable savings and service outcomes (not one-off cuts).

9. Manage change and risks

   Communicate the “why,” reinvestment story, and service-level implications. Provide playbooks/scripts for policy changes (e.g., T&E, device, events). Monitor customer/employee NPS where changes touch experience; stage gates to correct if quality dips.

10. Continuous improvement (ZBx)

    Quarterly: re-benchmark unit costs, revalidate volumes and standards, identify further automation/vendor opportunities, and sunset temporary controls. Annual: rerun challenge sessions on rotating towers.

6. Example: Zero-based Budgeting in Action

Context: “BrightHome,” a $4.2B global consumer durables company, saw SG&A rise from 21% to 25% of sales amid channel expansion and inflation. Growth investments were underfunded. The CEO launched a ZBB program across corporate and commercial functions with a 15% addressable SG&A ambition and a commitment to reinvest 50% of sustainable savings into digital growth and service.

Approach

• Scope: Marketing, Sales support, T&E, Facilities/Real Estate, IT, Professional Services, HR, Finance, Logistics overhead. Supply chain variable spend addressed via separate design-to-value/procurement program.
• Baseline: Driver-based model: events/activations, media impressions, agency hours; trips and hotel nights; sq.ft. and cleaning standards; devices/licenses/tickets; legal/advisory hours; fleet size/miles; security posts.
• Challenge: Service tiers defined for each tower. External benchmarks used for agency rates, facilities $/sq.ft., IT helpdesk $/ticket; clean-sheet of marketing production; lease consolidation via hybrid work.

Decisions

• Marketing: Shift 20% spend from high-cost events to digital with clearer ROI; consolidate agencies from 14 to 5; in-house part of creative; standardize production specs.
• Facilities/Real estate: Reduce footprint −18% via hub-and-spoke and flexible seating; cleaning from 5× to 3× weekly in non-customer areas with NPS monitoring.
• IT: Standardize devices; extend refresh from 3 to 4.5 years; renegotiate SaaS licenses; move helpdesk Tier 1 to a shared service; automate password resets.
• T&E: Travel class policy tightened; virtual-first for internal meetings; negotiated hotel caps by city tier.
• Professional services: Introduce rate cards and panel firms; require business case for non-panel engagements; knowledge reuse library.

Outcomes (12 months)

• Savings: Addressable SG&A −13.8% (annualized $128m); 52% reinvested in e-commerce, data/analytics, and service network upgrades; net P&L benefit $61m.
• Service levels: Employee IT satisfaction +4 pts; helpdesk cost/ticket −27%; marketing ROI improved (digital CPA −19%); no material dip in customer NPS; facilities complaints transient then normalized.
• Sustainability: 11 buildings exited; energy use −14%; travel emissions −22% vs. baseline.
• Governance: Installed monthly tower reviews and a spend control tower; benefits tracked and signed off by finance.

What made it work: executive sponsorship, reinvestment commitment, driver-based transparency, clear service tiers, and integration with procurement and FP&A. The narrative emphasized “funding growth,” not “across-the-board cuts.”

7. Strengths and Limitations

Strengths

• Strategic reallocation: Frees up funds to invest in growth and capabilities.
• Transparency: Makes spend drivers and service levels visible and debatable.
• Ownership and accountability: Category owners and tower reviews create clear responsibility.
• Sustainability: Designed as an ongoing capability (ZBx), not a one-off event; savings stick.

Limitations

• Data and effort: Requires building driver-based baselines and reliable dashboards.
• Behavioral risk: If framed as a cut-only exercise, it erodes trust and undermines growth.
• Quality risk: Poorly defined service tiers can degrade customer/employee experience.
• Complexity: Too many categories, exceptions, and bespoke rules can create bureaucracy.

8. Common Pitfalls (and How to Avoid Them)

• Across-the-board cuts
  What goes wrong: “Take 10% out of everything” ignores priorities; harm to growth and quality.
  How to avoid: Anchor in strategy and service tiers; reallocate, don’t amputate.
• Accounting exercise, not operating change
  What goes wrong: Spreadsheets re-label spend without changing how work is done.
  How to avoid: Pair ZBB with procurement, process redesign, automation, and policy changes; assign owners.
• One-and-done campaign
  What goes wrong: Savings fade as behaviors revert.
  How to avoid: Install ZBx governance—monthly tower reviews, driver dashboards, policy enforcement.
• False precision
  What goes wrong: Weeks lost debating minor rates; momentum stalls.
  How to avoid: 70–80% accuracy is enough to choose; refine after decisions land.
• Hidden demand and shadow budgets
  What goes wrong: Spend shifts off-books (corporate cards, project codes).
  How to avoid: Tighten policies, consolidate channels, and integrate data sources; audit exceptions.
• No reinvestment story
  What goes wrong: Organization resists; talent disengages.
  How to avoid: Pre-commit to reinvest a share in growth/capabilities and communicate wins.
• Ignoring outcomes and experience
  What goes wrong: Savings at the expense of customer/employee NPS.
  How to avoid: Monitor SLAs and NPS; use guardrails and staged rollouts.
• Underpowered governance
  What goes wrong: Decisions drift; exceptions proliferate.
  How to avoid: Clear decision rights, approval matrices, and a control tower with FP&A/procurement.

9. How Zero-based Budgeting Relates to Other Frameworks

• Value Driver Trees (VDT): ZBB uses driver-based logic (volumes × unit costs). VDTs connect those drivers to EBITDA/FCF; use VDTs to size and prioritize ZBB initiatives.
• Activity-Based Costing / TDABC: Provide the measurement backbone for ZBB’s activity costs and service levels.
• Should-cost / Clean-sheeting & Design-to-Value: Techniques to set efficient unit costs and redesign specs; core to ZBB challenge sessions.
• Operating Model 4D / 7S / Star Model: ZBB decisions (service levels, sourcing, shared services) must align with structure, processes, and governance.
• Procurement Category Management: Executes sourcing levers and vendor rationalization that ZBB identifies.
• Balanced Scorecard & OKRs: Use BSC to keep a balanced view (customer/employee outcomes); use OKRs to deliver ZBB initiatives reliably each quarter.
• ROIC / EVA / CFROI: ZBB improves NOPAT and reduces invested capital needs (e.g., facilities, inventory support), lifting returns above WACC.
• Beyond Budgeting / Rolling Forecasts: ZBB’s clean-sheet discipline complements dynamic planning; combine for agility with cost rigor.

10. Key Takeaways

• Zero-based Budgeting rebuilds spend from zero using activities, service tiers, and cost drivers—not last year’s baseline.
• It is a reallocation engine: free up funds from low-value spend to fuel growth and capabilities.
• Success requires category ownership, driver-based baselines, clear service levels, and tight governance (ZBx).
• Avoid blunt cuts and bureaucracy; pair ZBB with procurement, process redesign, and automation to make savings stick.
• Integrate ZBB with FP&A, VDTs, OKRs, and operating model frameworks to sustain performance and protect customer/employee experience.

11. FAQs About Zero-based Budgeting

Is ZBB just cost cutting?
No. Cutting is a by-product. ZBB is about reallocation—stopping low-value spend, resetting service levels, sourcing efficiently, and funding growth. The best programs pre-commit to reinvest a share of savings.

How long does a ZBB program take?
A focused first wave (major SG&A towers) can deliver in 8–12 weeks from kickoff to approved plan, with 6–12 months to realize savings and embed governance. Treat it as a capability (ZBx), not a one-time project.

What savings are typical?
Context-dependent, but 10–20% of addressable SG&A is common in first cycles when complexity has built up; 3–5% annually from ongoing governance. Indirect procurement and facilities/real estate often yield early wins.

How do we avoid bureaucracy?
Keep the taxonomy pragmatic, focus on the biggest towers, standardize a few service tiers, and automate driver dashboards. Aim for 70–80% accuracy; don’t let perfect be the enemy of done.

How is ZBB different from traditional budgeting?
Traditional budgets start from last year and adjust. ZBB starts from strategy and service levels, builds volumes × unit costs, and requires explicit choices for each category. It links spend to outcomes, not history.

Which functions are best suited?
SG&A and indirects (marketing, T&E, facilities, IT, professional services, HR, finance, legal) are prime. Operations benefit too via should-cost and design-to-value, but production costs are often addressed through other methods in parallel.

What tools do we need?
Start with a robust data model (GL, invoices, contracts) and BI dashboards. As you scale, integrate driver-based planning into FP&A and deploy spend analytics, benchmarks, and workflow for approvals and policy enforcement.

How do we handle inflation?
Use ZBB to separate inflation (unit cost changes) from demand and standards. Offset inflation via spec simplification, sourcing, and productivity; pass-through pricing where strategy allows. Refresh unit costs quarterly.

How do we prevent “salami slicing” and quality erosion?
Decide at the service-tier level, not line-by-line cuts. Monitor SLAs/NPS; stage changes; reverse if quality dips. Keep a balanced scorecard alongside cost KPIs.

Will ZBB demotivate teams?
It can if framed as cuts. Anchor the narrative on funding strategy, empower category owners, and invest some savings in tools/training that make work better. Celebrate reinvestments visibly.