FDF Labs
Sinqro V2

An insurer's core system, rethought.

Sinqro V2 is a clickable concept: what an insurer's core system would look like if it were organized around each day's work. It runs beside a classic core, connected to it through its API. All the data is invented.

One claim, from the portal to the classic coreLive

  1. ClaimIt's filed on the claims portal.
  2. PhotosPhotos and reports, each with its SHA-256 fingerprint.
  3. WorkshopReceives the car, photographs it and signs the report.
  4. BridgeEvery 2 seconds, what's new goes through the API.
  5. ClassicThe core system opens the claim with all its files.

V2And Sinqro V2 shows that claim live, linked to the same case in the classic core.

135 menu items, 15 entries.

There are no separate screens for lookups, sign-offs or listings: each item of the classic menu becomes a view, a filter or an action on what you're looking at. A test checks that none is left out.

Operations
Home, Claims, Underwriting, Collections, Payments and Approvals. Home gathers what needs your action today, from any area, in one list, and Approvals is a single inbox for every two-person decision.
Records
People, Policies and Documents. One record per person, each policy with its instalments, endorsements, claims and documents, and every file linked to what it proves.
Closing
Accounting, Reinsurance and Compliance. The month-end close as a board of dependencies, automatic cessions to each reinsurer, sanctions screening and the regulator's calendar.
Company
Reports and Settings. You request a report and it arrives when it's ready, without freezing the screen.

One claim, from report to payment.

Every claim goes through the same six stages: report, evidence, coverage, workshop, repair and close. In the list, each row says what to do next.

  1. 01

    Report

    The clerk finds the policy by the ID number the caller reads out, types up the account and, with one click, asks the insured for photos of the damage through a link.

  2. 02

    Workshop

    The workshop's estimate waits for a decision. Then come the part, the pick-up notice and the sign-off the insured signs through a link.

  3. 03

    Payment

    The workshop's invoice is matched against the repair order, and the payment order waits for its approval. The reserve is worked out from the claim's movements.

What we built.

Sinqro's portals for claims, workshops, tracking and verification already existed. We built the concept, the bridge that connects them to a classic core, and a way to measure the difference.

The concept
A clickable web app with all 15 entries, in light and dark, on desktop and phone. A test walks every screen and every link, and fails on any error or dead end.
The bridge
It reads what is filed on the portals and writes it into the classic core only through its API: the claim, its photos and documents, and the inspection report once it is signed. A restart duplicates nothing, and a test compares every file byte for byte.
The measurement
Fifteen everyday processes of an insurer, walked by a robot in both systems. It counts screens, clicks, fields and characters, and a measurement only counts if two runs agree exactly.

Run an insurer?

Tell us which process costs you the most today.

Write to us

← Back to home