There is no single correct percentage of revenue that every company should spend on IT. For executive planning, a reasonable starting point is to compare your organization with companies in the same industry and of similar complexity, then adjust for what the business is trying to accomplish.
Current benchmark research shows why a single percentage can mislead. Avasant's 2025/2026 North American study reported median operational IT spending of 2.9% of revenue across its composite sample, while emphasizing that industry sector matters more than company size for this metric. Capgemini's 2025 research used a broader definition of IT and technology spending and found an average of about 6% of annual revenue. Those numbers are not contradictory; they are measuring different scopes of technology cost.
The executive question is therefore not, “Are we above or below 3%, 5%, or 6%?” It is: Are we spending the right amount for our industry, operating model, risk, growth plans, and technology condition—and can we explain what the money is accomplishing?
Why IT budget percentages vary so widely
Revenue is a useful denominator because it lets leaders compare technology spending with the economic scale of the business. But the percentage moves dramatically depending on what kind of company is being measured.
A software company may spend heavily because technology is part of the product. A bank may spend more because digital channels, cybersecurity, resilience, data, and regulation are fundamental to the business. A manufacturer may show a lower percentage of revenue even while operating complex plants, ERP systems, operational technology, networks, cybersecurity controls, and supply-chain platforms.
Avasant's benchmark research explicitly cautions against using the composite percentage as a direct target for an individual company and recommends sector-level comparison instead. That is the right executive posture: benchmark against peers, but budget against strategy.
First, define what you mean by “IT budget”
Companies often compare percentages that are not actually comparable. Before using any benchmark, define what is included.
A useful enterprise technology budget may include:
- internal IT salaries, benefits, and contractors;
- managed service providers and outsourced support;
- Microsoft 365 and other SaaS subscriptions;
- cloud infrastructure and hosting;
- cybersecurity products and services;
- networking, telecom, internet, and mobility;
- end-user devices and hardware lifecycle;
- business applications such as ERP and CRM;
- data, integration, and analytics platforms;
- AI tools and AI-related infrastructure;
- implementation partners and professional services;
- support, maintenance, warranties, and licensing;
- technology capital projects and major transformation initiatives.
If one benchmark measures only the operational IT department while your internal number includes product engineering, factory automation, digital transformation, and business-unit technology, the comparison will be meaningless.
Use a range, not a magic number
The most useful benchmark is usually a range that reflects your industry and operating model. Treat the median as a reference point, not a budget target.
A company below its peer range may be highly efficient. It may also be deferring upgrades, underinvesting in cybersecurity, relying on key-person knowledge, carrying unsupported systems, or pushing technology work into business-unit budgets where it disappears from the central IT number.
A company above its peer range may be wasteful. It may also be funding an ERP replacement, acquisition integration, rapid growth, cybersecurity improvement, automation, AI adoption, or another temporary investment cycle.
Low spend is not automatically efficient, and high spend is not automatically excessive.
Seven factors that should move your IT budget up or down
1. Industry and technology intensity
Start with peer benchmarks for your sector. Technology-heavy, regulated, data-intensive, customer-digital, and high-availability businesses generally require more technology investment than simpler operating models.
2. Growth rate
Fast growth usually exposes capacity and process limitations. New employees, locations, customers, acquisitions, applications, vendors, data, and support requirements can all increase technology cost before the revenue benefit fully appears.
A business preparing to double revenue should not assume last year's technology ratio will remain appropriate.
3. Technical debt and lifecycle condition
A company that deferred infrastructure, application, security, or device investment for several years may appear inexpensive right up until the catch-up cycle begins.
Executive budgeting should distinguish sustainable run-rate cost from temporary remediation or modernization cost.
4. Cybersecurity and resilience requirements
Customer obligations, cyber insurance, regulatory requirements, critical operations, sensitive data, third-party dependencies, and recovery expectations all influence the appropriate level of spend.
The right question is not how much to spend on cybersecurity as a standalone category. It is which material risks need to be reduced, which controls are required, and what resilience the business expects.
5. Cloud and SaaS economics
Cloud and subscription models have shifted more technology cost into recurring operating expense. Avasant's 2025/2026 study found that cloud plus in-house data center spending had grown to 14.6% of the IT budget on average, while traditional IT capital budgets had fallen to roughly 13% of overall IT spending.
That means comparing capital expense alone with prior years can create a false impression that technology investment has declined.
6. AI and data investment
AI is creating another budget pressure. Avasant reported AI and business/data analytics as the top two areas for increased investment in its 2025/2026 study. Gartner's July 2026 forecast projected worldwide IT spending growth of 14.2% in 2026, with strong growth concentrated in AI infrastructure, cloud, and software.
For an individual company, that does not mean “increase the AI budget.” It means make room for worthwhile use cases while preventing duplicate tools, ungoverned subscriptions, weak data foundations, and experimentation without measurable business outcomes.
7. Strategic change
Acquisitions, divestitures, ERP replacement, cloud migration, new locations, regulatory changes, digital products, operating-model redesign, and large automation initiatives can all justify spending above the normal run rate for a defined period.
The budget should make these temporary investment waves visible instead of hiding them inside operating cost.
A better way to build the IT budget
Instead of starting with last year's budget plus an inflation adjustment, build the budget in four layers.
Layer 1: Run the business
Identify the recurring cost required to operate current technology safely and reliably. This includes people, support, SaaS, cloud, networks, devices, core applications, maintenance, security operations, backups, and other baseline services.
This is the cost of maintaining the current operating model—not necessarily the cost of improving it.
Layer 2: Fix material risk and technical debt
Separate work that cannot be deferred indefinitely: unsupported systems, weak identity controls, recovery gaps, fragile infrastructure, aging devices, serious vendor risks, compliance obligations, or high-consequence application issues.
This prevents mandatory remediation from competing invisibly with growth initiatives.
Layer 3: Grow and improve the business
Budget for the technology initiatives connected to specific business priorities: improved customer experience, greater operating capacity, faster cycle times, new revenue, automation, better data, integration, AI, new locations, acquisitions, or cost reduction.
Each material initiative should have an accountable business owner and an expected outcome.
Layer 4: Preserve decision capacity
Do not allocate every dollar at the beginning of the year. Technology conditions change quickly. New cybersecurity findings, vendor changes, acquisitions, AI opportunities, and business priorities will appear.
A modest reserve or executive reallocation mechanism can be more disciplined than forcing every unexpected need through emergency approvals.
Three tests for whether the budget is too low
Your IT budget may be too low if:
- critical systems remain unsupported because replacement is repeatedly deferred;
- cybersecurity or recovery risks are known but remain unfunded without explicit risk acceptance;
- executives are approving growth plans that technology capacity cannot support;
- key applications or integrations depend on one employee or vendor with no resilience;
- projects repeatedly fail because foundational work was never funded;
- business units are buying their own technology because central capacity cannot respond;
- the company has no credible 12-to-24-month technology roadmap.
An artificially low percentage can simply be future spending that has not yet arrived.
Three tests for whether the budget is too high
Your IT budget may be too high if:
- software, cloud, or managed-service costs are growing faster than business usage without a clear reason;
- multiple tools perform substantially the same function;
- premium licenses are assigned broadly without role-based need;
- vendors renew automatically without competitive or strategic review;
- projects continue after the original business case has weakened;
- the organization owns valuable capabilities that have never been implemented or adopted;
- leadership cannot connect material spend to an owner, outcome, risk, or business requirement.
Cost reduction should focus first on waste and low-value complexity—not on reducing the percentage for appearance's sake.
Illustrative example: the same percentage can mean two different things
Consider two hypothetical $50 million companies that both spend $2 million per year on technology, or 4% of revenue.
Company A has current systems, strong vendor contracts, well-managed Microsoft 365 licensing, tested recovery, clear cybersecurity priorities, and a roadmap tied to growth. Its 4% may be healthy.
Company B has an aging ERP platform, five overlapping security products, poor license management, unsupported servers, a major acquisition coming, no tested recovery plan, and no executive technology roadmap. The same 4% may be both inefficient and insufficient: money is being wasted in some areas while critical investment is being deferred in others.
The percentage alone cannot tell leadership which company is better managed.
What executives should ask before approving the IT budget
A useful budget discussion should answer these questions:
- What percentage of revenue are we spending, and what exactly is included?
- How does our spending compare with relevant industry peers?
- What portion of the budget runs today's business versus changes it?
- Which risks or lifecycle issues are we knowingly deferring?
- Which investments are required by our growth plan?
- Where are software, cloud, Microsoft 365, and vendor costs growing fastest?
- Which initiatives have measurable business outcomes and accountable owners?
- Which spending is temporary because of transformation, acquisition, or remediation?
- What would we stop or defer if revenue slowed?
- What important business objective would fail if we cut technology spending by 10%?
If the technology team cannot answer those questions, the budgeting problem is not primarily a percentage problem. It is a strategy and governance problem.
How the budget should connect to the technology roadmap
The strongest budget is the financial expression of a technology roadmap. The roadmap identifies business priorities, risk, dependencies, sequencing, owners, and decisions. The budget tells leadership what that plan costs and when funding is required.
Cyber Virtues' Technology Strategy & Roadmap service is designed around that executive connection: business priorities first, then technology decisions, investment, risk, and sequence.
Organizations that need continuing executive ownership of the budget, vendors, roadmap, cybersecurity priorities, and major initiatives may also benefit from Fractional CIO Services. If Microsoft subscriptions are a material cost driver, a focused Microsoft 365 Licensing & Advisory review can identify mismatched plans, unused capability, and portfolio overlap.
The executive answer
Use IT spending as a percentage of revenue as a diagnostic, not a target. Start with a relevant industry benchmark, make sure the definitions match, and then adjust for growth, risk, technical debt, strategic change, cloud economics, cybersecurity, AI, and the condition of the current environment.
The right IT budget is the amount that lets the company operate reliably, address material risk, and fund the technology changes required by the business strategy—without carrying avoidable waste.
If leadership cannot explain whether the current technology budget is too high, too low, or simply misallocated, Cyber Virtues can help build a decision-ready technology budget and roadmap. Start a conversation with Cyber Virtues to review technology spending, priorities, vendors, risk, and the investments that should come next.