Pipeline Stages in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers what pipeline stages are, how to design them for a service or sales process, how stage changes trigger automations, the difference between stages and tags, how to manage multiple pipelines, and the common stage design mistakes to avoid.

Reading time: about 5 minutes.

What Are Pipeline Stages in HighLevel?

Pipeline Stages in HighLevel are the named steps that define a contact’s position in a sales or service process. Each stage represents a distinct milestone – a point in the journey between first contact and completed transaction.

Stages appear as columns on the Kanban board in the Opportunities section. Each opportunity (a contact + deal combination) sits in exactly one stage at a time.

As the deal progresses, the opportunity card is moved to the next stage – either manually by dragging the card or automatically through a Workflow Builder action.

Configure pipeline stages at Settings, then Pipelines.

Where to Configure Pipeline Stages

Settings, then Pipelines shows all pipelines in the sub-account. Create a new pipeline by clicking to add.

Give the pipeline a name. Then add stages – click to add each stage and give it a descriptive name.

Drag the stages into the desired order. Save the pipeline.

The pipeline and its stages immediately appear in the Opportunities section as a Kanban board. Opportunities can be created and placed into any stage from the board or from a contact’s record.

Designing Stages for a Service Business

A service business – home services, medical practice, legal firm – typically tracks both the sales process (lead to booked appointment) and the service delivery process (appointment to invoice paid). A unified service pipeline might look like: New Lead, Contacted, Estimate Scheduled, Estimate Sent, Follow-Up Needed, Booked, Job In Progress, Job Completed, Invoice Sent, Invoice Paid, Won, Lost.

The “Won” and “Lost” terminal stages are important for reporting. Won means a deal that successfully converted to revenue.

Lost means a deal that was qualified but did not close. Having both terminal stages allows tracking conversion rates – what percentage of leads in the pipeline ultimately become Won deals versus Lost.

Not every deal needs to pass through every stage. A lead who calls, books immediately, and pays on completion moves from New Lead straight to Booked, then Job Completed, then Invoice Paid.

The intermediate stages for that deal are simply skipped.

Designing Stages for a Sales Process

A sales-oriented pipeline – agencies selling marketing packages, consultants selling retainers, B2B businesses – typically focuses on qualification and progression to close. A sales pipeline might look like: New Lead, Qualified, Discovery Call Scheduled, Discovery Call Completed, Proposal Sent, Negotiation, Closed Won, Closed Lost.

Sales pipelines benefit from having clear entry criteria for each stage – what must be true about a deal before it moves to the next stage? A deal should not move to “Proposal Sent” until the proposal actually goes out.

A deal should not move to “Qualified” until the lead has been called and confirmed as a viable prospect. Clear criteria prevent the pipeline from drifting into inaccurate representations of where deals actually are.

The Kanban Board View

The Kanban board is the primary visual interface for pipeline management. It shows all active opportunities as cards arranged in columns by stage.

Each card displays the contact name, deal value if configured, and other key fields. The board makes the entire active pipeline visible at once – which stages have many deals, which are empty, which deals have been stagnant for too long.

The Kanban view is how a business owner answers the daily question “where does everything stand?” without talking to anyone or pulling a report. New leads in the left column.

Deals awaiting follow-up visible in their stage. Jobs in progress in the mid-board.

Completed jobs with pending invoices in the late stages. The pipeline is the operational state of the business’s sales and service activity at a glance.

Moving Deals Through Stages

Deals move through stages in two ways: manually and automatically.

Manual movement is the most common for front-line tracking – a team member reviewing the Kanban board, noting that an estimate has been sent, and dragging the opportunity card from “Estimate Scheduled” to “Estimate Sent.” Manual stage updates require someone to remember to update the pipeline, but they also provide a natural review moment – the act of moving the card is an opportunity to assess whether the deal needs follow-up.

Automatic movement happens via a Workflow Builder action – Update Opportunity Status or Move to Stage – that moves a deal to a specified stage when the action is reached in a workflow. When an appointment is booked through the HighLevel calendar, a workflow can automatically move the associated opportunity to the “Booked” stage.

When an invoice is marked paid, a workflow can move it to “Invoice Paid.”

Stage Changes as Workflow Triggers

The Opportunity Stage Changed trigger in Workflow Builder fires when an opportunity moves to a specified stage. This is the connection between Kanban board movement and automated communication or CRM actions.

Moving a deal to “Job Completed” fires a review request workflow. Moving it to “Estimate Sent” fires a follow-up sequence.

Moving it to “Lost” adds a “Closed Lost” tag and potentially fires a re-engagement sequence scheduled for 90 days later. Each stage transition becomes an automation trigger – making the pipeline a driver of automated behavior, not just a visual tracking tool.

For this to work reliably, stage updates must happen consistently. A “Job Completed” workflow trigger only fires when someone actually marks the opportunity as Job Completed.

Teams that do not consistently update the pipeline miss the automation triggers that depend on those updates – which is the same problem as not updating appointment statuses.

