GoHighLevel Pipelines & Opportunities: CRM Setup (2026)

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

On this page: Pipelines vs opportunities · Designing stage names · Recommended stage ladder · Creating opportunities automatically · Stage-change automations · Pipeline hygiene rules · Reporting and forecasting · Multi-pipeline setups · Team accountability · Common mistakes · FAQ

Most GoHighLevel pipelines I audit were built in ten minutes on day one and never touched again. Half the leads never become opportunities, the board is clogged with cards that haven't moved since last quarter, and the owner — knowing the pipeline value is fiction — goes back to running the business from their inbox.

It doesn't have to be that way. In this guide I'll walk through how I build pipelines for Australian service businesses: the stage design, the automations, the hygiene rules, and the reporting that turns a kanban board into a forecast you can trust.

Pipelines vs opportunities: what's actually what

The terminology trips people up, so let's nail it down. A pipeline is the container: an ordered set of opportunity stages describing your sales process from first enquiry to won or lost. An opportunity is a single deal card sitting in exactly one stage of one pipeline at a time, carrying a monetary value, a status (open, won, lost, or abandoned), an assigned user, and a link to the contact record.

The distinction that matters: a contact is a person; an opportunity is a potential sale attached to that person. One contact can have multiple opportunities — a past client returning for a second project should get a fresh card, not a resurrected old one. Opportunities also inherit the contact's custom fields and tags, so anything you capture on a form (budget, service interest, suburb) can drive how the card is valued, routed, and filtered later. Everything below works on any plan — see the current GoHighLevel pricing page if you're deciding between tiers, because unlimited pipelines are included even at entry level.

Designing stage names around buyer commitment

The single biggest design error I see: stages named after internal admin. "Sent brochure." "Left voicemail." "Need to chase." Those describe your activity, not the buyer's commitment — and a card can sit in them forever without anything actually being true about the deal.

Good stage names are past-tense facts about the buyer. "Discovery call booked" is verifiable — either the appointment exists or it doesn't. When every stage is an observable buyer behaviour, your team stops arguing about where a card belongs, and your conversion reporting starts to mean something, because each transition represents real progress rather than a rep's optimism.

Three tests for a stage name

Before adding a stage, run it through these: (1) would two team members agree, without discussion, whether a deal belongs here? (2) does entry represent more buyer commitment than the previous stage? (3) does something specific fire when a card lands here? Fail any of the three and it's a task, a tag, or a note — not a stage.

A recommended stage ladder for a service business

For a typical Australian service business — trades, allied health, consultants, agencies — I deploy a variant of this seven-stage ladder, with entry criteria and a matching automation documented per stage.

Seven stages is the ceiling, not the target. For a short sales cycle — say, emergency plumbing — collapse it to four: New Enquiry, Contact Made, Quoted, Won/Lost. Use the smallest ladder that still tells you where deals die.

Creating opportunities automatically from forms, calls and DMs

A pipeline only reflects reality if every lead becomes an opportunity, and humans are terrible at doing that manually. So don't let them. Build one Workflow per lead source, each ending in a Create Opportunity action that drops the card into New Enquiry with a default value and the source recorded in a custom field.

The usual set: a Form Submitted trigger for website and funnel forms; a Customer Replied trigger filtered to Instagram, Facebook, and Google Business messages for DM leads; and a call-based trigger for phone enquiries coming through your LeadConnector tracking number. For that last one, pair it with a missed-call safety net — I've written a full walkthrough in my missed call text back setup guide — so an unanswered call still creates a card and fires an SMS instead of vanishing.

