About

We are building the operating layer for reinsurance.

It starts with the file every broker already sends — the submission — and makes everything after it traceable.

Company

Workflow walkthrough

Built where the work starts.

ReRao begins with the submission a broker already sends, and the chain of decisions that has to survive the next desk, the next renewal and the next audit.

Scoped evaluation
Security review
Integration scoping
Written pilot terms

How we work

Design partnership

scoped evaluation

What arrives

Your workflow

What you review

Written scope

Scoped evaluation

Source and state visible

Built layer by layer

Reinsurance is layered. So is the record.

We started where the work is densest — broker submissions — and built outward without changing the model underneath.

01

Primary

Attaching · working

Intake, extraction, and the first review pass — where most of the file's time is spent.

02

Working excess

Layered above attachment

Comparable placements and structure checks before a layer is quoted.

03

Catastrophe

Event-driven

Bordereaux and event data reconciled against the treaty it belongs to.

04

Retrocession

Programme level

The whole book, read as one governed record with its own evidence trail.

How we build

Four layers, each tested where it sits.

The programme is built the way cover is: in layers. Each one is measured on its own, and the gauge on the side reads the total that a client actually buys.

  1. 01

    RecordBase plate

    Immutable submissions and quotes — the layer everything else is bolted to.

  2. 02

    ModulesPlates

    Intake, pricing, evidence, reporting. Each plate is separate so it can be replaced.

  3. 03

    TestsSprings

    Each layer is loaded on its own. A bad module bends its plate and nothing under it.

  4. 04

    TotalGauge

    The dial reads the assembled stack — what a client buys, not a diagram of what we built.

Fig 4 · Layer rig, cutawayLayers stack in order · each one is tested on its own · the gauge reads the whole stack

What we believe about this work.

Reinsurance runs on judgment buried in documents, messages, spreadsheets, and treaty language. We build the layer that keeps that judgment visible, reviewable, and fast to reach.

AI-assisted workflows should remain reviewable by human experts.

Example workflows must be labeled and never imply customer outcomes.

Security and compliance status must be explicit.

The product should integrate with existing reinsurance systems rather than ask teams to start over.

Design-partner review

Talk to ReRao about a scoped evaluation.

Bring a real submission packet into a scoped design-partner evaluation for broker intake, placement handoffs, operations, or sovereign deployment.

Evaluation requested

Review-ready
Review pathBroker intake through the review packet
Evidence trailSource links, exceptions, and audit context
Evaluation scopeEvaluation language only, no live outcome claims