The kind of team this fits: a Lloyd's market specialty insurer, roughly USD 480M GWP, 40 underwriters, a submission driven portfolio spread across 12 classes.
The morning before
Every quarter, forty underwriters each carry their own instincts into 1,200 submissions. The portfolio view of risk only exists once someone has manually stitched all of it back together, weeks after the decisions were already made and the inconsistencies are someone else's problem to find.
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
Submissions arrive already structured
Each of the 1,200 submissions gets read and classified as it lands, not queued for a quarterly batch.
- 02
Pricing and referral run in parallel
Risk, pricing and referral checks run against the same case at once, instead of moving desk to desk.
- 03
A second opinion checks the first
A SPAR adversarial pass flags where one underwriter's call would have disagreed with another's, before either reaches a bound risk.
- 04
The underwriter still signs
Every bound risk still carries a named underwriter's sign-off. What changes is what they're signing off on.
What doesn't change
Every bound risk still needs a named underwriter's signature. The system finds the inconsistency, it doesn't decide the risk.
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.
6 weeks → 48 hoursPortfolio risk review cycle
90%+Underwriting output consistency
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 head of underwriting, 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.