Multiple Pipelines

A sub-account can have multiple pipelines for distinct processes. A home services company might have a Residential Pipeline and a Commercial Pipeline with different stages.

A real estate team might have a Buyer Pipeline and a Seller Pipeline. A marketing agency might have a Client Acquisition Pipeline and a Client Retention Pipeline.

Multiple pipelines allow tracking different processes on different boards – each optimized for its specific process – without mixing stages from different workflows. In the Opportunities section, switch between pipelines via the pipeline selector.

Stages vs. Tags

Pipeline stages and tags serve different roles. An opportunity can be in exactly one stage at a time – stages represent a linear position in a process.

A contact can have many tags simultaneously – tags represent attributes, statuses, and categories that are not mutually exclusive.

Use stages to track the primary process position: where is this deal in the sales or service journey? Use tags to track everything else: behavioral flags (Estimate Requested, Review Left), source indicators (Referral, Google), status attributes (VIP, Unresponsive), and any categorization that does not fit the linear stage model.

A deal in the “Estimate Sent” stage might have tags for “Source: Google,” “Insurance Claim,” and “Urgent Timeline” – attributes that are relevant to how the deal should be handled but do not represent its position in the sales process. Stages and tags are complementary, not competitive.

Common Stage Design Mistakes

Too many stages is the most common design mistake. A pipeline with 20 stages becomes a burden to maintain – every deal requires many updates to pass through the board, and team members start skipping stages rather than keeping up with the overhead.

Keep stages to the milestones that actually matter for visibility and automation triggers, not every possible sub-step of the process.

Stages without clear exit criteria is the second common mistake. If there is no shared understanding of what needs to be true before a deal moves from “Contacted” to “Estimate Scheduled,” different team members use the stage differently – and the pipeline becomes an inconsistent picture of the actual process state.

Missing terminal stages (Won and Lost) is the third common mistake. Without terminal stages, deals that are over – either closed or abandoned – linger in the active pipeline indefinitely, cluttering the board and distorting conversion metrics.

What Can You Do With It?

• See the complete state of the business’s sales and service pipeline at a glance: The Kanban board shows every active deal’s position in the process – where new leads are, where estimates are pending, where jobs are in progress – without reports or manual tracking.
• Trigger automated follow-up and actions when deals reach key stages: The Opportunity Stage Changed trigger connects pipeline movement to Workflow Builder automations – the right communication fires at the right moment in the process automatically.
• Identify stalled deals before they fall through the cracks: Deals that have not moved stages in several days are visible on the Kanban board – prompting proactive follow-up before the deal goes cold.
• Track conversion rates from lead to close: With Won and Lost terminal stages, the pipeline produces conversion metrics – what percentage of leads ultimately become Won deals, where the most deals fall out of the process, and which sources produce the highest-converting leads.

Key Definitions

Use Cases by Industry

Home Services – Service Delivery Pipeline

A plumbing company’s pipeline: New Lead, Call Attempted, Appointment Booked, Estimate Sent, Follow-Up, Job Scheduled, Job In Progress, Job Completed, Invoice Sent, Paid, Won, Lost. When a lead comes in via the website form, a workflow automatically creates an opportunity in the New Lead stage.

When the appointment is booked through the HighLevel calendar, a workflow moves it to Appointment Booked. Job Completed triggers the review request workflow automatically.

The owner reviews the Kanban board Monday morning. Anything in “Estimate Sent” for more than 3 days gets a call that day.

Anything in “Invoice Sent” for more than 5 days gets an invoice follow-up. The board is the weekly action list – no report, no spreadsheet, no guesswork about what needs attention.

Result: The pipeline is both the tracking system and the action trigger system. Stage updates are minimal because several stage moves happen automatically via workflows. The board shows what needs human attention; the workflows handle the automated actions.

Real Estate – Buyer Pipeline

A real estate agent’s buyer pipeline: New Inquiry, Consultation Scheduled, Consultation Completed, Actively Searching, Offer Made, Under Contract, Closed, Lost. Moving a buyer to “Consultation Completed” triggers a workflow that sends the consultation follow-up email and creates a task “Set up property alerts – due today.” Moving to “Under Contract” triggers a milestone email to the buyer and a task for the transaction checklist.

The pipeline gives the agent a real-time view of their entire buyer portfolio – how many active buyers are searching, how many have offers in, how many are under contract. The agent can see immediately whether their business is growing (more buyers entering the top of the pipeline) or contracting (fewer new consultations).

Result: Each stage change triggers specific workflows and tasks that the agent would otherwise need to remember manually. The pipeline is both the tracking view and the automation driver – reducing the manual work of client management while maintaining visibility into the entire book of business.

Who Is This For?

How to Set Up Pipeline Stages

Step 1: Map the process before building

Write out every significant milestone in the sales or service process from first contact to paid invoice. Circle the 5 to 10 most important ones – these become the stages.

Step 2: Navigate to Settings, then Pipelines

