Why transformation funding should start with the estate you already own

Enterprise transformation is often treated as a question of new investment.

Cloud migration, AI adoption, data platform modernisation, automation, and digital transformation programmes all require funding. The strategic case is usually clear. The challenge is often how to fund transformation while maintaining the infrastructure, contracts, and operational commitments that already exist.

The first article in RTK’s Strategic Infrastructure Liquidity series explored why enterprise hardware should be treated not simply as depreciating equipment, but as a balance sheet asset with recoverable value. The next question is what that means for transformation funding.

For global enterprises, the physical infrastructure estate is not only a cost base to manage. It can also influence how transformation is funded, sequenced, and accelerated.

Servers, storage, networking equipment, support contracts, data centre or colocation commitments, and refresh obligations all shape the financial reality behind transformation programmes. Some assets remain critical to operational resilience. Others may be underutilised, nearing retirement, or no longer aligned with future business requirements.

The question for CIOs and CFOs is no longer simply:

How much new budget do we need?

It should also be:

What funding capacity already exists within the infrastructure estate?

That is the next evolution of strategic infrastructure liquidity.

Transformation Ambition Is Growing Faster Than Funding Models

Transformation investment continues to rise. IDC has forecast worldwide digital transformation spending to reach almost $4 trillion by 2027, reflecting how central technology-led change has become to enterprise competitiveness.

But while transformation ambition has accelerated, many funding models have not evolved at the same pace.

Cloud, AI, and digital programmes are often planned around the future state: target platforms, migration waves, operating models, and new capabilities. Existing infrastructure commitments are treated as background cost or, in some cases, as sunk cost.

That creates a gap.

Technology teams may be ready to modernise, but the business case is still shaped by depreciation schedules, support renewals, hardware refresh cycles, data centre commitments, and operational dependencies.

When these factors are not evaluated together, transformation can stall before it scales.

The Estate You Already Own Is Part of the Business Case

Most transformation business cases begin with the question of what needs to be built next.

That is important, but incomplete.

Leaders also need to understand what already exists.

The current infrastructure portfolio affects cost, migration sequencing, resilience planning, support continuity, capacity decisions, and the timing of capital commitments. For IT leaders, the estate represents workloads, dependencies, performance requirements, and operational risk. For finance leaders, it represents depreciation, renewal obligations, balance sheet exposure, and capital allocation.

Both views are valid. The issue is that they are often assessed separately.

A hardware maintenance renewal may be approved to protect operational continuity while a transformation team is planning to exit the same environment. A refresh may be triggered because of lifecycle pressure, even though the strategic enterprise direction is cloud, AI, or consolidation. Infrastructure may be written down without considering whether it still holds market value.

In each case, existing infrastructure quietly reshapes the transformation business case.

Three Signs the Estate Is Shaping Transformation Funding

Infrastructure does not need to be obsolete to constrain transformation.

In many cases, it continues to function, but no longer aligns cleanly with the organisation’s future direction. It still supports critical workloads, but it also absorbs budget, time, and decision-making capacity.

There are three common signals that the existing estate is already influencing transformation funding.

1. Renewal and refresh decisions are being made before migration timelines are clear

A major hardware refresh can recommit capital to environments the business may ultimately want to reduce, migrate, or exit.

For IT teams, refresh decisions are often made to preserve supportability and resilience. For finance teams, they may appear as necessary investment. But when refresh cycles are not aligned with transformation plans, they can create avoidable capital pressure.

The question is not simply whether infrastructure can continue to operate.

It is whether new capital should be committed to it.

2. Support requirements are extending legacy dependency

Large-scale transformation rarely happens all at once.

Many organisations face hybrid periods where some systems remain on-premises for resilience, compliance, performance, or sequencing reasons. During this phase, support renewals, maintenance decisions, and temporary capacity requirements can extend the cost of legacy infrastructure while investment in the future state increases.

Without careful planning, organisations can end up funding both the old environment and the new one for longer than necessary.

3. Asset value is being considered outside the business case

Enterprise infrastructure rarely generates revenue directly, but it often retains recoverable value throughout its lifecycle.

The issue is timing.

If residual asset value is only assessed at disposal, many options may already have narrowed. Market demand may have shifted. Support commitments may have been extended. Refresh decisions may already have been made.

