Definition

Zero-based budgeting, or ZBB, builds a budget by justifying required activities and spending rather than treating the prior budget as an automatic entitlement. The analysis starts with current needs, service levels, and cost drivers, then determines the resources required to support them.

In procurement, this means challenging what the business needs before optimizing how it is purchased. The objective is a defensible requirement, not an arbitrary instruction to cut every category by the same percentage.

Separate demand decisions from price decisions

A sourcing event can obtain a competitive price for a requirement that is larger or more complex than necessary. ZBB asks whether the quantity, specification, and service level remain justified.

Should-cost analysis addresses the expected cost structure of an item or service. ZBB addresses the activity or requirement being funded, although the two approaches can work together.

VPP recommends keeping business ownership explicit. Procurement can challenge and support the analysis, but the accountable business leader must own the service and demand decision.

Rebuild the budget from drivers

Identify the factors that create the requirement. Depending on the category, these may include users, sites, transactions, operating hours, equipment, or service events.

  • Purpose: What business outcome does the spend support?
  • Demand: How much activity is justified?
  • Specification: Which features and service levels are necessary?
  • Delivery model: What internal or external arrangement fits the need?
  • Cost: What resources and prices support the chosen model?
  • Control: How will additions and exceptions be authorized during the year?

The analysis should preserve essential safety, compliance, and operating requirements. Cost challenge is not permission to remove controls without evaluating the consequences.

A hypothetical software budget

Assume a company budgets for 1,000 full-feature licenses at $400 each, or $400,000 annually. A requirement review finds that 700 users need the full feature set, 100 need a basic tier, and 200 no longer need access.

If the basic tier costs an assumed $200, the rebuilt annual requirement is $280,000 for full-feature licenses plus $20,000 for basic licenses, or $300,000 in total.

The $100,000 difference is a modeled budget opportunity. The business still needs to confirm actual usage, contractual minimums, renewal timing, migration needs, and operational consequences.

The example illustrates demand and specification changes before price negotiation. It is not a benchmark for expected savings from a ZBB program.

Avoid turning ZBB into a target-setting ritual

A preassigned reduction target can make teams negotiate the budget number instead of examining the underlying requirement. The method loses value if the answer is fixed before the evidence is reviewed.

Document assumptions and trade-offs. If a lower service level is chosen, show the consequence and who approved it rather than presenting the change as a cost-free efficiency.

Focus effort where the decision can change. Rebuilding every minor line with equal intensity can consume more management capacity than the insight justifies.

Connect approval to actual spending

An approved budget does not guarantee that contracts, ordering channels, and behavior will change. Translate the decision into supplier actions, catalog settings, authorization rules, and adoption responsibilities.

Track the difference between budget reductions, avoided future spend, and actual expense changes. Finance should validate how each outcome is reported.

Review new requests against the same drivers during the year. Otherwise, the organization may rebuild the old cost base through a series of unexamined exceptions.

Frequently asked questions

  • Does ZBB mean spending nothing? No. It means justifying the resources required for an agreed outcome.
  • Is it the same as should-cost analysis? No. One challenges the requirement and budget; the other examines the cost of a defined item or service.
  • Is a budget cut realized savings? Not automatically. Implementation and actual financial effects need separate validation.

Challenge the requirement before the rate

VPP helps teams connect demand, specification, and sourcing decisions with executable commercial actions. The objective is a justified cost base supported by operating accountability.