Pipeline stage definitions template
Most pipelines are defined by what the seller has done: demo given, proposal sent. Those are activities, and activities do not predict close. This template defines each stage by something the buyer has done, which is the only signal that survives contact with a forecast call.
Download it
What you get
- A stage table with entry and exit criteria written as buyer actions
- Forecast categories kept separate from stages, which is where most CRMs go wrong
- A deal inspection sheet for pipeline reviews
- A hygiene checklist for finding deals that are stalled but still counted
Who it's for
- RevOps and sales ops leads who own the forecast call
- Sales managers running weekly pipeline reviews
- CROs who want forecast categories they can defend to finance
What's inside
5 sections, each listed with its own size. The first is previewed below; the remaining 4 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Stage definitions | 5 columns, 4 worked example rows | Below |
| Forecast categories | 4 columns, 4 worked example rows | In the download |
| Deal inspection sheet | 6 columns, blank working sheet | In the download |
| Pipeline hygiene review | 6-point checklist | In the download |
| Why activity-based stages produce bad forecasts | Guidance notes | In the download |
Preview of section 1
Stage definitions
Exit criteria must describe something the buyer did. If it describes something the seller did, rewrite it.
| Stage | Definition | Exit criteria (buyer action) | Typical duration | Owner |
|---|---|---|---|---|
| Qualified | A real problem, a real budget owner, and a reason to act now | Buyer has named the business problem and confirmed who signs | AE | |
| Validated | Buyer agrees our approach could solve it | Buyer has shown us their current process or data | AE |
How to use it
1. Write exit criteria as buyer actions
'Demo delivered' is something you did. 'Buyer confirmed the problem is worth solving this quarter' is something they did. Only the second predicts anything. Rewrite every exit criterion until it describes the buyer.
2. Keep stage and forecast category separate
Stage is where the deal is; forecast category is how confident you are it lands this period. Collapsing them forces reps to move deals backwards to lower a forecast, which they will simply not do.
3. Make every criterion verifiable
If two people could look at the same deal and disagree about whether it has met the criterion, it is not written tightly enough. Verifiability is what makes stage-weighted forecasting worth anything.
4. Inspect deals against criteria, not against the rep
In pipeline review, ask which exit criterion is unmet and what will meet it. It is a shorter conversation than asking how confident someone feels, and it produces an action.
Frequently asked questions
What makes a good sales pipeline stage definition?
Exit criteria written as buyer actions rather than seller activities, and tight enough that two people inspecting the same deal would agree on whether it qualifies. 'Demo delivered' is an activity; 'buyer confirmed the problem is worth solving this quarter' is a signal.
Should forecast category be the same as pipeline stage?
No. Stage is where the deal is, forecast category is confidence it closes this period. Combining them forces reps to move deals backwards to lower a forecast, which they avoid, so the forecast stops reflecting reality.
How many pipeline stages should we have?
Few enough that every stage has a distinct, verifiable exit criterion. If you cannot state what the buyer must do to leave a stage, that stage is doing no work and should be merged with its neighbour.