Market Vision Paper

Modernization has reached its tipping point: Choose architecture over arbitrage

This Market Vision Paper is for CIOs, CTOs, and enterprise architecture leaders evaluating how to escape code-heavy operating models that inflate tech debt and stall AI-driven transformation.

Executive summary

New research serves as a wake-up call for CIOs and CTOs bleeding budget on implementation.

Enterprise transformation isn’t short on software; it’s weighed down by code sprawl and the ecosystem built to maintain it. Each new bespoke line of code adds a maintenance tail that inflates services spend and tech debt, pulling budgets into integration and upkeep while innovation waits. That strain on IT increases reliance on systems integrators and crowds out software-led change. Artificial intelligence (AI) will compound the problem if it simply generates more code on legacy stacks; however, used within guardrails to refactor, standardize, and assemble governed components, it can reduce tech debt. The current operating model must evolve.

HFS Research, in partnership with Unqork, surveyed 123 large enterprises to understand IT budgets, services-to-software ratios, systems integrator (SI) relationships, AI adoption, and governance patterns. The survey uncovered:

    • Services dominate multi-year transformation and modernization spending. Over 70% of transformation budgets are allocated to implementation, maintenance, and integration—not to new software or innovation. These services costs outpace innovation spending by 2x to 7x.
    • Tech debt is skyrocketing, driven by poor code quality (83%), skill shortages (80%), over-reliance on SIs (77%), and sprawling custom code (76%). AI is compounding the challenge, with 43% of enterprises already seeing it create new debt.
    • Additionally, of the leaders surveyed,

Four-panel stat callout row highlighting key findings from the survey. Panel 1: 86% say technical debt blocks strategy. Panel 2: 97% of business units inside enterprises want to build in parallel with IT departments. Panel 3: 84% expect AI to lower costs, yet 43% already see it creating new tech debt. Panel 4: 98% would adopt Services-as-Software™ under the right terms. Source: HFS Research, 2025.

The Bottom Line: As enterprises generate more “AI-assisted” code, they find themselves in an operating model with unintended consequences, such as runaway maintenance costs and increasing tech debt. IT is overwhelmed maintaining the systems they currently run while business leaders demand more, faster from them. Simultaneously, the C-suite is applying mounting pressure for AI implementation—not just pilots, but production with real return on investment.

The way through is a shift in models and architectures. IT needs to flip the services ratio and move from projectized services to productized outcomes in architectures that minimize customer code creation, maximize reuse, and embed governance so that AI reduces, rather than creates more tech debt.

The ecosystem is ripe for change

Only 18% of large enterprises’ transformation spending is allocated to software, while 58% of organizations dedicate over 70% of their three-year transformation budgets to services. Most spend 2–7x on services for every $1 of software; a $1 million software license can become a $2 million to $7 million total commitment after services and maintenance (see Exhibit 1). This erodes ROI, crowds out innovation, and compounds a “keep-the-lights-on” doom loop.

Exhibit 1: Transformation budgets skew to maintenance and services fees vs. software-led innovation

A side-by-side pair of horizontal bar charts, based on a sample of 123 decision makers across Global 2000 organizations. The left chart answers the question "Over a typical three-year period, what is the services-to-software cost ratio for major IT transformation projects in your organization?" Results: mostly services (more than 70%) at 58%, roughly equal (50%/50%) at 21%, mostly software (more than 70%) at 18%, and don't know at 3%. The right chart answers "For every dollar spent on software licenses, how much is spent on related services (implementation, integration, etc.)?" Results: $1 or less at 3%, $1 to $3 at 43%, $4 to $6 at 35%, $7 to $9 at 11%, $10 or more at 5%, and don't know at 2%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

Enterprises should avoid software that demands a standing army of engineers to keep it running. Reorient internal IT and systems integrators toward innovation, not perpetual upkeep, by standardizing on architectures where costs decline with scale through reusable components and pre-built integrations. The era of labor arbitrage has run its course; squeezing rates didn’t reduce code and architecture complexity, and now enterprises are constrained by the architecture and ecosystem built to maintain it.

Technical debt is a self-inflicted bottleneck

