Elite Pipeline Blueprint

Read me first

What this is: one pipeline, thirteen workflows, and three human SOPs that take a stranger from application to active member with no gap a person has to remember to cover. Money triggers the machine, humans rescue the exceptions, and every silent failure has an alarm.

The five design principles

1. The New Sale form is the day-one master trigger; Whop webhooks are the verification layer. Cash lands in Whop, which GHL cannot see natively, so the closer's form (submitted live on every call, §5) starts the machine. Whop's payment.succeeded and payment.failed webhooks feed a GHL inbound-webhook trigger to cross-check every sale and detect failed in-house installments. Until that's wired, the weekly Whop-vs-pipeline reconciliation (§10) is the net.
2. One definition of Closed-Won: cash collected + contract signed + onboarding call booked. Anything less is a leak in progress, and the pipeline shows it as one. Recommended policy: closer commission pays on cash collected with a signed agreement, which makes the closer the most motivated chaser in the system.
3. Payment type is a tag, not a stage. The current board splits Closed PIF and Closed Payment Plan into separate stages. That fragments close-rate reporting and doubles automation. One closed path, four plan tags. Confirmed Aug 25: PIF, in-house 2-pay/3-pay, and external financing (Klarna, Clearpay, Zip and similar, chosen inside the Whop checkout) all live in this ONE pipeline, distinguished only by [AI Elite] Plan: PIF / [AI Elite] Plan: 2-Pay / [AI Elite] Plan: 3-Pay / [AI Elite] Plan: Financed.
4. Automation detects, humans rescue. Research is blunt on this: reminder sequences plateau after 2-3 touches (GoodSign), and top onboarders win on speed of first human touch (2.4 hours vs 4.2 days for the bottom 20%, OnboardMap 2026). Every ladder in this spec escalates to a named human with a due-dated task.
5. At 0-20 buyers, automate the detection, personalize the delivery. Rone's personal welcome video, the Skool DM, the day-7 check-in: tasks prompt them, a human does them. This is also the product-validation instrument. Exit-interview every refund request.

Your draft questions, answered

• "Is GHL Contracts really the best for this?" Yes for validation, with four mitigations and one kill condition. Full verdict in §11.
• "Workflow reminders if people don't sign?" GHL has no native recurring reminder cadence for unsigned docs, so we build the ladder ourselves. HT01 in §6.
• "Integration to add people to Skool via GHL?" No native integration and no official Skool API exist. Chosen approach: the group invite link inside the welcome email, with a 24-hour join-verification task. §7.
• "A way to look at the price paid on the form to tag them?" Form fields map to custom fields, an If/Else branch routes to plan tags. HT00 in §6.
• "Designed so people don't fall through the cracks?" That is what §10 (stall alarms) exists for. Your board today has 28 opportunities parked in Booked Call because there is no stage or alarm to drain them.

The post-sale flow at a glance

The pre-sale side (application, booking, show-up, no-show, deciding) runs in front of this and is specified in §3 and the S-series workflows in §6.

Pipeline stages

One pipeline: AI Architect Elite Pipeline. Nine stages replace the current six. Never move opportunities to a different pipeline via automation (GHL wipes opportunity custom fields on cross-pipeline moves); everything happens as stage changes inside this one.

Status and value rules

• Opportunity status stays Open through stage 5 so unsigned money is visible risk on the board. It flips to Won at contract signature (HT02), Lost only at stage 9.
• Monetary value = full contract value ($3,997 or ~$4,497), set by HT00. Cash actually collected lives in elite_price_paid and the payment records, so PIF vs plan reporting never distorts the board.
• Loss reasons (required dropdown): price, timing, spouse/partner, no-show dead, ghosted unsigned, DQ not-a-fit, other.

Data layer

Custom fields (contact level)

Contact level, not opportunity level, because opportunity custom fields are wiped if an opportunity ever moves pipelines, and contact fields are what contract merge tags and If/Else branches read most reliably.

Tag taxonomy

Convention (decided Aug 25): every tag carries the [AI Elite] prefix so the whole offer groups together in tag pickers and never collides with other offers' tags; a colon marks a sub-state. Workflows match tags by exact string, so create the full set once, centrally, and never free-type variants.

Two standing rules. One: each S/HT workflow applies its stage's journey breadcrumb as it moves the opportunity (the workflow specs in §6 name only the machine tags, to keep the steps readable). Two: every workflow starts with an idempotency check on its own completion tag so double-fires (a real GHL behavior with document status triggers) can never double-send. Note on [AI Elite] Pending Application: it only exists if the application funnel captures email before the final submit step; if so, tag at partial capture and let [AI Elite] Completed Application replace the segment meaning downstream.

The New Sale form (upgrade of the existing one)

Keep the existing form URL. Required fields: buyer first/last, email, phone, elite_plan_type, elite_price_paid, elite_contract_value, elite_closer, launchpad_grad, grad_credit_applied, onboarding call date booked (confirmation checkbox), elite_sale_notes, and optionally financing_provider + whop_order_id. Every field maps to the custom fields above; the contract cannot merge correctly if this form is skipped, and with Whop as the processor the form is also what starts the machine, which is why the SOP submits it live on every call.

