A stage is a claim about what the buyer has done. Each one needs a condition anybody can check.
Use your own stage names. The conditions are what matter, and each one is a buyer action with something on the record that proves it.
| Stage | Exit criterion | Proof on the record |
|---|---|---|
| Discovery | The buyer confirmed a problem worth solving this year and agreed to a second meeting | The next meeting is on the calendar and the problem is recorded |
| Qualified | A budget range is confirmed and the person who approves it is named | Budget field and an approver contact role |
| Solution | The buyer saw the product against their own use case and named who else has to agree | Demo date and the buying group added as contacts |
| Proposal | A written proposal was delivered and the buyer agreed a decision date | Proposal attached and a decision date set with the buyer |
| Commit | Procurement, legal or security review has started | A procurement or legal contact on the deal and paperwork in flight |
| Closed won | The contract is signed | Signed contract attached |
| Weak | Rewritten |
|---|---|
| Had a good call | The buyer agreed a second meeting with a date |
| Budget discussed | A budget range is confirmed and the approver is named |
| Champion identified | A named contact introduced us to someone else at the account |
| Proposal sent | The buyer agreed a decision date after receiving the proposal |
| Verbal yes | Procurement or legal has been introduced |
In Salesforce, a validation rule can block a stage change until the proving field is filled, and Path can show the criteria on the record so reps see what the next stage needs before they try to move it.
In HubSpot, the pipeline settings let you require properties when a deal enters a stage. Keep the required list short, because every field that must be filled to move a deal is a field someone will fill with a period to get past the screen.
Restage every open deal against the new criteria in one review session rather than letting it happen gradually. Expect the distribution to move backwards and the weighted pipeline to drop. That drop is the forecast becoming accurate, and it is far better to see it in a planning meeting than at the end of the quarter.
Then watch two numbers. Conversion between stages should settle within a couple of quarters, and the five record test should pass: send the same five open deals to two people separately and get the same stages back.
The conditions that must be true before a deal moves to the next stage, written as buyer actions that are true or false, each with a field or artifact that proves it.
Five or six for most mid market B2B motions. The number matters far less than whether each stage has a condition two people would agree on without discussing it.
For the one or two criteria that matter most, yes. Enforce the proof field, keep the required list short, and rely on pipeline review for the rest.
They describe the same boundary from two sides. Writing exit criteria for each stage is enough, because the exit from one stage is the entry to the next.
Weighted pipeline usually drops at first as deals move backwards to where they really are. Accuracy then improves over the following quarters as conversion history builds on stages that mean one thing.
Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use browser storage to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.