Technical debt, or tech debt, is the cumulative cost, risk, and effort required to operate, secure, and evolve what’s already been built. While verifiable data to quantify tech debt is scarce, some estimate that global tech debt exceeds $1 trillion. Leaders surveyed cite both human and structural drivers of tech debt: poor code quality (83%), skills gaps (80%), over-reliance on systems integrators (77%), custom code proliferation (76%), and missing standards (74%). Most, 86%, of respondents say technical debt blocks strategic goals. Only about a third of code is reused, while two-thirds is rebuilt. In short, code is a liability class, as every new line of code created adds a maintenance and risk tail (see Exhibit 2).

Exhibit 2: Technical debt has become endemic, and it’s not improving

A three-part exhibit based on a sample of 123 decision makers across Global 2000 organizations. The upper left is a donut chart showing that 86% of respondents consider technical debt a hurdle to achieving their organization's strategic goals. The lower left is a donut chart showing the percentage of the code base that is reusable across applications, with an average of 33.17%: 0 to 10% at 2%, 10 to 15% at 7%, 15 to 25% at 29%, 25 to 50% at 39%, and 50% or more at 24%. The right side is a stacked bar chart showing the top contributors to technical debt, broken into "Strongly agree" and "Agree" responses for 13 factors: skills shortages (54% strongly agree, 26% agree), lack of architecture standards (45%, 29%), quality of code (42%, 41%), custom code created (42%, 34%), legacy architectures (41%, 31%), high SI dependence (41%, 36%), AI-generated code (37%, 24%), overlapping tools and platforms (35%, 34%), pressure to deliver fast (34%, 34%), runtime environments (32%, 32%), poor platform selection (29%, 33%), long vendor contracts (26%, 25%), and no clear ownership or roadmap (25%, 23%). Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

It’s a tremendous amount of effort, these things cut out all the time…I consider it, in my view, sort of friction. That friction costs teams, and it’s a lot of effort to upgrade, patch, and run maintenance.

— CIO, federal wholesale bank

Simultaneously, businesses are demanding more from IT, and for some, with the right platforms and tools, citizen development is now a strategy. Nearly all (97%) business units want to build in parallel with IT. Sales and marketing (51%), data and analytics (45%), and business operations (44%) show the highest desire for this empowerment, reflecting that traditional IT delivery speeds are not fast enough. This creates the risk that business units will attempt to do it themselves or create shadow IT (see Exhibit 3).

Exhibit 3: Business units would like to build apps in parallel with IT

A vertical bar chart showing the percentage of 123 Global 2000 decision makers whose business functions or areas want to create their own solutions without IT involvement. Results: sales and marketing at 51%, data/analytics/BI at 45%, business operations at 44%, HR or talent management at 36%, customer service or support at 31%, legal and compliance at 17%, and none of our functions or business areas have requested this at 3%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

The widespread desire for business to build apps in parallel with IT indicates that traditional governance structures no longer meet business needs for speed and flexibility. It’s not a tooling problem. It’s a model mismatch where current approaches cannot reconcile speed with scale. This compounds the possibility of shadow IT and creates a governance gap if proper guardrails are not implemented to harness this trend.

We need to be agile as a business, so it’s really looking for digital enablers that can help cross the silos of our teams to really speed up how our business responds to work.

— Head of Strategy & Operations, global banking major

The only scalable answer is sanctioned, governed self-service through platforms, with policy-as-code, cataloged components, and deep observability. Enterprise buyers must implement a control tower that governs architecture, data, security, and reuse; define a standard taxonomy for components; and demand reference patterns for integration from vendors. Success must be measured by faster business delivery and declining tech debt indicators, such as a services-to-software ratio trending downward, a reuse percentage trending upward, fewer one-off integrations, higher test coverage via platform tools, and a reduction in maintenance costs.

The SI model has evolved from maintenance to platform enablement

Drowning in tech debt, with more requests than ever, enterprise IT has traditionally turned to systems integrators for lower costs and support to maintain their code-heavy models. In addition to expertise, systems integrators brought an opportunity for labor arbitrage through offshoring. They are often pulled into maintaining the status quo because incentives and architectures favor maintenance over reuse. In a maintenance-weighted model, many relationships feel transactional and maintenance-oriented, rather than transformational—a real Catch-22 for systems integrators.

Exhibit 4: Systems integrators are necessary partners in a maintenance-weighted model

A vertical bar chart showing how satisfied 123 Global 2000 decision makers are with their current system integrators. Results: extremely satisfied at 20%, satisfied at 33%, neutral at 30%, dissatisfied at 13%, and extremely dissatisfied at 3%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

