How many pipeline stages should you have?
Most working pipelines settle around 5 to 7 stages. The count matters less than whether each stage marks a real change in the buyer's behaviour.
The short answer
- 5 to 7 stages is the most common working range for a sales pipeline; fewer than 4 tends to hide where deals stall, and more than 8 tends to track internal admin rather than the buyer's actual behaviour.
- A stage earns its place only if it marks something the buyer did (agreed to a demo, requested pricing, signed), not something the seller did internally, like 'proposal drafted' with no buyer action attached.
- A pipeline that requires reps to regularly skip stages, or that has two stages meaning almost the same thing, has more stages than the sales process actually needs.
- The stage list should match how that specific product is bought; a six-month enterprise sale and a same-day self-serve purchase should not share a stage list just because they share a CRM.
Why the number itself is the wrong first question
Teams often start by asking how many stages a pipeline should have, as if there is a universal count that fits every sales motion. There is not. A pipeline stage should represent a change in the buyer's behaviour or commitment, something the buyer did, not something the seller checked off. Once that filter is applied, the right number of stages falls out of the actual buying process rather than a general rule.
Most sales processes, once mapped this way, land somewhere between 5 and 7 stages: initial contact, qualified interest, some form of evaluation or demo, a proposal or pricing discussion, a decision point, and closed won or lost. Processes with a genuinely longer cycle (multi-stakeholder enterprise deals) sometimes need one or two more to separate distinct evaluation phases; short-cycle, low-touch sales sometimes need fewer.
The failure mode on the high end is stages that track internal admin: "proposal sent to legal", "internal approval pending", "waiting on finance". These describe what the seller's organization is doing, not what the buyer is doing, and they tend to accumulate over time as different teams each want visibility into their own step. The result is a pipeline that looks precise but actually obscures where the deal really stands with the buyer.
A common 6-stage baseline and what marks each transition
| Stage | What moves a deal into it |
|---|---|
| New / Contacted | First outreach sent or inbound lead received |
| Qualified | Buyer confirmed fit (budget, need, authority, or timeline signal) |
| Meeting / Demo | Buyer agreed to a call or demo |
| Proposal / Pricing sent | Buyer requested or received pricing |
| Negotiation | Buyer raised specific terms, objections, or a decision timeline |
| Closed Won / Closed Lost | Buyer signed, or the deal is confirmed dead |
A starting point, not a template; stages should be renamed and adjusted to match the specific buying process.
How to check whether your own stage list is working
Pull the last 20 to 30 closed deals and look at how they actually moved through the pipeline. If several stages are consistently skipped, they are not describing real transitions and should be merged or removed. If deals frequently jump backward between two stages, those two stages might actually be one stage with an internal sub-task attached to it. If a stage's name describes an internal task rather than a buyer action, it is a candidate for removal from the pipeline (it can still exist as a task on the deal).
Disclosure: SalesCrew is our product. Deal stages are configurable per pipeline, with weighted forecasting based on stage probability, and a deal's timeline shows every stage change with a timestamp, which makes this kind of audit a query rather than a manual review of every deal. It does not tell a team what its stages should be named; that stays a judgment call about the actual buying process.
More stages is not more control
Questions
- Is there a correct number of pipeline stages?
- No single correct number exists, but pipelines with 5 to 7 stages are the most common working range across sales teams. Fewer than 4 tends to hide where deals actually stall; more than 8 tends to track internal process rather than buyer behaviour.
- What is a sign a pipeline has too many stages?
- If reps regularly skip stages, or if a stage exists purely to mark an internal task (like 'contract sent to legal') rather than a change in the buyer's behaviour, the pipeline has drifted into tracking process instead of the deal.
- Should every product or team use the same stage list?
- No. A pipeline should reflect the actual buying process for that product, and a six-month enterprise sale and a same-week transactional sale rarely share a stage list. What stays constant is the discipline: each stage should mark a real change in buyer commitment.