Designing Pipeline Stages That Match How You Sell

Almost every CRM ships with a default pipeline — Lead, Contacted, Qualified, Proposal, Negotiation, Won — and almost every business keeps it, because changing it feels like a decision nobody has time for. Then six months later the board is full and nobody trusts it. Our guide to pipelines, stages and the deals you are actually going to close starts here, because a pipeline is only as useful as its stages are unambiguous.

A stage is a thing that happened

The single rule that fixes most pipelines: every stage must name an event you could prove. "Quote sent" is provable — either it went or it did not. "Interested" is not, and two colleagues will place the same deal in different columns depending on how the last call felt.

Test each of your stages by asking what specifically has to have happened for a deal to enter it. If the answer is a feeling, rename it after the action that usually accompanies that feeling — a viewing booked, a sample requested, a decision-maker introduced.

Follow the customer, not your process

Internal steps do not belong on the board. "Waiting for manager approval" and "preparing quote" are things you do, not stages the deal has reached, and they clutter a view that should answer one question: how close is this to money.

Where an internal step genuinely takes days and blocks progress, it can earn a stage — but the test is whether the customer would recognise the state they are in, not whether your team recognises the task.

Four to six is usually right

Too few stages and everything sits in the middle one. Too many and cards stop moving because nobody is sure of the difference between stage four and stage five, and updating the board becomes a chore that gets skipped.

1. New enquiry — someone has made contact and nothing has been established yet.
2. Qualified — you know what they want, roughly what it costs, and that they can buy.
3. Quoted — a specific price for specific work is in their hands.
4. Committed — they have said yes and something concrete has happened: a deposit, a signature, a date in the calendar.
5. Won or lost.

Five stages covers most service businesses. Add one only when you can name the decision it helps you make — and if a whole category of work keeps skipping stages, the answer is a second board rather than a longer one, as set out in when one pipeline is not enough.

“

If two people can look at the same deal and disagree about its stage, you do not have a pipeline. You have a mood board.

— be digital ai team

Put qualification early and mean it

The most valuable stage boundary is the second one, because it is where you decide whether to spend time. A deal that cannot articulate what it wants, has no budget, or is talking to the wrong person should not advance — and should be marked lost rather than left drifting in stage one for a quarter.

In a chat CRM most of that qualification happens in the conversation itself, often before a human reads it, which is the subject of qualifying and routing leads automatically. The pipeline should reflect the outcome of that, not repeat it.

Write down the exit criteria

For each stage, write one sentence describing what must be true to leave it. Not a document — one line, visible to everyone. "Leaves Quoted when the customer responds to the quote, in either direction."

This is the difference between a board everyone maintains the same way and one where each person has their own private interpretation. It takes ten minutes to write and is the single highest-return thing you can do to your pipeline.

Expect to change it once

Your first design will be wrong in one specific way, and you will find out within a month — usually because one stage holds eighty per cent of the deals, meaning it is really two stages, or because a stage is permanently empty, meaning it is not a real step. Fix it once, deliberately, and then leave it alone: a pipeline that changes shape every quarter cannot produce a comparison, and comparison is most of what a pipeline is for. When you do change it, decide where existing deals go before you delete a column, because bulk-moving them afterwards is exactly the sort of tidy-up covered in cleaning a pipeline that has gone stale.