The survey data reflects that satisfaction with SIs is tepid (only 20% of decision makers are “extremely satisfied”). Roughly a third of engagements end without a satisfied outcome, often prompting partner changes (see Exhibit 4). Meanwhile, 58% say the traditional SI model will be unsustainable within five years, and 76% want integration bundled with software, indicating a preference for integration and governance to be bundled into the product, rather than the traditional two-step model of “buy software, then hire an SI” (see Exhibit 5).

Exhibit 5: Enterprises want systems integration capabilities and governance built in

A set of three vertical bar charts, each answering a yes/no or three-option question, based on 123 Global 2000 decision makers. Left chart: "Have you ever chosen to permanently discontinue the relation with a system integrator due to a poor or failed engagement?" Yes at 33%, no at 67%. Center chart: "Do you believe the current system integrator model is sustainable over the next five years?" Yes at 29%, no at 58%, not sure at 13%. Right chart: "Would you prefer to have systems integration capabilities included in the software licensing costs?" Yes at 76%, no at 24%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

Systems integrators remain essential, but the value is shifting upstream to design standards, reusable patterns, and platform enablement with less bespoke delivery and more productized outcomes. The market is moving from project delivery to packaged outcomes. As enterprises look to vendors that help reduce the bespoke code they generate, maintenance requirements will decrease, and the integrator’s role in the enterprise IT ecosystem will evolve accordingly.

The double-edged AI sword amplifies promises and accelerates peril

The AI tech debt paradox

If AI is primarily used to generate more bespoke code on legacy stacks, it amplifies maintenance and accelerates the creation of tech debt. Deployed inside guardrails, AI can refactor, standardize, and assemble governed components, lowering run costs and debt while improving speed. If not implemented strategically, AI presents a paradox of promise and peril for software development. Organizations show the highest confidence in AI’s ability to reduce costs (84% agreement) and automate processes (80% agreement). Yet, 43% acknowledge that AI may create more tech debt, which ultimately increases costs.

Less than half of organizations (48%) believe AI will replace offshore teams, suggesting that organizations recognize AI will augment rather than replace human expertise. This recognition, combined with 77% of respondents believing AI empowers non-technical users, indicates that AI could be creating new dependencies rather than eliminating old ones (see Exhibit 6).

Exhibit 6: AI promises cost savings while threatening a new technical debt crisis, if it is not implemented strategically

A stacked horizontal bar chart showing responses from 123 Global 2000 decision makers to the question "Which of the following do you agree with regarding AI's impact on software development?" using a five-point scale from strongly agree to strongly disagree. Results by statement (strongly agree and agree combined): accelerates development and deployment (48% strongly agree, 32% agree, 17% neutral, 3% disagree), reduces reliance on SIs (30%, 40%, 25%, 2%), lowers operational cost (41%, 43%, 13%, 3%), improves quality/performance (37%, 28%, 24%, 10%, 2%), enables smart automation and analytics (43%, 37%, 16%, 3%, 2%), empowers non-technical users (35%, 42%, 18%, 2%), can replace traditional offshore teams (21%, 27%, 22%, 19%, 11%), creates more tech debt (21%, 22%, 40%, 17%). Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

The risks are equally clear: 43% anticipate AI creating new debt, 37% expect hard-to-maintain code, and the top concerns are security (59%), legacy integration (50%), and loss of visibility (42%). In the long term, sentiment splits, with 55% of respondents believing AI will reduce tech debt, while 45% anticipate an increase (see Exhibit 7).

Exhibit 7: AI may amplify developer productivity, and with it, new governance and maintenance challenges

A two-part exhibit based on 123 Global 2000 decision makers. The left side is a donut chart showing sentiment on AI's long-term impact on tech debt: 55% believe AI will reduce tech debt, while 45% believe it will increase tech debt. The right side is a horizontal bar chart showing the expected role of AI in software development over the next three years. Results: improving productivity of experienced developers at 52%, accelerating prototyping and experimentation at 43%, reducing reliance on systems integrators at 40%, empowering non-developers to build software at 38%, generating code that is hard to audit or maintain at 37%, replacing junior developers to reduce cost at 29%, replacing human developers at 26%, creating more tech debt faster than ever before at 24%, eliminating the need for offshoring at 18%, and minimal role (not planning to use it) at 4%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

