AI WorkerNew business, life

LEO

Life Insurance Underwriter

The workNew business, life

What this work looks like today

Life underwriting turns on evidence that arrives late and in the wrong format. Lab reports, ECG and TMT scans, financial documents and lifestyle disclosures come in over days, and the case sits still between them.

LEO holds that role. It reads the case, works it through the bench below, and returns a decision with the reasoning attached. Accountability for that decision stays with you.

Inside the WorkerThe agent bench

One Worker, a bench of agents

LEO is not a single model answering a prompt. It is a role, and underneath it sit agents that each do one part of the case. Scrutiny runs first on every case, whichever Worker holds it.

Scrutiny3 agents
Intake

Checks whether the application is complete against the product SOP and raises what is missing.

Vision

Reads the documents and pulls out the data points. Stops and asks for a re-upload if the scan is not readable.

Veritas

Cross-verifies the critical data points across documents and sources.

OSINT1 agent
Negative News Search

Leverages open source information available on the internet to identify any negative news.

Medical1 agent
Medical

Understands and analyses medical lab test reports and scans like ECG and TMT.

Financial1 agent
Financial

Does the financial calculations and analysis, for example bank statements.

LifestyleBench not published

This group is part of lifestyle work on this Worker, and the individual agents inside it are not published yet.

GovernanceThe five brains

Every output passes the same five checks

The bench above is how the work gets done. This is what every piece of it has to survive before anything leaves.

Configurable oversight

You set the boundary. Autonomy widens on your terms, not ours.

Auditable

Every step and every input retained, in the form an examiner asks for.

Creditable

Cited to the policy you set, line by line.

Zero bias

Same input, same answer, every time, and provably so.

Hard-grounded

Grounded in your data and your manual. Nothing invented in the gap.

Bring one queue
and a month of decided files.

Run LEO alongside your own team before it decides anything, so the comparison is against your people and your policy.