CIOs know the feeling. Projects are running slower than they should. Developers are blocked by systems no one fully understands. Releases that take four weeks when they should take two. The cost is real, it just doesn’t have a name on the spreadsheet.
Interface legacy is not a technology problem. It is a business problem, one that compounds quietly, quarter after quarter, until the organisation can no longer move at the speed the market demands. The challenge for CIOs is that its cost is never itemised. It hides in plain sight, distributed across budgets that have nothing to do with legacy on paper.
The invisible line item
Every CIO has a budget for infrastructure, for security, for licences, and for development capacity. What almost no one has is a line for interface legacy, and that absence is not because the cost doesn’t exist. It’s because the cost never arrives in one place.
It arrives as a developer who spends three days understanding a system before writing a single line of code. It arrives as a release that misses its window because a design change broke six components across four different style guides. It arrives as a support queue full of tickets about confusing interfaces, tickets that cost €35 each to resolve, at a volume of hundreds per month.
None of these appear as “legacy cost” in any report. They appear as overtime, as sprint carryover, as QA hours, and as attrition. They are invisible until an organisation decides to make them visible.
It’s not that CIOs ignore the problem. It’s that the problem is never presented as a problem, it’s presented as normal.
| 33% | 40% | 70% |
| of developer time consumed by technical debt | higher maintenance costs in high-debt organisations | of modernisation initiatives blocked by legacy systems |
| Stripe Developer Report | McKinsey Digital 2024 | McKinsey $2B study |
Why CIOS miss
The signals are there. They always are. But they are dispersed—fragmented across teams, tools, and departments, preventing a unified picture from forming. A CIO looking at a dashboard sees delivery velocity, not the cause of slow delivery. They see support ticket volume, not the interface failures driving it. They see developer headcount, not the percentage of that headcount absorbed by maintenance instead of building.
This is not a failure of data or KPPIs. It is a structural gap in how interface health is measured — or rather, how it is not measured. Organisations have matured their approach to infrastructure debt, security debt, and data quality. Interface legacy has not yet earned its own category in the strategic conversation.
There is a second reason: legacy is often invisible because it is the default. When a system has always been slow to change, slow becomes the benchmark. When a team has always spent half their time on maintenance, that ratio normalises. The cost is real but the reference point for what “healthy” looks like has been lost.
Interface strategy as a strategic layer
Legacy is typically understood as a technology problem, old code, outdated frameworks, and systems past their support date. This understanding is too narrow, and it leads organisations to address the symptom rather than the condition.
Interface legacy should be understood as a governance layer that sits across the entire frontend of an organisation. It is not defined by the age of a system. It is defined by the degree to which that system prevents the business from moving with the agility it needs. A system built two years ago on the wrong architecture is legacy. A process that runs on Excel is legacy. A frontend ecosystem with no owner is legacy.
Defined this way, interface legacy becomes a strategic concern, something that belongs in the CIO’s risk register, not just the engineering backlog. And like all strategic concerns, it can be measured, managed, and reduced.
6 signs your enterprise has an interface legacy problem
Most organisations exhibit several of these simultaneously. The more that apply, the higher the cost, and the more urgent the need for a structured response.
| 01 | Technology Fragmentation Multiple frontend stacks operating in parallel, OutSystems alongside React alongside a legacy IBM portal, create exponential coordination overhead. Every system boundary is a maintenance cost, an integration risk, and a knowledge silo. The frontend team cannot develop deep expertise in any one stack; they develop shallow familiarity with many. |
| 02 | Design System Entropy Multiple style guides, inconsistent component libraries, and visual standards that exist in slide decks but not in running code. A rebrand becomes a multi-quarter project. A new product feature requires negotiating between three competing visual languages. The accumulated cost of inconsistency is invisible until a redesign reveals it. |
| 03 | No Governance Layer No UI architect. No ecosystem owner. Teams making independent decisions that conflict at integration. This is one of the most expensive forms of legacy because it is self-replicating: without a governance layer, every new project adds more fragmentation. The design system owner understands design but not architecture. The architect understands systems but not design. No one owns the intersection. |
| 04 | Tribal Knowledge Loss Key engineers left and took the system’s logic with them. Documentation was never written because there was never time. Onboarding a new developer takes months, not weeks, because the knowledge lives in people rather than in the system. Every change carries hidden risk — not because the code is complex, but because no one fully understands it anymore. |
| 05 | Compliance Exposure The EU Web Accessibility Directive creates hard legal obligations. Outdated software licences and frozen API versions create a security risk. Legacy interfaces built before modern standards were set may be non-compliant in ways the organisation has not yet identified. Regulatory pressure on digital interfaces is increasing, legacy systems are disproportionately exposed. |
| 06 | Delivery Velocity Collapse Features that should take two weeks take two months. Not because the team is slow, but because the system resists change. Every new capability must negotiate with years of accumulated decisions. Maintenance crowds out building. The backlog grows faster than the team can clear it, and the gap between what the business needs and what engineering can deliver widens every quarter. |
Making the cost visible: the model
The core challenge is not that organisations cannot fix interface legacy. It is that they cannot justify fixing it — because the cost has never been quantified. A problem without a number does not make it into the budget conversation.
The Interface Legacy Cost Calculator translates the six dimensions above into a conservative annual cost estimate. The model has five components, each grounded in published market research.
How the model works
The model starts from a simple baseline: total frontend investment, the number of engineers multiplied by their fully loaded annual cost. Everything else is a multiplier on that baseline, derived from the variables that signal legacy severity.
| COST COMPONENT | LOGIC | SOURCE |
| Lost dev productivity | Healthy organisations spend ~20% of dev time on maintenance. Every percentage point above that is waste. At 50% maintenance, 30% of your entire frontend budget is absorbed before a single new feature is built. | Stripe Developer Report; CodeScene 2024 |
| Fragmentation tax | Each additional frontend stack adds ~8% overhead in coordination, tooling, hiring premium, and context-switching cost. Each additional design system adds ~4%. A three-stack, three-guide organisation pays a 20%+ premium before writing a line of new code. | McKinsey Digital 2024 |
| Governance & knowledge loss | The absence of a UI owner adds ~5% in misalignment and rework. Each key person who leaves costs approximately 35% of their annual salary to replace. Missing documentation adds a ramp-up tax on every new hire. | CISQ Cost of Poor Software Quality 2022 |
| Compliance exposure | Accessibility non-compliance carries risk-adjusted annual exposure of €15K–40K under the EU Web Accessibility Directive. Outdated licences and API lock-in add €8K–25K in security and integration risk. | EU Web Accessibility Directive; Forrester Research |
| Delayed time-to-market | Each week of excess delivery time costs 0.5% of frontend budget in opportunity cost. Support tickets caused by interface failure cost ~€35 each to resolve. At 100 tickets per month, that is €42K per year from interface failure alone. | Stripe 2-month delay study |
What the model does not capture
The model is deliberately conservative. It does not attempt to quantify competitive disadvantage — the market share lost when a competitor ships features faster. It does not capture customer churn driven by poor interface experience. It does not model the strategic cost of being unable to adopt AI-accelerated development because the codebase is too fragile.
These are real costs. They are simply harder to bound. The model focuses on what can be estimated from variables an organisation can reasonably know: team size, stack count, maintenance ratio, and delivery velocity. The result is a floor, not a ceiling.
The number the calculator produces is almost certainly lower than the real cost. Its job is not to be exact, it is to make the invisible visible.
What a structured response looks like
Understanding the cost is step one. The organisations that reduce interface legacy most effectively share three characteristics.
They appoint an owner. A UI architect or frontend tech lead with genuine authority over standards, tooling, and architecture decisions. Not a design system manager who produces guidelines. Someone who governs the intersection of design and engineering across every team that touches the interface.
They establish a single source of truth. A design system that is operational, not aspirational, built into the development pipeline, version-controlled, and maintained like a product. Not a Figma file. Not a Confluence page. A living system that every team builds from.
They treat consolidation as investment, not cost. Moving from three stacks to one is not a technical exercise, it is a business decision with a calculable return. The maintenance overhead eliminated, the coordination cost reduced, the velocity regained: these are recoverable budget, redirected from keeping the past running to building the future.
If any of the six signs above resonated, the cost is almost certainly higher than you think — and higher than it needs to be. Use our calculator to put a number to it, then let’s talk about what a realistic path forward looks like for your organisation.
A model to be a baseline
For us, the most important thing about this model is to open a new perspective on the way our clients, partners, and community see and manage the interfaces. Why is this important? Because, as we believe in Hi Interactive, every interface should light up every user’s life.
Sources & references:
- Stripe Developer Report — 33% of developer time absorbed by technical debt across surveyed engineering organisations.
- McKinsey Digital, “Driving impact at scale from automation and AI” (2024) — high-debt organisations spend 40% more on maintenance; deliver features 25–50% slower than competitors.
- McKinsey $2B modernisation study — 70% of digital transformation initiatives blocked by legacy systems.
- CodeScene Technical Debt Research (2024) — up to 42% of developer capacity consumed by technical debt in severe cases.
- CISQ, “Cost of Poor Software Quality in the US” (2022) — $1.52 trillion global impact; average enterprise carries $3.61M in technical debt.
- Forrester Research — $100 return on every $1 invested in UX; accessibility and interface quality directly correlated with business outcomes.
- EU Web Accessibility Directive — enforcement obligations for public sector and qualifying private organisations; WCAG 2.1 AA compliance required.
- Aalpha (2025) — 60–80% of IT budgets in legacy-heavy organisations consumed by maintenance rather than innovation.
- DEV Community Developer Survey (2025) — 23% baseline figure for technical debt as share of engineering capacity in healthy organisations.
