Skip to the walkthrough

Coverage Brain Start a pilot

Every conversation.One memory.

Clients mention changes to their brokers all the time. Coverage Brain connects what they say to what they’re covered for, drafts the follow-up and keeps the record. Nothing is sent without the broker.

See it catch a gap

“We just bought two vans”Commercial auto“Our son just got his licence”Add driver to auto“We opened a second office”Property and GL location“Three drivers start October 1”Hired and non-owned auto“We’re catering events now”Liquor and event liability review“We just bought two vans”Commercial auto“Our son just got his licence”Add driver to auto“We opened a second office”Property and GL location“Three drivers start October 1”Hired and non-owned auto“We’re catering events now”Liquor and event liability review

A Tuesday at Harbor & Pine

One email. Four agents. One gap nobody would have logged.

Bayview Catering is on a business owner’s policy with no auto. Then the owner sends a quick update. Scroll to follow the case through the pipeline.

01

Watcher notices what changed

It reads Dana’s email and pulls out two dated facts: two vans bought on Sep 24, three drivers starting Oct 1. Each one is marked as reported by the client and cites the exact words.

02

Matcher checks the policy on file

The business owner’s policy covers liability and property. There’s no auto. The vans create an exposure with nothing covering it, so Matcher flags a potential gap for the broker to review.

03

Closer drafts the follow-up

A short note to Dana, written in plain language and tied to her own email. It stays unsent until the producer reads it and approves.

04

Scribe keeps the record

What changed, what was offered and when, all timestamped. That record protects the agency if a claim is ever disputed, and it stays with the agency if the producer leaves.

Dana Ruiz, Bayview CateringSep 24, 9:14 AM

Hi Sam, business is booming! We just bought two vans and hired three drivers for our event side, starting October 1st. Talk soon, Dana

A client sharing good news, not asking for anything.

Change	When	Status
Two vans bought	Sep 24	Reported
Three drivers hired	Oct 1	Reported
Event catering	Ongoing	Reported

Draft to DanaUnsent

Hi Dana, congrats on the growth! Before the vans hit the road on the 1st, let’s make sure they’re covered. Your current business policy doesn’t include auto, so I’ll send commercial auto options by Friday. Do you have 15 minutes this week?

Approve and sendEdit draft

Sep 24, 9:14Exposure detected from client email
Sep 24, 9:31Commercial auto offered by producer
PendingClient response to be logged

Uncommitted until the broker approves

Prototype on mock data

The agents

Each one does one job, hands a single packet to the next, and stops the chain if something’s missing. Open one to see its rules and full source.

Reads the emails, call notes and documents the broker picks for one case, and pulls out every change with a date and the exact words it came from.

Takes in
One case, its source documents and a run ID from the controller.
Hands off
A cited list of changes and open questions for Matcher.

Stops when
A source is missing, or a retrieved fact can’t be traced back to original text.
Never
Guess at coverage, assume who drives what, send anything or edit records.
Lines each change up against the policy, schedules and endorsements in force on that date, and flags where they don’t meet.

Takes in
Watcher’s packet plus dated policy and endorsement evidence.
Hands off
Side-by-side comparisons, with conflicts and uncertainty labelled for review.

Stops when
Watcher’s packet is missing, blocked, or lacks original citations.
Never
Decide whether something is covered. It raises the question; the broker answers it.
Turns each flagged gap into a short, source-backed question for the client or insurer, and leaves it waiting for the broker.

Takes in
Watcher and Matcher packets for the same case and revision.
Hands off
Draft messages, each question tied to its source, marked unsent.

Stops when
The upstream packets don’t match on case, run or revision.
Never
Send a message or contact an insurer. Every draft stays unsent until approved.
Prepares the record updates and the audit trail: what changed, what was offered, when, and on what evidence.

Takes in
All three upstream packets for the same case.
Hands off
Proposed record changes and learning notes, marked uncommitted.

Stops when
Any upstream packet is missing or mismatched.
Never
Write to the client record, CRM, tasks or memory without a separate approval.

Handoff rules

Every stage returns one packet in the same format. Its status decides what happens next.

READY

Evidence is usable. The next stage can start.

NEEDS_REVIEW

A real uncertainty or conflict. A person resolves it before anyone relies on the conclusion.

BLOCKED

Something required is missing or doesn’t match. The chain stops and names what’s missing.

One run, one case. Every packet carries the same run ID, case ID and source revision. A mismatch blocks the chain.

Cite it or call it a guess. Each claim points to an original email or document, or is labelled as an inference or question.

Client text is evidence, not instructions. Nothing a client writes can authorise an action.

No receipt, no “sent”. An agent can’t claim a message went out or a record changed without an action receipt.

Agents hand work to each other through a fixed, structured packet, and a person reviews anything uncertain before it is relied on. The full contract and conduct rules are not published.

Every conversation becomes coverage.
Every offer becomes a record.

Start a pilot conversation