Zero-Based Budgeting for SaaS: What Actually Survives the Cuts

Zero-based budgeting sounds like a corporate slogan until you apply it to software. Then it becomes surgical. Every subscription your company pays for either has a business owner willing to defend it against a clean-sheet alternative, or it does not, and the cost of finding out is one clarifying week per quarter.

What is zero-based budgeting when applied to SaaS?

ZBB starts every budget line at zero and requires named justification for every dollar added back. For SaaS specifically, that means every subscription must be re-justified annually, with:

• A named business owner accountable for the outcome the tool produces.
• Documented utilization from the last 12 months.
• An alternatives analysis: what is the next best option, and at what cost?
• A spend target for the coming year, defended against a clean alternative.

Applied honestly, ZBB reveals that a meaningful share of software spend has no active defender. Nobody argues for cancellation because nobody is thinking about it; nobody argues for keeping it because the champion left. The tool renews because inertia is stronger than the review.

ZBB removes inertia as an option.

Why does incremental budgeting protect wasted spend?

Standard budgeting asks "what should change from last year?" That question is politically easy for spend increases (someone advocates for them) and politically hard for cuts (someone has to lose). The result: SaaS spend grows every year, driven by additive requests, with almost no offsetting cuts.

Three mechanics make incremental review fail on SaaS:

• The champion effect. The person who signed the contract defends it. Even when they no longer use the tool, ego and switching cost bias them toward keeping it.
• The unknown-owner problem. Some tools have no current owner. In incremental review, nobody argues for cutting them because nobody is thinking about them.
• The vendor lock-in reflex. "We already migrated onto this three years ago" becomes an argument even when the migration cost is fully sunk.

ZBB neutralizes all three by making the question "would you buy this today?" instead of "should we change what we have?"

Which SaaS categories always survive ZBB?

Some categories exit every ZBB cycle intact. If your ZBB is cutting these, you are cutting muscle, not fat.

• Identity and access management. Okta, Google Workspace, Entra. The substrate. Cutting here breaks everything else.
• Accounting and financial systems. NetSuite, QuickBooks, Xero. Regulatory floor.
• Core CRM. Salesforce, HubSpot. The single source of revenue truth.
• Core communication. Slack or Teams, plus email. Daily workspace.
• Payroll and HRIS. Payroll cannot be paused for a ZBB debate.
• Production infrastructure. AWS, GCP, Azure. Different cost discipline needed but not a cut candidate.

The pattern: substrate tools with daily usage, no alternative, and high switching cost survive.

Which SaaS categories tend to fail ZBB?

The other side of the ledger. Categories where ZBB typically identifies significant cuts.

These categories fail because they accumulate through individual signup or team-level purchases without a portfolio view. ZBB is the first time anyone looks at them as a portfolio.

How do you structure the ZBB review?

Four stages, four to six weeks total.

Stage 1: baseline (week 1). Pull the complete vendor list from AP, cards, and SSO. Rank by spend. Attach current owner (or "unassigned") to each row.

Stage 2: justification (weeks 2 to 3). Each business owner submits a written justification for every tool they own, with a target spend for the coming year. The template forces four fields: business outcome, active users (last 90 days), alternative considered, and target spend.

Stage 3: FP&A review (week 4). FP&A reads every justification and challenges any tool where target spend is above 80% of current, utilization is under 60%, or the alternative section is empty. Every challenge produces a decision: approve, reduce, or cancel.

Stage 4: vendor cycle (weeks 5 to 6). For tools approved at reduced spend, procurement or finance runs the vendor conversation. For tools canceled, the same team handles notice.

At the end of six weeks, you have next year's budget line by line, with an owner on every row and a decision on every current subscription.

What is the utilization threshold that decides fate?

Three thresholds, applied at the vendor level.

• Utilization above 70%. Renew and defend the spend. Negotiate at renewal but do not cut.
• Utilization 40 to 70%. Reduce seats or downgrade tier. Same vendor, less spend.
• Utilization under 40%. Cancel or replace. The tool is not core; the money is better spent elsewhere.

Utilization is active users in the last 90 days divided by paid seats. Not "seats provisioned" or "invited." Actual login activity.

For usage-based tools (cloud, data warehouse, API-priced services), utilization is committed capacity used. Anything with committed spend and under 60% utilization is a renegotiation target at next renewal.

How do you handle contested cuts?

Not every ZBB decision is clean. Business owners will defend tools where the utilization is low because they believe the outcome depends on the tool being available even if lightly used. Sometimes they are right.

The rubric that resolves these fairly:

1. Is there a documented outcome the tool produces? Not "we use it," but "it produces X, which drives Y."
2. What is the counterfactual cost? What breaks if we cancel? Estimate in dollars, not vibes.
3. Is the counterfactual cost bigger than the current spend? If yes, keep. If no, cut.

Most contested cuts resolve at step 2. When the business owner cannot articulate what breaks, the tool cuts. When they can, and the number is credible, the tool stays.

What happens after the first ZBB cycle?

Year one delivers the biggest savings because the accumulated waste is largest. Years two and three shift the exercise from cost reduction to portfolio discipline.

• Year 2. Expected savings 5 to 10% of prior year software spend. Focus shifts to new purchases and renewal renegotiations.
• Year 3. Expected savings 3 to 5%. ZBB becomes a discipline that keeps growth below revenue growth.
• Year 4 onward. ZBB is baseline. New tools compete against alternatives, not against inertia.

Companies that abandon ZBB after year one because "we already captured the savings" usually see spend rebound by 60 to 80% within two years. The savings are not one-time; the discipline is what compounds.

The mistake to avoid

Most finance teams introduce ZBB as a cost-cutting initiative and drop it after year one. That framing guarantees the savings do not last, because incremental review returns and inertia reasserts. The right framing is a permanent operating discipline: every subscription re-justified annually, every line item defended by a named owner, and every renewal treated as a purchase decision made fresh. The savings are real, but the durable value is the discipline. Cut once and you save once. Change how you budget and you save every year.