How a Sales Pipeline Actually Works

It's Tuesday, 7pm. You're a plumber, three quotes out this week, and you honestly can't remember which one you promised to ring back. One of them just booked someone else.

That gap — quote sent, nothing chased — is where most jobs leak. A sales pipeline fixes it by giving every enquiry a place to sit and a next step. Here's how a pipeline actually works, and how to choose stages that match the job you do, not a template built for enterprise sales teams.

Key takeaways

• A pipeline is a row of stages every lead moves through, from first enquiry to paid.
• A valid stage is an observable event the customer caused — never a feeling.
• Map ten real jobs to find your true stages instead of copying someone else's.
• More stages don't fix a leak; naming the missing follow-up step does.

What is a sales pipeline, in plain terms?

A sales pipeline is the row of stages every lead moves through, from "just enquired" to "paid and done". Each stage is a holding spot. Each lead sits in exactly one stage at a time, and moving them forward means something specific happened.

Think of it as a whiteboard with columns. New enquiry in the first column. Quote sent in the next. Booked in the one after. When you can see every lead in a column, you can see where they're stuck — and stuck leads are lost jobs.

Most owners already run a pipeline in their head or a notebook. Writing it down is the first win, before you touch any software.

Why generic pipeline advice doesn't fit a trade

Standard sales pipelines use words like "Discovery", "Proposal" and "Negotiation". That's language for a software rep chasing a six-month deal. It's useless for a sparky quoting a switchboard on Thursday.

Your pipeline runs enquiry to job to payment. Something closer to: New Enquiry → Quote Sent → Booked → Job Done → Invoiced → Paid. Every one of those is a real thing that happens in your week. That's the whole point — the stages should read like your day.

Don't force B2B sales stages onto a job that's really a booking and an invoice. If the advice doesn't sound like your trade, it isn't for you.

What makes a stage valid?

A valid stage is an observable event the customer caused — not a feeling you have about them. "Warm lead" fails the test. Warm is your mood, not their action. "Quote opened" passes, because they did something you can point to.

Run every proposed stage through one question: Did the customer do something I can see?

• "Contacted" — did they reply, or did you just leave a voicemail? Split it: Attempted vs Replied.
• "Interested" — fails. There's no event.
• "Deposit paid" — passes. Money moved.
• "Booked" — passes. A time is on the calendar.

When stages are events, moving a lead forward is a fact, not a guess. Two people looking at the board agree on where everyone sits. That's what makes the board trustworthy at 7pm when you're tired.

The exercise: write down your last ten jobs

Stop guessing your stages. Write your last ten jobs across a page and, for each one, list every step from first contact to money in the bank. Enquiry came in how? What happened next? When did they commit? When did you get paid?

Do it for all ten. The steps that show up on nearly every job are your stages. The ones that appear once aren't stages — they're exceptions you handle by hand.

This beats any template because it's built from your actual work. A cleaner's pipeline and a physio's pipeline look different, and they should. If you want to see where those steps quietly break, our guide to finding where your pipeline leaks walks through the same map from the leak side.

Set exit criteria for each stage

Every stage needs an exit rule: the one thing that must happen before a lead moves to the next column. Without it, leads drift and the board turns to mush.

• New Enquiry exits when you've made contact and captured what they want.
• Quote Sent exits when they accept — not when you "feel good" about it.
• Booked exits when the job's done.
• Invoiced exits when the payment lands.

Write the exit rule next to each column. Now anyone can move a lead correctly, and "where's this one up to?" has one answer.

Split the sales process from the job process

Keep selling and doing as two separate flows. The sales pipeline ends at Won — they said yes. The job process (schedule, do the work, invoice, collect) is delivery. Cramming both into one giant row is why pipelines balloon to twelve columns.

A long sales pipeline with delivery stages bolted on looks busy but tells you nothing about where you're losing jobs. Keep the sales side short and sharp. Handle delivery in your booking and quote-to-invoice flow instead.

Why a twelfth stage hides the leak

Adding stages feels like progress. It isn't. If quotes go out and nothing comes back, splitting "Quote Sent" into "Quote Sent", "Quote Viewed" and "Quote Considered" doesn't win a single job. It just gives the leak more places to hide.

The fix is a follow-up step with a clear action, not another column. When a quote sits three days with no reply, someone chases it. That's the leak, sealed. Our post on automating quote follow-ups shows the exact chase sequence to run so no quote goes cold.

Most owners get this wrong: they redesign the board when they should just chase faster. Speed to reply matters — see the 60-second rule on speed-to-lead.

How IgniteOS does this for you

Build your pipeline once and IgniteOS moves leads through it as things happen. A new enquiry from your website, a form or a missed call lands in the CRM and drops into the first stage on its own. When a quote's accepted or a deposit's paid, the lead advances — no dragging cards at 9pm.

The automations handle the chase: quote sits too long, IgniteOS texts and emails the follow-up for you, so the leak seals itself.

Want to see the whole flow from first click to booked job? Start with how leads flow through IgniteOS, and our calculator puts a typical replaced stack at about $18,000 a year — one login instead of the pile of apps you're juggling now.

One step to take today: write your last ten jobs across a page and circle the steps that repeat. That's your pipeline, and you'll spot the leak before you finish the list.

Frequently asked questions

What are the stages of a sales pipeline for a service business?

For a trade or service business, stages should map to the job: New Enquiry, Quote Sent, Booked, Job Done, Invoiced and Paid. Skip generic B2B labels like "Discovery" or "Proposal". Each stage should read like a real step in your week, and the ones that show up on nearly every job are your true stages.

How many stages should a sales pipeline have?

Keep the sales side short — usually four to six stages from enquiry to won. Too few loses visibility on where leads stall; too many creates admin. Adding a twelfth stage doesn't fix a leak, it just gives it more places to hide. Fix the missing follow-up step instead of splitting columns.

What makes a pipeline stage valid?

A valid stage is an observable event the customer caused, not a feeling you have. "Warm lead" fails because warm is your mood. "Quote accepted" or "deposit paid" passes because the customer did something you can point to. Run every stage through one test: did the customer do something I can see?

How do I stop losing quotes I've sent?

Add a follow-up step with a clear action, not another column. When a quote sits three days with no reply, someone chases it. IgniteOS can text and email that follow-up for you automatically, so quotes don't go cold. See how leads move through the whole flow at /solutions/get-leads.