Field Notes
Banks in the $500M–$10B asset range live in a squeeze: fintech expectations on the customer side, examiner expectations on the risk side, and a technology estate built for neither. The temptation is to buy a way out — a new core, a new digital banking vendor, a new data platform. The pattern we see instead is that the winners fix the operating model first and let the technology follow.
The phrase “core modernization” hides three separate problems. The first is the core itself — usually stable, usually fine. The second is the accumulated middleware around it — batch files, point-to-point integrations, a message bus from 2009 — which is where the fragility actually lives. The third is the operating model that grew around the limitations of the first two: manual reconciliations, swivel-chair onboarding, product launches that take a fiscal year.
A Transformation Sherpa attacks them in reverse order. Operational fixes generate savings and credibility in the first quarter. An API wrapper around the core decouples new work from the core’s release calendar in the second. Only then does the question “replace or strangle the core” get answered — with a dependency map on the table instead of a vendor deck.
The regulatory dividend
Everything above happens inside an exam cycle. That’s not a constraint to route around; it’s the moat. A mid-market bank that can ship modern onboarding and produce model-governance evidence on demand is genuinely hard to compete with. We design programs so the audit trail, the data lineage, and the decision logs accumulate automatically — compliance as exhaust, not as a project.
Who leads it
This work needs someone who has sat in the CIO chair at a bank, taken an exam finding personally, and shipped through it anyway. That’s what the Sherpa network is for: fractional executives who have done this exact climb before, embedded with your team two to three days a week, gone in a year — leaving behind a bank that ships.