Reverse your thinking and your forecast gets more accurate
A stage is a claim about the buyer. Not a checklist for the seller. Define them that way and the pipeline stops lying to you.
Process · 7 min read
How to define sales process stages
Sales process stages should describe what the buyer has done, not what the seller just finished doing. Each stage needs one exit criterion you can verify from the record, like a problem statement in the buyer's own words or a meeting that happened with whoever signs. Stages built that way forecast reliably, because buyer behavior predicts outcomes and seller activity does not.
Most sales stages describe what the salesperson did. And once that is how the pipeline reads, reps manage their activity instead of the deal. Here is the structure I run into most:
Contacted, Qualified, Scheduled, Demo Complete, Following Up, Proposal Sent, Won, Lost.
Every one of those can be true while the buyer has no intention of purchasing anything.
The test for a good stage
A stage needs an exit criterion a manager can check without relying on the rep's read of the room. If the only evidence is that the rep feels good about it, the stage is doing no work for you.
- It describes something the buyer did or agreed to
- Someone else could confirm it from the record
- It is binary. The deal meets it or it does not
- Meeting it changes the odds of closing in a way you can see in the numbers
A workable default set
Five stages is usually right for a B2B cycle under six months. Fewer and you cannot see movement. More and reps start guessing which one applies, which is worse than having no stages at all.
Stage 1. Qualified
The buyer has described a problem in their own words and confirmed it is worth solving this year. You know roughly what it costs them today. Exit criterion: a written problem statement plus a reason to act on a timeline. Something like "current system cannot handle multi-currency invoicing and their auditor flagged it in March."
Stage 2. Scoped
You know what a solution has to do, who is affected, and what they already tried. Exit criterion: the buyer has agreed to a written summary of requirements.
Stage 3. Validated
The people who would use the thing have seen it and said it solves the problem. Exit criterion: a technical or user stakeholder confirmed fit, in writing or on a call your manager could listen to.
Stage 4. Economic buyer engaged
Whoever controls the budget has been in a conversation, not copied on an email. You know the approval path and the dates on it. Exit criterion: a meeting happened with the person who signs.
Stage 5. Agreement
Terms are in negotiation and the buyer has named a decision date. Exit criterion: the buyer has reviewed pricing and there is a mutual close plan.
Nothing in that list mentions a demo. A demo is an activity. It can happen in stage two or stage four, and by itself it tells you nothing about whether the deal closes.
Rules that keep the stages honest
- 01Deals move forward one stage at a time. A skip means the earlier criterion was never met.
- 02Deals can move backward. A team that never regresses a deal is lying to its own forecast.
- 03The manager owns the definitions. The rep applies them.
- 04A stage with no exit criterion gets deleted, not debated.
Rolling it out
Rewriting stages in the CRM takes an afternoon. Getting a team to apply them the same way takes a quarter of weekly reinforcement. Expect month one to look worse than the old pipeline, because it will finally be accurate. Tell your board that before it happens, not after.
The moment that decides everything is the first forecast call where a rep wants a deal to stay in stage four without ever having met the economic buyer. Whatever the manager does on that call becomes the real process. Not the document.