Define pipeline stages by business state and exit criteria, not probability
A stage says what is true about the deal and what must happen to leave it. Probability and forecast category are derived from that—never typed in its place.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
Opportunity stages were configured from a vendor template and sellers pick them by feel. Each team reads them differently, probability is typed by hand, and the weekly review debates whether deals are really where they say. Forecasts built on these stages cannot be compared across teams or explained afterwards.
02Decision drivers
- D01
Stages must mean the same thing to every reader
- D02
Reviews need evidence, not opinions
- D03
Forecast categories must be consistent across motions and regions
- D04
Sellers should not maintain fields nobody uses
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| Probability-led stages: a percentage per deal, typed by the seller | Very small teams with one seller type | Measures optimism; cannot be coached or audited | Rejected |
| Vendor-default stages with default probabilities | A first pipeline is needed before the sales motions are understood | Stages describe the tool, not the business; no exit criteria | Rejected |
| Stages as business states with entry and exit criteria; probability and category derived | Any pipeline that is reviewed and forecast | Criteria must be designed per motion and kept current | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
Define each stage as a business state: what must be true to enter, what must be true to leave, the owner, the evidence and the expected next action. Capture exit evidence with as few fields as possible. Derive the forecast category from the stage mapping and calibrate probability from history by motion; managers adjust the forecast, not the stage. Changes to stage definitions go through the RevOps governance forum.
05Consequences
What this choice changes elsewhere in the system.
- Management cadence
Reviews discuss evidence and next steps instead of percentages.
- Forecast
Forecast categories mean the same thing in every region and motion.
- Measurement
Probability becomes a measured output that can be calibrated.
- Governance
Stage definitions become a governed asset with an owner.
06Revisit when
The decision holds while its context holds. Challenge it when:
Deals are fully transactional and close in one interaction.
A motion has too little history for stage-based calibration.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
08Related decisions
Decisions this one depends on, or constrains.