The Tax Nobody Line-Items: Making the Case for Legacy Modernization

Legacy modernization is the investment every executive agrees is necessary and almost nobody prioritizes — because the business case is usually framed as risk reduction, and risk reduction loses budget fights against growth stories almost every year. · Juan Vegarra

Legacy system modernization is the technology investment every executive agrees is necessary and almost none of them prioritizes, because it's the rare capital allocation decision where the business case genuinely looks weaker on paper than nearly everything else competing for the same budget. New AI capability comes with a growth story attached. Legacy modernization comes with a risk-reduction story, and risk-reduction stories lose budget fights against growth stories in almost every organization, almost every year, until the legacy system fails at a genuinely bad moment and the risk-reduction case becomes retroactively obvious to everyone in the room, at a considerably higher cost than it would have been to address proactively.

The scale of the number nobody sees

The honest reason legacy modernization keeps losing this fight isn't that executives don't understand the risk in the abstract. It's that the business case is usually built wrong, framed narrowly as an IT hygiene project instead of what it actually is: a continuous constraint on every other technology initiative the organization wants to fund. The scale involved is larger than most non-technical executives realize. McKinsey research finds that technology debt can account for forty to fifty percent of total IT investment spend, and that figure rarely appears anywhere as a single, visible line item in a budget document.^[1] Deloitte's 2026 Global Technology Leadership Study puts technical debt's share of total IT spending at twenty-one to forty percent.^[1] In many organizations, seventy to eighty percent of total technology spend goes toward legacy systems in some form, split roughly between direct costs — infrastructure, labor, licensing, vendor support, and increasingly scarce specialist talent — and hidden costs including productivity loss, downtime, delayed releases, and accumulating security risk.^[1] Accenture estimates the broader business cost of technical debt at $2.41 trillion annually across U.S. businesses.^[1] And the specialist talent required to maintain aging systems has become genuinely scarce and expensive: contractor rates for specialized legacy skills widely run $180 to $250 an hour in 2026, up from roughly $120 an hour in 2022, as the pool of engineers who understand these systems continues to shrink through retirement.^[1]

Reframing what the case is actually about

Making this case well means quantifying that tax specifically, not gesturing at it in a single slide with a red-yellow-green risk indicator. What is the actual delivery time delta for new initiatives that have to integrate with the legacy core, compared to a modernized one? What is the run-rate cost of the workaround layer that's accumulated around the legacy system over the years, built specifically to route around its limitations rather than resolve them? What initiatives has the organization quietly not pursued at all, or pursued in a smaller, more limited form, because the legacy constraint made the full version too expensive or too risky to attempt? That last question is usually the most powerful one in an actual board conversation, because it surfaces an opportunity cost that's currently invisible in every budget document the organization produces, precisely because the foregone initiative never got funded in the first place and therefore never generated a line item anyone could point to.

Consider what's actually true in most organizations carrying significant legacy debt: the AI and automation initiatives generating genuine boardroom excitement almost always require clean data flows and modern integration points that legacy systems structurally cannot provide without extensive, expensive workarounds. Every new capability then gets built on top of an increasingly elaborate integration layer designed specifically to route around the legacy constraint rather than resolve it, and each of those workarounds becomes its own maintenance burden and its own point of fragility. The legacy system isn't a risk sitting quietly in the corner, waiting to fail. It's a continuous tax on every subsequent technology investment, paid quietly in slower delivery, higher integration cost, and constrained architecture choices that nobody ever line-items back to the original decision to defer modernization five or eight years earlier.

A path that doesn't require betting the company

Part of why modernization struggles for funding is a false assumption that it requires a single, high-risk, multi-year rewrite — the kind of program that shows up in case studies precisely because it went badly and became a cautionary tale. The lower-risk path, increasingly well documented, is a phased, business-case-led program that addresses the highest-impact systems first, which typically reaches positive ROI in twelve to fourteen months, compared to thirty-six to forty-eight months for a full ground-up rewrite.^[1] Framing the choice as "modernize everything at once or don't modernize at all" is itself part of why the initiative loses funding — it forces a comparison against a growth initiative's much shorter payback period, when a properly phased modernization program can compete on very similar terms.

The honest counter-case

It's worth being direct that not every legacy system deserves modernization investment, and treating this as a universal mandate is its own mistake. A legacy system running a genuinely stable, low-change part of the business, with no roadmap dependency on it and no material security exposure, may be perfectly rational to leave alone and simply maintain, redirecting modernization capital toward the systems that are actually constraining growth. The discipline is distinguishing legacy systems that are quietly taxing the roadmap from legacy systems that are simply old but not actually in the way, and funding modernization for the former without reflexively applying it to the latter just because both are running on outdated technology.

The reframe that actually gets funded

The executives who successfully fund modernization don't win by making the risk case louder in the same meeting where it's lost for the last three years running. They win by making the growth case for modernization instead — reframing it from "reduce our risk of failure" to "remove the constraint currently taxing every growth initiative on this roadmap." That's a fundamentally different budget conversation, competing against a different set of alternatives, and it's the version of the business case that actually gets funded before the system fails at a genuinely bad moment, rather than after. What initiatives has your organization quietly not pursued because of a legacy constraint nobody has ever put a number on?

Juan Vegarra is the author of An Outsider's Playbook (forthcoming). The views here are his own. More essays · Write me