I've been through enough core system selections to fill a small library with RFP responses. Every vendor presentation looks the same. The slides are polished. The demos are rehearsed. The references are hand-picked. The messaging is consistent: their system will transform your bank, modernize your operations, and position you for growth.

After a few of these, you learn to read between the lines. You learn what's not being said.

Here's what core banking vendors don't tell you.

What Core Banking Systems vendors don't tell you

Our implementation timeline assumes everything goes perfectly

The vendor will show you a project plan with clean phases, clear dependencies, and optimistic durations. What they won't show you is what happens when things go wrong. And things always go wrong.

Data migration takes longer than planned. Business requirements change mid-project. Key people leave. Regulatory interpretations shift. The vendor's own resources get pulled to other clients.

I've never seen a core implementation finish on the original timeline. Not once. The question isn't whether you'll slip — it's by how much, and what you'll have to compromise to get back on track.

Our reference clients aren't like you

The vendor will provide references. They'll be glowing. What you won't hear is how those clients achieved their success — often with years of customization, armies of consultants, and budgets far beyond what you're planning.

I always ask references three questions the vendor doesn't want me to ask:

  1. If you could start over, what would you do differently?

  2. What's the single hardest thing you didn't expect?

  3. How much did you actually spend, including everything?

The answers are usually illuminating.

Customization is expensive, but we'll let you discover that yourself

Vendors will tell you their system is configurable. What they mean is: you can customize it. And customization is where the real costs hide.

Every customization adds complexity. Every customization creates maintenance burden. Every customization pushes you further from the vendor's upgrade path. Five years in, you'll have a system that's effectively proprietary, with upgrade costs that rival the original implementation.

The vendors know this. They just won't tell you until you're already committed.

Our architecture is modern, except for the parts that aren't

Every vendor claims modern architecture. Microservices. APIs. Cloud-native. Real-time. The reality is often messier.

Most core systems are layered products built through acquisition. The core ledger might be decades old. The "modern API layer" might be a thin wrapper around legacy code. The cloud deployment might require significant re-architecture you'll pay for later.

I ask to see the actual architecture. Not the marketing diagram. The real one. And I ask about the oldest code still running in production.

You'll own your data, but good luck getting it out

Vendor lock-in is real. Once your data is in their system, structured according to their data model, leaving becomes a multi-year project. The contracts say you own your data. They don't say how hard it will be to extract.

I ask about data portability before signing, not after. I ask to see the schema. I ask about export tools and APIs. I ask what happened to the last client who left.

Our pricing is transparent, except for the parts that aren't

The license fee is just the beginning. Implementation services. Data migration. Integration. Training. Customization. Ongoing maintenance. Upgrade costs. Add-ons. The list goes on.

I've seen banks sign deals based on license pricing, only to discover that the total cost of ownership over five years is three to four times what they modeled.

We'll be your partner, until we're not

Vendor relationships are great when things are going well. When things go wrong — when you have a production outage, a data corruption issue, a performance problem — the partnership dynamic shifts. Suddenly you're dealing with support tickets, escalation paths, and contractual service levels.

The vendor's incentives are not your incentives. They want to minimize their cost of support. You want your system fixed. Those don't always align.

What I've learned

Core vendors are not bad people. They're selling a product, and like any product, it has limitations. The problem is that those limitations only become visible after you've bought.

The only defense is to go in with eyes open. Ask the hard questions before you sign. Talk to clients who aren't on the reference list. Build realistic budgets and timelines. And never assume the vendor's interests are the same as yours.

Because when something goes wrong at 2 AM on a Sunday, the vendor's glossy sales deck won't help you. Only your own preparation will.