GoHighLevel Pipeline Setup: Designing a Sales Pipeline That Forecasts Revenue (2026)

Most GoHighLevel pipelines are built as glorified to-do lists. Stages have vague names, no exit criteria, and opportunity values that someone entered once and never touched again. The result is a pipeline view that looks busy but tells you nothing about next month's revenue. This post walks through how to build a GHL sales pipeline that produces a genuine weighted forecast — one you can actually base financial decisions on.

Why most GHL pipelines don't forecast revenue

GoHighLevel gives you the infrastructure: Opportunities, pipeline stages, opportunity values, and a pipeline report. What it doesn't give you is a forcing function to use those tools correctly. The common failure pattern is:

• Stages defined by activity ("Proposal Sent") rather than buyer progress
• Opportunity values left blank or filled with rough guesses
• No stage probability assigned, so every deal looks equally likely
• Opportunities that never move because no one is responsible for advancing them

A pipeline that forecasts revenue needs four things working together: well-defined stages with clear exit criteria, accurate opportunity values, realistic stage probabilities, and automated hygiene to keep data current.

Designing stages with exit criteria

Each stage in your GHL pipeline should represent a verifiable step forward by the prospect — not an action you took. The question to ask for every stage is: "What has to be true for an opportunity to sit here, and what has to happen for it to move forward?"

Exit criteria are the minimum conditions that must be met before an opportunity advances to the next stage. Without them, stages become subjective and different team members move deals inconsistently, which destroys forecast accuracy.

For a consultative B2B sale — common for Australian agencies and service businesses using GHL — a six-stage pipeline works well. Below is a reference pipeline with exit criteria, probability weightings, and an example weighted value calculation in AUD.

These probabilities should be calibrated to your own historical close rates over time. The numbers above are a starting point, not a permanent setting.

Setting opportunity values accurately

The opportunity value in GHL is the field that drives your weighted forecast. For project-based work, enter the total contract value. For recurring services, enter either the monthly recurring revenue (MRR) or the first-year contract value — pick one and use it consistently across every opportunity.

If your service has variable scope, use custom fields to record the components (e.g., setup fee, monthly retainer, add-ons) and populate the main opportunity value field with the total. Custom fields are available under Contacts → Custom Fields in GHL, and you can attach them to the opportunity record directly.

For upsells and expansions, create a separate pipeline rather than cramming expansion revenue into the same pipeline as new business. Mixing the two makes your forecast harder to read and your conversion rates meaningless.

Using stage probability to calculate your weighted forecast

Once every opportunity has a value and every stage has a probability, GHL's pipeline report multiplies them automatically. The weighted value for any opportunity is:

Weighted Value = Opportunity Value × Stage Probability

So if you have ten opportunities at Proposal Sent stage, each worth $5,000 AUD, your weighted forecast contribution from that stage is $30,000 (10 × $5,000 × 60%). This is not a guarantee — it's a probability-adjusted estimate. The forecast becomes meaningful when your stage probabilities reflect actual historical conversion rates and your opportunity values are honest.

In the GHL pipeline report (accessed under Opportunities → Reports), you can see total pipeline value, weighted pipeline value, and conversion by stage. Export the report monthly and track whether your weighted forecast is over- or under-predicting closes. Adjust stage probabilities annually as you accumulate data.

If you are also scoring inbound leads before they enter the pipeline, a behaviour-based lead scoring system in GoHighLevel can help you prioritise which opportunities deserve the most attention at each stage.

Automations that keep opportunities moving

A pipeline with accurate data requires consistent human input, which means you need automations to prompt that input rather than leaving it to memory. In GHL, this means building Workflows that trigger based on stage age or inactivity.

Useful pipeline automations include:

• Stale opportunity alert: If an opportunity has not changed stage in 7 days, send an internal notification (SMS or email) to the assigned user with the opportunity name and current stage.
• Stage-entry task creation: When an opportunity moves to Discovery Complete or Proposal Sent, automatically create a follow-up task assigned to the rep with a due date.
• Value prompt: If an opportunity is created with a $0 value, trigger an internal notification asking the rep to update the value within 24 hours.
• Lost reason capture: When an opportunity is moved to Lost, trigger a short internal form or custom field update asking for the loss reason. This data is invaluable for refining stage probabilities later.

All of these are built in Automation → Workflows using the "Opportunity Stage Changed" or "Opportunity Created" triggers. Keep these workflows simple — one trigger, one or two actions. Complex multi-branch automation belongs in your onboarding or nurture sequences, not your pipeline hygiene workflows.

If you are onboarding new clients through GHL and want to connect pipeline stages to a structured client setup process, the GoHighLevel SaaS mode client onboarding system covers how to integrate pipeline movement with your client delivery workflow.

