Contact person: Life Insurance Lead Generation Platform

Phone:Show

Email:Show

Location: Pittsburgh, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"The project involves building an end-to-end life-insurance-focused lead generation and distribution system that functions both as a central “lead store” and a self-service portal for agents.

Core flow
Leads will be captured from paid ads, landing pages, data partners, and API feeds, funneled into a single database, scored in real time, then made available for purchase or automatic assignment to licensed life-insurance agents. Agents must be able to log in, view available leads that match their filters, fund their balance, claim or auto-receive leads, and track contact attempts and outcomes.

Key modules and expectations
• Admin console – configure lead sources, pricing tiers, delivery rules, refunds, compliance settings, and detailed reporting (conversion, cost per acquisition, ROI).
• Lead store – searchable inventory with dynamic pricing and stock visibility, integrated with Stripe or a comparable gateway for instant checkout.
• Agent portal – dashboard, lead inbox, smart filtering (age, location, policy value, etc.), real-time notifications (SMS/email/web push), and basic CRM notes.
• Distribution engine – round-robin, performance-based, or bid-based delivery algorithms with throttling to prevent oversell.
• API endpoints & webhooks – REST/JSON for external lead suppliers and downstream CRMs.
• Compliance – TCPA consent capture, audit trail, data-retention controls, and role-based permissions.

Tech preferences
I’m open to frameworks such as Laravel, Node.js, or Django backed by Postgres or MySQL, provided the stack is cloud-ready (AWS, GCP, or Azure) and can scale horizontally.

Acceptance criteria
1. New life-insurance lead can be posted via API and appears in the admin queue within 2 seconds.
2. Agent with matching criteria receives a push/email within 3 seconds of purchase or auto-assignment.
3. Refund workflow (bad contact info) triggers credit return and audit log.
4. System sustains 500 concurrent agent sessions with sub-300 ms query times in staging tests.

Deliverables
• Source code in private repo with commit history
• Deployed staging site + documentation for cloud setup
• API & data-model documentation (OpenAPI preferred)
• Two-week post-launch bug-fix window

If additional clarification is needed on workflows, data schema, or integrations, I’m readily available to jump on a call or provide wireframes." (client-provided description)