Zero-based budgeting rebuilds the operating budget from zero rather than incrementing last year's numbers.
Zero-based budgeting (ZBB) forces every line item to be re-justified from scratch each cycle, rather than starting from the prior year and adjusting. In steady-state companies, incremental budgeting compounds small mistakes: a project funded three years ago because it seemed promising still receives funding today because nobody has questioned it. ZBB interrupts that compounding by requiring active justification for every dollar. It's most valuable at inflection points — post-fundraise strategy reset, after a leadership change, or during a runway-extension exercise — and least valuable as a permanent ritual, where it typically becomes performative.
High-value triggers: (1) new CFO or CEO wants to understand what's actually being spent and why; (2) runway needs to extend by 6+ months and traditional cost-cutting has exhausted obvious targets; (3) strategic pivot means the prior year's budget reflects a strategy you no longer pursue; (4) post-M&A integration where two budgets need to become one thoughtful budget rather than an additive frankenstein. Low-value triggers: annual planning where the strategy hasn't materially changed — you'll spend weeks producing a budget that ends up 90% similar to last year's, and burn political capital in the process.
(1) Set the target — total spend envelope, headcount cap, cash burn ceiling. Non-negotiable inputs. (2) Decompose into cost drivers — headcount by team, T&E, marketing programs, cloud spend, contractors, tooling, real estate. (3) For each driver, force a bottom-up build with a stated purpose. Team leads present: what they'd do with 80%, 100%, and 120% of last year's spend. (4) Rank all initiatives across the company by strategic priority, not by team. (5) Fund from the top of the priority list until the envelope is exhausted. (6) Communicate the cuts explicitly and why. Timeline: 4-6 weeks for a first ZBB, 2-3 weeks in subsequent years.
Consistent hit list across companies running first-time ZBB: SaaS tool sprawl (10-20% of tooling spend goes to underused licenses), duplicated contractor spend across teams, marketing programs continued past their effectiveness date, legacy infrastructure kept running for a small internal user base, T&E for events that no longer generate ROI, and organizational overhead from a headcount structure designed for a prior stage. Typical first-year ZBB savings: 8-15% of controllable spend without meaningfully reducing output.
ZBB is technically simple and politically hard. Team leads who were promised a budget last year now must re-justify it, sometimes to peers who compete for the same pool. Done clumsily, ZBB triggers a defensive-crouch response where everyone inflates estimates to protect their turf. Mitigations: transparent evaluation criteria published upfront, cross-team review sessions (not top-down cuts), explicit protection of certain 'strategic' spend from cuts to reduce anxiety, and leader modeling — the CEO or CFO taking cuts to their own function first.
ZBB is not a permanent operating model for most companies. Two years of ZBB usually exhausts the accumulated waste; year three produces marginal benefit at high organizational cost. Better long-term rhythm: annual incremental budgeting with an explicit 'zero-based challenge' to 20-30% of the budget each year (rotating which functions get the deep review), plus continuous SaaS-spend audits and periodic contractor reviews. Reserve full ZBB for actual inflection points.
Investor directory · Fundraising library · Articles A–Z · Company funding database