Custom software development — a product team, shipped as a service — for Insurance

Insurance carriers and brokerages run on legacy systems — most core policy admin, claims, and underwriting platforms in DACH and the broader EU were architected 15–30 years ago and have grown layers of integrations on top. The result is a sector where data lives in 8–15 systems per business unit, where analytics runs through Excel exports and weekly reports, and where every new product launch waits 6–12 months for IT bandwidth. The decision-makers are typically risk-averse for good regulatory reasons (BaFin, EIOPA, Solvency II) but increasingly under board-level pressure to modernise. The buying pattern: cautious vendor selection, long procurement cycles, but real budget once trust is established and a small win has been shipped.

• ▸API layer on top of legacy core — most insurance modernisation projects fail because they try to replace the core. Wrap it instead.
• ▸Event-driven architecture for downstream workflows — claims, payments, communications fire on policy/claim state changes.
• ▸Strong separation between policy admin (system of record) and engagement (system of differentiation) — different cadence, different teams.
• ▸Internal admin tools are 60% of the value — claims handlers and underwriters need better UIs more than customers need a new portal.
• ▸TypeScript + a hardened framework (NestJS, Spring, .NET) for backend — insurance domain logic is gnarly enough that type safety pays back the first month.
• ▸Compliance-grade audit logging as a first-class concern — every state change, every read of sensitive data, every export.

For a mid-sized DACH broker, we built a custom claims-management tool sitting on top of their legacy policy system — reducing per-claim handling time by 41% and enabling first cross-border claims processing without changing the underlying core.