Financial Services2 min read

The Core System Contract You Signed Seven Years Ago

Core platform contracts in financial services are long, auto-renewing, and negotiated once. Most firms discover their position ninety days before a renewal, which is ninety days too late.

The core platform is the system the firm runs on. Portfolio accounting, custody interface, policy administration, loan servicing, whichever applies. It was chosen years ago, probably by people who have since left, and the contract has renewed automatically at least once.

Ask three questions and watch what happens.

What is the total annual cost, including modules, users, transaction fees and the professional services that never quite ended? What is the notice period for termination, and when does the current term expire? What would it take to get your data out in a usable form?

Most firms cannot answer any of the three from memory. Many cannot answer them within a week.

Why the position erodes quietly

Core system contracts have a shape that favours the vendor over time, and no individual step in the erosion is unreasonable.

Pricing is per-user or per-transaction, so growth increases cost without any renegotiation. Modules get added mid-term at list price, because you needed them and the vendor knew you needed them. Integrations get built around the platform's quirks, which raises the cost of leaving every year. Staff who understood the original terms leave. And the renewal arrives in an inbox with a notice deadline that has already passed by the time anybody reads it.

Seven years in, you are paying substantially more than you agreed to, you cannot credibly threaten to leave, and the vendor's account team knows both facts better than you do.

Leverage exists, but only early

The single most valuable thing you can do about a core contract is know its renewal date eighteen months out.

At eighteen months you can genuinely evaluate alternatives, and the vendor can tell you are doing it. At six months you can negotiate at the margins. At ninety days you can accept what is offered.

The gap between those three positions is routinely twenty to thirty percent of annual spend, and occasionally much more when a firm has been paying for modules and seats it no longer uses.

What to establish before the conversation

Actual usage. Named users versus active users. Modules licensed versus modules in production. Transaction volumes against the tiers you are paying for. Vendors do not volunteer that you are over-provisioned.

The real total. Licence plus support plus hosting plus the professional services line that has been running for three years plus the third-party components the platform requires. Firms routinely underestimate their core spend by a third because it sits across four budget lines.

Exit cost, honestly. What data comes out, in what format, at what fee, and what would have to be rebuilt. This number is the ceiling on your leverage and you should know it before the vendor calculates it for you.

What the market looks like now. Not to switch, necessarily. To have a defensible reference price and a credible alternative.

The renewal is also a governance moment

A core contract renewal is the one moment where the firm has a natural reason to ask whether the platform still fits. Not whether it works, but whether the constraints it imposes on product, reporting and client experience are constraints you are willing to accept for another five years.

That question rarely gets asked, because renewals are handled as procurement rather than strategy. It is worth asking once per cycle, in front of the people who own the strategy.