Payment rails (Whop)

• All money flows through Whop checkout links: one for PIF $3,997, one each for the in-house 2-pay and 3-pay plans (Whop runs the installment schedule; exact amounts pending §12, D4). The closer drops the link in Zoom chat and the buyer picks their path inside Whop's checkout.
• External financing (Klarna, Clearpay, Zip and similar) happens inside the Whop checkout. The provider pays the company in full after fees, so financed buyers are operationally PIF: tag [AI Elite] Plan: Financed, no dunning, ever. Record actual net in elite_price_paid if you want fee-true cash reporting, or gross with fees tracked in Whop; pick one convention and stick to it.
• In-house 2-pay/3-pay are the only buyers the company carries risk on, so they are the only dunning-eligible group (HT05), and the contract clauses in §12 D5 exist for them.
• Whop → GHL visibility is a webhook, not native. Build task: point Whop webhooks (payment.succeeded, payment.failed) at a GHL inbound-webhook trigger URL. That powers the payment watchdog (HT00w), dunning detection (HT05), and the cure path (HT05r). Until it's wired, the form is the sole trigger and the weekly reconciliation in §10 is the net.
• Grad credit: a Whop promo code or a dedicated discounted checkout link. Tag [AI Elite] Launchpad Grad either way.

The closer's post-yes SOP

The most dangerous moment of the deal is right after the yes. The closer switches instantly from selling to logistics and runs this five-step ritual while the buyer is still on Zoom. Target: under six minutes. Nothing here is automation; the automation assumes this happened.

1. Charge the card live. Send the Whop checkout link in Zoom chat and stay on while they complete it (they pick PIF, an in-house plan, or external financing right inside the Whop checkout). Payment first, always: the card is the commitment, the signature is the protection. Note which option they chose; it goes on the form next.
2. Submit the New Sale form live. Thirty seconds while the buyer is right there. This releases the contract with correct price and plan terms merged in.
3. Point at the agreement, do not hold the call for it. "It just hit your email and phone, takes about two minutes. Knock it out today, a laptop works best, phones sometimes glitch on signatures." The closer does not wait for the signature; the HT01 ladder and the sign-at-kickoff backstop (§9) own it from here.
4. Book the kickoff live if the call allows, from the Calendars view onto the Elite Onboarding calendar, inside 48-72 hours. Live booking is the ideal, not the requirement: when there is no time, HT02/HT03 send the self-book link and chase it to booked.
5. Inoculate the remorse (Sandler post-sell). "Sometime in the next day or two a voice may ask if this was crazy. Totally normal on a real decision. When it shows up, text us instead of sitting with it, deal?" Buyers who pre-agree to bring doubt to you bring it to you, not to their bank.

Workflows

Thirteen workflows: four pre-sale (S-series) and nine post-sale (HT-series). Naming maps to the original draft like this: draft HT01 became HT00 + HT00w + HT01, draft HT02 became HT02 + HT03, draft HT03 became HT04. Two GHL platform constraints shape everything here:

Pre-sale (S-series)

Post-sale (HT-series)

Skool access, the honest version

Chosen approach (decided Aug 25): the group invite link. HT02's welcome email carries the Inner Circle invite link (repeated in the welcome SMS); the buyer clicks it, hits Join, done. Zero integrations, zero moving parts, live on day one. Two hygiene rules: use Skool's membership question to capture their purchase email so joins match buyers, and if the link ever leaks or circulates, rotate it in Skool and update the welcome template the same day.

Join verification: HT02 creates a +24h ops task: confirm {name} appears in the member list, SMS nudge with the link if not. Two minutes per buyer at validation volume. If Zapier gets connected later, invite + verification can automate (GHL tag → Skool Invite Member with course access, Skool New Member → GHL tag back); that stays an upgrade path, not a launch dependency.

Removal is always human. One saved task checklist, used on refund ([AI Elite] Lost: Refunded) and dunning suspension (day 10): remove from Skool, pause course access, revoke Archie seat, confirm in Slack. The blueprint treats access removal as an SOP with an alarm, never as automation, because no automation can do it.

First-hour Skool experience matters: DM every new member within ~10 minutes of joining with exactly one action (intro post or start-here video). Communities with broken first-day onboarding lose the majority of silent members in week one; target 30%+ day-1 activation. This is a task in HT02's orbit, owned by whoever runs community.

Copy inventory

Thirty-four assets to write. The S-series and HT01 are the launch-blocking set; HT04 can trail by a week or two since the first buyer won't reach day 3 of the ramp until roughly day 10 of the system being live.

Yes, that sums past 34; the recap template and video script are half-assets. Email and SMS copy is supplied separately; the Closer's Playbook is the voice source.

Ghost policy (paid, not yet signed)

Decided (Aug 25): chase hard for 72 hours, then the kickoff call is the signing backstop. Signature before the call is the goal; signature at the top of the call is the floor. No access of any kind until signed, either way.