Open the Pipelines settings. Create a new pipeline with a descriptive name.

Step 3: Add stages in order

Add each stage in process order. Include Won and Lost as terminal stages at the end.

Step 4: Define exit criteria

For each stage, define what needs to be true before a deal moves to the next stage. Document this briefly – even a one-line description per stage helps teams use the pipeline consistently.

Step 5: Save and view the Kanban board

Save the pipeline. Navigate to Opportunities to see the Kanban board with the new stages as columns.

Step 6: Create initial opportunities

Add existing active leads as opportunities and place them in the appropriate current stage. Getting real data on the board immediately makes the pipeline useful from day one.

Step 7: Build stage-triggered workflows

In Workflow Builder, create workflows triggered by Opportunity Stage Changed for the most important stages – Job Completed triggers review request, Estimate Sent triggers follow-up sequence.

Step 8: Establish the weekly pipeline review habit

Block 15 minutes each Monday to review the Kanban board. Move stalled deals to follow-up status or to Lost.

The weekly review is the maintenance practice that keeps the pipeline accurate.

Step 9: Track conversion metrics monthly

Monthly, review the proportion of leads that reach Won vs. Lost. Identify which stage has the highest dropout rate – this is where the process or follow-up needs improvement.

How Does It Connect to HighLevel?

• Opportunities: Opportunities are the individual deal records that live within pipeline stages. Each opportunity is assigned to a pipeline and a stage – the combination of pipeline + stage defines where the deal stands.
• Pipeline Management: Pipeline Management is the broader feature covering pipeline operation, reporting, and deal management. Pipeline Stages are the structural foundation of Pipeline Management.
• Workflow Builder: The Opportunity Stage Changed trigger in Workflow Builder connects stage movement to automated actions. Stage changes drive workflows; workflows drive business outcomes.
• Tags: Tags and pipeline stages are complementary systems. Stages track linear process position; tags track multi-dimensional attributes. Both belong on deal and contact records for different purposes.
• Contact Management: Every opportunity is linked to a contact record. The opportunity’s stage is visible on the contact’s activity timeline – part of the complete record of the contact’s history with the business.

Common Questions

What are Pipeline Stages in HighLevel?

Named steps in a sales or service process displayed as Kanban board columns. Opportunity cards move between stage columns as deals progress.

Stage changes trigger Workflow Builder automations.

Where do I create and edit Pipeline Stages in HighLevel?

Settings, then Pipelines. Create a pipeline, add stages in order, save.

The pipeline appears as a Kanban board in the Opportunities section.

How many Pipeline Stages can I have in HighLevel?

No strict limit, but 5 to 10 stages is the practical sweet spot. Fewer lacks visibility; more creates update overhead that teams avoid.

Can stage changes trigger automations in HighLevel?

Yes. The Opportunity Stage Changed trigger in Workflow Builder fires when a deal moves to a specified stage – connecting pipeline movement to automated communication and CRM updates.

Can I have multiple pipelines in HighLevel?

Yes. Multiple pipelines with different stage sets for different processes – residential vs. commercial, sales vs. renewal.

Each is viewable as a separate Kanban board in the Opportunities section.

What is the difference between Pipeline Stages and Tags in HighLevel?

Stages track linear process position (one stage at a time). Tags track multi-dimensional attributes (many tags simultaneously).

Use stages for process tracking; use tags for everything else.

To Wrap It Up

Pipeline stages are the structured visibility layer that separates businesses that know where their deals stand from businesses that are guessing. The Kanban board with well-designed stages answers the most important daily operational question – “what needs attention today?” – at a glance without reports, without asking team members, and without relying on memory.

The automation layer on top of stages is what makes the pipeline an active business system rather than a passive tracking board. Stage changes that trigger review requests, follow-up sequences, and task creation mean the pipeline does work rather than just representing work.

Every move of an opportunity card activates the appropriate automation for that stage – no manual follow-through required.

Design the stages before building any pipelines. A few minutes mapping the actual process and identifying the key milestones produces a stage structure that the team uses consistently.

Stages designed reactively – adding a stage whenever something seems like it needs one – produce the cluttered, over-staged pipelines that teams abandon.

1. Map the sales or service process on paper – from first contact to completed transaction
2. Identify the 5 to 10 key milestones that have operational significance
3. Navigate to Settings, then Pipelines and create the pipeline with those stages
4. Add Won and Lost as terminal stages
5. Add existing active leads as opportunities in their current stage
6. Build Workflow Builder triggers for the most important stage changes
7. Establish a weekly Kanban board review – move stalled deals, identify conversion bottlenecks

Add the terminal stages (Won and Lost) on day one – not after several months of use. Deals that are over but not marked as Won or Lost accumulate in active stages, making the pipeline board misleading.

A pipeline that shows 200 active opportunities when 80 of them are actually dead deals is not a useful management tool. Clean terminal stages from the start keep the board accurate and the conversion metrics meaningful.