Skip to content

Lead Flow

Source of truth for how leads enter, convert, and resolve. Owned by Pete, mirrored on bridge /lead-flow.

Where leads come from (today, UK trades pilot)

Source Status Volume target
Katie's cold calls LIVE from 2026-06-22 40-50 dials/day
Brother pilot referrals Pending Day-7 feedback Word-of-mouth
Direct site / Carrd UK page Built, low traffic Opportunistic

Where leads come from (archived US Audit motion)

Source Status
Apollo scrape (medical practices) DORMANT
Google Maps scrape (lead-scraper.js) DORMANT
Cold email F0 (variants a/b/c) DORMANT
Cold email F1 (follow-up) DORMANT
Polly cold-pitch outbound DORMANT

Conversion path — UK trades (LIVE from 2026-06-22)

  1. Katie dials → live conversation → YES (trade agrees to 7-day free trial)
  2. Captures details in the Call Log sheet → fills name, business, mobile, network, callback email
  3. Sends row for approval — 🚀 YE Provision → Send active row to Matt for approval. Matt gets a one-click audit email, taps Approve.
  4. Bridge auto-provisions within ~60 seconds: clones the Polly assistant for the trade's business, buys their dedicated UK Twilio number, binds it, sends the trade their welcome SMS (containing two vCard download links). Status flows back into the Sheet's Status column.
  5. Trade taps the vCard links → saves "Polly ON" and "Polly OFF" as contacts on their iPhone → taps "Polly ON" → 5-second no-answer forward activated. (Tested + locked 2026-06-21; see forwarding-codes.md.)
  6. Test call — from any other phone, ring the trade and don't pick up → Polly answers in ~5s → captures fake job → trade gets job-handoff SMS within 20s. They hear / see the product work on their own number.
  7. Day 6 → Matt SMSes payment prompt → YES = Stripe link → live customer (£99/mo recurring)
  8. Day 30 → renewal anniversary, churn check

What changed vs the original plan

Step 3 used to be "Matt clones Polly + buys 2nd UK number manually within the hour". As of 2026-06-21, that's fully automated via the bridge /api/provision-pilot/* flow + Apps Script menu in the Call Log Sheet. Step 5 used to be "trade dials forwarding code by hand" — now it's vCard contacts. Net effect: time from "YES on call" to "Polly live" dropped from ~60 min to ~5 min.

Conversion path — original US (paid Cal.com flow)

  1. Direct site or cold email → CTA
  2. Cal.com paid audit event ($999, 30-min) → Stripe checkout → webhook
  3. Webhook posts to bridge /api/cal-webhook → schedules Polly outbound at slot time
  4. Polly runs the discovery (mode discovery) → 48h audit report (report.js → email.js)
  5. Customer reviews report → upsell to build engagement ($3-5K)

Outcomes

  • ✅ Audit report delivered (US)
  • ✅ Pilot live → £99/mo recurring (UK)
  • ✅ Build engagement closed ($3-5K, US)
  • ❌ Opt-out — STOP via SMS or email reply → opt-outs.json

See also

  • Diagram — full Mermaid flowchart of every entry point and surface
  • Polly — the assistant on the receiving end
  • Bridge service — the wiring that connects it all

Maintenance rule

When any of the following change, update both this file AND /opt/yourevenings/bridge/src/lead-flow.js:

  • A new entry point added
  • A Polly mode added/renamed
  • A Stripe product changed
  • Cal.com event added/renamed
  • An outbound channel paused

Then rebuild the bridge.