Setter Pipeline — stpierre.ai
Setter Pipeline
Primary KPI: Booked Calls
What this is
How an ad lead turns into a booked, confirmed sales call.
Master pipeline
Sales (delivery). Collins builds the automation.
What Collins does here
Close the gap between the by-hand flow and the agent flow.
🔒 Locked — do not touch
The SMS worker (our text-message sender) is frozen. A live TCPA case is open. TCPA is the law that governs business texting. Cold texts may go only to leads who opted in on a form. Live message tests go only to the phone ending 5477.
Read this pipeline two ways
On the left: how it runs today, by hand. On the right: what it becomes when an agent runs it. Collins closes the gap between them.
Human-run today
The real flow. Booking-gated. Locked 2026-07-12. Tap a step for the SOP.
- 1New Ad Lead
from a Meta (Facebook / Instagram) ad
- 2Application
a short Typeform (online form)
- 3Booking
the lead books on Calendly
- 4Custom Demo
a personalized demo is built
- 5Confirmation Text
delivers the demo link
- 6Sales Call
Akash runs it
Leads book themselves. Akash does not cold-call or chase leads. The first text is scripted and sent by the system. It is not held for approval.
Residual stages that still run: Qualified → Appointment Confirmed. Reminders fire 1 hour, 30 minutes, and 15 minutes before the call. Then the lead is handed to Akash.
Agent-run end state
What it becomes when a setter agent owns the front of this pipeline.
A setter agent runs:
- speed-to-lead texts
- follow-up
- confirmations
- no-show detection
Akash keeps the close. No agent ever takes the call.
Live pieces today:
- Live Process 1 worker: lead form → tracker → fast reply → demo → booking → call.
- Live GHL sales system (our sales CRM): a 17-stage pipeline. sales.stpierre.ai, live 2026-07-12.
- Live Scripted speed-to-lead SMS (text) sends on its own.
The gap Collins builds
- BuildingNo-show detection + recovery loop. An agent that spots a missed call and wins the lead back. Today this is manual or legacy.
- LaterCustom-demo engine. The front of the booking flow. Not built yet, so the demo is hand-assembled for now.
- ConstraintNo paid traffic is running. So there are very few live leads to test the setter agent against. This is the biggest limit right now.
Who owns what
Collins
Builds and runs the setter automation. Owns the agent work end to end.
Akash
Owns the relationship and any human touch. Keeps the close.
Legacy stage map
Legacy — EyeFly-era model. Kept below as a visual reference only.
The stages here — call within 5 minutes, Power Dialer, a 7-day daily-call cadence, and manual text-back — are from the old EyeFly setter model. They are not the current process. Today, "follow-up" means working opted-in leads through the booking flow above.
Registry note: there is no standalone setter lane. The work is split across the Demand Agent and the CRM + Systems Agent.
Tap any stage circle to open its steps. Grey stages are EyeFly-era history.