The real cost of legacy systems (and how to measure it)
A rigorous framework for quantifying legacy drag — not just on IT, but on every function it touches.
Most organizations undercount the cost of legacy systems by an order of magnitude. They measure the IT budget — licences, hosting, maintenance contracts — and stop there. The real cost is elsewhere: in the engineers who cannot ship new features because the old system is in the way, the ops team manually reconciling data between systems that should talk, and the revenue opportunities that never get built because the platform cannot support them.
The four cost categories to measure
A rigorous legacy cost audit covers four categories. Most organizations have numbers for the first. Almost none have instrumented the other three.
- Direct IT cost — licences, hosting, break-fix maintenance, vendor contracts
- Engineering drag — sprint velocity lost to working around legacy constraints, incident time, manual deployments
- Operational burden — manual work created by integration gaps, reconciliation, workarounds
- Revenue ceiling — features not built, markets not entered, integrations not completed because the platform cannot support them
Measuring engineering drag
The most tractable number to measure is engineering time lost to legacy systems. Run a two-week diary study with your engineering team: every ticket that involves a legacy system constraint gets tagged. At the end of two weeks, calculate the percentage of engineering capacity consumed by working around the old system rather than building new value. Most organizations are surprised by how high this number is.
Legacy drag is not an IT problem — it is a growth ceiling that only looks like an IT cost on the surface.
Building the business case
The business case for modernization is built from these four numbers, discounted appropriately. Direct savings are certain and near-term. Engineering drag savings take 3–6 months to materialise as the team recovers velocity. Revenue ceiling removal is the hardest to quantify but often the largest number. Present all four with confidence ranges, not false precision.
Common mistakes in legacy cost assessments
- Counting only IT budget line items — ignores the operations, support and rework cost carried by other teams
- Using fully-loaded engineer cost without accounting for opportunity cost
- Not measuring ops burden separately from IT cost
- Treating modernization as cost-neutral when velocity recovery alone often covers the investment
Application Modernization
Migrate legacy systems to modern, cloud-native architectures without disrupting the business.
Start a conversation
Let's find where value is leaking in your ecosystem.
Bring us the workflow, the channel, or the half-built thing that's stuck. In 30 minutes we'll tell you plainly which parts should connect, where intelligence pays back — and what it takes to ship.