A pipeline isn’t a report for the boss — it’s the operating system for a sales team’s week. Most GoHighLevel pipeline setups fail the same way: too many stages, no attached behaviour, and within a month nobody updates it. Here’s the setup that survives contact with real salespeople.
Stage design: fewer, sharper
Five to seven stages, each defined by something that objectively happened: New → Contacted → Qualified → Quoted → Negotiation → Won/Lost. If two colleagues could file the same deal in different stages, the definitions aren’t sharp enough. Kill vanity stages (“Interested”?) — feelings aren’t stages.
Attach behaviour to every stage
- New: instant acknowledgement to the lead; task + WhatsApp ping to the assigned rep; auto-escalate if untouched in 30 minutes.
- Contacted/Qualified: follow-up cadences start automatically and stop the moment a reply lands.
- Quoted: the money sequence — paced follow-ups, proof, and a task for a human call at day five.
- Stale anywhere: deals idle 14+ days surface on a manager view. Silence is data.
- Won: onboarding kicks off, accounts notified, review request scheduled. Lost: reason captured (one required field, not an essay) and a 90-day revival sequence queued.
Ownership rules that prevent chaos
Round-robin assignment with working-hours awareness, clear rules for reassignment, and one commandment: if it’s not in the pipeline, it didn’t happen. Adoption comes from the automations doing work for reps — pre-written follow-ups, automatic reminders — not from management nagging.
Reports managers actually need
Stage-to-stage conversion, average days-in-stage, pipeline value weighted by stage, and lost reasons ranked. Those four answer “where do deals die?” — which is the only question a pipeline exists to answer.
I set these up white-label for agencies deploying GHL to clients — snapshot-ready, documented, adopted. Book a call if your pipelines are currently decorative.