1. Hours 0-72: the full HT01 ladder runs (nudge at 3h, closer call at 24h, Rone personal touch at 48h, final nudge at 72h).
2. Rone's pre-call check, every kickoff: before the call, glance at contract status. Unsigned → first agenda item: "Before we build anything, let's knock out the agreement. I'll wait, it takes two minutes." Re-share the SAME document link in Zoom chat (never a new doc from the same template, §6 footgun), watch the status flip to Completed, then run the call. HT02 fires the moment it completes, so welcome + Skool access flow right behind it.
3. The one true dead end: day 7 unsigned AND no kickoff held (they ghosted the call too). Decision task to Rone + program owner, plus Slack; a human decides keep-chasing vs refund case by case, with the chargeback math in mind (holding money with no signed agreement and no contact is dispute exposure). Never auto-refund; the refund is always a human action.
4. Guard: HT04 checks [AI Elite] Closed: Contract Signed at entry, so nobody is ever marked onboarded unsigned.

Stall alarms + scoreboard

Alarms are Stale-Opportunity triggers (subject to the §3 footgun: nurture never touches opportunity records) plus the in-workflow escalations already specified. Slack channel: one #elite-pipeline channel, wins and alarms together, so the feed stays alive.

Scoreboard (weekly, 15 minutes, Mondays)

Validation phase means these establish baselines, not chase benchmarks. Published industry ranges conflict wildly (close rates are quoted anywhere from 10% to 50%+ depending on lead warmth), so trust your own numbers by buyer 10.

Contract tooling verdict

Verdict: native GHL Documents & Contracts, with four mitigations and one kill condition. The direct answer to "is GHL Contracts really good enough": for this flow, yes. It auto-sends from a workflow, merges custom values, fires a Completed trigger, works as a goal event, and auto-emails + stores the signed PDF. Its real weaknesses are the mobile signing experience (documented "signed but never submitted" complaints), no native reminder cadence (we build our own, HT01), no cancel action, and the same-template duplication freeze.

• Mitigation 1: desktop-first ask in the closer script and every chase message.
• Mitigation 2: automation gates on the Completed status event only, never on a human saying "they signed."
• Mitigation 3: one live document per contact per template, re-share the same link to remind.
• Mitigation 4: Rone's pre-kickoff check (§9) means an undetected signing failure surfaces at the kickoff call at the latest, never weeks later.

Open decisions

Build order + test checklist

Phase 1 · The money path (build first)

Definition of done: a test sale tomorrow flows end to end with zero human memory involved.

• Custom fields, tags, New Sale form upgrade (§4)
• Products + payment links (PIF now, plans when D4 lands)
• Elite Client Agreement template with merge fields
• Pipeline stages renamed/created per §3
• HT00, HT00w, HT01, HT02, HT03b, HT03 + Slack channel
• Closer SOP (§5) walked through with the closer, live

Phase 2 · The guards

• S02 show-up, S03 no-show recovery
• Stall alarms (§10) + weekly scoreboard sheet
• Stripe smart retries + card updater; HT05 + HT05r dunning (needs D4)
• Skool invite link wired into the welcome template, removal checklist saved as a task template

Phase 3 · The ramp

• S01 booking push, S04 deciding ladder
• HT04 30-day ramp once copy is written and compliance-checked
• Not-Now long-term nurture + day-60 reapplication push

Test matrix (run before the first real buyer touches it)

• End-to-end test purchase: payment → form → contract → sign → welcome → Skool invite → onboarding booked. Use a real test contact, verify every Slack ping.
• Merge-field render check on the contract (name, price, plan terms) for each plan type.
• Sign on desktop AND attempt on mobile; confirm Completed status behavior both ways.
• Duplicate-template test: confirm the build never sends a second doc from the same template to one contact.
• Form-missing alarm: pay without submitting the form, confirm HT00w fires at 30 min.
• Form-without-payment path: submit form only, confirm the verify-charge alarm.
• Rebill exclusion: simulate an installment (Customer Not Present) and confirm welcome/intake does NOT re-fire.
• Failed-payment simulation: confirm HT05 fires, and HT05r restores on cure.
• Staff-booked appointment fires S02/HT03b (the Modified-By footgun test).
• No-show marking fires S03 within 15 minutes.
• Unsigned chase: let a test contact sit unsigned, confirm the +3h/+24h/+48h/+72h ladder, the "going into kickoff unsigned" flag, and the day-7 decision task.
• Stale alarms: age a test opportunity in stages 4, 5, 6 and confirm pings.
• Refund walk-through: run the access-removal checklist once as a drill.

Sources behind the numbers: GHL Help Center articles with 2026 modification dates (triggers, goal events, documents, payments, tasks, stale opportunities), GHL Ideas board + changelog, Skool help + Zapier community (integration reality), OnboardMap 2026 onboarding benchmark report, Better Proposals conversion reports, GoodSign reminder data, Blake Wyatt sub-3.5% refund playbook, Sandler post-sell, Hormozi BAMFAM, dunning playbooks (Digital Applied, DepositFix) and coaching-program suspension policies. Full research briefs available on request.