Two details that save headaches later: keep "Allow Multiple Opportunities" off for most service businesses (so a lead filling in three forms doesn't create three cards), and set a realistic default monetary value per source so pipeline totals mean something from day one — reps update the value at Proposal Sent.

Stage-change automations: where the leverage lives

This is where GoHighLevel pipelines beat a spreadsheet. Two triggers do the heavy lifting: Pipeline Stage Changed (fires when a card moves between stages) and Opportunity Status Changed (fires when it's marked won, lost, or abandoned). Between them, you can automate everything that happens around the sale. Three patterns I build on every project:

1. Entry actions. Each stage change triggers its own Workflow: Proposal Sent starts the follow-up sequence and creates a call task; Discovery Booked kills the chase sequence (use Remove From Workflow so booked leads stop getting chased). If you're new to building these, start with my primer on GoHighLevel Workflows, triggers and actions.

2. Stale-opportunity rescue. Add a 7-day Wait after stage entry: if the card hasn't moved, send a re-engagement SMS ("Hi {{contact.first_name}}, still keen to get that quote sorted?"), notify the assigned user, and add a stale tag; a second wait at 21 days escalates to the manager. This one Workflow recovers more revenue than any ad campaign, because it works leads you've already paid for.

3. Won/lost housekeeping. On Opportunity Status Changed to Won: fire the onboarding handover and schedule the review request. On Lost: require a loss reason (a dropdown custom field) and route the contact into a 90-day nurture — a decent share of "lost" service leads buy within six months from whoever stayed in touch.

Pipeline hygiene rules your team can actually follow

Automation handles most hygiene, but you still need a few human rules, written down and enforced. Every open card must have an assigned user, a monetary value, and a next task — no orphans. No card sits in one stage longer than 14 days without a logged activity; the stale-rescue Workflow flags breaches automatically. Close your losses: marking cards Lost with a reason is what makes your conversion data honest. Finally, run a 15-minute weekly review — filter the board by "no task scheduled" and by the stale tag (smart lists on the contacts side make this quick), and clear both before Monday's marketing meeting. Fifteen minutes a week is the entire ongoing cost of a trustworthy pipeline.

Reporting: conversion, velocity and forecast

Once opportunities are created automatically and stages reflect buyer commitment, the reporting section (and your dashboards) becomes genuinely useful. Three numbers to watch:

Stage-to-stage conversion. A weak enquiry-to-booking rate is a speed-to-lead problem; a weak proposal-to-won rate is a pricing or follow-up problem — the ratios tell you where to work. Velocity. Average days per stage exposes bottlenecks; if cards spend 12 days in Proposal Sent, your follow-up cadence is too polite. Forecast. The sum of open values weighted by historical stage conversion gives a defensible revenue forecast — only as good as your hygiene. Build all three into a custom dashboard so the owner sees them without asking; the official HighLevel help centre documents the current dashboard widgets and opportunity report filters.

Multi-pipeline setups: sales vs onboarding

One pipeline should answer one question. The sales pipeline answers "will they buy?" — so a Won deal shouldn't keep haunting the sales board. Create a second Onboarding pipeline (Welcome Sent → Kick-off Booked → In Delivery → Complete → Review Requested) and use the won-status Workflow to create a fresh opportunity there automatically. Sales sees a clean board of live deals, delivery sees active clients, and you can report on each function separately.

The same logic extends to genuinely different offers — a $500 service and a $50,000 retainer shouldn't share a ladder. But resist sprawl: if two pipelines have identical stages, they should be one pipeline with a tag separating the offers. This flexibility is one of the clearest differences when you compare GoHighLevel vs Pipedrive — HighLevel bundles unlimited pipelines with the automation engine rather than gating them by seat count.

Team accountability: assignment and round robin

An unassigned opportunity is an unowned outcome, so the opportunity-creation Workflow should include an Assign User step. For teams, distribute new enquiries round robin — via the Workflow's assignment action or round-robin calendars at the booking step — so leads are shared evenly and no single rep becomes the bottleneck.

Then make ownership visible. Filter the board by owner in the Monday review and read out each rep's stale count and proposal conversion — the data settles arguments that opinions can't. Conversation AI can handle first-response and qualification around the clock, but a named human still owns every card; the AI books the call, the rep closes the deal.

Common mistakes to avoid

• Stages named after internal admin ("Sent info", "To chase") instead of buyer commitments — cards drift and reporting turns to mush.
• Manually creating opportunities. If a human has to remember to add the card, 30–40% of leads never make it onto the board.
• Too many stages. Twelve-stage pipelines feel thorough but nobody maintains them; keep it to seven or fewer.
• No monetary values on cards, which makes pipeline totals and forecasts meaningless from day one.
• Deleting lost opportunities instead of marking them Lost — you destroy your conversion history and your nurture list in one click.
• Letting won deals sit in the sales pipeline instead of handing them to an onboarding pipeline, so the sales board never reflects live deals.

If you want a pipeline that your team actually keeps clean — with automations doing the chasing — 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 ordered set of stages that describes your sales process, while an opportunity is an individual deal card that moves through those stages. Each opportunity belongs to one contact, sits in exactly one stage at a time, and carries its own value, status, and assigned user.

How many stages should a GoHighLevel pipeline have?

Five to seven stages suits most service businesses; short-cycle businesses can run four. Every stage must pass three tests: two team members would agree a deal belongs there, it represents more buyer commitment than the previous stage, and something specific happens when a card enters it. Anything else should be a task or a tag, not a stage.

Can GoHighLevel create opportunities automatically?

Yes. Build Workflows using triggers such as Form Submitted, Customer Replied (for social DMs), or inbound call events on your LeadConnector number, then add a Create Opportunity action that places the card in your first stage with a default value, lead-source field, and round-robin user assignment.

How do I stop opportunities going stale in my pipeline?

Use a Pipeline Stage Changed trigger with a Wait step: if a card hasn't moved after 7 days, automatically send a re-engagement SMS, create a task for the assigned user, and tag the card as stale; escalate to a manager at 21 days. Combine that with a 15-minute weekly review of cards with no scheduled task.

Should I use separate pipelines for sales and onboarding?

Yes. When a deal is marked Won, a Workflow should create a fresh opportunity in a dedicated onboarding pipeline (Welcome Sent through to Review Requested). This keeps the sales board showing only live deals, gives delivery its own clean view, and lets you report on each function separately.