The stages almost everyone uses
Names vary; the shape does not. Nearly every B2B pipeline is a version of this:
| Stage | What it means | The buyer has… |
|---|---|---|
| Lead | Someone who might be a fit | …done nothing yet |
| Qualified | Confirmed fit, budget and need | …answered questions honestly |
| Meeting | A real conversation is booked | …given you time |
| Proposal | Numbers are in front of them | …asked what it costs |
| Negotiation | Terms are being agreed | …involved someone who signs |
| Won / Lost | It resolved | …decided |
Read the right-hand column on its own. Every entry is something the *buyer* did. That is not a stylistic choice — it is the only way stages stay honest.
The test for whether a stage is real
A deal may only move forward when the buyer takes an action you can name. If you cannot name it, the deal has not moved and you are describing your own optimism.
This sounds pedantic until you watch a forecast fail. Pipelines rot when stages track effort — *I sent the proposal*, *I chased them twice* — because effort is entirely under your control and therefore says nothing about whether money is coming. A deal sitting in Proposal because you sent one is not the same as a deal in Proposal because they asked for one.
Why most teams have too many stages
Stages get added when something goes wrong. A deal stalls at legal, so someone adds a Legal Review stage. A deal needs a demo, so someone adds Demo Scheduled. Each addition is individually reasonable and the total is a pipeline nobody updates, because moving a deal now requires a judgement call between two stages that mean nearly the same thing.
Five to seven stages is where most teams land after they have simplified. If two stages are consistently skipped, or consistently entered on the same day, they are one stage.
Stage probability, and how it goes wrong
Most tools let you attach a percentage to each stage — Proposal is 60% likely to close, and so on — and then multiply it by deal value to produce a weighted forecast. This is useful and routinely abused.
The percentage is meant to be derived from your own history: of the last hundred deals that reached Proposal, how many closed? If you have not measured that, the number is a guess dressed as arithmetic, and a weighted forecast built on guesses is less honest than an unweighted list, because it looks precise.
Until you have enough closed deals to calculate real rates, the more useful view is a plain count of deals per stage and how long each has been sitting there.
Time-in-stage is the metric people skip
A deal that has been in Negotiation for six weeks is not a deal in Negotiation. It is a lost deal that nobody has marked lost, and it inflates the forecast every week it stays there.
Set a rough expected duration per stage from your own data and treat anything at double that as needing a decision — revive it with a specific next action, or close it out. The pipeline exists to tell you the truth. A pipeline padded with corpses does the opposite.
Lost reasons are worth more than they cost
Marking a deal Lost with one word — price, timing, competitor, no decision — takes two seconds and is the only structured feedback most sales teams ever collect. After fifty deals it will tell you something you did not know, and *no decision* being the largest category is the most common and most actionable finding there is.
Once the stages are clean, the next question is what to do with the numbers: sales forecasting without a data team covers the arithmetic.