IT Budget Planning: A Practical Guide
How to build and manage IT budgets that support business objectives. Capital vs operational spending, cost allocation, optimisation strategies, and budget governance.
Budget components
IT budgeting is where technology strategy meets financial reality. Done well, a budget aligns spending with business priorities and gives everyone visibility into where the money goes. Done badly, it leads to overspending in some areas, chronic underfunding in others, and perpetual tension between IT and finance.
Run vs Grow vs Transform
A useful way to categorise IT spend:
- Run (60–70%): keeping the lights on. Infrastructure, support, maintenance, licensing, patching. The stuff that breaks things when you stop paying for it.
- Grow (20–25%): enhancing existing capabilities. Upgrades, new features, process improvements. Making what you have work better.
- Transform (10–15%): new capabilities entirely. Digital initiatives, innovation, new business models. The stuff that moves the business forward.
The budget trap: Many organisations spend 80% or more on "Run," leaving almost nothing for improvement and innovation. Aging systems and technical debt consume ever more budget to maintain, creating a vicious cycle where you can't invest in modernisation because you're spending everything on keeping legacy systems alive.
Capital vs operating expenditure
CapEx covers major investments: hardware purchases, perpetual software licences, custom development projects. These get depreciated over time on the balance sheet.
OpEx covers ongoing costs: SaaS subscriptions, cloud services, maintenance, support staff. Expensed in the year they're incurred.
Cloud migration shifts spend from CapEx to OpEx. This sounds like an accounting detail, but it matters. Some organisations prefer CapEx (it creates assets on the balance sheet), others prefer OpEx (more predictable cash flow, no depreciation management). Talk to your CFO before assuming one is better.
The budgeting process
Annual planning cycle
- Strategic alignment. Start with business priorities and work backward to technology implications. Not the other way around.
- Baseline establishment. Document your current run costs and already-committed spending. This is your floor.
- Initiative planning. Identify and size new initiatives that align with the strategy. Each one needs a cost estimate and a value proposition.
- Prioritisation. You won't fund everything. Rank initiatives by business value and feasibility. Involve business stakeholders in this. It's not just an IT decision.
- Budget construction. Assemble everything within the available envelope. Make the trade-offs explicit.
- Review and approval. Present to stakeholders and executives for sign-off. Make sure the constraints and trade-offs are visible.
Zero-based vs incremental
Incremental budgeting starts with last year's budget and adjusts for known changes. It's fast but perpetuates historical inefficiencies. That server nobody uses still gets funded because it was funded last year.
Zero-based budgeting justifies every line item from scratch. Thorough, but extremely time-consuming. A practical approach: do a zero-based review every 3–5 years to flush out waste, with incremental budgets in between.
Cost categories
| Category | Typical % | What's in it |
|---|---|---|
| Personnel | 35–45% | Internal staff, contractors, training, recruitment |
| Software | 20–30% | Licences, SaaS subscriptions, custom development |
| Infrastructure | 15–25% | Cloud, data centre, networking, hardware |
| Projects | 10–20% | New implementations, integrations, migrations |
| Support | 5–10% | Vendor support contracts, managed services |
Personnel and software together typically consume 55–75% of the IT budget. Everything else (infrastructure, projects, support) fights for the remainder. This is why project budgets are always squeezed.
Cost optimisation
Before asking for more budget, look for waste in what you're already spending. Common quick wins:
- Unused licences: SaaS seats that nobody's logged into for months
- Oversized cloud resources: instances running at 10% utilisation
- Duplicate tools: three project management tools across different teams
- Expired projects: test environments still running for projects that finished last year
- Support contracts for retired systems: you'd be surprised how often this happens
Strategic cost reduction
- Cloud right-sizing: match instance sizes to actual workloads, use reserved instances for predictable loads, enable auto-scaling
- Licence consolidation: fewer vendors, enterprise agreements, volume discounts
- Automation: reduce manual effort in repetitive processes (backups, provisioning, monitoring)
- Technical debt reduction: retiring legacy systems cuts their ongoing maintenance cost permanently
Budget governance
Tracking and reporting
- Monthly variance analysis: actual spend vs budget, with explanations for significant differences
- Forecast updates: revised projections based on actual spending trends
- Project cost tracking: individual initiative status and burn rates
- Trend analysis: spending patterns over time, highlighting cost creep
Change control
Budgets change. New requirements emerge, priorities shift, vendors raise prices. You need a clear process for amendments: who approves, what justification is required, and how overspends in one area get funded. Without this, the budget becomes fiction by Q2.
Business chargebacks
Allocating IT costs back to business units creates accountability but adds complexity. Options range from simple headcount-based allocation to full activity-based costing. Start simple: per-headcount or per-department splits. Add granularity later if the value justifies the administrative overhead.
Common pitfalls
- Underestimating projects. IT projects regularly exceed estimates. Build in contingency: 20–30% for well-understood projects, more for novel ones.
- Ignoring hidden costs. The software licence is just the start. Integration, training, change management, and ongoing support often cost more than the software itself.
- Shadow IT. Business units buying their own SaaS tools outside central budget visibility. You can't manage what you can't see.
- Use-it-or-lose-it mentality. Spending money in Q4 just to avoid having next year's allocation cut. This wastes resources and trains finance to distrust IT budgets.
- Ignoring inflation. Vendor price increases, salary growth, cloud cost creep. Last year's budget plus 2% isn't enough if your licences went up 8%.
Frequently asked questions
What percentage of revenue should IT spending be?
Depends on your industry. Technology companies: 10–20%. Financial services: 7–10%. Manufacturing: 2–5%. Professional services: 5–8%. These are rough benchmarks. What matters more is whether your spending is aligned with your business priorities and delivering value.
Should cloud always be OpEx?
Not necessarily. Some cloud committed use contracts can be capitalised under certain accounting standards. And some organisations prefer CapEx for tax or financial structuring reasons. This is a finance decision, not a technology decision. Involve your CFO early.
How do I justify increased IT spending?
Connect spending to business outcomes. Not "we need a new CRM" but "reducing customer response time by 40% requires a CRM upgrade, which is projected to improve retention by X%." Business cases with measurable outcomes get funded. Technology wish-lists don't.
Key takeaways
- A Run/Grow/Transform split helps balance keeping systems running with investing in improvement.
- Cloud migration shifts spend from CapEx to OpEx. Understand your finance team's preferences before committing.
- Personnel and software typically consume 55–75% of IT budgets. Everything else fights for what's left.
- The biggest pitfall: spending 80%+ on "Run" with nothing left for innovation.