Zen Insurance
A proof of concept for a property-insurance startup idea. It follows one policy through the whole pipeline: quote → underwriting → servicing → claims. Mock data throughout. Every flow below is clickable, and the role workspaces share one submission thread, so what a customer submits shows up in the underwriter's queue.
Pick a role
Customer flow
Sign in (mock), describe the insured and the property, choose a line, design the policy, submit it.
Underwriter flow
Work the referral queue: cat-model scores, flagged rules, approve / refer / decline, then price and bind.
Case & Claims flow
Service the bound policy, take first notice of loss, and feed the loss profile back to underwriting.
Onboarding channels
Direct customers, producers and mortgage servicers arriving at one property, with identity tiers that gate paid data pulls.
Plan designer
Five property products as data: nested provisions, rules as data, live rating, accessible expand / collapse.
Platform architecture
How a real build would scale: five business flows over an event-sourced spine, shared AI and data services, GCP or AWS.
Architecture per flow
The same platform, one business flow at a time, in plain language.
How this demo is built
Site map, the shared submission thread, and the plan-design engine: static files, strict CSP, no backend.