Quick answer: A coaching or consulting pipeline should show the few sales milestones that require a different next action: new inquiry, qualified, call booked, call completed, proposal or decision, follow-up, won, and lost. Keep contact data, tags, and pipeline stages separate so automations and forecasts stay reliable.
A clean GoHighLevel pipeline answers three questions without opening the contact record: where is this deal, who owns the next action, and when is that action due? If the board cannot answer those questions, adding more automation will usually make the confusion faster.
The six-stage pipeline to start with
- New inquiry. A person submitted a form, replied, called, or was entered by the team. The required action is fast first contact and basic qualification.
- Qualified. The problem, fit, and reasonable next step are confirmed. This is not the same as simply having an email address.
- Call booked. A meeting exists on the calendar. Confirmation, reminders, and rescheduling logic belong here.
- Call completed. The conversation happened and the owner must record the decision, objections, value, and promised next step.
- Proposal or decision. A defined offer is under consideration. Every deal needs a decision date and a next follow-up date.
- Won or lost. Closed deals trigger onboarding. Lost deals require a reason so you can separate poor fit, timing, price, no decision, and competitor losses.
Add a separate no-show stage only if the recovery workflow is meaningfully different. Add a long-term nurture stage only if it has an owner and a defined re-entry signal. A stage called “follow-up” with no deadline is usually a parking lot.
Contacts, opportunities, fields, and tags do different jobs
The contact is the person. The opportunity is the possible transaction. A returning client can stay one contact while creating a new opportunity for a new program, engagement, or renewal.
- Opportunity stage: current sales milestone.
- Opportunity value: realistic deal value for forecasting.
- Custom fields: stable facts such as service interest, company size, or qualification answers.
- Tags: temporary behavior or automation signals.
- Notes and tasks: human context and the next accountable action.
For the detailed cleanup rules, use the companion guide on GoHighLevel tags versus custom fields.
Define entry and exit rules before workflows
Each stage needs one entry condition and one exit condition. “Call booked” begins when a valid appointment is created. It ends when the person attends, cancels, or becomes a no-show. The workflow should support that movement, not guess what the salesperson meant.
- Create the opportunity once, then update it instead of creating duplicates.
- Assign a named owner when the opportunity is created.
- Create a task with a due date whenever human judgment is required.
- Stop nurture and reminder workflows when the deal changes stage.
- Record a lost reason before moving an opportunity to lost.
The minimum follow-up automation
Start with the handoffs that prevent revenue loss: immediate confirmation, internal owner notification, appointment reminders, no-show recovery, post-call recap, proposal follow-up, and closed-won onboarding. Do not build twelve branches before the team consistently updates the pipeline.
The post-call process is where many coaching deals disappear. Use the strategy-call follow-up system to define the messages, deadlines, and stop rules.
What to measure
A pipeline becomes useful when it produces a small operating scoreboard. Track new inquiries, qualified rate, booking rate, show rate, proposal rate, close rate, days in stage, lost reasons, and revenue by source. If a stage cannot support a decision or an action, it probably does not belong on the board.
GoHighLevel pipeline FAQ
How many pipeline stages should a coach use?
Start with six to eight stages. Add one only when it changes ownership, follow-up, forecasting, or the next required action.
Should every lead become an opportunity?
No. A subscriber or unqualified contact can remain a contact. Create or advance an opportunity when there is a real potential transaction worth managing in the sales process.
Should tags be used as pipeline stages?
No. Use opportunity stages for sales status, custom fields for stable facts, and tags for temporary behaviors or automation triggers.