CRM

GoHighLevel Pipeline Setup: How to Build a CRM Pipeline Your Team Actually Uses

Step-by-step guide to setting up GoHighLevel pipelines: choosing stages, automating stage changes, tracking won and lost deals, and reporting that shows where revenue leaks.

  • Published
  • Reading time3 min
  • AuthorMuhammad Umar
Book a Free Consultation

A CRM is only as useful as its pipeline. If stages are vague, deals get dragged around randomly, nobody trusts the numbers, and the team goes back to spreadsheets.

This guide shows how we set up GoHighLevel pipelines for service businesses and agencies so they stay accurate with very little manual work.

How GoHighLevel pipelines work

In GoHighLevel, a pipeline is a set of stages. Each deal is an opportunity, linked to a contact, sitting in one stage at a time. Opportunities also have a status (open, won, lost or abandoned), an optional value and any custom fields you add.

Stages describe where a deal is in your process. Status describes how it ended. Keeping those two ideas separate is the foundation of a clean pipeline.

Step 1: Map your real sales process first

Before touching GHL, write down what actually happens from first enquiry to paying customer. For a typical service business it looks like this:

  1. New lead: an enquiry arrives
  2. Contacted: someone has spoken to or messaged the lead
  3. Appointment booked: a call, consultation or visit is scheduled
  4. Appointment completed: the meeting happened
  5. Proposal sent: a quote or proposal is with the client
  6. Won: closed as won (status)

Missed appointments and dead deals are handled with statuses and tags rather than extra stages, which keeps the board readable.

Step 2: Define an entry rule for every stage

Each stage needs a rule that removes guesswork. For example:

  • Contacted means a two-way conversation has happened, not just that an automated text went out.
  • Proposal sent means a price has been shared in writing.

Write these rules into your team SOP. When everyone uses the same definitions, your conversion rates between stages finally mean something.

Step 3: Add the fields you will actually report on

Add opportunity custom fields only for information you will use, such as:

  • Lead source
  • Service or package of interest
  • Estimated deal value
  • Lost reason (dropdown, not free text)

A dropdown for lost reasons, such as price, timing, chose a competitor, no response or not a fit, turns a pile of lost deals into insight you can act on.

Step 4: Automate stage changes from real events

The best pipelines move themselves. In GoHighLevel workflows we typically connect:

EventPipeline update
Form or ad lead submittedCreate opportunity in New lead
Lead replies to first messageMove to Contacted
Appointment bookedMove to Appointment booked
Appointment showedMove to Appointment completed
Appointment no-showTag no-show and start a recovery workflow
Invoice paidMark opportunity Won

Your team then only handles the judgement calls, like sending a proposal or marking a deal lost, instead of dragging every card by hand. Our speed-to-lead guide shows how the first two steps work in practice.

Step 5: Catch deals that go quiet

Stuck deals are where revenue leaks. Use workflows to:

  • Alert the owner when an opportunity has not moved for a set number of days
  • Send a gentle check-in to leads stuck in Proposal sent
  • Add long-dormant deals to a reactivation campaign instead of deleting them

Step 6: Report on conversion, not just volume

Once the pipeline is accurate, three reports tell you almost everything:

  1. Stage-to-stage conversion: where do deals drop off?
  2. Lead source performance: which channels produce won deals, not just leads?
  3. Lost reasons: what is the most common reason you lose, and can you fix it?

Common pipeline mistakes

  • Creating a stage for every tiny step, so nobody keeps it updated
  • Using stages for outcomes like “Lost” instead of the opportunity status
  • Running several near-identical pipelines that split reporting
  • Leaving stage changes entirely manual
  • No lost reason, so the same problem repeats every month

Get your pipeline built properly

A clean pipeline with automated stage changes and reporting is usually part of a full GoHighLevel setup, which typically takes 15 to 25 hours at our flat hourly rate. If you are an agency, we can also package it into a reusable GoHighLevel snapshot. See our GHL services or book a free consultation.

Frequently asked questions

What is a pipeline in GoHighLevel?

A pipeline in GoHighLevel is a visual board of sales stages. Each deal is an opportunity card that moves from stage to stage, with a status of open, won, lost or abandoned and an optional monetary value.

How many stages should a GoHighLevel pipeline have?

Most service businesses work best with five to seven stages. Fewer stages hide where deals get stuck, while too many make the pipeline tedious to maintain and less likely to be used.

Can GoHighLevel move opportunities between stages automatically?

Yes. Workflows can create or update opportunities and move them to a new stage when events happen, such as an appointment being booked, a no-show, a reply, or an invoice being paid.

Should I use one pipeline or several in GoHighLevel?

Use a separate pipeline only when the sales process is genuinely different, such as new client sales versus renewals. Running similar offers through one pipeline keeps reporting simple.

Related articles

Ready to automate your backend and scale your operations?

Get dedicated technical support starting at $10/hour. Let’s build something durable.