The kind of team this fits: a UK regional motor insurer running direct and broker channels, roughly 320,000 policies in force, 90 FTE in operations.
The morning before
A policy that takes eleven days to move from quote to issuance doesn't feel slow to any one person in the chain. It feels slow because it passes through six of them, each waiting on the one before, and a claim on that same policy means starting the handoff chain all over again.
Image, the morning beforeA photo or illustration of what this looks like today, before any of this runs.
How this could run
Not a feature list. The actual sequence, from the moment the case lands to the moment someone signs it.
- 01
One workflow, not four handoffs
Quoting, underwriting, issuance and claims run inside one connected pipeline instead of four separate ones.
- 02
FNOL starts the moment it's reported
Phone, web or app, first notice of loss is captured and structured immediately.
- 03
Straightforward claims move without a desk
Damage assessment and reserve setting run automatically for claims that fit the straight-through path.
- 04
Complex cases still reach a person
Anything that doesn't fit routes to an adjuster with the full context already attached.
Image, inside Zen StudioScreenshot of a Zen Studio canvas configured for a workflow like this one.
What doesn't change
An adjuster still owns every case that doesn't fit the straight-through path. Automation picks up the routine, not the judgment calls.
What this could mean
Illustrative, based on the shape of a workflow like this one. The real number depends on the case, the team, and how it's configured.
11 days → 4 hoursQuote to policy issuance
70%Claims settled without human handoff
Image, inside Zen PilotScreenshot of the Zen Pilot dashboard or explainability panel for a run of this workflow.
Where this lives in the platform
For a coo, insurance operations, a workflow like this starts as a conversation with Zara, describing the process in plain language and getting a first draft of the team back in the same session. Zen Studio is where engineering opens that draft, sets the guardrails node by node, and versions it before it goes live. Zen Pilot is where it actually runs, and where anyone can watch a case move through it in real time, node by node, with the reasoning attached.
