Lead Lifecycle Dashboard

Status
planning
Tier
Tier 2 — Platform
Owner
Ryan Colston
Started
2026-04-26

One-line description. Universal UUID lead_id across FUB/Kit/Ghost/DocuSign/Mojo plus a Streamlit dashboard for funnel analytics.

Why

The seller sales motion launched 2026-05-01 with zero historical setter data. Designing the dashboard schema before launch lets day-1 dials produce clean data for the questions I actually want answered. Retrofitting in June would cost weeks.

The other half is identity. A lead in FUB, Kit, Ghost, DocuSign, and Mojo today is 5 different rows in 5 different systems. A universal UUID lead_id collapses them into one. That's the foundation for both the seller motion and the future buyer motion.

Current state

Idea-stage. Captured 2026-04-26. The "design before May 1" window has effectively closed (today is 2026-05-02, post-launch). 3 open decisions still need locking before plan-writing. The longer this sits, the more day-1 data drifts without a clean schema to land in.

Next 3 actions

(none — surface when relevant)

Decisions log

Locked design decisions: - Identity is UUID, not email. Email is a resolution attribute. - Surface is Streamlit on Cloud Run. No GCP-native option meaningfully better. - Voice-content LLM choice (for related market-report build): Claude Sonnet 4.6 / Opus 4.7 with Hormozi rules + few-shot. Not Gemini Flash.

Open issues

References