Designed and built a 20-stage lead lifecycle state machine driven by a single custom field (seller_disposition).
Built the sync automation that reads that field and updates tags, pipeline stage, and campaign enrollment accordingly.
Built the "10 Days in Heaven" high-frequency outreach workflow — a single workflow with if/else branching on message copy depending on whether the lead is brand-new or a revived lead (old CRM import). Not two separate workflow builds.
Built the reply-sentiment routing logic: a positive or neutral reply routes the lead to Hit List; a negative reply routes to Cold Follow Up. Cold Follow Up loops back to Hit List on any subsequent reply — this cycle can repeat indefinitely.
Configured Closebot AI as the default operator at Hit List — it drives the qualifying conversation and books appointments autonomously until a human manually replies and takes over. At that point the human sets the disposition value based on what they determine from the actual conversation.
Integrated Closebot AI with two qualification paths based on lead origin: DTS path (direct inbound, property details pre-verified) and County Record path (Signal Sniping leads, address confirmed first before qualifying).
Packaged the entire system as a reusable GHL snapshot for deployment across client accounts.
How it works
Technical Implementation
Core mechanism
Single custom field seller_disposition acts as the state variable. A sync automation watches it and fans out updates to tags, pipeline stage, and campaign enrollment — keeping the whole system consistent from one source of truth.
20-stage lifecycle
Full lead journey from first contact through outreach, reply routing, Hit List qualification, and long-term follow-up cadences. Each stage change triggers the sync automation, which cascades the correct tag, pipeline position, and campaign enrollment.
10 Days in Heaven
High-frequency outreach workflow (multiple texts/day for 10 days). Single workflow engine with an if/else condition that branches the message copy based on whether the lead is brand-new or a revived lead from an old CRM import. Not two separate workflow builds.
Reply-sentiment routing
The lead's reply is what routes the disposition — there is no separate qualifying stage before a reply. A positive or neutral reply moves the lead to Hit List. A negative reply moves them to Cold Follow Up. Cold Follow Up loops back to Hit List on any subsequent reply — this cycle repeats indefinitely.
Hit List — Closebot as default operator
Closebot (AI) is the default operator at Hit List — it is not one of two parallel options alongside a human. It drives the qualifying conversation and books appointments autonomously. Closebot keeps working the lead until a human manually replies to the conversation. That manual reply is an interrupt/takeover — not a path chosen up front. Once the human takes over, they manually set the next seller_disposition value based on the outcome of the actual conversation.
Closebot — two paths by lead origin
DTS path (Direct to Seller — direct inbound leads, property details already pre-verified): bot qualifies motivation and timeline only. County Record path (Signal Sniping / niche data leads): bot first confirms the address, then qualifies.
Snapshot deployment
The entire system is packaged as a GHL snapshot, enabling consistent deployment across client accounts without rebuilding manually each time. Deployed across 190+ active accounts at Closer Control.
Architecture
State Machine Overview
The seller_disposition field drives the entire lifecycle. Every stage change fires the sync automation, which cascades updates across tags, pipeline, and campaigns.
Results
Deployment & Scale
The system was packaged as a reusable GHL snapshot and deployed across 200+ active client accounts at Closer Control — the primary production metric for this build.
Resume
Resume Bullets
Architected a 20-stage lead lifecycle state machine in GoHighLevel, driven by a single custom field, automating tag, pipeline, and campaign updates across the full lead journey.
Designed and deployed a reusable GHL automation snapshot adopted across 190+ active client accounts.
Configured Closebot AI as the default operator at Hit List — qualifying leads and booking appointments autonomously until a human manually takes over — with dual paths based on lead origin (direct inbound vs. county-record-sourced niche leads).
Skills demonstrated
Skills & Technologies
State-machine system designCRM automation architectureReusable snapshot deploymentThird-party AI integrationLead qualification logic
GoHighLevel WorkflowsCustom FieldsPipelinesCampaignsGHL SnapshotsClosebot AI
Related projects
Extended in Project 1b
The shared seller_disposition-changed sync automation built here was later extended for a separate Closer Control client with 7 new foreclosure-stage dispositions — including compliance-driven auction-date automation and a Bankruptcy Hold legal hold. See Project 1b →