GoHighLevel Sales Pipelines with Custom Stages

Before creating a single pipeline, I mapped every path an opportunity can take through the business — new leads, review requests, giveaway entrants, mobile gym survey respondents, and formal lead intake. Each path became its own pipeline, so no two unrelated processes share the same board.

The primary sales pipeline. Every new lead lands here and moves through 5 clean stages from first contact to close. Workflows drop opportunities in at the top stage automatically, and stage advancement is triggered by actions (booked appointment, quote sent, deposit received, closed). This is where the day-to-day sales work happens.

A dedicated pipeline for the reputation / review process. Happy customers are pushed into this pipeline and moved across 4 stages (review requested → review clicked → review posted → verified), so the team always knows which requests are outstanding and which have converted — no more guessing at Google review performance.

A lightweight 2-stage pipeline built specifically for giveaway campaigns. Entrants land in stage 1, and winners / converted entrants move to stage 2. Keeps giveaway leads completely separated from real sales opportunities so the main forecast never gets polluted.

A 3-stage pipeline that tracks respondents from the Mobile Gym survey through follow-up. Respondent → Contacted → Converted. Purpose-built so the team can work survey follow-ups without them getting lost inside the main lead pipeline.

The most detailed pipeline in the stack: a 7-stage formal lead intake flow used for higher-touch leads that need qualification, discovery, and structured onboarding before they ever reach the main sales pipeline. Ensures the team follows the exact same intake protocol on every single high-value lead.

Every pipeline got stages named in the client's own language — not generic 'Stage 1 / Stage 2' placeholders. Total: 21 custom stages across 5 pipelines, each with a clear entry rule and a clear exit rule so nothing ever sits ambiguously in-between.

Pipelines aren't manual. Workflows automatically create opportunities in the right pipeline on trigger events (form submission, survey submission, status change, giveaway entry) and move them across stages when the corresponding action happens (email opened, appointment booked, deposit paid, review posted). The team drags cards only when a human judgment call is required.

Every opportunity in every pipeline must eventually resolve as Won, Lost, or Abandoned — with a reason. This gives real reporting data: which sources close, which stages leak, and which campaigns actually produce revenue.

The end result: a real-time, drag-and-drop view of the entire business across 5 pipelines. Owners can see forecast, team can see workload, and campaigns like giveaways and surveys have their own accountable board — all inside one clean GoHighLevel Pipelines architecture.