They Asked Us To Build An Insurance Portal.
We Ended Up Automating The Entire Policy Lifecycle.
Build a portal where insurance agency partners could submit quote requests.
6
Core modules
4
Integrations
1
Connected platform
Project Snapshot
- Industry
- Insurance
- Platform
- Multi-Tenant Insurance Management Platform
- Focus
- Policy Lifecycle & Partner Workflow Automation
- Integrations
- Firebase · Google Places · EmailJS · Resend
- Core Modules
- • Partner Portal• Client Management• Quote Requests• Policy Management• Renewal Engine• Admin Portal
The brief
The original request sounded simple.
Build a portal where insurance agency partners could submit quote requests.
Manage their clients. View active policies. Keep everything organized in one place.
At first, it looked like another CRM.
But after mapping how insurance agencies actually operate, we realized the portal wasn't the business.
The workflow behind every policy was.
The Quote Was Only The Beginning
Submitting a quote only takes a few minutes. What follows can take weeks.
Without one connected workflow, information quickly becomes scattered across emails, spreadsheets, and multiple insurance systems.
Client information
Policy comparisons
Carrier communication
Inspection documents
Policy creation
Renewal reminders
What We Discovered
Every step depends on the one before it.
The business didn't need another portal for submitting quotes.
It needed one operational platform that connected agency partners, clients, quote requests, policies, and renewals.
Engineering Note
Every client belongs to exactly one agency partner. Duplicate email addresses are blocked across the platform to prevent ownership conflicts and duplicate records.
The portal wasn't the business. The workflow behind every policy was.
Quotes And Policies Needed To Stay Independent
One thing surprised us during discovery. Most people assume a quote automatically becomes a policy. That wasn't how this business operated.
Quotes were reviewed externally. Policies were entered separately once coverage had been confirmed.
Trying to force both into the same workflow actually created unnecessary complexity.
Instead, we designed the platform so quotes and policies remain independent while still belonging to the same client journey.
Agency partners submit quote requests. Administrators manage policies. Both stay connected through the client profile without becoming tightly coupled.
Design Decision
Policies appear instantly in the partner portal through Firestore's real-time listeners as soon as an administrator creates them—no manual synchronization or page refresh required.
One Form Couldn't Handle Every Insurance Product
Home insurance
Auto insurance
Flood insurance
Liability insurance
Home insurance. Auto insurance. Flood insurance. Liability insurance. Each required completely different information.
Rather than creating one enormous form, we redesigned the experience around policy-specific workflows.
For example, the Home quote request guides partners through a step-by-step experience with conditional questions.
If a property is more than twenty years old, inspection requirements are automatically introduced into the workflow.
The platform asks only for information that's actually relevant.
Engineering Note
Home insurance uses a multi-step conditional workflow with Google Places address lookup, automatic mailing address logic, and inspection requirements generated dynamically based on property details.
Renewals Shouldn't Depend On Someone Remembering
Renewal workflow
Renewal template management with approval workflow and global default settings.
Engineering Note
Renewal emails follow an approval workflow. Partners submit draft templates, administrators approve or reject them, and only approved versions are used when the automated renewal process runs.
Insurance renewals are one of the most valuable parts of the business. Missing one means risking an existing client.
Instead of relying on staff calendars, we automated the renewal workflow.
Every day, the platform checks policies approaching expiration.
Exactly sixty days before expiry, the appropriate renewal email is prepared and sent.
Agency partners can personalize their own renewal messaging. Administrators maintain final approval before anything reaches clients.
Compliance Needed To Be Built Into The Platform
Not every partner should always see every policy. Some agencies require temporary visibility restrictions.
Some policies become inactive automatically. Some inspection documents need to remain attached to quote requests rather than policies.
Instead of leaving these decisions to users, the platform enforces them automatically.
Per-agency policy visibility
Automatic expired policy handling
Inspection document attachments
Self-updating inspection badges
Quote-to-policy separation
One Thing We Learned
Expired policies aren't stored as a separate status. The platform calculates them automatically from expiration dates, reducing maintenance while keeping partner views accurate.
Built Around Agency Partners
As development continued, the portal evolved into much more than a quote submission tool.
Agency partners manage clients, submit quote requests, upload inspection documents, view active policies, and personalize renewal templates.
Administrators manage every agency partner, review quote requests, create and edit policies, approve renewal templates, manage branding, and control policy visibility.
Everyone works inside one connected platform while seeing only the information relevant to their role.
Platform modules
Partner Portal
Client Management
Quote Requests
Policy Management
Renewal Engine
Branding Controls
Admin Portal
Engineering Note
Authentication doesn't rely on custom JWT claims. User roles are determined by Firestore documents, making onboarding and administration significantly simpler while keeping permissions scalable.
Admin portal and agency partner portal connecting clients, quotes, policies, and renewals.
Designed To Grow Beyond Version One
During planning, several integrations were intentionally kept outside the MVP.
Platforms like QQCatalyst, AgencyZoom, EZLynx, QuoteRush, and Client Dynamics were already considered in the architecture.
Rather than tightly coupling the platform to one insurance ecosystem, we designed clean workflows that could accommodate these integrations as the business grows.
That meant today's manual processes could become tomorrow's automated ones without redesigning the platform.
Future integrations
QQCatalyst
AgencyZoom
EZLynx
QuoteRush
Client Dynamics
Engineering Note
Earlier versions used webhook-driven quote-to-policy binding. During redesign, we intentionally simplified the workflow so quotes and policies became independent, making future CRM integrations significantly easier to introduce.
The Outcome
Agency partners manage clients from one place.
Quote requests follow structured workflows.
Policies appear automatically.
Renewals happen without manual tracking.
Compliance is built into everyday operations.
What started as an insurance portal became a complete policy lifecycle platform.
Instead of simply digitizing paperwork, the platform automates how insurance agencies manage clients long after the initial quote is submitted.
Explore The Demo
Experience the platform from both the Agency Partner and Administrator perspectives, and see how clients, quotes, policies, renewals, and compliance workflows work together inside one connected insurance management platform.