A sales pipeline is just a way of answering one question: for every deal you're working on, where is it and what happens next? Get the stages right and that answer is a glance. Get them wrong — too many, too vague, or not matched to how you actually sell — and the pipeline becomes a chore nobody keeps up to date.

This guide covers what each stage means, how many you actually need, and a simple template you can copy today. It's written for small sales teams, not enterprise sales operations — so no "solution engineering handoff" stages you'll never use.

What a sales pipeline stage actually is

A stage is a step a deal passes through on its way to a decision. Each one should represent a real, observable change — not a mood or a guess. "Interested" isn't a stage; it's a feeling. "Proposal sent" is a stage, because either you sent one or you didn't.

That's the test for every stage you add: can you tell, objectively, when a deal has entered it? If two people would disagree about which stage a deal is in, the stage is too fuzzy — and a fuzzy pipeline is one nobody trusts.

The 6-stage template you can copy

Most small B2B sales teams can run their entire pipeline on six stages. Here's the template, with what each one means and when a deal moves out of it.

1. Lead — A new contact worth pursuing. No real conversation yet.
2. Qualified — You've confirmed there's a genuine fit: a real need, roughly the right budget, and a reason to act.
3. Contacted / Meeting — A two-way conversation has happened. You understand what they want; they understand what you do.
4. Proposal — You've sent a quote or proposal. The ball is in their court.
5. Negotiation — They're engaged on terms, price, or scope. A decision is close.
6. Won / Lost — The deal closed, one way or the other. Both outcomes matter — losses tell you where deals stall.

That's it. Six stages, each with a clear entry point. Notice there's a Qualified stage early on: the fastest way to clog a pipeline is to let every vague lead sit in it forever. Qualifying early keeps the pipeline honest, so the numbers you see reflect real, live opportunities.

Adapt it to how you sell

Treat the template as a starting point, not gospel. A team that sells after a single demo might merge Contacted and Proposal. A team with a longer cycle might split Qualified into "Discovery" and "Qualified". The principle holds: every stage earns its place by marking a real, observable step.

How many stages should you have?

For a small team, five to seven is the sweet spot. Fewer than four and the pipeline doesn't tell you enough. More than seven and it becomes admin — deals get stuck between hair-splitting stages and people stop updating it.

A good rule: if you can't explain what makes a deal move from one stage to the next in a single sentence, you have too many. The point of stages is clarity, not precision for its own sake.

Stages are only useful if deals actually move

Here's where most pipelines quietly fail. The stages are fine — but deals sit in them for weeks because nobody's tracking movement. A pipeline isn't a filing cabinet; it's a picture of momentum. Two habits keep it honest:

Give every open deal a next step with a date. A deal with no scheduled next action isn't really in your pipeline — it's just a hope. This is also the thing that makes a pipeline predictable: if every deal has a next step, nothing goes quiet by accident.

Watch for deals that stop moving. A deal that's been in "Proposal" for three weeks is telling you something. The best small-team CRMs surface these for you rather than making you hunt — so a stalled deal gets a nudge before it goes cold. (More on that in logging calls and next steps properly.)

Common pipeline-stage mistakes

Stages based on your process, not the buyer's. "Sent to legal" is about you. "Negotiation" is about where the buyer is. Stages that track the buyer's journey are far more useful for forecasting.

A "nurture" black hole. A stage where deals go to be forgotten. If something genuinely isn't active, close it as lost (you can always reopen it) rather than letting it inflate your pipeline.

Too many stages, added one at a time. Pipelines rarely start bloated — they get that way as people add a stage to capture some edge case. Review your stages every few months and merge the ones that don't earn their keep.

Making it real in a CRM

Pipeline stages work best when moving a deal forward is a single, satisfying action — a drag from one column to the next — and when the pipeline is visible to the whole team without anyone compiling a report. That's exactly how FoxLink's drag-and-drop pipeline works: set your stages once, drag deals as they progress, and everyone sees the same live picture. If you're still weighing up tools, we wrote a companion guide on choosing the best CRM for a small sales team.

But the tool matters less than the discipline. Six clear stages, a next step on every deal, and a quick look each morning at what's stalling — do that consistently and your pipeline stops being a data-entry task and starts being the thing that tells you exactly where to spend your day.