Draft · client work, figures, partner tiers, offices and people are placeholders until approved
Case study · Regional insurer

Claims settled in 3 days instead of 19

An event-driven claims platform on managed cloud replaced four legacy systems and a spreadsheet.

A claims handler works through documents beside a laptop
Client
Regional insurer
Industry
Financial services
Practices
Cloud platforms, Product engineering
Duration
14 weeks, then managed service
Context

A regional insurer with 2.1 million policies and a claims team of 240 handlers.

Challenge

Claims moved between four legacy systems and a shared spreadsheet, so an average claim took 19 days and fraud checks ran after payment.

Approach

How the work ran

  1. WK 0–2
    Frame
    Mapped the claim journey with handlers and agreed the target: settle simple claims in under five days.
  2. WK 2–6
    Prove
    Built motor claims end to end on the new platform and ran them alongside the old systems.
  3. WK 6–14
    Build
    Added home and travel claims, inline fraud scoring and the payment integration.
  • AWS
  • Kafka
  • Kotlin
  • PostgreSQL
  • Terraform
Results

What changed

19→3days
Average claim handling time
14wks
Kick-off to production
−38%
Run cost in the first year

“They shipped the thing our last three vendors put in a roadmap.”

Chief Operating Officer, regional insurer
Related work

More from this route

All case studies

Want claims moving this fast?

We can show you the first six weeks of the plan we used, adapted to your book.

Discuss your claims platformhello@speey.com