Zero-based budgeting (ZBB) is a budgeting method in which each budget is built from zero for the coming period. Instead of taking last year’s spending and adjusting it up or down, every cost has to be justified by what it delivers. Applied to IT, that means asking for each application, license, circuit, contract, cloud service and team: do we still need this, at this level, from this provider, at this price? ZBB is often used as a cost-reset tool, and it works best when it is backed by good spend data.
At a glance
- Each cost is justified from scratch, rather than inherited from last year’s budget.
- In IT, it tends to surface unused licenses, duplicate tools, idle services and legacy circuits.
- It takes more time and data than incremental budgeting.
- Many organizations apply it selectively or on a rotating cycle.
- Contracts limit how fast savings arrive, so renewal dates shape the plan.
What problem it solves
Traditional incremental budgeting starts from what was spent last year and adds or subtracts a percentage. In IT that tends to lock in spending that no longer earns its place: software renewed automatically, lines and circuits kept after a site closed, overlapping tools bought by different teams, and services sized for needs that have changed. Each item is small, so nobody asks why it is there.
Zero-based budgeting reverses the burden of proof. Each cost owner has to explain what a cost delivers and why it is needed at that level. That often reveals spending that can be cut, consolidated or renegotiated, and frees money for new priorities without simply raising the overall budget. It also gives finance leaders a clearer view of what IT spending supports.
How it works
Build the inventory. List IT costs by vendor, service, contract and owner: software and SaaS, cloud, network and voice services, hardware, support contracts, outsourcing and staff. Tools for software asset management and telecom expense data help here.
Group into decision units. Organize costs around business services or functions, such as collaboration, customer support or a particular application, so they can be judged by what they deliver.
Justify each unit. Owners describe what the service does, who uses it, what would happen without it, and options at different levels of service and cost.
Rank and fund. Leaders rank options against business priorities and fund the ones that make the cut. Total cost of ownership (TCO) and price benchmarking help test whether costs are reasonable.
Plan around contracts. Where a cost is committed under a contract, ZBB usually records it as fixed until the next renewal or exit point and plans what to do then. Exit and renewal terms vary, so check them with counsel before assuming a cost can be removed.
Sustain it. Chargeback and showback and cloud FinOps practices help keep costs visible after the exercise.
When it matters for buyers
- A new CFO or a cost target. ZBB is a common response when leadership wants spending reset rather than trimmed.
- Vendor sprawl. Years of team-by-team buying leave duplicate tools that ZBB tends to expose. A SaaS management platform can give the usage data to back those decisions.
- Mergers and downsizing. Changes in size or structure make last year’s budget a poor guide.
- Before major renewals. Starting a zero-based review a few months before big contracts renew gives time to negotiate or switch.
- Funding new projects. It can free money for new initiatives from within the existing budget.
Questions to ask vendors
- Can you provide usage data for every license, line or service we pay for?
- Which of our services are under a commitment, and when can each be reduced or ended?
- What would a lower service tier or smaller quantity cost, and what would we lose?
- Are there services we pay for that overlap with others in your portfolio or ours?
- What would it cost to consolidate several of our services with you?
- What notice do you need for reductions at renewal?
How it differs from IT financial management
IT financial management (ITFM) is the ongoing discipline of planning, tracking, allocating and optimizing IT spending throughout the year. Zero-based budgeting is a specific method for setting the budget at the start of a period. An organization can run ITFM with incremental budgeting, or use ZBB as part of its ITFM practice. ITFM supplies the cost data and allocation that make ZBB workable; ZBB is one of several ways to use that data to decide what to fund.