The Hidden Cost of Minimum Viable Modernization

TL;DR: Deferring agentic readiness during a legacy modernization project does not eliminate the cost. It converts it into a future project, one that competes for budget from scratch, consumes 18 to 24 months of engineering capacity, and runs at a competitive disadvantage the whole time. The economic case for building it in now is straightforward: the incremental effort during an active project is marginal, and the cost of the alternative is concrete and compounding.

What Gets Decided When Nobody's Looking

Every organization in a legacy modernization project is making a budget decision about 2027. Most of them don't know it.

The scoping conversation that happens in the first weeks of a modernization project determines whether the resulting system can support intelligent automation in two to three years. Those decisions, including how data is structured, where workflow logic lives, how exceptions are handled, and whether the system can be instructed by something other than a human, get made once. They rarely get revisited without another full project cycle.

Most scoping conversations stay focused on the forcing function: the vendor end-of-life, the accumulated technical debt, the maintenance cost that finally broke tolerance. That focus produces a system that solves the problem. It also sets up the next one.

This is the hidden cost of minimum viable modernization. The new system is stable, more secure, and cheaper to maintain. But the infrastructure capable of supporting the AI initiative on next year's roadmap isn't there.

The Decision Has Already Been Made

Here's the relevant economic context: most organizations reading this aren't deciding whether to invest in AI. Gartner research on enterprise AI strategy found that roughly 80% of enterprises fall into the 'Extend' category, using AI to improve operational performance, increase productivity, and create new revenue streams (Source: Gartner webinar, AI Value Creation: Achieving ROI Demands a Labor-based Mindset Shift). Five to fifteen percent are in 'Defend' mode, focused on stability. Five to fifteen percent are in 'Upend' mode, pursuing transformational business change.

The Extend category is the modal enterprise AI strategy. The investment is already planned or already underway. What determines whether it delivers is the infrastructure it runs on. That infrastructure is being decided right now, inside modernization projects that may not realize they are making that determination.

Deferring the architectural decisions that make a system agent-ready doesn't push the cost off the ledger. It converts it into a future project, with a future budget, competing against every other roadmap priority that accumulated in the time between.

Three Factors That Make the ROI Case

Factor 1: The Incremental Cost During an Active Project Is Marginal

The engineering work required to produce an agent-ready system is largely the same work required to produce a minimum viable one. Data architecture is already being redesigned. Workflow logic is already being rewritten. Integrations are already being rebuilt.

The difference is not whether that work happens, but how it gets done.

Designing data with ownership, consistent definitions, and usable structure adds marginal effort to work already underway. Separating workflow logic from business logic is a design decision made in the same pass as the rebuild. System interfaces get defined during integration work whether or not they are designed to be extensible.

There is one additional factor that has changed the economics of this decision over the last two years. Modernization projects have historically defaulted to minimal scope partly because the assessment phase was expensive. Cataloging what existed, reverse-engineering undocumented codebases, reconstructing business logic from systems no one fully understood, that required significant time and budget before any new system could be built. AI has compressed that phase meaningfully. The cost of scoping beyond the forcing function is lower now than it has ever been.

Factor 2: The Cost of a Third Modernization Cycle Is Concrete and Compounding

An organization that completes a modernization project without building for agentic readiness and then launches an AI initiative on that infrastructure faces a specific, predictable sequence.

The AI initiative encounters the same constraints the legacy system had. The data isn't in a state where models can use it. The workflow logic is in the application; changing it requires a rebuild. The system wasn't designed to be instructed by an agent. A third modernization cycle goes on the roadmap.

That cycle means 18 to 24 months of engineering capacity spent rebuilding infrastructure rather than delivering capability. It means a new budget competing with every other priority on the roadmap, including the AI initiatives the current system can't support. It pulls leadership attention back into a problem the organization believed it had solved.

It also means operating at a disadvantage for the full duration of that work.

