GoHighLevel Pipelines & Opportunities Guide (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 16 July 2026 · 9 min read

On this page: Pipelines vs Opportunities · Designing your stages · Building the pipeline step by step · Attaching Workflows to stage changes · Reporting · Patterns for service businesses vs agencies · Common mistakes · FAQ

Most of the pipelines I audit inside Australian sub-accounts have the same problem: they are lovely to look at and completely manual. Leads sit in a stage called “Contacted” for three weeks because contacting them depended on somebody remembering to do it. The pipeline records history instead of driving behaviour, which means it is a diary, not a sales system.

This guide covers how I design pipelines for clients as an HL Growth Partner: what Opportunities actually are under the hood, how to choose stages with clear exit criteria, and — the part that matters most — how to wire Workflows to the Pipeline Stage Changed, Opportunity Status Changed and Stale Opportunity triggers so the follow-up runs itself.

Pipelines vs Opportunities: what each one actually is

A pipeline in GoHighLevel is a container: an ordered set of stages that represents one sales process. You will find them under Opportunities in the left menu, and each sub-account can hold multiple pipelines — one for sales, one for reactivation, and so on.

An Opportunity is a card inside that pipeline. It is not the same thing as a contact. A contact is a person; an Opportunity is a potential deal attached to that person, with its own name, monetary value, owner, source and stage. One contact can hold several Opportunities — the same customer might be a won deal in your services pipeline and an open card in your upsell pipeline at the same time.

Every Opportunity also carries an opportunity status, which is separate from its stage: open, won, lost or abandoned. Stage tells you where the deal sits in the process; status tells you how it ended (or that it has not ended yet). This distinction matters for automation, because HighLevel gives you different Workflow triggers for each: Pipeline Stage Changed fires when a card moves between stages, while Opportunity Status Changed fires when a deal is marked won, lost or abandoned. Confuse the two and your “congratulations, welcome aboard” email goes out when someone merely reaches the proposal stage.

Designing stages that mirror your real sales process

The 5–7 stage rule

Almost every HighLevel pipeline I inherit has too many stages. Twelve stages feels thorough on day one and becomes guesswork by week three, because nobody can tell the difference between “Interested” and “Warm”. My rule: five to seven stages, and each stage must describe a state the deal is in, not an activity you performed. “Booked” is a state. “Called them” is an activity that belongs in the notes, not the board.

Write an exit criterion for every stage

Before building anything, write one sentence per stage: “A card leaves this stage when…”. If you cannot finish that sentence objectively, the stage should not exist. Exit criteria do two jobs. They stop team members parking deals wherever feels right, and they tell you exactly which event each Workflow should hang off. A stage whose exit criterion is “the prospect books a call” pairs naturally with your calendars: the appointment-booked event moves the card, and the stage change triggers the confirmation sequence.

Here is a six-stage pipeline I deploy, with slight variations, for most service businesses:

Notice that every stage has both an exit rule a human can apply and a Workflow that acts while the card sits there. That combination is what makes the pipeline self-running rather than decorative.

Building the pipeline step by step

With the design settled on paper, the build itself takes under an hour:

1. Create the pipeline. Go to Opportunities → Pipelines → Create Pipeline, name it for the process (not “Main Pipeline” — call it “New Client Sales”), and add your stages in order.
2. Set up supporting custom fields. Add opportunity-level custom fields for anything you will report on or personalise with later: lead source detail, service interested in, quoted value. Fields beat free-text notes because Workflows can read them.
3. Standardise your tags. Agree on a small tag taxonomy (source tags, intent tags, disqualification tags) before automation multiplies whatever mess exists. Tags drive smart lists and Workflow branching, so inconsistency here compounds.
4. Automate card creation. Use the Create/Update Opportunity action inside your lead-capture Workflows so every form fill, ad lead and inbound call creates a card in stage one automatically. If cards are created by hand, some leads never enter the pipeline at all.
5. Wire the movement events. Appointment booked moves the card to Call Booked; invoice paid or document signed marks it won. The fewer manual drags, the more trustworthy the board.

If you are setting up the wider account at the same time — calendars, custom values, phone and email deliverability — work through a proper GoHighLevel CRM implementation checklist first, because a pipeline built on a half-configured sub-account inherits every one of its problems. HighLevel’s own documentation at help.gohighlevel.com covers the click-by-click mechanics if you get stuck on a specific screen.

Attaching Workflows so follow-up runs itself

This is the section that separates a Kanban board from a sales machine. Three triggers do most of the work.

Speed-to-lead on entry to stage one

Build a Workflow with the Pipeline Stage Changed trigger filtered to your pipeline and the New Lead stage (or trigger on opportunity creation). Within the first minute it should send a personalised SMS, send an email, and assign a call task to the owner. Response inside five minutes remains the highest-leverage change most businesses can make; pair this Workflow with missed-call text-back so a lead who rings while you are on-site gets a text before they dial your competitor.

Stage-specific nurture

Each stage gets its own nurture Workflow triggered by the card arriving, with a matching “remove from Workflow” goal when the card leaves. Engaged-stage leads get value content plus a booking link; Proposal Sent leads get objection-handling touches on days two, five and nine. If you want replies handled at 11 pm on a Saturday, connect Conversation AI to answer SMS and chat and book appointments straight onto your calendars — the Opportunity card moves itself when the booking lands.

Stale-opportunity revival

The Stale Opportunity trigger fires when a card has sat in a stage beyond a duration you define. I set it at 14 days for proposal stages and 7 days for early stages. The Workflow sends a pattern-interrupt message (“Should I close your file?” outperforms “Just checking in” every time I have tested it), notifies the owner, and after a final non-response marks the status abandoned and shifts the contact to a long-term smart list. Abandoned is the honest status for deals that went quiet; save lost for an actual no, so your loss-reason reporting stays meaningful.

Status-driven handoffs

Finally, use Opportunity Status Changed for the transitions that matter commercially. Won fires onboarding: welcome email, intake form, kick-off booking link, an internal Slack or SMS notification, and a “client” tag that suppresses all marketing sequences. Lost fires a polite close-out and a 90-day re-engagement campaign. None of this requires a human to remember anything — that is the whole point.

Reporting: pipeline value and stage conversion

Once Opportunities carry real monetary values, the dashboard’s funnel and stage-distribution charts become genuinely useful. Two numbers deserve a weekly look. Open pipeline value tells you whether next month’s revenue exists yet; if the top of the funnel is thin today, no amount of closing skill fixes it in thirty days. Stage-to-stage conversion tells you where deals die. If 80% of cards reach Call Booked but only 25% reach Proposal Sent, your problem is show-up rate or call quality, not lead generation — and you fix show-up rate with reminder Workflows, not more ad spend.

Keep the data honest by making status changes mandatory: no card should ever be deleted, only marked won, lost or abandoned with a loss reason in a custom field.

Common patterns: service businesses vs agencies

Local service businesses (trades, clinics, studios) usually need one short sales pipeline like the six-stage example above, plus a second pipeline for quotes or treatment plans if jobs are quoted individually. Speed dominates: the speed-to-lead Workflow and missed-call text-back generate more revenue than everything else combined, because these buyers ring three providers and hire whoever answers first.

Agencies and consultancies run longer cycles, so the Stale Opportunity trigger and proposal follow-up sequences carry more weight, and deal values on cards matter for forecasting. If you manage client sub-accounts, build your best pipeline once, wire its Workflows, then save the whole thing as a snapshot so every new client sub-account starts with a proven pipeline instead of a blank board. On an agency plan, unlimited sub-accounts make this a genuine margin play — check current tiers on the GoHighLevel pricing page.

Common mistakes to avoid

• Stages named after activities, not states. “Follow up sent” is not a stage; it forces constant manual card-shuffling and hides where the deal actually sits.
• No exit criteria. If two team members would file the same deal in different stages, your conversion reports are fiction.
• Creating Opportunities manually. Any lead source not wired to a Create Opportunity action will leak cards — automate creation from every form, ad and call.
• Triggering the won sequence off a stage instead of status. Use Opportunity Status Changed for won/lost/abandoned events; use Pipeline Stage Changed for in-process moves.
• Leaving deal values at zero. Empty values make pipeline-value reporting useless and forecasting impossible.
• No stale-deal safety net. Without the Stale Opportunity trigger, quiet deals rot silently; with it, every stalled card gets one more genuine chance to close.

If you want a pipeline that chases every lead for you — designed, built and automated by a certified team — book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

What is the difference between a pipeline and an opportunity in GoHighLevel?

A pipeline is the container: an ordered set of stages representing one sales process. An Opportunity is an individual deal card that moves through those stages, carrying its own value, owner, source and status. Contacts are people; Opportunities are potential deals attached to those people, and one contact can hold several Opportunities across different pipelines.

How many stages should a GoHighLevel pipeline have?

Five to seven for most businesses. Fewer than five usually hides meaningful steps; more than seven creates ambiguity about where deals belong, which corrupts your conversion reporting. Every stage needs a written exit criterion — if you cannot state objectively when a card leaves a stage, delete that stage.

What does the abandoned opportunity status mean and when should I use it?

Abandoned is for deals that went quiet without an explicit no — the prospect stopped responding. Reserve lost for an actual rejection, ideally with a loss reason recorded in a custom field. Keeping the two separate means your loss reports reflect real objections rather than silence, and abandoned contacts can be routed to a long-term reactivation smart list.

Can a Workflow move an opportunity between stages automatically?

Yes. The Create/Update Opportunity action inside Workflows can create cards, change their stage, update their monetary value and set their status. Common patterns include moving a card to Call Booked when an appointment is scheduled on one of your calendars, and marking it won when an invoice is paid or a document is signed.

How do I copy a finished pipeline to other client accounts?

Save the sub-account containing your pipeline, Workflows, custom fields and tags as a snapshot, then load that snapshot into each new client sub-account. Everything arrives pre-wired, so a new client starts with your proven pipeline and automations on day one instead of a blank board.