- No single share of revenue shows whether you over- or under-invest in IT; sector, size, technology intensity and what you count all change the figure
- A benchmark is a reference point for comparison with similar organisations, not a minimum budget
- Use mutually exclusive accounting categories, then tag security, compliance and innovation as a separate view so nothing is counted twice
- Refresh cycles of 4 to 5 years for laptops and 5 to 7 years for servers are starting assumptions, adjusted for vendor support, workload and cost
- A three-year forecast that separates recurring costs, planned replacements and projects is easier to defend than a single annual figure
Why IT budgets often fall short
Many smaller organisations treat IT spending as reactive. Hardware fails and gets replaced. Software licences auto-renew. A new hire needs a laptop. Nobody adds these costs up, nobody plans for the cycle, and nobody asks whether the spending matches what the business actually needs.
The result is often too little investment in prevention, combined with unpredictable spikes when things fail. A single serious incident can cost more than several years of planned maintenance, but that comparison stays invisible until something breaks.
Security tooling, monitoring and proactive maintenance also produce no visible return in a normal year. The return appears only when something bad does not happen, which nobody notices. That makes IT budgets an easy target for cuts until a breach, a ransomware attack or a long outage changes the conversation.
What share of revenue should go to IT?
There is no reliable single answer. Published figures for IT spend as a percentage of revenue vary widely and are hard to compare, because they depend on factors that differ between organisations:
- Sector and business model. An online retailer or software company depends on technology to deliver its product; a construction firm may use it mainly for administration.
- Size. Fixed costs such as security tooling, support and core systems are spread over fewer people in a small business.
- Technology intensity. The number of users, devices, specialist systems and integrations.
- What is counted. Whether the figure includes internal IT salaries, technology embedded in operations (machines, tills, clinical devices), outsourced services and annualised capital spend.
- Software producers versus consumers. A company that builds software for sale books much of its development as technology cost; a company that only uses software does not.
A revenue percentage on its own therefore cannot show whether you are over- or under-investing. A more useful starting point is what your business model depends on, which obligations apply and what drives the cost.
If you compare your spend with published figures or with peers, treat the result as a reference point, not a floor your budget must reach and not a target. Compare with organisations of similar size, sector and operating model, check that both figures count the same costs, and then investigate the differences. A gap may point to a real shortfall, a deliberate choice or simply a different way of counting.
Which costs belong in the IT budget?
Start with accounting categories in which every cost appears once and only once. A typical structure:
- Devices and hardware. Laptops, desktops, phones, servers, network equipment and peripherals, bought or leased.
- Software and subscriptions. Microsoft 365 or Google Workspace, finance and ERP, CRM, specialist applications and separately licensed security tools.
- Connectivity and cloud infrastructure. Internet lines, mobile data, cloud hosting, storage and backup capacity.
- Support and managed services. Help desk, managed service provider fees, maintenance contracts and outsourced security services such as managed detection and response (MDR).
- IT personnel. Total cost of internal IT staff, including employer costs, benefits and training.
- Projects. One-off work such as migrations, new systems or office moves.
Then add a second, management view that tags lines from those categories instead of adding new ones: security, compliance and innovation. This prevents double counting. Security shows why: part of it sits in licences (security features included in a Microsoft 365 plan), part in infrastructure (backup storage) and part in support (an MDR contract). A separate security budget for the same items would overstate the total.
Do not start from fixed percentages per category. Proportions differ between organisations, so derive them from your actual invoices, contracts and payroll. The same goes for security: its budget should follow your risks, legal and contractual obligations and the controls you need, including security already paid for inside licences and service contracts.
Hardware refresh cycles
Refresh cycles are planning assumptions, not fixed rules. Common starting points are 4 to 5 years for business laptops and 5 to 7 years for on-premises servers and network equipment such as switches and firewalls. Adjust them per asset type for:
- vendor support and security updates for hardware, firmware and operating system
- workload: what users and applications actually demand
- reliability and failure history
- maintenance cost and warranty cover
- energy use and residual or resale value
Keeping equipment longer is not automatically more expensive; a supported device that still performs well can be good value. The firm limit is security support. A firewall or operating system that no longer receives security updates is a risk however well it runs, so record vendor end-of-support dates in your asset inventory.
Example: a 50-person business with 55 laptops at an average replacement cost of £1,200 has a fleet worth £66,000. On a 4-year cycle, that is an annualised planning cost of £16,500 a year. Actual cash spend will differ from year to year, depending on when devices are bought and whether you buy or lease.
The software licensing audit you have not done
Many organisations have no accurate picture of which licences they pay for and which are used. Unused or underused licences can be a material cost, especially in growing businesses where tools are added department by department.
Review the contracts (term, minimum seat numbers, notice and renewal dates), the users assigned to each licence, real activity such as last sign-in dates in admin consoles, and the renewal terms. Ask team leads which tools they rely on; duplicate tools are common, such as two departments using different project management applications.
Hypothetical example: if an audit finds eight unused seats on a tool costing £30 per user per month, removing them saves £240 a month, or £2,880 a year. Whether you can realise that saving depends on the licence rules; some contracts only allow reductions at renewal. Set reminders 90 days before major renewals so decisions are not made under auto-renewal pressure.
Building your budget
Step 1: Asset inventory. List every device, its age, replacement value and planned replacement date, and build a year-by-year forecast for the next three years.
Step 2: Contracts and software. Document every licence, subscription and service contract with its cost, term, commitment and renewal date, and compare it with actual use.
Step 3: Support and personnel. Record the total cost of internal IT staff, including employer costs and benefits, plus current managed service fees or quotes.
Step 4: Security scenario. Define the controls your risks and obligations require, then check which you already pay for. For a 50-person office-based business, an illustrative scope could cover identity and multi-factor authentication (for example Microsoft Entra ID P1, included in Microsoft 365 Business Premium), endpoint protection with EDR, backup to immutable or offline storage with regular restore tests, security awareness training, and specialist support for configuration, monitoring and incident response. In Cyvra's experience a scope like this often adds somewhere around £8,000 to £15,000 a year, but the figure varies widely with existing licences, suppliers and the level of monitoring. Treat it as a scenario, not a threshold.
Step 5: Three-year forecast. Group everything into recurring costs, planned replacements and projects for each of the next three years.
What else to include
- Capex and opex. Separate purchases you capitalise (hardware, some implementation work) from operating costs (subscriptions, support, leases); finance treats them differently.
- Total cost of ownership. For any new system, include implementation, training, integration, support and exit costs, not only the licence price.
- Personnel. Internal IT salaries and employer costs are often a large line and are frequently missing from IT budgets.
- Contract commitments. Record minimum terms, notice periods and renewal dates, so you know which costs are fixed.
- Currency exposure. Some software and cloud services are priced in US dollars; allow a margin for exchange-rate movements where that applies.
- Contingency. Hold a reserve for unplanned replacements, price rises and incidents.
- Budget versus actuals. Compare spend with budget at least quarterly and explain the differences.
- Supplier concentration. Note where one supplier provides several critical services and what switching would cost.
Illustrative three-year example
The figures below are illustrative for a 50-person business without internal IT staff. They are not benchmarks.
IT budget conversations become straightforward when you present the spend as infrastructure, not IT.