Pipeline hygiene rules

A forecast is only as good as the data behind it. Establish these hygiene rules and enforce them with automation and team accountability:

• Every opportunity must have a value greater than zero before it leaves the New Lead stage.
• Opportunities that have had no activity in 14 days must be reviewed in the weekly pipeline meeting — either advanced, put on hold with a note, or marked Lost.
• Lost opportunities must have a loss reason recorded via a custom field (e.g., "Price", "Timing", "Chose competitor", "Uncontactable").
• Closed Won opportunities should trigger a snapshot or tag that initiates onboarding, so the pipeline and delivery systems stay in sync.
• Run a pipeline audit monthly: sort by oldest opportunity, check for duplicates, and verify that stage probabilities in Settings still reflect current conversion rates.

For deals where speed of follow-up affects conversion — particularly inbound leads — a fast initial response is one of the highest-leverage pipeline activities. The GHL speed-to-lead 5-minute response workflow explains how to automate the first contact so leads don't go cold before they reach your pipeline.

Reading the pipeline report

GHL's pipeline report gives you three views worth monitoring regularly:

1. Total pipeline value: The sum of all open opportunity values, unweighted. This is your theoretical maximum revenue if every deal closes.
2. Weighted pipeline value: The probability-adjusted forecast. This is the number to use for revenue planning.
3. Stage conversion rate: The percentage of opportunities that advance from each stage to the next. A sudden drop in conversion at a particular stage (e.g., Proposal Sent → Negotiation) is a signal to investigate — pricing, proposal quality, or follow-up process may need attention.

Review the weighted pipeline weekly for deal-level decisions, and monthly for trend analysis. If your weighted forecast consistently over-predicts closes, your stage probabilities are too high. If it consistently under-predicts, they're too low. Adjust by stage, not uniformly.

Common mistakes to avoid

• Using stage names that describe your actions rather than the buyer's position (e.g., "Email Sent" instead of "Qualified")
• Setting probability to 0% or 100% on every stage, which removes all nuance from the forecast
• Allowing opportunities to pile up in early stages because moving them to Lost feels like failure — a clean Lost pipeline with good loss reasons is more useful than a bloated active pipeline
• Creating too many stages — five to seven is sufficient for most service businesses; more than eight stages usually means you're tracking tasks, not buyer progress
• Not separating new business from expansion or upsell revenue into distinct pipelines
• Forgetting to update opportunity values when scope changes mid-deal
• Running pipeline reviews without looking at the stage conversion rates — the number that reveals where deals are dying

If you want a pipeline that gives you a reliable revenue forecast, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

How many stages should a GoHighLevel sales pipeline have?

Five to seven stages suits most Australian service businesses and agencies. Each stage should represent a distinct and verifiable step in the buyer's decision process. If you find yourself with more than eight stages, audit them — you may be tracking internal tasks rather than buyer progress, which belongs in a project management tool or a separate post-sale pipeline, not your sales forecast.

How do I set stage probabilities in GoHighLevel?

Stage probability is configured in the pipeline settings under Opportunities → Pipelines → Edit Pipeline. Each stage has a probability percentage field. Set these based on your historical close rates from each stage — for example, if 60% of deals that reach Proposal Sent eventually close, set that stage to 60%. If you don't have historical data yet, use the reference table in this post as a starting point and revise after your first quarter of consistent data.

Can GHL calculate a weighted revenue forecast automatically?

Yes. Once you have assigned an opportunity value to each open deal and set stage probabilities, GHL's pipeline report calculates weighted pipeline value automatically. Access it under Opportunities → Reports. The weighted value is the sum of (opportunity value × stage probability) across all open deals. This figure updates in real time as you move opportunities and edit values.

What triggers should I use to automate pipeline stage movement in GHL Workflows?

The most useful triggers for pipeline automation are "Opportunity Stage Changed," "Opportunity Created," and "Appointment Status Changed." Use "Opportunity Stage Changed" to create tasks, send internal notifications, or trigger follow-up sequences when a deal moves to a specific stage. Use "Opportunity Created" to enforce data quality rules like value entry. Avoid automating the stage movement itself unless the signal is unambiguous — for example, a signed contract or a completed payment, which are reliable enough to trigger an automatic move to Won.

How often should I audit my GoHighLevel pipeline?

Run a brief deal-level review weekly, focused on stale opportunities and upcoming follow-up tasks. Run a full pipeline audit monthly: check for deals with missing values, review stage conversion rates in the pipeline report, archive or mark Lost any opportunities with no activity in the past 30 days, and verify that your stage probabilities still reflect current conversion rates. A quarterly review of the overall pipeline structure — stage names, exit criteria, and whether you need additional custom fields — keeps the system aligned with how your business actually sells.