Legacy Modernisation Without a Rewrite
Modernising insurance systems without switching anything off: a new layer on top, twenty old systems still running underneath.

An insurance group of more than twenty carriers, selling 12+ types of cover and quoting 300+ risk types across 50 US states, plus Canada and the EU.
Replacing core systems all at once is extremely risky. Here, pricing rules lived only in old code, payments split across twenty companies, and late data from partners regularly put regulatory deadlines at risk.
- 01Give agents, brokers, partners and regulators one stable interface
- 02Route every payment to the correct company out of 20+
- 03Get pricing rules out of old code and into clear documentation
- 04Meet reporting deadlines even when partner data arrives late or messy
We put a modern layer in front of the old systems — and kept the old ones running until each new part proved itself. Replacement went gradually: one product, one state at a time.
- Step 01Built partner-facing interfaces, with a translator layer to the legacy policy, claims and billing systems
- Step 02Created one shared data model with automated pipelines, checked at the source
- Step 03Ran old and new side by side — each old component switched off only when nothing used it any more

Old and new systems now work together, figures always match, and every number is traceable for regulators. Pricing rules exist as documentation, not just code.
Let’s modernise without a rewrite.
Tell us about your legacy systems. We’ll modernise them step by step — no downtime, no big bang.
