Get your audit

Guide Intelligence

Sales pipeline stages for a service business.

A service business can run on six stages from first inquiry to paid job: new inquiry, contacted, visit booked, quote sent, won, and paid, with lost as the exit. Each stage has one rule for moving forward and one number to watch.

Marcus Barber, Digital Solomon ยท Updated

The stages, from inquiry to paid job

The stages follow what actually happens to a job: someone asks, you reach them, you see the work, you price it, they say yes, and they pay. A pipeline is simply that path made visible. The help pages for GoHighLevel describe pipelines as visual tools that show the progress of leads, deals, or customers from start to finish[1].

  • New inquiry. A call, form, text or message has arrived. Nobody has spoken to them yet.
  • Contacted. A person has had a real conversation and knows what the job is.
  • Visit booked. An estimate visit, a site survey or a diagnostic is on the calendar.
  • Quote sent. The customer has a price in writing.
  • Won. They said yes and the job is scheduled.
  • Paid. The work is done and the invoice is settled.
  • Lost. The exit from any stage, with a reason recorded.

Many businesses stop the pipeline at "won". Keep going to "paid": a job that is done but unpaid is still a sale you have not finished.

What moves a lead between stages

A lead moves only when a specific thing has happened, written down in advance, so two people would put the same job in the same stage. The same help pages make the point directly: stages should be clearly defined and action-oriented so users know exactly when an opportunity should move forward[1].

  • New inquiry to contacted: a two-way conversation happened, not a voicemail left.
  • Contacted to visit booked: a date and time are on the calendar and the customer confirmed.
  • Visit booked to quote sent: the quote left your hands in writing.
  • Quote sent to won: the customer accepted, verbally or in writing, and a start date exists.
  • Won to paid: the invoice is settled in full.
  • Any stage to lost: the customer declined, went quiet past your follow-up limit, or was not a fit. Record which.

Resist adding stages for every nuance. The same guidance advises limiting pipelines to only the stages that matter most[1]. If a stage has no rule for leaving it, it is a note, not a stage.

One number per stage

Watch one number per stage, so you know where jobs stall without building a dashboard nobody reads. Check them monthly.

  • New inquiry: minutes to first human reply. In a 2007 study of calls to web leads at six companies, the odds of reaching a lead decreased by over 10 times in the first hour[5]. See how fast to respond to a new lead for its limits.
  • Contacted: share that book a visit.
  • Visit booked: share of visits that happen as booked.
  • Quote sent: share accepted, and the median days to a decision.
  • Won: days from yes to start.
  • Paid: days from job done to payment.

Lost reasons are the number behind all of these. If "price" leads the list every month, that is a pricing or a qualification question, not a follow-up problem.

Put a source on every record

Every record needs a source field, filled in at the moment the lead arrives, or you will never know which marketing pays. Asking later, from memory, does not work.

  • Use a short fixed list. Google search, Google Business Profile, referral, repeat customer, yard sign, and so on. Free text turns into twenty spellings of the same thing.
  • Fill it automatically where you can. Forms can carry the campaign a visitor came from: Google's analytics help explains adding UTM parameters to links in order to identify the campaigns that refer traffic[4].
  • Ask on the phone when you cannot. "How did you hear about us?" is a fair question on the first call.

With a source on every record, the pipeline answers the question owners care about most: which channel produces paid jobs, not just inquiries.

Pipelines and opportunities in the CRM

In GoHighLevel, each job in a pipeline is an "opportunity", and opportunities move from left to right through the stages as they progress[1]. Each opportunity stores the prospect's contact information, deal value, and historical notes[2].

Its help page also shows an example service business pipeline running from new inquiry through payment collected to onboarding[1], which is close to the shape above. The workflow action that creates an opportunity can populate the opportunity name, source, and status automatically[3], so a form submission can arrive in the right stage with its source already filled.

If you are still deciding on a platform, read whether it suits a small business first.

Keep it honest

A pipeline is only as good as the discipline of moving cards, so make updating it part of an existing routine rather than a separate chore. A stale pipeline is worse than none, because people trust it.

  1. Review the pipeline once a week, in the same meeting, for fifteen minutes.
  2. Close out anything that has sat in one stage past its limit: follow up once more, or mark it lost with a reason.
  3. Check that every new record from the week has a source.
  4. Once a month, write down the six numbers and compare them with last month.

Owning this record, and learning from it, is what our Intelligence pillar is about.

Common questions

How many pipeline stages should a service business have?

Six working stages plus a lost exit covers most service businesses: new inquiry, contacted, visit booked, quote sent, won and paid. Add a stage only if it has a clear rule for leaving it.

Should repeat customers go through the pipeline?

Yes, with the source set to repeat customer. It shows how much of your work comes back, which is worth knowing.

What is the difference between a lead and an opportunity?

A lead is a person who asked. An opportunity is a specific job you might win from them, with a stage and a value. One customer can have several opportunities over time.

Do I need a CRM to run a pipeline?

Not to start. A spreadsheet with the same stages and rules works for a small volume. A CRM helps once leads arrive from several channels and several people handle them.

Sources

  1. HighLevel Support Portal, Understanding Pipelines. https://help.gohighlevel.com/support/solutions/articles/155000001982-understanding-pipelines, accessed November 1, 2026.
  2. HighLevel Support Portal, Understanding Opportunities in HighLevel. https://help.gohighlevel.com/support/solutions/articles/155000001983-understanding-opportunities-in-highlevel, accessed November 1, 2026.
  3. HighLevel Support Portal, Workflow Action: Create Opportunity. https://help.gohighlevel.com/support/solutions/articles/155000004752-workflow-action-create-opportunity, accessed November 1, 2026.
  4. Google Analytics Help, URL builders: Collect campaign data with custom URLs. https://support.google.com/analytics/answer/10917952?hl=en, accessed November 1, 2026.
  5. Dr. James Oldroyd and InsideSales.com, copy hosted by Mortech, The InsideSales.com/MIT Lead Response Management Study (2007). https://www.mortech.com/hs-fs/hub/25649/file-13535879-pdf/docs/mit_study.pdf, accessed November 1, 2026.

Researched and drafted with AI from the sources listed. Reviewed and approved by Marcus Barber before publishing.

Digital Solomon runs GoHighLevel, Pabbly Connect and Ranked.ai in its own work. They are the only tools these guides name. This page has no affiliate links.

Digital Solomon also builds client systems on GoHighLevel.

Find out where you stand.

Eight questions, about five minutes. You see your result right away, and a written audit follows by email within minutes.

Get your AI Readiness Audit