Why pipelines rot
Open a neglected GoHighLevel account and the pipeline tells the story: twelve stages, half of them with one deal, a "Follow up" stage holding 300 contacts from last year. The team stopped moving deals because moving them didn't change anything, and the stages didn't match the conversation they were actually having with customers.
A pipeline works when each stage is a fact about the customer. "Quote sent" is a fact. "Follow up" is a to-do list pretending to be a stage.
Entry and exit rules
For every stage we write two sentences before building it. The entry rule: what has to be true for a deal to arrive here? The exit rule: what event moves it on? For a roofing company:
- New enquiry: enters when a lead is created. Exits when a survey is booked.
- Survey booked: enters on calendar booking. Exits when the survey is marked complete.
- Quote sent: enters when the estimate email goes out. Exits on acceptance or decline.
- Won / Lost: terminal, with a lost reason field required.
If we can't write both rules for a stage, the stage is merged into its neighbour. That test alone usually halves the stage count.
The six-stage rule
Across every account we've run, update discipline collapses somewhere above seven stages. Six is the sweet spot for a sales pipeline: enough to see where deals stall, few enough that a rep can place any deal without thinking. Details that don't deserve a stage become a tag or a custom field instead.
A stage answers "where is this deal?" A tag answers "what is true about it?" "Quote sent" is a stage. "Needs finance", "Referral", "Repeat customer" are tags. Mixing them is how twelve-stage pipelines happen.
What fires at each stage
Every stage change triggers exactly one thing, so the team can predict it. Moving to "Survey booked" sends the confirmation and reminder sequence. Moving to "Quote sent" starts a three-touch follow-up that stops on reply. Moving to "Lost" asks for the reason and schedules a gentle check-in in ninety days. Moving to "Won" starts onboarding and, later, the review request. If a stage triggers nothing, ask whether it should exist.
When you need more than one pipeline
Separate pipelines are for genuinely different processes: sales versus onboarding, or residential versus commercial jobs with different steps. They are never for different lead sources or campaigns; that's what the source field is for. When in doubt, one pipeline and good tags beat three pipelines the team has to remember to check.
Key takeaways
- Name stages after what the customer has done, not what the rep should do next.
- Every stage needs a written entry rule and exit rule. If you can't write them, merge the stage.
- Six or seven stages is the ceiling for a sales pipeline; more than that and updates stop.
- Attach one automation per stage change: a task, a message, or an alert. Nothing more.
- Separate pipelines only for genuinely different processes, never for different campaigns.