Insurance Quoting & Policy Platform
Multi-step quoting, policy comparison and document handling for an insurance product.
Role
Senior React Developer
Engagement
Full-time at Latitude Technolabs
Client
Latitude Technolabs — insurance client
Period
2022
The problem
Insurance quoting collects a lot of sensitive, interdependent data, and abandonment in long forms is the whole game. The UI had to be trustworthy, forgiving, fast, and precise about validation — a wrong field label here becomes a wrong policy.
My responsibility
Built the quoting wizard and policy holder portal: form architecture, validation, comparison views and document upload.
Surfaces shipped
Quote wizard
Multi-step data capture with validation, pricing feedback and comparison.
Policy holder portal
Active policies, documents, claims status and renewal flows.
Architecture
How it was structured, and the reasoning behind each boundary.
- 01
Schema-driven validation
Field rules come from one schema shared with the backend, so client and server agree on what valid means and error copy is consistent.
- 02
Per-step persistence
Draft quotes survive navigation and reloads; users can leave mid-flow and return without re-entering data.
- 03
Accessible document upload
Upload with progress, retry, accepted-format messaging and an announced status — usable with keyboard and screen reader, not just mouse.
Key challenges
- 01
Interdependent fields
Coverage selections change which questions apply. Conditional visibility was modelled declaratively so hidden fields never contributed stale values to a quote.
- 02
Trust through clarity
Pricing breakdowns, excesses and exclusions had to be legible at the moment of decision rather than buried in a PDF.
Implementation
- 01
Inline, specific error messaging
Errors point at the field and say what to do, shown on blur and re-checked on submit rather than dumped at the end.
- 02
Comparison that scales
Cover levels compared across a responsive table that degrades to stacked cards on small screens without losing the comparison.
Results
- 01Long quoting flows became resumable, cutting abandonment from incomplete sessions.
- 02Client and server validation agreed by construction, reducing rejected submissions.
- 03Policy documents and claims status self-serve, lowering support contact volume.
Technologies
- Next.js
- React
- TypeScript
- React Hook Form
- Zod
- Tailwind CSS
- Node.js
Technical highlights
- Shared validation schema between client and server
- Declarative conditional field logic with no stale hidden values
- Accessible upload with progress, retry and announced status
Building something similar? I’d like to hear about it.
Start a conversation