Ask two salespeople where a deal stands and you will often get two answers - "it’s hot", "it’s nearly there" - that mean nothing you can act on. That gap is almost always a pipeline-stage problem: stages named after feelings instead of facts.
Fix the stages and a lot of pipeline confusion disappears. This guide is about defining stages that describe something anyone can verify, so two people always agree where a deal is and what comes next.
What makes a good pipeline stage?#
A good stage is an observable fact, not an opinion. "Quote sent" is something anyone can check; "warm lead" is a feeling that rots in a week. When stages are facts, the pipeline becomes trustworthy - two people will always place a deal in the same stage, which is what lets you act on it.
Why name stages by buyer action, not feeling?#
Because feelings drift and facts do not. A rep who is optimistic calls everything "hot"; a cautious one calls the same deals "warm". Name the stage after what the buyer has actually done - enquired, been qualified, received a quote, responded - and the optimism drains out of the pipeline, leaving something you can forecast from.
How many stages should you have?#
Five to seven for most teams. Fewer than five and the stages are too vague to guide the next action; more than seven and reps stop updating because it feels like admin. A durable default: New enquiry, Qualified, Quoted, Negotiation, Won, Lost - with a Site visit or demo stage added only for longer cycles.
How do you write an exit rule per stage?#
Write one line per stage naming the observable thing that must be true before a deal advances. It removes the arguments and the wishful thinking - a deal that cannot meet the rule stays put, however far along it "feels".
| Stage | Exit rule (advances when…) | Next step |
|---|---|---|
| New enquiry | A lead has arrived from any source | Qualify within 24 hours |
| Qualified | Need, decision-maker and rough budget confirmed | Prepare and send a quote |
| Quoted | A written quote has been sent | Follow up on the quote by a set date |
| Negotiation | The buyer has responded with questions or a counter | Resolve the open point, set a decision date |
| Won | Written or verbal go-ahead received | Hand over to delivery |
When should you add or merge a stage?#
Only when a deal genuinely behaves differently there. If deals do real, distinct work in "Site visit done", it earns a stage; if it is just a feeling between Qualified and Quoted, cut it. Long cycles like real estate or machinery often need one extra stage; transactional sales may not even need Negotiation. The test never changes: does a deal behave differently here?
Want stages built around how you actually sell? Book a quick CIPHER CRM demo or message us on WhatsApp.