For most enterprises, the conversation around IT costs eventually narrows to a single tension:
How much are we spending to keep the lights on, how much are we transforming the technology estate, and how much are we investing in growth?
Run vs Change spending reflects strategic posture. It determines whether IT is operating defensively or enabling transformation.
Get it wrong, and innovation stalls.
Overcorrect, and operational stability erodes.
Balancing IT costs between Run and Change is one of the most consequential financial decisions CIOs and CFOs make.
IT costs are increasingly categorized across three domains in the Run–Transform–Grow (RTG) model:
Run: Operational spending required to maintain existing services, infrastructure, and operational stability.
Transform: Investments that modernize technology platforms, architecture, and operating models, such as cloud migration, platform consolidation, or large-scale modernization initiatives.
Grow: Investments that enable new business capabilities, digital products, and competitive differentiation.
A healthy balance between Run, Transform, and Grow depends on industry, organizational maturity, and strategic priorities. The key is transparency. Without structured cost modeling and classification, organizations cannot reliably measure, benchmark, or optimize how spending is distributed across these domains.
Run IT costs represent the ongoing spending required to operate and maintain existing technology services.
These typically include:
Infrastructure operations
Application maintenance
Service desk and support
Security operations
Licensing renewals
Managed services
Run spending is often described as “keeping the lights on,” but that framing can be misleading.
Stable operations are not optional. They protect revenue, ensure compliance, and safeguard customer experience. Within the TBM framework, these IT costs support value drivers such as financial performance, operational efficiency, compliance, and experience.
The challenge is that Run IT costs tend to grow incrementally over time, especially in hybrid and Cloud+ environments where legacy systems coexist with modern platforms.
Without structured oversight, runaway spending becomes inertia.
Transform IT costs fund initiatives that modernize technology platforms and operating models.
These investments improve efficiency, resilience, and scalability rather than directly generating new business capabilities.
Typical Transform initiatives include:
Cloud migration programs
Application modernization
Infrastructure consolidation
Platform re-architecture
Data platform modernization
Automation of operational processes
Transform IT costs are critical because modernization initiatives often determine the long-term structure of operational spending. Successful transformation programs can reduce long-term run IT costs while improving agility and operational efficiency.
However, poorly governed transformation initiatives can also increase operational complexity and long-term costs.
This is why strong financial governance is essential when evaluating transformation investment.
Grow IT costs support initiatives that create new business capabilities.
These investments enable innovation, revenue growth, and competitive differentiation.
Examples include:
Digital product development
AI and advanced analytics initiatives
Customer experience platforms
New digital services
Strategic innovation programs
Data-driven business capabilities
Unlike Run or Transform spending, Grow IT costs are typically tied to forward-looking outcomes rather than operational stability.
As a result, they often receive greater executive scrutiny and require clear business cases and measurable outcomes.
When governed effectively, Grow spends on technology investment as a driver of business expansion rather than simply a cost center.
Historically, many organizations evaluated IT costs through a simple Run vs Change ratio, often targeting roughly 60–70% Run spending and 30–40% Change investment.
However, this model can obscure an important distinction.
Transformation initiatives that modernize platforms and infrastructure are fundamentally different from investments that create new digital capabilities. Separating spending into Run, Transform, and Grow provides clearer visibility into how IT costs support operational stability, modernization, and innovation.
What matters most is not a fixed ratio but the ability to answer critical governance questions:
Is Run spending structurally optimized?
Are transformation initiatives reducing long-term operational IT costs?
Are growth investments aligned with measurable business outcomes?
Are shared services allocated fairly?
Can leadership trace IT cost growth to demand or inefficiency?
Within the TBM model, structured cost classification enables organizations to categorize IT costs consistently across these domains.
Without that discipline, organizations misclassify projects, obscure overhead, and distort reporting.
One of the most common distortions in IT cost analysis is misclassification.
For example:
A “modernization” initiative may include significant maintenance overhead.
AI pilots may quietly become recurring operational expenses.
Cloud optimization programs may sit in Run despite being transformation enablers.
Without a standardized classification aligned to a structured taxonomy, run vs. change reporting becomes subjective.
Cost modeling (aligned to TBM-style categorization) ensures that:
Costs are consistently classified
Comparisons are defensible
Benchmarks are meaningful
Trade-offs are visible
To balance IT costs, you need to identify structural inefficiencies:
Redundant application
Underutilized infrastructure
Overlapping SaaS subscriptions
Manual operational processes
Excessive support demand
FinOps practices increasingly intersect here, particularly in Cloud+ environments where SaaS and AI expansion introduce new operational overhead.
Optimizing Run frees up financial capacity for Change — but only if savings are verified and deliberately reinvested.
This is where governance matters.
Within the TBM Framework, cost transparency ultimately connects to Organizational Value Drivers:
Financial performance
efficiency
innovation
compliance
experience
sustainability
Run spending supports efficiency, compliance, and experience.
Change spending supports innovation and strategic growth.
A balanced IT cost structure ensures that none of these drivers are neglected.
When leadership can clearly see how Run and Change spending map to value drivers, budgeting shifts from reactive defense to strategic prioritization.
Balancing IT costs isn’t static.
Cloud adoption, AI experimentation, and M&A activity can shift the Run/Change ratio rapidly.
Mature IT Finance teams use scenario modeling to answer:
What happens to Run if we accelerate AI deployment?
How does a cloud migration shift operational expense?
What Change programs increase long-term Run overhead?
Structured forecasting enables proactive adjustments instead of reactive cost-cutting.
Serviceware’s IT Financial Management platform, powered by the Digital Value Model (DVM), enables structured classification, allocation, and forecasting across Run and Change spending.
Organizations can:
Classify costs consistently across services and projects
Trace spending from GL to service to business unit
Benchmark Run vs Change ratios
Model scenario impacts before budget approval
Align spending with TBM value drivers
By embedding governance into the financial backbone, Run vs Change becomes a strategic lever rather than a reporting exercise.
Balancing IT costs between Run and Change is about transparency, discipline, and strategic alignment.
Run protects stability.
Change fuels growth.
Without structured cost modeling and classification, the balance becomes guesswork.
With it, leadership can optimize operations, fund innovation, and align technology investment with measurable business outcomes.
IT costs include all expenses related to operating and evolving technology services, including infrastructure, applications, cloud, SaaS, labor, and transformation initiatives
Run refers to operational spending that maintains existing systems. Change refers to investment in new capabilities, modernization, and innovation.
While many organizations aim for 60–70% Run and 30–40% Change, the appropriate ratio depends on strategy, maturity, and industry context.
Cost modeling ensures consistent classification and allocation of IT costs, enabling transparent comparison, benchmarking, and governance.
FinOps can reduce unnecessary Run costs by optimizing cloud and SaaS usage, freeing capacity for strategic Change investments.