Strategic infrastructure liquidity requires senior leadership to consider infrastructure value earlier in the transformation planning process.

Not as an ITAD afterthought.

As part of the transformation business case.

Why This Is an IT Issue as Much as a Finance Issue

It is easy to frame transformation funding as a finance problem. But the strongest business cases depend on IT insight.

Only IT teams can properly understand which workloads depend on existing infrastructure, which systems carry operational or compliance risk, which environments are underutilised, and where temporary capacity may be needed before migration is complete.

Finance can assess capital impact, but IT determines what is operationally possible.

That is why infrastructure liquidity must sit between the CIO and CFO agenda as a shared endeavour.

Gartner has highlighted the need for infrastructure and operations leaders to identify future requirements and seek insights that support implementation. For enterprise leaders, that means infrastructure planning can no longer remain a reactive operational discipline. It needs to support broader transformation outcomes.

The most effective organisations do not ask IT to modernise first and finance to fund it later.

They bring infrastructure, finance, procurement, and transformation leaders into the same conversation earlier.

From Funding Request to Funding Readiness

A traditional transformation funding conversation starts with a request for new budget.

A more strategic conversation starts with a clearer view of the current estate.

Before seeking new transformation funding, leaders should ask:

  • Which infrastructure commitments are already shaping the transformation timeline?
  • Where are renewal, refresh, or support decisions creating avoidable funding pressure?
  • Which assets still hold financial value, and when should that value be assessed?
  • Where does the current estate support transformation, and where does it slow progress?
  • How can IT and finance build a shared view of infrastructure’s role in the business case?

These questions change the nature of the conversation.

Instead of viewing existing infrastructure only as a constraint, leaders can begin to understand where it may support the next phase of change.

This is not simply about selling old hardware. It is about understanding how infrastructure decisions shape transformation economics.

In some cases, the opportunity may be capital recovery. In others, it may be avoiding unnecessary refresh spend. In others, it may be preserving operational continuity while reducing long-term exposure.

The common thread is visibility.

Without visibility, infrastructure remains a cost line. With visibility, it becomes part of the funding strategy and a critical component of the transformation business case.

Evidence from Enterprise Programmes

The financial impact of this approach is not theoretical.

In one RTK engagement, an EMEA insurance enterprise faced a material disconnect between depreciated IT asset book value and fair market value during a planned cloud exit. RTK’s Deep Dive Assessment reconciled financial ledgers with on-site infrastructure validation, established defensible fair market value, and enabled a structured 13-month leaseback model. The engagement supported approval of a €36 million multi-year cloud programme while maintaining operational continuity.

This example demonstrates a broader point: infrastructure decisions can materially influence how transformation is funded.

The opportunity is not just in the assets themselves. It is in connecting lifecycle data, operational dependency, market value, and transformation timing into a single executive view.

Moving from Infrastructure Cost to Transformation Capacity

Transformation will continue to demand investment. Cloud, AI, data modernisation, and digital platforms are no longer optional priorities for most global enterprises.

But the funding conversation needs to evolve.

For many organisations, transformation capacity may not only depend on new budget. It may also be shaped by infrastructure they already own, commitments they can reassess, and lifecycle decisions they can make more strategically.

This is where RTK works with enterprises as a strategic infrastructure advisor, helping leaders evaluate infrastructure estates through both an operational and financial lens.

Through programmes such as RTK’s Cloud and AI Acceleration Programme (NEXCAP), organisations can identify the financial, contractual, and lifecycle constraints that sit beneath transformation programmes. RTK positions NEXCAP around aligning infrastructure, finance, and migration timelines to turn legacy constraints into acceleration capital.

For CIOs and CFOs, the opportunity is clear: infrastructure should not simply be managed as a cost to maintain or an asset to depreciate. It should be evaluated as part of the enterprise’s broader capital strategy.

When viewed through that lens, existing infrastructure becomes more than a legacy obligation.

It becomes a potential lever for funding transformation.

This article is part of RTK’s Strategic Infrastructure Liquidity series, exploring how enterprise leaders can treat infrastructure as a strategic financial asset.

For organisations facing this issue specifically in the context of cloud migration, RTK’s Executive Playbook, How Unlocking Trapped Capital in Legacy IT Hardware Accelerates Cloud Migration, explores how legacy infrastructure, book value constraints, capital lock-in, and finance-backed business cases can affect the path to cloud.