Acorn Life
“An Irish life insurer” (Acorn Life)
A proprietary integration platform retired incrementally, at a third of the integration cost. Legacy logic was preserved, not rewritten.
3×Lower integration cost
ZeroDowntime, book in force
Insurance
Modernising a specific insurance workflow without breaking the book, the loss ratio, or regulatory control.
Industry framing
Underwriters spend more time reading submissions, chasing missing data, and routing risk than pricing it. Claims leak margin through manual intake, coverage checks, and handoffs while cycle times stretch and loss ratios climb. The policy, claims, and rating platforms holding your book of business make every product change a multi-year program, and the same fragmented data across PAS, claims, actuarial, and external feeds is exactly what stalls AI in pilot.
Meanwhile, Solvency II reporting and AI-Act pricing rules have moved regulation into the technology stack itself. Every underwriting, claims and pricing decision must now be explainable, auditable and defensible.
The question is no longer can we digitally transform, it's can we modernise a specific insurance workflow, without breaking the book, the loss ratio, or regulatory control.
How our solutions apply here
Modernize your legacy core
Policy and claims logic is preserved and containerised rather than rewritten from a specification nobody has. In-force business keeps running throughout, and the reporting feeds Solvency II depends on stay intact slice by slice.
Migrate without downtime
Policy, claims and customer records move into a cleaner normalised model, reconciled field by field, with the option to roll back until the new platform has earned the switch. Off the proprietary integration layer, permanently.
Automate manual operations
Document capture and intake are re-engineered underneath the process rather than bolted on top, with review steps a risk team can audit. Lower cost-to-serve per policy, and an audit trail that exists by default.
Proof
JS Insurance
“A UK insurance provider” (JS Insurance)
Hour-long manual deploys replaced by minutes, on a normalized PostgreSQL model that made the data reportable again.
1 hr → minDeploy time
PostgreSQLNormalized from MySQL
“A healthcare-data platform” (DataTower)
Regulated records migrated intact, reshaped and anonymised in flight through an HL7-FHIR Level-4 ETL with field-level reconciliation.
Level 4HL7-FHIR ETL
Field-levelReconciliation before switch
Talk to an expert who has done this in insurance.
Send us the constraint you are working around. We will tell you how we would approach it, what it usually takes, and where the risk sits.