What Is Zero-Based IT Budgeting and How Do You Rebuild Your IT Budget From Zero?

The short answer

Zero-based IT budgeting rebuilds the technology budget from nothing, so every licence, contract, service and role must be justified against what the business needs now rather than what it spent last year. It is the most effective way to flush out legacy costs that incremental budgeting quietly carries forward. It works best with a complete spend inventory, clear funding tiers and protection for security and critical systems.

Why traditional IT budgets drift

Most IT budgets are built incrementally: take last year's actuals, add an inflation factor, add new projects, trim if needed. The problem is that every past decision becomes permanent by default. A platform bought for a project five years ago, a support contract for a system already retired, extra storage provisioned for a migration, all roll into next year's baseline unless someone actively removes them.

Over time the budget reflects the history of the organisation rather than its current strategy. Zero-based budgeting resets that.

Incremental versus zero-based budgeting

When does zero-based IT budgeting make sense?

It is particularly useful when:

• Technology spend has grown faster than the business and nobody can fully explain why.
• The organisation has been through an acquisition, restructure or major system change.
• A new CEO, CFO or CIO wants a clear baseline.
• Trading conditions require a substantial, defensible reduction.
• Technology bought by departments sits outside central visibility.

It is less useful as an annual ritual in a well-governed environment, where it may cost more effort than it saves.

Step 1: Build a complete inventory

Zero-based does not mean starting with no information. Gather every technology cost from the ledger, accounts payable, corporate cards and departmental budgets: people, contractors, managed services, software, cloud, hardware, telecommunications and projects. For each item, capture the owner, contract terms, renewal date and usage data.

Step 2: Define the services IT provides

Group costs into services the business recognises, such as end-user computing, finance systems, customer platforms, collaboration, security and data. Budgeting by service makes it easier to ask whether each one is worth what it costs.

Step 3: Classify every cost line

Use simple, agreed tiers:

1. Mandatory. Required by law, regulation or contract, such as record retention, privacy obligations and security controls expected by your regulators or insurers.
2. Essential to operate. Systems the business cannot run without, at the minimum viable level of service.
3. Improvement. Spend that raises service levels, productivity or resilience above the minimum.
4. Discretionary or growth. New capabilities and projects that support strategic goals.

Each tier needs its own justification, and higher tiers should show a clear benefit.

Step 4: Challenge each line

For every cost, ask:

• Do we still need this at all?
• Do we need this much of it, at this service level?
• Is there a cheaper way to deliver the same outcome, such as a capability we already license?
• Is the price competitive, and when can we renegotiate?
• What happens if we stop?

Usage data should drive answers wherever possible. Licence and subscription costs in particular benefit from the approach in our SaaS licence optimisation guide.

Step 5: Fund by priority

Fund mandatory and essential tiers first, then allocate the remaining budget to improvement and discretionary items ranked by business value. This produces a budget that can be explained line by line and adjusted quickly if conditions change, because everyone knows which items sit at the bottom of the list.

Step 6: Lock in the governance

The budget is only as good as the controls that follow it. Assign owners to every service, review actuals against budget monthly, require approval for new technology purchases, and maintain a renewal calendar so contract decisions happen on time.

Common pitfalls to avoid

• Cutting maintenance and security to hit a number. Deferred patching, unsupported systems and lapsed security tools create larger costs later. Treat core security as mandatory.
• Ignoring contract realities. Some costs cannot be removed until a contract ends; record the earliest exit date and plan for it.
• Underestimating effort. The first zero-based cycle takes real work, mostly in the inventory. Start early.
• Turning it into a contest. If business owners feel they must defend every dollar against IT, the process stalls. Frame it as a shared review of value.
• Never repeating it. A lighter refresh every few years, or a zero-based review of the largest categories each year, keeps the baseline honest.

How this fits with your broader budget

Zero-based budgeting sets the baseline; it does not replace planning. Once you have a defensible number, our IT budget planning guide covers building the forward plan, and how much should a business spend on IT helps you judge whether the result is right for your industry and strategy.

How The Technology Office rebuilds IT budgets

The Technology Office runs zero-based IT budget reviews as an independent, CIO-level partner to the CFO and executive team. We build the complete spend inventory, including technology outside the IT budget, classify every line against clear funding tiers, and link each recommended change to a specific contract, licence or service. We have no products to sell and no resale margins, so the only aim is a budget that is lean, defensible and aligned to your strategy.

Security and critical systems are protected as a non-negotiable tier in every review. We work with businesses of any size and industry across Australia, typically through our IT cost optimisation service, with fractional CIO support available to embed the governance afterwards.