For years, executives have asked a simple question: what should our IT budget be as a percent of revenue? The appeal is obvious. A single percentage feels like clarity. It suggests comparability. It implies discipline.
But in modern enterprises — especially those operating across cloud, SaaS, and AI — that number alone tells you very little. The real question isn't "what's the right percentage?" but "is our IT spend structurally aligned to our strategy, risk profile, and growth ambition?"
There is no universal "correct" IT budget as a percent of revenue. Industry research, including Gartner studies, consistently shows that IT spending as a share of revenue varies significantly by sector, operating model, regulatory burden, and digital maturity. In Cloud+ environments, where AI, SaaS, and multi-cloud consumption are expanding rapidly, revenue percentage alone is an incomplete benchmark.
The right approach is to:
Use revenue percentage as a directional indicator
Classify IT costs consistently
Separate Run vs Change
Align spending to value drivers
Apply structured cost modeling
Without that structure, percentage comparisons are misleading.
Across industries, IT spend as a percent of revenue can differ dramatically. Financial services institutions, for example, typically operate with higher IT ratios due to compliance, cybersecurity, and transaction infrastructure requirements. Manufacturing organizations may run leaner IT footprints relative to revenue but invest heavily during modernization cycles. Digital-native and SaaS companies often exceed traditional averages because technology is the product.
Even within the same industry, two companies can have radically different ratios depending on:
Legacy system burden
Cloud adoption maturity
M&A activity
AI investment cycles
Regulatory exposure
Outsourcing strategies
A single percentage can't capture those structural differences.
Traditional IT budget benchmarks were developed in an era when infrastructure was relatively stable and centralized. That context no longer applies.
According to the 6th Annual State of FinOps report, FinOps has expanded beyond cloud into a broad technology value discipline:
98% of organizations now manage AI spend (up from 63% last year and 31% two years ago).
64% manage licensing.
57% manage private cloud.
48% manage data center.
28% are beginning to include labor costs.
Technology cost is no longer a contained infrastructure category. It is a distributed, multi-domain investment portfolio spanning AI, SaaS, cloud, licensing, data center, and increasingly human capital.
At the same time, optimization alone is no longer the primary story. While workload optimization remains important, practitioners report diminishing returns after "hitting the big rocks" of waste. Governance, forecasting, and scope expansion now collectively outweigh pure cost reduction as priorities.
In that environment, benchmarking IT budget as a percent of revenue becomes more complicated. Revenue is relatively stable and reported annually. Technology cost is dynamic, usage-based, and expanding across domains. Without structured allocation, forecasting, and scenario modeling, revenue-percentage comparisons risk masking volatility, misclassification, and unmanaged growth. Modern IT cost governance requires understanding how technology investments are evolving.
Revenue percentage answers only one question: "how large is IT relative to total company revenue?" It doesn't answer:
How much of IT spend is Run vs Change?
How much supports innovation vs maintenance?
How efficiently cloud resources are used?
Whether spending aligns with strategic priorities?
Whether cost growth reflects demand or inefficiency?
Within the TBM Framework cost transparency and benchmarking require structured classification and modeling. The TBM Taxonomy enables consistent categorization of technology costs across towers, services, and business capabilities. Without that consistency, cross-company comparisons become unreliable.
Revenue percentage without classification discipline is simply a ratio. With structured cost modeling, it becomes a strategic diagnostic.
A more actionable question than revenue percentage is: "how is our IT budget distributed between Run and Change?" Run spending protects operational stability. Change spending fuels transformation and growth.
Two organizations with identical IT-to-revenue ratios can look radically different depending on how that spending is distributed. For example:
70% Run / 30% Change may signal operational drag or regulatory complexity.
50% Run / 50% Change may reflect aggressive transformation.
Without structured cost modeling, that distinction is invisible.
Instead of chasing an external percentage, leading organizations set their own benchmark using five steps.
Adopt a structured cost taxonomy aligned to services, infrastructure, and business capabilities. This ensures comparability over time.
Understand what portion of spending maintains the business versus evolves it.
Given the volatility of Cloud+ environments, isolate consumption-based spending for governance and forecasting.
Within the TBM Framework IT spend should connect to value drivers such as financial performance, efficiency, innovation, compliance, experience, and sustainability. This shifts the discussion from "cost burden" to "value contribution."
Revenue projections fluctuate. So does demand. Scenario modeling allows leadership to test what happens to the IT-to-revenue ratio during rapid growth, during revenue contraction, and as AI expansion affects operational overhead. Mature IT Finance teams use rolling forecasts rather than static annual ratios.
Cost modeling connects revenue percentage to operational reality. It traces spending from general ledger through cost pools and allocation drivers to services and business units. With structured cost modeling, organizations can benchmark internally over time, compare peer ratios responsibly, identify inefficiencies, justify transformation investments, and model growth scenarios. Without it, revenue percentage becomes an abstract metric disconnected from execution.
Revenue percentage is useful, but only as a signal. What matters more is governance:
Can Finance reconcile every rate back to the ledger?
Can IT explain cost growth and drivers?
Can leadership model future scenarios before approving budgets?
This is also where structured IT cost benchmarking earns its place — comparing your ratios against relevant peers on a normalized model, rather than against a generic industry average.
Serviceware's 2026 IT Benchmarking Initiative, developed with McKinsey & Company, benchmarks IT budget, run/change profile, and service costs against relevant peers — turning a vague percentage into a defensible peer comparison.
Serviceware's IT Financial Management platform, powered by the Digital Value Model (DVM), enables structured cost classification, allocation, and scenario modeling aligned with TBM principles. Instead of debating a static percentage, leadership gains a dynamic, model-driven view of IT's financial posture.
There's no universal "correct" IT budget as a percent of revenue. Industry benchmarks vary widely. Cloud and AI expansion are reshaping cost structures. Governance maturity matters more than comparison. Revenue percentage is a starting point. Structured cost modeling, consistent classification, and scenario-based forecasting turn that starting point into strategic control.
Discover how structured IT Financial Management and TBM-aligned cost modeling enable defensible budgeting and transparent governance. Book a demo
There is no universal average. IT spending as a percentage of revenue varies significantly by industry, digital maturity, and regulatory environment.
Different industries have different operational requirements, regulatory burdens, and digital dependencies, which directly influence IT investment levels.
Cloud introduces consumption-based variability, which can cause IT spend to fluctuate independently of revenue unless governed by structured forecasting and allocation.
Peer benchmarking can be useful directionally, but only if cost classification is consistent. Without structured modeling, comparisons can be misleading.
No. Revenue percentage provides scale context, but effective governance requires cost modeling, allocation, forecasting, and value alignment.