A sales pipeline is only as useful as its stages. Get them right and the pipeline becomes a working model of revenue — you can see where every deal stands, forecast what's likely to close, and spot the deals quietly dying. Get them wrong — vague stages, deals parked for months, everyone's “90% sure” — and every number built on top is fiction. This is what the stages mean, how many you need, and how to make them honest.
What is a sales pipeline stage?
A stage is a step a deal passes through on its way to a close, and crucially, each one marks a real change in the deal's odds. A deal in “Proposal” is genuinely more likely to close than one in “Discovery,” and that difference is what lets you forecast. Stages are how you measure progress — separate from how good or how big a deal is.
The test for a stage: does it change how confidently you'd forecast the deal? If two stages would carry the same probability, they're really one stage.
The five core stages
Your exact stages should match how you sell, but most B2B pipelines follow this shape. The probabilities are typical starting points — tune them to your own win data over time.
1. Qualified
~20%A scored, routed lead has become a real opportunity worth working. This is where qualification hands off — fit and intent are established, a rep owns it.
2. Discovery / Demo
~40%You're learning the need and showing fit. Probability rises as the buyer engages and the use case sharpens. Many teams split this into two stages.
3. Proposal
~60%A concrete offer is on the table. This is usually where a required field — budget, decision date, economic buyer — earns its keep before the deal advances.
4. Negotiation
~80%Terms, pricing, and approvals. High-probability but not done — and the stage where deals most often stall, so an SLA flag helps surface the ones going quiet.
5. Won / Lost
100% / 0%The terminal stages. Winning promotes the contact to customer; losing captures a reason that feeds win/loss analysis. Either way the outcome sticks to the record.
How many stages — and how to adapt them
Five to seven is the sweet spot. Fewer and you can't see where deals stall; more and reps stop respecting them. Adapt the shape to your motion: a high-velocity, transactional team might collapse Discovery and Demo into one; an enterprise team might add “Technical validation” and “Procurement.” And because new business, renewals, and partner deals often move differently, it's common to run more than one pipeline — each with its own stages.
Stage probability and the weighted forecast
The reason honest stages matter so much is the forecast. When each stage carries a probability, every open deal counts at its value × that probability — so a $50k deal at a 60% stage contributes $30k. Sum that across the pipeline and you get a weighted forecast that reflects reality instead of the sum of everyone's hope. Drift in the stages — deals sitting in “Negotiation” for a quarter — and the forecast inherits the lie.
Common stage mistakes
Three patterns wreck a pipeline. Activity stages (“Call made”) that track what the rep did instead of where the buyer is. Catch-all stages where deals go to hide. And advancing on hope — moving a deal because the rep feels good, not because something happened. The fix for the last one is structural: require the fields that prove a stage was truly reached.
How KudosCRM handles stages
In KudosCRM you configure each stage's probability, color, SLA, and required fields, set the terminal Won and Lost stages, and turn on rules that restrict skipping or backtracking. Deals only advance when they qualify, stale deals surface with a filter, and the weighted forecast updates the moment a deal moves. You can run multiple pipelines, and renaming or archiving a stage never rewrites history — transitions snapshot the stage name at the time of the move.