The kind of team this fits: a commercial lines brokerage renewal desk, roughly 450 renewals a quarter.
The morning before
450 renewals a quarter, a twelve day median, and most of them need rework because the first pass missed an exposure change that was sitting in the file the entire time.
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
Renewal history gets read in full
Policy, client and renewal history are checked for opportunities and exposure changes before terms are proposed.
- 02
Coverage adequacy gets reviewed, not assumed
Adequacy and pricing adjustments are recommended based on what's actually changed.
- 03
The pack arrives ready to sign
Confirmation and documentation are issued for broker sign-off, not assembled from scratch by the desk.
Image, inside Zen StudioScreenshot of a Zen Studio canvas configured for a workflow like this one.
What doesn't change
The desk still signs off on every renewal pack. What changes is whether the first draft already caught what used to require rework.
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.
12 days → 1 dayRenewal review to confirmed terms
83%Renewals processed without manual rework
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 renewal desk lead, 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.