The traceability of AI-authored changes and platform-generated tests, as default artifacts, must be a table stake in evaluating vendor offerings, and compliance controls must be embedded. Enterprises must use AI to assemble, refactor, and test governed components, rather than generating bespoke code. Platform-level policy checks and automated documentation must be built in—not bolted on.

Remember, without proper governance, quality controls, and architectural discipline, AI risks becoming the next generation’s technical debt crisis, where today’s shortcuts become tomorrow’s expensive remediation projects.

Enterprises are ready to offload legacy under the right conditions. With an outdated approach to transformation and more budget and resources tied to an ecosystem geared toward never-ending maintenance, the market stands ready for a fundamental shift in how legacy systems are managed.

Nearly all (98%) of decision makers surveyed are ready to offload legacy to a Services‑as‑Software model (buying outcomes where integration, operations and governance are features of the product, not separate projects) under the right terms: prioritizing AI‑enabled management (69%), quality (61%), and security (57%) ahead of pure cost reduction (42%).

This preference suggests organizations want to overcome legacy burdens by enhancing capabilities rather than solely pursuing cost arbitrage. That’s a mandate to buy outcomes with integration, governance, and reuse built in—precisely the lever that could help flip the services ratio and contain tech debt (see Exhibit 8).

Exhibit 8: Under the right terms, a Services-as-Software model is positioned to reshape the legacy software market

A horizontal bar chart showing the conditions under which 123 Global 2000 decision makers would offload all their legacy software to a Services-as-Software model. Results: it is AI-enabled at 69%, deliver higher quality at 61%, it is more secure and compliant at 57%, it accelerates modernization/transformation at 53%, someone could do it cheaper at 42%, and I would not do it at 2%. Source: HFS Research, 2025.

Sample: 123 decision makers across Global 2000 organizations
Source: HFS Research, 2025

Evolving the operating model

The research is unambiguous: Current models consume budgets, slow delivery, and harden tech debt, just as AI raises the stakes. The escape is a new operating model—Services-as-Software—a governed architecture that minimizes custom code and maximizes reuse, and AI applied within those guardrails to accelerate safely.

To make this shift, enterprises must:

  • Transition from services-heavy delivery to Services-as-Software, bundling integration and operations into the platform to productize outcomes.
  • Meet the demand for businesses to build apps with IT‑set guardrails for data, security, integration, and reuse, bringing “shadow” into the light.
  • Design for reuse. Treat 33% reuse as a floor to beat, and raise code reuse with governed, versioned components to cut rebuild, risk, and run costs.
  • Use AI to refactor, standardize, document, and test within a governed platform, so it reduces debt instead of creating it.

Partner with vendors that bundle integration, enforce governance through architectures that minimize or eliminate code sprawl, and use AI to standardize, refactor, and test to reduce the services multiplier, compress run spend, and avoid the next wave of technical debt.

The Bottom Line: Code generated in the enterprise—by both humans and AI—requires maintenance, which increases service costs and compounds tech debt.

Transformation is stymied by the status quo: an ecosystem built to manage the maintenance burden of infinite code creation, not innovation. What’s needed is a new model that rewrites the economics of transformation to unlock innovation, embrace AI responsibly, and accelerate development without compounding cost and adding complexity.

Enterprises must pivot now to upend the status quo and help evolve an ecosystem that prioritizes code maintenance:

  • Avoid buying software that requires a standing army of services to function.
  • Mandate integration-included models with enforceable reuse ratios.
  • Use AI within platforms that constrain complexity rather than multiply it.

Flip the spending, shrink the surface area, and demand outcomes instead of buying obligations. This is how transformation becomes sustainable.

Sign in to view or download this research.

Login

Register

Insight. Inspiration. Impact.

Register now for immediate access of HFS' research, data and forward looking trends.

Get Started

Download Research

    Sign In

    Sign up for a free
    research account

    With the exception of our Horizons reports, most of our research is available for free on our website. Sign up for a free account and start realizing the power of insights now.

    By registering you agree to our privacy policy.

    I hereby consent that HFS Research can process my personal data.

    Digests/Newsletters: Overviews of the latest news, insight, and research by HFS.

    HFS Events: Exclusive invitations to HFS webinars, roundtables, and summits, bringing together key industry stakeholders focused on major innovations impacting business operations.

    Premium Access

    Our premium subscription gives enterprise clients access to our complete library of proprietary research, direct access to our industry analysts, and other benefits.

    Contact us at [email protected] for more information on premium access.

      Contact Ask HFS AI Support