PRESENTED BY JACK HENRY

How Infrastructure Is Changing and the Choice You Face

Financial services technology is no longer evolving along a single, steady path. It’s diverging.

Banks now operate in a landscape where the underlying infrastructure they choose will directly determine how quickly they can respond to market shifts, adopt new capabilities, and deliver the experiences customers expect.

What was once a question of technology modernization has become something more fundamental: what kind of future you’re building toward, if any at all.

Three Paths—Three Futures

Today, the available infrastructure choices roughly fall into three camps. Each reflects a different philosophy about risk, investment, and control.

1. Technology without a long-term future.
2. Bolt-on technology that’s not fully integrated.
3. Modern technology with built-in optionality and a future-proof path.

1. Technology Without a Long-Term Future

Running Out of Runway

Some core technologies are no longer being meaningfully advanced. They’re just being maintained.

This category is often described as “legacy,” but that understates the issue. These are systems that are approaching the limits of what their architecture can support. They were built for a slower, more predictable environment with fewer integrations, limited capacity, lower customer expectations, and less pressure to adapt in real time.

That mismatch is becoming impossible to ignore.

In these environments, change is difficult. Systems are closed. Enhancements take time and cost more than expected. Even small updates require coordination across aging dependencies. As a result, innovation doesn’t feel like forward motion; it feels like disruption.

The more in-depth problem, however, is not operational friction. It’s the absence of meaningful reinvestment. Often, there’s no clear or credible path to modernization. Instead, financial institutions encounter incremental fixes, partial upgrades, and messaging that implies progress without delivering structural change.

You can easily identify true “legacy” infrastructure by simply asking vendors:

1. How much are you investing in the technology in dollar terms?
2. How many new lines of code have you added in the last 12 to 18 months?

The answers should tell you exactly what you need to know.

Vendors in this category often rely heavily on narrative. They talk about transformation, repackage existing capabilities, and signal evolution through announcements rather than actual advancement. The intent is to reassure. But reassurance isn’t the same as progress. You can’t build the future on a foundation that is no longer evolving.

Under the surface, the limitations remain. These platforms struggle to support modern integrations. They’re difficult to extend without introducing risk. And every attempt to layer new functionality puts additional strain on an environment that wasn’t designed to support it.

This leads to a familiar outcome. The longer financial institutions stay on these platforms, the more constrained they become. Costs rise as maintenance grows more complex. Change slows as dependencies accumulate. The gap between what the platform can do and what the market demands continues to widen.

The Bottom Line

What appears to be stability is often just inertia.

Financial institutions sticking with something built for the past increasingly risk hitting a dead end. In today’s fast and adaptable world, holding onto that position is unsustainable.

2. Bolt-On Technology That’s Not Fully Integrated

Risks With an Illusion of Progress

In response to legacy constraints, many banks have taken a different approach. Instead of replacing foundational systems, they bolt new infrastructure onto them.

At first, this feels like momentum. New capabilities can be introduced more quickly. Digital experiences improve. Specific gaps get filled. But over time, this approach reveals its trade-offs.

What emerges is not unified infrastructure but a Frankenstein-like hodgepodge of solutions: a new digital layer here, a separate lending platform there, and a payments solution introduced to meet specific needs. Each component may serve a purpose, but they’re not deeply integrated into a shared architecture.

This fragmentation shows up in the user experience. Customers encounter processing lags and inconsistencies across channels and products. Internal teams work across disconnected workflows. Data doesn’t flow cleanly from one system to another, requiring additional effort to reconcile, interpret, and act on it.

Risky “Side Core”

Behind the scenes, the architecture becomes increasingly fragile and complex. Many organizations introduce “side cores”—standalone platforms designed to deliver a specific capability quickly. These systems operate adjacent to the primary core, rather than within it.

Side-core architectures often create parallel systems of record. Data is duplicated across environments. Business logic is replicated. Processes that should be unified become distributed and harder to manage. Each new system adds capability but also risk and coordination cost.

Initially, the benefit is speed. Financial institutions can bring a specific product or feature to market more quickly than they could within the constraints of their core system. But that speed is localized. It applies to the first implementation, not to the broader infrastructure.

As more solutions are added, complexity compounds. Each integration introduces new dependencies. Each vendor increases operational overhead. Each data handoff becomes another potential point of failure and/or UI/UX speed degradation. What starts as a shortcut to move faster often becomes the very thing that holds you back.

Over time, this model begins to slow the organization down. Teams spend more time managing connections than creating value. Changes require navigating an increasingly intricate web of systems. What once felt like flexibility starts to feel like fragmentation.

The cost is not only technical. It’s strategic. Innovation becomes harder to coordinate. Scaling new capabilities across the enterprise becomes more difficult. The organization is forced to work around its architecture rather than through it.

The Bottom Line

Bolt-on approaches can deliver short-term wins, but introduce long-term constraints.

The system appears modern on the surface but is increasingly fragile underneath—more expensive to maintain, harder to scale, and more difficult to evolve with confidence.

3. Modern Technology With Built-In Optionality

A Bridge to the Future, Not a Flimsy Workaround

