Lead Rescue OS MVP Build Tickets

Lead Rescue OS MVP Build Tickets

Status: internal software build plan. Start with sample data only.

Sprint Goal

Build a useful local/prototype version of Lead Rescue OS that can support sales demos before any client integration.

Ticket 1 - Lead Card Data Model

Build fields:

• id
• company
• source
• service lane
• route
• urgency
• customer preference
• status
• summary
• missing information
• suggested response
• next action
• next action due
• owner
• guardrails
• activity log

Done when:

• sample WeatherSeal cards load cleanly
• cards can be filtered by urgency, owner, service lane, and status

Ticket 2 - Demo Dashboard

Build:

• card list
• lead detail panel
• filters
• KPI row
• guardrail display
• action buttons as non-live demo controls

Done when:

• five sample leads are readable on desktop and mobile
• no live external action exists

Ticket 3 - Intake Classifier Prompt

Build a structured prompt that converts a transcript/form note into:

• service lane
• urgency
• summary
• next action
• owner suggestion
• guardrails

Done when:

• it handles missed call, storm urgency, Magic Bath financing, old estimate, and warranty/service examples
• uncertain items are flagged for human review

Ticket 4 - Suggested Response Draft Generator

Build:

• draft response by lane
• tone rules
• forbidden claims
• human approval status

Done when:

• no draft quotes price, financing terms, warranty coverage, or insurance outcome
• every draft can be approved, edited, or rejected

Ticket 5 - Answer Neo Call-Flow Adapter

Build:

• Answer Neo demo call-flow script storage
• fields needed from Answer Neo output
• mapping from call summary to lead card

Done when:

• a sample Answer Neo call summary can create a sample lead card
• no phone, SMS, calendar, CRM, webhook, or customer data is connected

Ticket 6 - Owner Report

Build:

• leads by status
• overdue next actions
• priority callbacks
• old estimate reactivation candidates
• service/warranty handoffs

Done when:

• a one-page owner report can be exported from sample cards

Ticket 7 - Review / Proof Worker Stub

Build:

• completed job trigger
• review request draft
• job proof notes
• photo/story prompt

Done when:

• sample completed job creates a review/proof task, not an auto-send

First Tech Stack Recommendation

For the first real coded prototype:

• Next.js / React dashboard
• TypeScript
• local JSON or SQLite first
• OpenAI structured extraction for classifier/drafts
• Answer Neo for call-flow/voice intake
• Postgres later when real multi-client use starts

First Demo Rule

No live external actions. The prototype should demonstrate workflow value before connecting to any client system.