GoHighLevel pipeline setup for a service business, stage by stage
A pipeline is not a to-do list. Each stage should mean something specific and trigger something automatic. Here is the structure I use and why.
The most common pipeline I see has stages like “New”, “In progress” and “Done”. It tells you nothing and automates nothing. A good pipeline mirrors how a customer actually moves from enquiry to invoice.
The seven stages
- New lead. Created automatically from forms, Meta ads, calls and chat. Speed-to-lead fires here.
- Contacted. Moved automatically when the lead replies or you log a call. Starts the three-day follow-up if nothing is booked.
- Appointment booked. Moved when a calendar slot is taken. Confirmation plus 24-hour and 2-hour reminders.
- Quoted. Moved when you send the estimate. Nudges on day 1, 3 and 7, each one short and different.
- Won. Deposit paid or contract signed. Triggers the job-scheduling sequence and, later, the review request.
- Lost. Record the reason. Tagged for the 90-day reactivation campaign.
- Completed. Job done and invoiced. Review request goes out two hours later.
Rules that keep it honest
- Stages move automatically wherever possible. Humans forget; triggers do not.
- Every opportunity has a value, even an estimate. Otherwise the reports are meaningless.
- Nothing sits in a stage for more than seven days without a task being created for someone.
The two reports to watch
Conversion by stage: what share of leads become appointments, and appointments become quotes, and quotes become jobs. If one step is weak, that is where to spend time. Cost per won job by source: this is what tells you whether Meta ads, Google or referrals deserve more budget.
Want this built with your own stages and automations? Book a free audit.