Making the internal case for modernisation in your 2027 budget

TL;DR: For many businesses, 2027 technology budgets started taking shape in September and will be finalised before Christmas. For those with an April year end, the decisions follow in early 2027.The businesses that funded modernisation two years ago are now building AI capability on solid foundations, while the cost of deferral compounds for everyone else. This post gives the champion, the Operations Director or IT lead who already knows the systems need work, a structure for making the case internally that a finance director can actually evaluate. It covers what the problem costs today, what changes measurably, what phase one looks like and what a board will ask.

If you are reading this in October, the budget conversation is either happening now or it is about to. And if modernisation is on your list, the window to get it funded for 2027 is shorter than it feels.

This post is written for the person who has to make the case rather than the board evaluating it: the Operations Director who has been managing around the limitations of the current platform for two years, the IT lead who knows exactly what the system cannot do and is tired of explaining why certain things take as long as they do, the person who is right about the problem and has not yet found the argument that makes it fundable.

The argument exists. It is just rarely structured in a way that connects to how finance decisions actually get made.

Why this year is different from last year

The macro case for modernisation has not changed, but the cost of waiting has, and that shift is what makes this year's version of the conversation different.

According to research published by IT Brief UK in December 202588% of UK organisations have a two-year roadmap to modernise their IT but only 36% report their plans are fully funded. That gap between intention and investment is not closing. It is widening, because the businesses that closed it two years ago are now compounding the advantage.

The same research found that 61% of UK organisations report that technical debt from legacy platforms now actively blocks efforts to integrate AI. That is not a future problem. It is a current one that widens every quarter. The organisations that funded modernisation in 2023 and 2024 are not just running on better infrastructure. They are building AI automation on top of it. The businesses that deferred are now facing two decisions simultaneously: the modernisation they put off and the AI readiness work they cannot start until it is done.

Presenting this as a single compounding cost is the most honest framing of what deferral actually means in 2026. It is also the framing most likely to land with a finance director who has seen technology investment requests before and knows how to interrogate them.

The three reasons most modernisation business cases fail

Before building the case, it is worth understanding why most of them do not get funded. The problem is almost never the number. It is one of three structural weaknesses that a finance director or board partner can spot in the first five minutes.

No agreed problem definition. The business case describes the solution in detail and the problem in general terms. "The system is outdated" is not a problem definition. "The system requires twelve hours of manual reconciliation per week that would be eliminated by a modern integration layer, at a fully-loaded staff cost of approximately £X per year" is a problem definition. Finance directors fund outcomes, not upgrades.

A case built on technology rather than operational outcomes. The language of the business case is IT language: latency, architecture, technical debt, APIs. These are accurate descriptions of real problems but they do not connect to the operational and commercial outcomes a board evaluates investment against. Every technical problem in the case needs a translation into what it costs the business in staff time, error rates, delayed decisions or missed capability.

A number nobody can defend under questioning. The investment figure is presented as a range with no clear basis. When a finance director asks what phase one delivers and what it costs, the answer needs to be specific enough to defend. A range of £200k to £800k with no phase structure attached to it does not survive that question. A phase one scoped to a specific component with a specific operational outcome and a specific cost estimate does.

The structure that works

This is not the only way to frame a modernisation business case. It is the structure that addresses the three failure modes above and gives the champion the best chance of getting to a decision rather than a deferral.

Step 1: Quantify what the current platform costs today

Not in rebuild terms, but in operational terms. How many staff hours per week go to workarounds, manual processes and error correction that a modern system would eliminate or reduce? What is the fully-loaded cost of those hours? What integration capabilities does the business not have because the current platform cannot support them, and what is that costing in delayed decisions or missed commercial opportunity?

This is the section of the business case most champions skip because it requires internal data gathering that is uncomfortable to do. It is also the section that determines whether the case gets funded. A finance director who can see a quantified current cost has something to compare the investment against. One who cannot has nothing to anchor the decision to.

Step 2: Define what changes measurably in phase one

Not everything changes in phase one, and the business case should be clear about what does: a specific component, a specific process, a specific integration, a specific operational outcome that can be measured before phase two is approved.

