GoHighLevel pipelines: the complete setup guide

Pipelines are where every GoHighLevel setup starts, and where most of them go wrong. The default template gives you a generic funnel that matches nobody’s actual sales process, and people either fight it for months or quietly stop using the CRM altogether.

This guide walks through building a pipeline from scratch, the way I build them for client sub-accounts.

Start from the customer’s journey, not the software

Before you touch a single stage in GoHighLevel, write down what actually happens when someone wants to buy from you. For most service businesses it looks something like:

1. Lead arrives (form, call, chat, referral)
2. Qualification — are they real, are they in your area, can they afford you
3. Quote or proposal sent
4. Follow-up sequence
5. Won or lost

That’s five stages. The default GHL pipeline has stages like “Lead in”, “Contacted”, “Customer” — vague enough that nobody agrees what they mean, so the pipeline becomes a graveyard of stale contacts in “Contacted”.

*Rule: every stage should be a state the customer is in, not an action you took. “Proposal sent” is your action. “Considering proposal” is the customer’s state. The difference matters because automations trigger on stage changes — and you automate around customers, not around your own to-do list.

Building it in GoHighLevel

Settings → Pipelines → create new. Name it after the thing you’re selling, not “Pipeline 1”. If you sell two genuinely different things (say, domestic installs and commercial contracts), use two pipelines — don’t cram both into one.

For each stage:

• Name it with the customer state — “Qualifying”, “Quoted”, “Negotiating”, “Won — Job Booked”, “Lost”.
• Set a colour — sounds cosmetic, but a pipeline you can read at a glance is a pipeline people will keep updated.
• Decide what automation fires on entry — this is the whole point of the stage.

Stage-entry automations that earn their keep

The three that matter for almost every business:

1. New lead stage — instant reply (SMS or email, whichever channel they came in on), notification to the right person, start a missed-call text-back if it was a call.
2. Quoted stage — queue the follow-up sequence: day 2 “any questions?”, day 5 value content, day 10 “still interested?”. GHL’s workflow builder makes this a drag-and-drop job.
3. Won stage — booking link for the job, review request workflow scheduled for after completion, move them out of sales campaigns.

The mistakes everyone makes

• Too many stages. If a stage exists that contacts sit in for weeks without an automation attached, you’ve built a filing cabinet, not a pipeline. Seven stages is plenty; five is usually right.
• Automating before mapping the journey. Build the stages, drag a handful of real contacts through manually for a fortnight, then wire up workflows. Automating a broken process just breaks it faster.
• No “Lost” hygiene. Add a “Lost” stage and a workflow that moves lost deals into a long-term nurture campaign. Most “lost” deals are “not yet” — the money is in the follow-up.
• Letting the pipeline mirror your org chart. Stages named after team members (“With Dave”) break the moment Dave leaves. Customer states, always.

Once it’s live

Watch two numbers weekly: how many contacts sit in each stage, and the average age of contacts in each stage. A healthy pipeline moves. If “Qualifying” has 200 contacts with an average age of 40 days, your qualification automation isn’t running — or your leads are junk and nobody’s admitting it.

The pipeline is the spine of the whole CRM. Get this right and calendars, conversations and campaigns all bolt onto it cleanly. Those get their own guides.