Core modernization programs routinely run past their original timeline. An eighteen-month plan stretching past two years isn't unusual.
Vendor scoping issues surface mid-project, while regulatory sign-off adds another delay. Each one pushes go-live back further. The client experience stays frozen for the length of the program. Nothing changes until the new core is live, and that date keeps moving.
Meanwhile, competitors that keep shipping on their existing systems don't pause growth to replace their core first.
What gets lost during the wait is harder to see on a project tracker: clients and deals that went to a competitor who kept moving.
The reason isn't one bad vendor
Three core providers, FIS, Fiserv, and Jack Henry, serve more than 70% of U.S. banks, according to the Federal Reserve Bank of Kansas City. Many of those banks run on core systems designed in the 1980s and 1990s, according to McKinsey & Company. At that scale, a core replacement rarely lands on the schedule it started with.
It's tempting to pin an eighteen-month plan that runs to month twenty-six on the vendor who hit the scoping issue, or the regulator who added the sign-off delay. In reality, neither one is the real cause.
A core system touches every account the bank runs, retail and commercial alike, and every product built on top of it: deposits, lending, payments, trade finance. Replacing it means remapping and recertifying all of that at once, with every regulator who has a stake in any part of it. Any vendor would hit the same scope-discovery and sign-off delays at this scale. The size of the task causes them, not a poorly run project.
The crossroads every transformation roadmap hits
A core replacement rarely lands on schedule. That forces every transformation roadmap into the same choice: keep the plan waiting on a core that keeps slipping, or start modernizing around it now.
The former bets everything on the core, creating a journey similar to this:
- Year one is spent on vendor selection and scoping, with a steering committee and a program budget, but nothing that a client or a banker touches changes yet.
- Year two is data migration and integration testing, but still nothing changes.
- By year three, if the regulatory sign-off holds, the bank runs the old and new cores in parallel for months before the actual cutover.
The program gets funded as a single line item, and every other initiative waits for it to land. The bank asks its board and its clients to wait for a go-live date that keeps moving. Until that date arrives, the RM's daily experience looks exactly the same as it did on day one.
The latter path leaves the core exactly where it is. It keeps doing the one job it's good at: processing transactions and keeping the books. Nothing about it needs a vendor migration or a regulatory recertification, because nothing about it changes at all.
The coordination work happens somewhere else entirely: in a layer built above the core, connecting credit, treasury, payments, and service into one view a commercial banker sees. That layer can start with one connection, the one causing the most pain for the RM right now, and go live in weeks rather than years. There's no cutover weekend and no parallel run, and each connection that ships makes the next one land faster, because the layer above the core keeps growing while the core underneath never has to move at all.
Progressive modernization, without touching the core
Don't wait for a core replacement to modernize. Build the connection above the core, one commercial journey at a time, while the core keeps doing the one job it's already good at. Connect one function at a time, instead of replacing the core outright. Each connection made makes the next one easier.
For a commercial bank, that means picking a real, specific pain point, such as the FX exposure number a treasurer keeps calling about, or a payment status a client wants tracked. The next step is building one connection above the core first to address the issue. Prove it works, then do the next one.
That's the difference between a transformation program and a transformation. The former waits for a finish line that keeps moving, while the latter delivers one proven piece at a time, with the core exactly where it's always been.
