How many sales pipeline stages should we have?
There is no ideal universal number. Use the smallest set that captures meaningful changes in your buyers’ process.
Lynka guide
Pipeline stages should describe progress, not decorate a board.
A useful sales pipeline has a small number of stages that everyone interprets the same way and that correspond to meaningful changes in the buying process.
Teams often add stages because the board looks too simple. The result is a pipeline where “Qualified,” “Discovery,” “Needs Analysis” and “Evaluation” mean different things to different reps and nothing reliable to a report.
Good stages reduce ambiguity. A manager should be able to ask why a deal is in a stage and hear evidence, not a feeling.
01
Start with buyer progress
A stage should represent something materially different about the sale: the opportunity has been qualified, a commercial proposal exists, a decision is pending or the deal has reached an outcome.
Avoid stages that exist only to describe internal busyness, such as “Follow-up 2,” unless that step truly changes how the team manages the opportunity.
02
Write an entry rule for every stage
An entry rule explains what must be true before the deal moves in. For example, a proposal stage might require a real commercial offer to have been prepared for the buyer.
Entry rules reduce pipeline inflation because reps cannot advance a deal simply to make it look active.
03
Write the condition that moves the deal forward
An exit rule defines the evidence that justifies the next stage. It could be customer feedback, internal approval, a scheduled decision meeting or acceptance of the commercial offer.
If no one can explain the exit rule, the stage may be too vague to be useful.
04
Treat amount and probability as separate from stage names
Expected amount should describe the commercial value the team is working with. Probability should express likelihood according to the company’s chosen method. A stage can influence probability, but the two concepts do not have to be identical.
Do not rename a stage “80%” and assume that creates forecasting discipline.
05
Make the expected close date evidence-based
The close date should reflect the buyer’s decision timing, procurement step, contract event or another plausible milestone. Repeatedly pushing the date without understanding why is a signal worth reviewing.
A close date is a forecast assumption, not a promise. Record changes honestly rather than protecting an old forecast.
06
Require a believable next action
Every open opportunity should have a next action that could change the state of the sale. “Check in” is weak unless the rep knows what they are checking for.
Activities with owners and due dates turn the pipeline from a static forecast into an operating list.
07
Make won and lost real outcomes, not pipeline stages
A won deal should represent a completed sales outcome. A lost deal should leave the active pipeline and, where useful, carry a reason that can be reviewed later.
Do not keep dead opportunities in an open stage simply because the team hopes the customer may return months later. A future sale can become a new opportunity.
08
Review stage aging and attention, not only totals
Pipeline value by stage is useful, but managers should also inspect deals with old next actions, repeatedly pushed close dates or long stage duration.
A healthy pipeline review asks whether the evidence still supports the deal, not merely whether the total pipeline number is large enough.
Stage-design workshop
- List the real buying milestones in your current process.
- Remove stages that describe the same buyer state.
- Write one sentence for entry into each stage.
- Write one sentence for exit from each stage.
- Define when an opportunity is won.
- Define when it is lost.
- Require an owner and next action on every open deal.
- Review old and repeatedly pushed deals separately.