A sales pipeline for a service business is a short list of stages, where each stage records something the customer did or something that happened, and every open job sits in exactly one. Six to eight stages is plenty. If you cannot say what moves a job into a stage, the stage should not exist.
Most pipelines go wrong because they are built from the seller’s point of view: “Warm”, “Hot”, “Negotiating”. Those are feelings. Two people will put the same customer in different stages. A stage like “Quote sent” cannot be argued with, and that is what makes sales pipeline management possible.
The rule: each stage is something the customer did
Check each proposed stage with one question: how would a stranger looking at the record know the job belongs there? If the answer is a date, a message, a booking or a document, keep it. If the answer is “the rep’s gut”, rewrite it.
| Weak stage | Better stage | Evidence |
|---|---|---|
| Warm lead | Contacted | A two-way conversation is logged |
| Interested | Site visit booked | A date is in the calendar |
| Negotiating | Quote sent | The document went to the customer |
| Hot | Customer replied after the quote | A reply is logged |
| Closing | Verbal yes | The customer said yes, awaiting paperwork or deposit |
A starting set of sales pipeline stages
Use this as a template and change the names to match how your customers talk.
- New enquiry. They have contacted you and nobody has replied. This stage should be nearly empty at the end of each day.
- Contacted. You have had a real conversation, by phone or message. A voicemail left does not count.
- Booked. A site visit, consult, discovery call or appointment is in the diary.
- Quote or proposal sent. The document has gone out. Record the value and the date.
- Decision pending. The customer has replied or acknowledged, and is deciding. This is where follow-up lives.
- Won. Accepted, with a deposit, signed agreement or confirmed booking.
- Lost. Closed with a required reason from a fixed list.
Notice what is absent. There is no “nurture” or “cold” stage inside the main pipeline. People who are not ready now belong in a separate follow-up list with a future date, so the main pipeline only holds live opportunities. People who stall at an early stage need steady contact, and our lead nurturing examples show what to send them.
The same idea for three kinds of business
The principle holds across industries; the stage names change.
A trade or home-services business
New enquiry, Contacted, Site visit booked, Site visit done, Quote sent, Decision pending, Won, Lost. The extra “Site visit done” stage is there because a lot of quotes stall between the visit and the written price. Seeing a pile of records in that stage tells you where your own delay is.
A clinic or practice
New enquiry, Contacted, Appointment booked, Attended, Treatment plan or engagement sent, Decision pending, Started, Lost. “Attended” matters because a booked appointment that does not happen is a different follow-up from one that does. Accountants and other professional practices run a version of this too, which we cover in CRM for accounting firms.
A builder
New enquiry, Contacted, Site or plans reviewed, Quote or estimate sent, Decision pending, Contract signed, Lost. Building jobs take longer to decide, so the Decision pending stage will hold records for weeks, and that is fine as long as each one has a dated next action. See how builders follow up quotes.
Exit rules: what must be true to move a stage
For each stage, write two lines in plain words: what must be true to enter, and what happens next. Put it in a shared document. Here is one example:
- Quote sent: enter when the written price is delivered to the customer. Next: a follow-up task due in two business days.
- Decision pending: enter when the customer has replied or confirmed receipt. Next: a check-in task on a date the customer agreed to, or a week out if none was agreed.
- Lost: enter when the customer says no, or after your last follow-up goes unanswered. Required: a lost reason.
Those timings are examples. Set yours to match your sales cycle, and change them after you see how long jobs really take.
Every open record needs a next action
A pipeline is a list of promises. A record in any open stage without a dated next action is a promise to nobody. Make it a habit, or a required field, that no record can be saved in an open stage without one.
Review the board once a week by sorting on the next action date. Anything overdue is either a task you forgot or a dead job you have not closed. Both are worth knowing about. The number of follow-ups worth making is covered in how many times to follow up a quote.
Lost reasons are the most useful field you have
When a job is marked Lost, require a reason from a short list. Something like:
- Price
- Timing
- Chose someone else
- No response
- Not a fit (outside area, wrong service)
- Project cancelled
After a quarter, count them. A worked example, with invented numbers: if you lose 40 jobs and 22 are “No response”, your problem is follow-up. If 22 are “Price”, your problem is positioning or how you present the quote. The fix is different, and without the reasons you would guess.
How to measure a pipeline without a statistics degree
You only need three numbers per month, and a CRM can show them.
- Conversion from Quote sent to Won. Quotes won divided by quotes sent. Track it per month and per job type.
- Time in stage. Average days in Quote sent and Decision pending. Rising numbers mean slowing follow-up.
- Value in the pipeline. The total of open quotes. Useful, but treat it as a rough guide, because not every quote will convert.
For example, if you sent 20 quotes last month and won 6, your quote conversion is 30 per cent. Those are invented figures; use yours. A rough pipeline value is far less useful than the trend in conversion and time in stage.
Reading the board on a Monday morning
Once the stages are fixed, a weekly look at the pipeline takes ten minutes and tells you where to spend the week. Go from right to left, from closest to a decision back to the newest.
- Decision pending. Which of these have a next action dated this week? Do those first. Which have none? Add one now.
- Quote sent. Any older than your follow-up rule allows? Contact them today.
- Booked. Are the site visits and consults confirmed for the coming days? A short confirmation text reduces no-shows.
- Contacted. Who has gone quiet since you spoke? Decide whether to move them forward or to the follow-up list.
- New enquiry. This should be empty or close to it. Anything here is a customer waiting on you, which is the cheapest lead to lose. Our guide to how fast to reply to an enquiry covers targets for it.
Working right to left matters because the records nearest a decision are the most valuable, and the ones most likely to be neglected while you chase fresh leads.
A stale-job rule
Agree how long a record may sit in each stage before someone must act. For example: two days in New enquiry, five in Contacted, and a set number of follow-ups in Decision pending before the job is closed as Lost with a reason. The exact numbers depend on how fast your customers decide, so start with your best guess and adjust after a quarter. What matters is that the rule exists and the system shows the records that have broken it.
Common mistakes with pipeline stages
- Too many stages. At fifteen, nobody knows which to pick. Merge until each stage has a clear entry.
- Stages for your internal tasks. “Draft quote” and “Check pricing” are work steps and say nothing about what the customer did. Use tasks for those.
- Jobs that never leave. If records sit in Decision pending for months, close them as Lost with a reason, and move the person to a future follow-up list.
- One pipeline for everything. If you sell a one-off job and a recurring service, they behave differently. Give each its own pipeline.
Setting it up in your CRM
Any CRM can hold these stages. The harder part is agreeing them, then keeping the names fixed. Build the pipeline before you import data or add automation, as in our CRM implementation steps. If you are still working from a sheet, CRM vs spreadsheet explains when the move is worth it. CentriWeb can set up and look after a pipeline like this as part of its CRM service.