five things, two heights
You are being sold five different things that all call themselves AI for insurance, and they are not competing with each other.
They do not all sit at the same height: four of them sit inside the work and one sits above the work. Knowing which you are buying is the difference between a tool that overlaps what you have and one that wraps it.
The control layer sits above the work, not inside it
═ the control layer ═
Evaluation, approvals, policy checks, logging and monitoring — applied to whatever runs underneath, rather than built into any one of them.
Between companies
Moving risk, terms and status between brokers, insurers and third parties without anyone re-keying it.
Serves: Brokers, insurers, third parties
Pointed inward
Helping the person doing the work — reading a submission, drafting a summary, finding a comparable.
Serves: Underwriters, assessors, brokers
Pointed outward
Making the thing a customer touches simpler — buying it, claiming on it, understanding it.
Serves: Customers, frontline staff
The product itself
Changing what is sold — continuous cover, parametric triggers, a policy with no discrete claim step.
Serves: The market
We are the band. The four boxes inside it are where the copilots, the portals and the platforms live — and most of them are good at what they do. We read from them and we do not replace them.
The things, and the height each one sits at
- 1Between companiesinside the work
- 2Pointed inwardinside the work
- 3Pointed outwardinside the work
- 4The product itselfinside the work
- 5The control layerabove the workthis is the one we are
two heights, not five. The four inside the work are not stacked on each other and we do not claim they are — an interop layer does not sit above an experience layer. What differs is whose problem each solves. The height that matters is the one between all four of them and the thing that can stop them.
What this is not a claim about
It is not a claim that nobody else does governance.
Several companies do, some of them well, and one of them says in its own words that it created the category. We name them on the comparison rather than pretending they are not there.
It is a claim about where the thing sits.
A layer that wraps a workflow behaves differently from a panel inside one, and the difference shows up the first time a control has to stop something. A panel can be dismissed by the person it interrupts. A layer cannot.
The place to check that claim is the step where the work stops: plate 05, where a control blocks the submission and names itself. And the fuller list of what gets refused is on what it refuses to do. What actually runs underneath the band — dispatch, model access, memory, governance — is on the architecture page.
Four working papers. A person sends the one you pick — no download wall, and no meeting is booked.
Work out what this costs