The third path takes a fundamentally different approach.

It doesn’t assume you must replace your existing foundation. Nor does it attempt to work around it. Instead, it starts from a more practical and more powerful premise: your core infrastructure remains central to your bank. Moreover, it must continue to evolve through ongoing investment, not be sidelined by parallel systems.

A bolt-on “side core” works beside your system, while a modern platform works within and through it.

In this model, modernization happens through deep, intentional integration, not separation.

Modern platforms with built-in optionality act as a true extension of your foundational technology, fully connected to it and designed to enhance it over time. They don’t create a second system to manage. They don’t introduce a competing source of truth. They become part of how your core environment operates.

Optionality Without Disconnection

At the center of this approach is optionality: the ability to move in multiple directions without being constrained by your technology.

You can adopt new capabilities, bring in fintech collaborators, and respond to shifting market demands as they happen. But unlike bolt-on strategies, you do this without fragmenting your environment. There are no parallel data structures to reconcile, no duplicated workflows to manage, and no need to stitch together disconnected systems after the fact.

Every new capability operates in alignment with your core, drawing from the same data, participating in the same processes, and contributing to a unified experience.

This is what makes continuous transformation possible. Change is no longer disruptive because it doesn’t happen outside the system. It happens as part of it.

Integrated by Design, Not Forced Together

The failure point of most modernization efforts is not ambition—it’s integration.

Bolt-on architectures rely on connecting separate systems after they have already been built. That approach inevitably introduces friction: data must be synced, logic must be duplicated, and gaps must constantly be managed. And perhaps more crucially, it translates into deep operational inefficiency, blocking any efficiency gains made elsewhere—gains that all financial institutions must make to remain viable in the era of automation and AI.

You’re not managing connections between systems; you’re extending the system you already trust.

Modern optionality platforms eliminate this problem by starting with integration as a design principle. They’re built to operate in context with your core from the outset, not be connected to it later through layers of middleware and workarounds.

The result is a system where data flows naturally, workflows remain intact, and experiences are consistent because they’re all anchored to the same foundation.

Innovation Anchored to a Living Core

A critical part of this model is the recognition that the core itself is not static. It’s continuously updated, enhanced, and invested in.

Modern platforms don’t replace that evolution; they accelerate it.

Because they’re tightly integrated, they allow banks to introduce advanced capabilities—such as real-time data access, AI-driven insights, and intelligent automation—directly into the operational fabric of the organization. These capabilities don’t sit outside the system waiting for synchronization. They operate on live data in seamless workflows, where immediate decisions are made.

This creates a powerful effect. Innovation is no longer something that must be layered on top of the core or routed around it. It becomes part of how the core functions every day.

From System of Record to System of Possibility

When integration is done this way, the role of technology begins to shift.

The core is no longer just a system of record. It becomes the foundation of a broader platform that supports an evolving ecosystem of capabilities and vendors without losing cohesion.

Banks can connect to fintechs, embed services into external experiences, and quickly bring to market new innovations—such as tokenized money that bridges fiat and on-chain monetary systems (stablecoins, tokenized deposits, deposit tokens). But they do so without giving up control of their data, their workflows, or their vendor relationships, because everything remains grounded in a unified infrastructure.

This is what separates optionality from complexity. It allows financial institutions to expand outward without creating fragmentation inward.

Scale That Strengthens, Not Strains

In most architectures, scale introduces stress. Every new integration adds overhead. Every new capability increases maintenance.

In an optionality-driven model, the opposite is true.

Because integration is already built into the system, adding new capabilities doesn’t create new silos or duplicate effort. Data remains consistent. Processes remain aligned. Operational burden doesn’t compound with each addition. The more you add, the more cohesive it becomes, rather than more fragile.

Over time, the platform becomes more capable without becoming more complicated. Growth strengthens the system instead of destabilizing it.

The Bottom Line

This is not a side system. It’s not an overlay.

It’s not a temporary bridge between old and new. Not only that, but it’s a fully integrated extension of a continuously evolving core that allows you to modernize without fragmentation, innovate without disruption, and scale without accumulating complexity.

It delivers something the other approaches can’t: the ability to move forward without leaving your foundation behind.

And in a market defined by constant change, that ability is more than technical. It’s strategic.

The Choice Ahead

Every financial institution is already operating within one of these models, whether by design or by default. The question isn’t whether change is needed; it’s whether the current foundation can support it.

Remaining on technology that’s no longer evolving limits what’s possible. Relying on bolt-on strategies introduces growing complexity over time. But moving to a platform built for optionality and continuous evolution opens the door to continuous progress.

The future for banks will not be defined by any single feature or product. It will be shaped by how quickly they can adapt.

Modern technology isn’t just an upgrade. It’s a shift in how systems are designed, how ecosystems are built, and how innovation happens. And in that environment, optionality is not a luxury. It’s the advantage that determines who moves forward and who falls behind.

You face pressure from every direction, from generational change and fintech disruptors to emerging models like tokenized money.

Discover where opportunity is taking shape and how you can adapt faster, invest smarter, and compete with confidence in the 2026 Strategy Benchmark.