A Finance Director's Guide to IT Investment
IT expenditure should be transparent, predictable and connected to the capabilities the business requires. A low budget can indicate efficiency, but it can also conceal deferred projects, unmanaged risk and future cost.
For many Finance Directors, the most difficult part of assessing IT cost is establishing what the organisation is actually spending.
IT expenditure may be distributed across managed services, internal salaries, Microsoft licensing, security products, cloud services, business applications, departmental software, connectivity, hardware, projects, consultancy and ad hoc support. The total may be difficult to identify. The organisation may receive an apparently predictable monthly invoice while significant software, project and internal resource costs sit elsewhere in the accounts.
"The lowest IT cost is not necessarily evidence of good financial management."
"How much should IT cost?" is a reasonable question, but it is incomplete. A stronger question is: what should the organisation receive in return for its IT investment?
Two organisations can spend the same amount on IT and receive very different levels of value, protection and capability. The right IT budget is not the lowest possible number. It is the level of investment required to operate reliably, manage risk, control future costs and support the organisation's plans.
Technology expenditure falls into five distinct categories. An organisation may appear to have a low IT cost because it is funding only the"Run" category.
Maintains today's operations.
Run
Maintains today's operations.
Protect
Protects revenue, assets and the ability to operate.
Maintain
Prevents planned costs becoming urgent failures.
Improve
Improves productivity, margin and control.
Advance
Supports the business it wants to become.
IT expenditure can be hidden across technology budgets, departmental budgets, software subscriptions, professional services, communications, office equipment, capital expenditure, marketing systems, HR applications, finance platforms and internal salaries. Before assessing whether IT costs are appropriate, the organisation needs to know the actual total.
The managed-service invoice is not the same as the total IT budget.
A technology cost register is the most practical starting point. Each entry should capture the supplier, product or service, business owner, technical owner, number of licences, monthly or annual cost, renewal date, notice period, expected price increase, business purpose, data held, criticality, any overlapping applications and whether the item is a run or change cost.
This exercise regularly surfaces duplicate subscriptions, unused licences, unmanaged cloud resources and contracts that have auto-renewed without review. The savings from a single cost register exercise often exceed the cost of the exercise itself.
IT spend as a percentage of revenue is a widely used reference. Broad indicative ranges for UK businesses are:
A percentage benchmark cannot tell you whether expenditure is effective.
Could indicate
Or may also mean
Could indicate
Or may also mean
Broad indicative ranges only
| Sector | Indicative IT Spend | Common Cost Drivers |
|---|---|---|
| Financial Services | 7% to 10% | Regulation, cyber risk, audit, resilience and data |
| Professional Services | 5% to 7% | Secure collaboration, mobility, client data and specialist applications |
| Charities and Not-for-Profits | 3% to 5% | Cost control, donor or beneficiary data and limited internal IT resources |
| Retail and Hospitality | 3% to 5% | Ecommerce, customer data, point-of-sale systems and seasonal demand |
| Manufacturing | 3% to 5% | ERP, supply chains, sites, operational technology and production systems |
Sector benchmarks should help explain why costs differ. They should not be treated as a mandatory budget.
The following indicative figures are based on a 100-user organisation with approximately £15 million annual turnover. They represent recurring monthly IT run costs, excluding hardware and major project expenditure.
| Component | Low | Mid | High |
|---|---|---|---|
| Managed IT Services | £4,000 | £6,000 | £8,000 |
| Microsoft 365 and Core Licences | £2,000 | £3,500 | £5,000 |
| Security Tooling | £1,000 | £2,000 | £3,500 |
| Cloud, Azure and Backup | £1,500 | £3,000 | £6,000 |
| Other SaaS and Subscriptions | £500 | £1,500 | £3,000 |
| Total Monthly IT Spend | £9,000 | £16,000 | £25,500 |
| Scenario | Annual Run Rate | % of £15m Revenue |
|---|---|---|
| Low | £108,000 | 0.7% |
| Mid | £192,000 | 1.3% |
| High | £306,000 | 2.0% |
Note: These figures represent recurring operational IT costs, not the complete technology budget. They exclude hardware replacement, major migrations, transformation programmes, acquisition integration, significant security projects, new business systems, consultancy and internal IT salaries unless specifically included.
"Core monthly IT run costs are often lower than broad industry benchmarks because the benchmark also includes people, projects, hardware and change."
Benchmark your organisation and estimate an indicative level of IT investment based on your size, sector and operating requirements.
Estimate My IT BudgetDividing total annual IT expenditure by the number of supported users produces a per-user cost that is often easier to interpret than a revenue percentage. The result should then be broken down into its components: support and operations, Microsoft and licensing, security, cloud, business applications, internal employees, projects, hardware and connectivity.
A higher per-user cost may reflect stronger security, specialist applications, 24-hour operations, greater availability requirements, better support or deliberate productivity investment. A lower figure may indicate efficiency or underinvestment. Neither number is meaningful without understanding what it includes.
Total annual IT expenditure / supported users = cost per user
Combining run costs and change investment in a single IT budget line makes it difficult to understand whether the organisation is overspending on operations or underinvesting in improvement. The two categories serve different purposes and should be tracked separately.
"A low run rate does not prove that the business is adequately investing in its future."
Deferring IT investment can improve the current budget while creating larger future projects, operational risk, increased support cost, emergency expenditure, reduced employee productivity and security exposure. Common areas of deferred expenditure include ageing devices, unsupported applications, deferred infrastructure replacement, weak security controls, manual processes, end-of-support deadlines, unresolved technical debt, limited training and delayed cloud or application migration.
A costed 12 to 24-month technology roadmap is the most effective way to make deferred costs visible before they become urgent. The roadmap should support future business objectives, not only replacement and maintenance. For guidance on aligning IT planning with business strategy, see Is Your IT Strategy Supporting Your Business Strategy?
Deferred investment does not reduce the total cost of IT. It shifts it forward, often with interest in the form of emergency spend, downtime and security incidents.
A £10-per-user application for 100 employees has an apparent annual licence cost of £12,000. Its real cost may be considerably higher once implementation, configuration, integration, data migration, security review, support, training, administration, compliance, reporting, business continuity, specialist knowledge and exit or replacement cost are included.
Software should be selected only after the required capability, process, data and ownership have been defined. For a practical framework on avoiding common software selection mistakes, see Why Software Selection Fails and How to Get It Right.
The strongest technology investments support both growth and operational efficiency. For a detailed view of how technology can improve both the top and bottom line, see How Technology Can Improve Revenue and Profitability.
Cost reductions may affect monitoring, backup, security remediation, identity controls, resilience, specialist expertise, supported software, regulatory evidence and business continuity. Before removing any control, the annual cost of the control should be weighed against the likelihood and financial impact of the risk it reduces.
Not every risk requires the most expensive possible control. Investment should be proportionate to business exposure, data sensitivity, regulation, customer requirements, risk tolerance and operational dependence on technology.
Annual cost of the control
What it costs to maintain
Likelihood x financial impact of the risk it reduces
What it would cost if removed
The complete IT cost is visible and major categories can be explained.
Renewals, projects, lifecycle expenditure and price changes are forecast.
Every important system, service, risk and project has an owner.
Controls reflect the organisation's risks and obligations.
Licences, contracts, cloud use and suppliers are actively managed.
Expected expenditure over the next 12 to 24 months is understood.
Projects have defined benefits connected to productivity, risk, growth or profitability.
Recurring problems and unnecessary complexity are reduced over time.
Technology investment supports the organisation's strategic priorities.
Do we know the complete cost of IT?
Does the total include internal employees and departmental software?
Can every significant subscription be explained?
Are we paying for overlapping products?
Are purchased licences being used?
Are renewal dates and notice periods centrally recorded?
Are run costs separated from change investment?
Is there a costed 12 to 24-month roadmap?
Are future hardware and software lifecycle costs visible?
Would proposed savings reduce security, resilience or support?
Are technology projects producing their intended benefits?
Can the current environment support the business plan?
Are software purchases assessed using total cost of ownership?
Are cloud costs monitored and explained?
Are unexpected costs genuinely unexpected, or were they simply not identified early enough?
Wavex provides fully managed and co-managed IT services designed to give clients clear recurring service costs, costed technology roadmaps, fixed-fee pre-scoped projects, commercial and operational reporting, asset and lifecycle visibility, security and risk reporting, licensing oversight, proactive service improvement, strategic planning and support for internal IT teams.
"The objective is not simply to minimise expenditure. It is to ensure that IT costs are deliberate, understandable and connected to the capabilities the organisation requires."
A practical framework for aligning technology investment with business objectives, growth plans and risk appetite.
Read articleThere is no universal IT budget. Expenditure depends on size, sector, risk, complexity, operating model, regulation, growth plans and dependence on technology. Percentage-of-revenue and per-user benchmarks are useful starting points, but neither demonstrates value.
The more useful questions are:
Can the organisation operate reliably?
Is it appropriately protected?
Are costs transparent and predictable?
Can technology support the organisation's future plans?
"The objective is to invest the right amount, in the right capabilities, at the right time."
"Does our IT investment provide the visibility, protection and capability the business needs, at a cost we can understand and control?"
Speak with a sector specialist. No sales pitch - just an honest conversation about your IT challenges and how we can help.