From Policy Number to Digital Relationship

Insurance · Omnichannel · Digital Enterprise Solutions

From Policy Number to Digital Relationship
March 7, 2026
Roland Hildebrandt
Roland Hildebrandt

Associate Partner

Dr. Arnaud Fietzke
Dr. Arnaud Fietzke

Associate Partner

From Policy Number to Digital Relationship

Customers no longer accept a paper-first, call-center-centered relationship with their insurer. More than 80% of customers say they would switch carriers if their insurer lacks a user-friendly digital interface (PwC) – and 29% churn after a single negative experience. InsurTechs and digital-first challengers have turned those expectations into features: fast in-app claims, proactive policy alerts, and genuinely useful self-service.

For most incumbents the obstacle isn’t design teams or app stores – it’s architecture. Siloed data, monolithic policy administration systems, and a lack of APIs make modern, mobile-first customer communication fragile or impossible. This article gives a practical three-stage roadmap for insurers: digitize touchpoints, integrate channels, then personalize and anticipate – with concrete itestra entry points at each stage.

Why the Status Quo Is a Loyalty Risk

Digital friction is silent but decisive. A single negative interaction drives 29% of customers away; with InsurTechs offering smooth onboarding and fast claims, the alternative is just a few taps away. Examples from the German market underline the gap: Ottonova reports an NPS above 70, while Getsafe achieved an 80% in-app claim resolution rate within 24 hours by late 2024.

The business impact is measurable: low engagement equals fewer cross-sell opportunities, weaker renewal rates, and higher acquisition costs to replace lost customers. PwC’s finding that over 80% of customers would switch insurers without a usable digital interface should be a red flag for retention-focused executives.

The Root Cause: Architecture, Not UX

When a digital initiative stalls, product teams blame UX and marketing. In our experience across 90+ enterprise customers, the technical reality tells a different story:

  • Legacy policy administration systems often contain decades of certified actuarial logic – risky to replace and expensive to reverify.
  • Data is scattered across billing, claims, underwriting, and partner systems – creating inconsistent customer views.
  • Monolithic systems expose few APIs, so mobile apps end up as fragile front-ends that duplicate logic or call back-end functions inefficiently.

Fixing the customer experience therefore requires an API-first, incremental modernization approach that preserves proven business logic while exposing functionality and data to modern channels.

A Three-Stage Maturity Model

The path from transaction to relationship is a sequence, not a single project. Below are pragmatic stages you can implement in parallel across product lines.

Stage 1 – Digitize touchpoints

Objective: Make standard tasks work digitally and reliably – policy lookups, document access, payments, and simple claims.

What to do:

  • Deliver a responsive customer portal or mobile app that exposes read/write access to policy and claim status.
  • Implement document ingestion and classification so customers can submit documents via mobile – first measurable results often within 4–6 weeks.
  • Use fixed-price Health Checks (1–2 weeks) to map APIs, BiPRO interfaces, and document flows.

Why it works: Quick wins build trust. Customers who can check their policy, upload photos, and see claim status are less likely to call and more likely to remain engaged.

Stage 2 – Integrate channels

Objective: Create a consistent, omnichannel experience – web, mobile, phone, and broker portals share the same data and business rules.

What to do:

  • Introduce an API layer that exposes canonical customer and policy data – leaving core systems intact but accessible.
  • Standardize message formats and integrate BiPRO where relevant.
  • Implement event-driven notifications – SMS, push, and email – from a single notification service.

Why it works: Integration reduces manual handovers and inconsistent customer messaging. It also lowers maintenance costs by centralizing cross-cutting concerns.

Stage 3 – Personalize and anticipate

Objective: Move from reactive to proactive communication – personalized alerts, intelligent claim triage, and cross-sell offers based on real behavior.

What to do:

  • Add ML-driven classification for inbound documents and initial claim routing to increase STP.
  • Use behavioral data to trigger context-aware communication – renewal nudges, safety tips after extreme weather, or targeted product offers.
  • Close the loop with analytics that measure engagement, NPS, and STP improvements.

Why it works: Personalized, timely communication increases perceived value and loyalty – and it’s feasible only once data and APIs are consolidated.

Where itestra Helps – Concrete Entry Points

We take an incremental approach that preserves proven business logic and reduces operational risk:

  • Health Check (1–2 weeks): Fixed-price assessment of customer touchpoints, API readiness, and document flows – delivers an actionable backlog and effort estimate.
  • Portal Renovation: Modernize the front-end and implement a thin API façade – measurable improvements in weeks, not months.
  • API-First Modernization: Expose core functions via canonical APIs; incrementally replace or refactor back-end modules behind the API.
  • AI for Claims & Documents: Deploy focused models for document classification and initial triage – increases STP and shortens cycle times. itestra has helped clients reach STP cycle times under 5 minutes in targeted flows versus a 72-hour industry average.

Typical engagement: a 2–8 week discovery followed by prioritized, fixed-size sprints. This keeps ROI transparent and enables early business value.

Where to Start

If your customer portal underperforms or mobile adoption is low, start with a 1–2 week Health Check. It clarifies whether the barrier is front-end design, missing APIs, or deeper policy-system constraints – and produces a prioritized roadmap with effort estimates and measurable milestones.

Contact: Roland Hildebrandt, Lead Engineer & IT Strategy Consultant. We’ve worked with insurers across DACH for 20+ years and with 90+ enterprise customers – our approach is pragmatic, evidence-driven, and incremental.

Ready to move from transactional interactions to a digital relationship? A short Health Check is a low-risk, high-clarity first step.