Appearance
Agent Platform — Overview
Status: Living document. Last updated April 17, 2026. Version: Phase 1 shipped (v0.4.1). Phase 2 next.
What this is
AskFlorence's agent platform is a parallel product track to the consumer experience. It recruits licensed ACA insurance agents and agencies, gives them a portal where they receive pre-qualified leads with pre-filled applications, and lets them review + submit enrollments in 5-6 minutes each. Recurring commissions are paid for the life of each enrolled member.
Two partnership models:
| Model | Split (net to agent) | Effort per enrollment | Designed for |
|---|---|---|---|
| Full Service | 50/50 ($11.50 net PMPM) | 30-60 minutes — call, gather info, guide, submit | Relationship-heavy agents |
| Submit-Ready | 80/20 ($4.60 net PMPM) | 5-6 minutes — review pre-filled package, verify, submit | Volume scale agents |
Despite the lower per-member rate, Submit-Ready agents typically out-earn Full Service by 2-3x at scale because they can submit 5-10x the applications.
Terminology
- Agent — individual licensed producer. May be solo, or part of an agency.
- Agency — organization with multiple agents. Agency owner/manager can invite their team to join AskFlorence under the agency.
No "broker" wording is used in any agent-facing content. Pre-April-2026 documents may still say "broker"; all new content says "agent" or "agency."
Ship order (phase roadmap)
| Phase | Status | What | Where |
|---|---|---|---|
| 1 | ✅ Shipped v0.4.1 | /agents landing + /agent-onboarding waitlist | Current (Vercel) |
| 2 | Next | /agent-discovery 11-screen research survey | Current (Vercel), after /privacy ships |
| 3 | Ops task | MongoDB permissioned users (app_writer_survey etc.) | MongoDB Atlas |
| 4 | Planned | AWS migration (Issue #47) | Blocks Phase 5+ |
| 5 | Post-AWS | Agent portal: auth, NIPR, ID verify, dashboard, admin | New infra |
| 6 | Post-Phase-5 | Activation + Tier-2 security before leads flow | New infra |
Why Phase 5+ waits for AWS: agent data includes PII (NPN, name, email), and eventually member PHI flows through activated agent accounts. CMS EDE (Enhanced Direct Enrollment) audits look back at how you've been operating for months, so we build on SOC 2 / HIPAA / EDE-ready foundations from day one rather than migrate under audit pressure later.
Current state (what's live at askflorence.health/agents)
- Public marketing landing page, 8 sections, indexable
- Mobile-intentional design with full 100svh hero, scroll cue, hamburger nav, floating CTA
- Waitlist form at
/agent-onboardingcollecting: name, role (individual agent vs agency owner/manager), company or agency name, email, phone, NPN (validated 6-10 digits) - Ops notifications email to
[email protected]on every signup - Cross-promotion to the discovery survey (once it ships) from the waitlist success screen
No auth yet. No real portal yet. Both come in Phase 5.
Related documents
- Auth Architecture — Tier 1 / Tier 2 / super-admin auth paths and session design
- MongoDB Permissioning — DB user scopes, migration path, production exit criteria
- Compliance Model — SOC 2 / HIPAA / CMS EDE alignment, audit log, consent capture
- Data Models — collections, indexes, retention policies
Source of truth
The full compliance-first architecture plan lives at ~/.claude/plans/jolly-forging-thacker.md on Taha's machine. These docs pages are the checked-in version of the decisions already locked in.