Gartner's value model makes the sequence explicit. Agility, created by refactoring technical and process debt, sits at the foundation. Every layer of business value depends on it. Delay the foundation and everything above it is delayed with it. The cost isn't just financial. It's time, attention, and competitive position, compounding for every quarter the organization operates on infrastructure that can't support the AI investment already committed.

Factor 3: The People Funding AI Are Not in the Scoping Room

According to Gartner data, 47% of AI initiative funding now flows from outside IT. Business unit and function budgets account for the single largest share at 34%. In many organizations, the leaders committing capital to AI outcomes in year two and year three aren't in the room where the modernization scope is being set right now.

That is the mechanism by which projects undershoot. A COO or business unit leader funds an AI initiative. An IT-led scoping conversation, focused on the forcing function, produces infrastructure that can't support it. The scope decision and the AI investment decision get made in separate rooms by separate people, with no shared view of what one requires from the other.

An AI initiative funded by a business unit leader, built on infrastructure that can't support it, will not deliver what it was funded to deliver. The modernization project underway right now is the moment to fix that. The fix belongs in the scope conversation.

The Competitive Dimension

The 80% of enterprises in the Extend category are not waiting. They are actively building on modern, agent-ready infrastructure, using AI to improve operational performance, increase productivity, and create new revenue streams.

The gap between organizations already running on agent-ready systems and those still building the foundation shows up in specific, operational ways: faster response to market changes, more accurate pricing, fewer people required to execute the same transaction volume. Competitors who respond faster, price more accurately, and operate with fewer people in the loop win deals. The gap shows up in margin and cycle time before it shows up anywhere visible.

The organizations still building the foundation when their competitors are already running on it will find the gap harder and more expensive to close than it would have been to prevent. That is not a speculative concern. It's the predictable arithmetic of a third cycle running in parallel with a competitive market that didn't pause.

What It Costs to Find Out Later

The conversations that surface 18 months after a modernization project closes are consistent across industries and organization types:

"The data is there, it just is not in a state where we can use it."

"The logic is in the application. To change it, we would basically have to rebuild it."

"We can build that integration, but it is going to be a bigger lift than it should be."

These aren't failures of execution. The team delivered against the defined scope. Nobody asked it to solve for 2027.

The cost of minimum viable modernization isn't visible on the day the new system goes live. It surfaces when the AI initiative the organization committed to funding can't run on the system the organization just built, and the only path forward is reopening a completed project, competing for budget from scratch, and pulling an engineering team back to infrastructure work they thought was behind them.

The Questions That Put a Number on It

For organizations currently in or approaching a modernization project, three questions make the economic case concrete:

What is the labor cost of manual exception handling in the workflows being modernized? Every exception that gets handled by whoever is on shift is a cost that agent-ready architecture would eliminate. That's a number. Put it on the table.

Is there an AI initiative on the roadmap for the next 12 to 24 months that depends on data, workflow, or infrastructure this project will touch? If the modernization produces a minimum viable outcome, does that initiative still work? If the answer is no, the cost of the gap is the cost of the AI initiative, plus the third cycle required to close it.

What would a third modernization cycle cost, and what would it displace? 18 to 24 months of engineering capacity has a number. A new budget cycle competing against existing roadmap priorities has a number. The AI initiatives that can't launch during that window have a number. Add them up and compare to the marginal incremental effort required now.

The organizations that answer these questions before the scope locks tend to make different decisions than the ones that answer them in the post-mortem.

Back to Part 1: Most Legacy Modernization Projects Set Up a Third Cycle. Here's Why.

Back to Part 2: The Five Architectural Decisions That Determine Whether AI Can Run in Your Systems

Up next in this series: Six Questions to Ask Before You Lock the Scope of Your Modernization Project—the business case builder framework for COOs, CTOs, and Heads of Operations making the internal argument for expanded scope.

Want to put a number on the gap in your current modernization project? Book a strategy session with a Sparq architect.

Part 3 of 4 in Sparq's series on Legacy Modernization and Agentic Readiness.