Product Requirements Document: PolicyChat

Overview

Product Name: PolicyChat (working title)

Product Type: Multi-tenant SaaS lead distribution and management platform

Description: PolicyChat is a modern, AI-powered lead marketplace and CRM platform built for insurance agents and lead distribution administrators. The platform consists of two integrated portals:

1. Agent Portal — A self-service marketplace where insurance agents can fund accounts, purchase filtered leads in real-time, manage their pipeline via a built-in CRM, integrate with external tools, and receive AI-driven recommendations to maximize ROI.

2. Admin Portal — A back-office command center for operators to manage lead sourcing, buyer/vendor integrations, third-party validation and enrichment services, agent relationships, call routing, marketing communications, and platform analytics.

Target Launch: Life insurance vertical first, with rapid expansion to Health, Medicare, Auto, Home, Final Expense, and Commercial insurance verticals.

Vision: Become the most trusted, intelligent, and agent-friendly lead distribution platform in the insurance industry—where data quality, transparency, and AI guidance create measurable ROI for agents and predictable revenue for operators.


Problem Statement

Insurance agents today face several pain points when buying leads:

Meanwhile, lead distribution operators struggle with:

PolicyChat solves both sides with a unified, intelligent, fully integrated platform.


Goals & Success Metrics

Business Goals

Goal Metric Target (12 months post-launch)
Acquire active agents Monthly Active Agents (MAA) 2,500+
Drive lead volume Leads sold per month 100,000+
Recurring revenue GMV (Gross Merch. Value) $5M+ ARR equivalent
Agent retention 90-day retention rate ≥ 65%
Agent satisfaction NPS ≥ 50
Lead quality Dispute rate < 5%
Platform reliability API uptime 99.95%

Product Goals


User Stories

Agent Stories

Admin Stories


Requirements

Functional Requirements

A. Agent Portal

A1. Authentication & Onboarding

A2. Wallet & Payments

A3. Lead Marketplace

A4. Lead Delivery & CRM

A5. Integrations (via Pipedream Connect)

A6. AI Assistant

A7. Call Routing (Inbound)

A8. Disputes & Returns

A9. News, Deals, & Communications

A10. Analytics & Reporting


B. Admin Portal

B1. Agent Management

B2. Lead Source / Buyer API Management

B3. Third-Party Enrichment & Validation

B4. Lead Routing Engine

B5. Call Routing & IVR

B6. Pricing & Catalog Management

B7. Dispute Management

B8. Communications & Marketing

B9. Analytics & BI

B10. Compliance & Audit


Non-Functional Requirements

Category Requirement
Performance Lead delivery latency p95 < 2s; UI responsiveness < 200ms TTI on key pages
Scalability Support 100K leads/day at launch; horizontally scalable to 1M+/day
Availability 99.95% uptime SLA; multi-AZ deployment
Security SOC 2 Type II within 12 months; encryption at rest (AES-256) and in transit (TLS 1.3); PCI DSS scope minimized via Stripe Elements
Compliance TCPA, CAN-SPAM, GLBA, GDPR, CCPA, state insurance regulations
Accessibility WCAG 2.1 AA compliance
Browser support Latest 2 versions of Chrome, Safari, Firefox, Edge
Mobile Responsive web at launch; native iOS/Android in Phase 2
Internationalization English at launch; framework in place for Spanish (Phase 2)
Observability Structured logging, distributed tracing, error tracking (Sentry), uptime monitoring (Datadog)

Technical Considerations

Suggested Architecture

Key Risks & Mitigations

Risk Mitigation
Lead vendor API instability Connector framework with retry, circuit breakers, dead-letter queues
TCPA litigation exposure Strict consent capture, DNC scrubbing, audit trail, legal review
Stripe payment disputes Clear refund/credit terms in ToS; in-app dispute resolution
AI hallucinations in recommendations Constrain to factual data from agent's history; show source citations
Lead quality complaints Pre-delivery validation pipeline; transparency in source/enrichment data
Multi-tenant data leakage Row-level security in Postgres; tenant isolation testing

Scope & Constraints

In Scope (v1.0)

Out of Scope (v1.0)

Constraints


Timeline & Milestones

Phase Duration Key Deliverables
Phase 0 — Discovery & Design Weeks 1–4 Final PRD, UX wireframes, design system, technical architecture
Phase 1 — Foundation Weeks 5–10 Auth, agent onboarding, Stripe wallet, admin user mgmt, schema, infra
Phase 2 — Marketplace Core Weeks 11–16 Filter builder, lead catalog, basic routing engine, lead delivery to CRM
Phase 3 — Admin & Integrations Weeks 17–22 Vendor API connectors, enrichment pipeline, Pipedream Connect, disputes
Phase 4 — AI & Communications Weeks 23–26 AI assistant, news/deals, in-app messaging, analytics dashboards
Phase 5 — Call Routing & Polish Weeks 27–30 Twilio IVR, inbound call routing, performance optimization
Phase 6 — Beta Weeks 31–34 25–50 beta agents, bug bash, NPS feedback loop
Phase 7 — GA Launch Week 35 Public launch, marketing campaign, sales activation
Phase 8 — Vertical Expansion Weeks 36+ Add Medicare, Health, Final Expense, then Auto/Home

Open Questions

1. Pricing model: Is the business take-rate (% markup on each lead) or subscription + lower markup? Hybrid?

2. Exclusive vs. shared default: What's the default lead-sharing policy (e.g., max 3 agents per shared lead)?

3. Refund policy: What is the dispute window (24h, 48h, 7 days)? Per-vertical?

4. Carrier relationships: Should we pursue direct carrier appointments to facilitate quote-to-bind in-platform?

5. Geographic licensing: Do we block agents from purchasing leads in states where they're not licensed, or warn only?

6. AI data usage: Do agents opt in to having their conversion data used to train cohort-level recommendations?

7. Vendor onboarding: Will we use a self-service vendor portal or admin-mediated onboarding only?

8. White-label: Should architecture support white-label resellers from day one to avoid expensive refactor later?

9. Compliance budget: What's the SOC 2 / legal counsel budget allocation for year 1?

10. Mobile priority: When does native mobile become a competitive necessity vs. nice-to-have?


*Document Version: 1.0*

*Status: Draft for stakeholder review*