A twenty-year-old claims system was replaced one capability at a time, with old and new running side by side until the legacy platform had nothing left to do.
The challenge
The claims platform at a property and casualty insurer predated most of the people who maintained it. A full replacement had been scoped, priced, and shelved three times; the business could not accept a cut-over weekend on a system that pays policyholders after the worst day of their year.
Our approach
We mapped the platform into capabilities and sequenced them by risk and value. Intake moved first—a new front end writing to both systems—followed by adjudication and then payments. Each slice ran in production for a full cycle before the legacy path was retired. Rollback was rehearsed for every release and used once.
What we built
- A capability map and sequenced roadmap, agreed with operations
- New intake, adjudication, and payment services behind an API layer
- Dual-write and reconciliation tooling for the transition period
- Observability across legacy and new paths from the first release
- Knowledge capture from the two engineers who understood the original code
What changed
- No cut-over weekend, no freeze on new claims, and no big-bang risk
- Each slice funded the next with capacity released from the legacy system
- The estate is documented for the first time in its history
This engagement is representative of the work Loonwise undertakes; client names and specifics are shared in conversation.
Contact
From ambition to working software.
Whether you are accelerating AI adoption, modernizing a critical system, or building the capabilities to innovate faster, we bring the consultants who scope the work and the engineers who build it—the same people, from the first conversation. A senior engineer responds within one business day.
Get in touch