DemonstrationBuilt by AgentContext. Every carrier, program, producer and figure below is invented — nothing here is a real account.
BABinding Authority· delegated underwriting
Who you are right now

Imogen Vasquez — Chief Underwriting Officer. Imogen runs the underwriting operation. Every program, every carrier, every figure — the only person here who sees the whole book.

Sees 9 of 9 risks · 3 of 3 programs. Every program on every carrier, and the one figure nobody else gets.

Where Claude fits

In a production build, Claude would screen a submission against the binder version in force on the date the risk would be bound, and send anything over the cap or past a referral trigger to the carrier for referral instead of binding it.

It would work inside the signed-in user’s scope: Dmitri’s program for Dmitri, Meridian paper for Harriet, and nothing for Cormac that names the carrier behind his business.

Risks in view
9
of 9 in the book
Bound premium
$503,000
8 bound
Authority breaches
2
checked against terms in force at bind
Loss ratio
67%
weighted, in scope
Which authority are you checking against?

A binder is not one document. It is a series of them, each effective from a date, and a risk is bound under whichever one was in force that day. Check the book against the terms sitting in the system right now and 2 of 2 breaches disappear — not because anything was fixed, but because the carrier later restored authority it had withdrawn.

The query that returns clean is the one almost every system writes, because the binder terms live in one row that gets updated in place. Tick the box and watch the count.

Neither number is a lie. Only one of them is the question the carrier will ask at claim time.

Carrier concentration

agency-wide
Meridian Specialty
$400,000 · 80% of bound premium
Kestrel National
$103,000 · 20% of bound premium
This is the figure the agency negotiates against. It is also the figure that, shown to the wrong reader, negotiates against the agency.

What this is. A working demonstration of the access model underneath a delegated underwriting book — who can see which carrier the business sits with, which aggregates are entitlements and which are disclosures, and whether the record can answer whether a risk was bound inside the authority as it stood that day. The carriers, programs and figures are fabricated; the two mechanics are not — binder terms really are versioned and effective-dated, and some risks really must be referred rather than bound.

The demonstration date is fixed at Sep 16, 2026. Nothing on this page is legal, regulatory or underwriting advice.

This is a demonstration. Access boundaries here are simulated in your browser; in a production build, records a user isn’t permitted to see are never sent to it.