This framing does two things. It makes the investment defensible because the return is specific and verifiable. And it reduces the perceived risk of the programme because the board is approving a defined phase with a defined outcome rather than a multi-year programme with a wide cost range.

According to Mobisoft Infotech's analysis of modernisation ROI published in May 2026, organisations typically allocate 60 to 80% of their IT budget to maintaining existing systems. Presenting phase one as a step toward rebalancing that ratio, rather than as an additional spend, changes the framing from cost to reallocation.

Step 3: Present staged and full rebuild as legitimate alternatives

The business case should not assume one approach is obviously right. A staged modernisation, which replaces the highest-friction components while the existing system continues to run, has different implications from a full rebuild. Both are legitimate depending on the organisation's circumstances. Presenting both with honest trade-offs demonstrates that the champion has thought carefully about the options and is not advocating for the most expensive path by default.

For our work with Insite Energy, a full replacement of a legacy billing system serving over 28,000 homes was the right approach because the existing platform had reached the point where incremental improvement cost more than replacement. For our three-year engagement with Islands Energy Group, a staged approach across three regional utility brands was the right path because continuity of service was the overriding constraint. The approach follows the circumstances, not the other way around.

The three questions a finance director will ask

Prepare answers to these before the conversation happens. They are almost always asked and the quality of the answer determines whether the conversation moves forward.

What does this cost if we do nothing? This is the question the business case answers in Step 1. The answer needs to be specific: staff hours, error rates, missed capability. If the honest answer is "we are not sure," that is the first piece of work to do before taking the case to a board.

What does phase one deliver and what does it cost? This is the question the business case answers in Step 2. The answer needs to be specific enough to defend under follow-up. A scoped phase with a specific outcome and a defensible cost estimate. Not a range. Not "it depends."

How do we know this will not run over budget and timeline? This is the question most business cases do not address directly. The answer is a combination of how phase one is scoped, what governance sits around it and what the track record of the delivery partner looks like. A reference to a completed similar project is more useful here than a methodology description. Frequently asked questions

How do I make a business case for software modernisation to a UK board? The most effective structure addresses three things: a quantified current cost in operational terms rather than technology terms, a specific phase one outcome with a defensible cost estimate and an honest comparison of staged and full rebuild approaches. Finance directors fund outcomes not upgrades. Every technical problem in the case needs a translation into what it costs the business in staff time, error rates or missed commercial opportunity.

Why do most technology modernisation business cases fail to get funded? The three most common failure modes are no agreed problem definition, a case built in technology language rather than operational outcomes and an investment figure nobody can defend under questioning. None of these are about the quality of the underlying argument. They are about how the argument is structured and presented.

What is the cost of not modernising legacy systems for a UK business in 2026? According to IT Brief UK research from December 2025, 88% of UK organisations have a two-year roadmap to modernise but only 36% have their plans fully funded. 61% report that technical debt from legacy platforms now actively blocks AI integration. Organisations typically allocate 60 to 80% of their IT budget to maintaining existing systems. The cost of deferral is not staying still. It compounds as the gap widens between organisations that modernised and those that did not.

What is the difference between staged modernisation and a full rebuild? Staged modernisation replaces the highest-friction components of an existing platform while the system continues to run, spreading the investment and reducing disruption. A full rebuild replaces the platform entirely and is appropriate when incremental improvement costs more than replacement or when the existing architecture cannot support what the business needs to build next. Both are legitimate depending on the organisation's circumstances and constraints.

When should a UK business start the modernisation budget conversation? The UK technology budget cycle for 2027 runs from October to December 2026. Starting the internal conversation in October gives enough time to build a defensible business case, gather the operational data needed to quantify the current cost and present to a board before decisions are made. Starting in January means competing for budget that has already been allocated elsewhere.

How Aecor helps

We work with Operations Directors and IT leads at the point where the internal case needs to be built as much as the technical work needs to be scoped. Our Legacy System Modernisation service starts with an honest assessment of the current state that produces the operational cost data the business case needs. For organisations earlier in that conversation, our Digital Transformation Consulting service is the right starting point.

If it would help to talk through the business case alongside scoping the technical work, a free consultation is a good place to start.

Book a free consultation