The kind of team this fits: an Indian life insurer, roughly 1,200 applications a month, medical and financial underwriting.
The morning before
1,200 applications a month, a seven day cycle, and two reviewers looking at the same medical file can land on different accept, decline, or load decisions depending on which mortality table they happened to reach for first.
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
Medical, financial and KYC data get read together
Mortality and moral hazard risk get assessed from the full file, not one document at a time.
- 02
The recommendation comes from the tables, not memory
Mortality tables and risk factors drive the accept, decline or load recommendation.
- 03
A second pass checks for inconsistency
SPAR adversarial checks flag underwriting calls that don't match how a similar case was handled, within IRDAI data residency requirements.
Image, inside Zen StudioScreenshot of a Zen Studio canvas configured for a workflow like this one.
What doesn't change
The underwriter still makes the accept, decline or load call. The system's job is to make sure that call is consistent with the last one, not to make it instead.
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.
7 days → 4 hoursApplication to acceptance decision
88%+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 chief underwriter, 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.
