
Adam Foster
Fractional RevOps
ESSAY
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
6 min
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
“A stage should change when the buyer does something, not when we do.”
Ask a sales team what “Proposal Sent” means and you’ll get the same answer every time: we sent the proposal. Ask what it tells you about the chance of that deal closing and the room goes quiet.
That’s the problem with most sales pipelines I look at. The stages describe our activity. Meeting booked, demo done, proposal sent. All of them can be ticked off without the buyer agreeing to anything. So a deal can sit at 60% probability because a rep was busy, while the customer hasn’t opened the email.
Why activity-based pipeline stages break your forecast
Every stage in a pipeline carries a probability, whether you’ve set one or not. When a sales director looks at the pipeline and says “we’ve got £400k at proposal stage”, they’re making an assumption about how much of that will close. If the stage only means a document was emailed, that assumption has nothing underneath it.
Activity-based stages also reward the wrong behaviour. Reps learn that moving a deal forward is about doing the next task, not about getting the buyer to commit. The pipeline fills up with deals that look healthy and aren’t. The weekly meeting then turns into an interrogation, because the sales leader can’t trust what the stages say and has to ask about every deal one by one.
The result is a forecast that depends on the sales leader’s gut feel, and a CRM that nobody really believes.
Define pipeline stages by buyer commitments
A better test is to ask what the buyer has agreed to at each point. Not what they said on the call, but what they did. Did they introduce you to the person who signs off the budget? Did they share their current numbers? Did they agree a date to review the proposal together?
Each of those is a small commitment, and each one is evidence. When a deal moves stage because the buyer did something, the stage starts to mean something. When it moves because we did something, it’s just a log of effort.
This is sometimes called defining exit criteria: the specific things that must be true before a deal can leave one stage and enter the next. The important word is “true”. An exit criterion should be something you could prove to a sceptical sales manager, not a feeling that the call went well.
Example sales pipeline stages and exit criteria
Every business is different, but for a typical B2B sale I’d expect something like this:
Qualified: the buyer has confirmed a problem worth solving and roughly when they need it solved. Evidence: the problem and timescale are written on the deal record in the buyer’s words.
Discovery complete: we’ve spoken to the person who owns the budget, or the buyer has agreed to set that meeting up. Evidence: the decision maker is a named contact on the deal.
Solution agreed: the buyer has confirmed what they’d buy, in their own words, before any price is on the table. Evidence: a short summary sent to the buyer and acknowledged.
Proposal reviewed: we’ve walked through the proposal with them, live, and know what’s left to resolve. Evidence: a dated review meeting and a list of open points.
Contracting: the paperwork is with their side and there’s a date for signature. Evidence: contract sent, signatory named, target date agreed with the buyer.
The names matter less than the exit criteria. Write them down, put them where the team can see them, and make the CRM ask for the evidence before a deal can move.
How to build exit criteria into your CRM
Writing the criteria down is half the job. The other half is making the system support them, so the process holds up when the sales leader isn’t watching.
Make fields required at the right stage. If a deal can’t move into Discovery complete without a decision maker, make that contact association required when the stage changes. Don’t make it required when the deal is created, because the rep won’t know yet.
Rename stages to match the criteria. “Proposal reviewed” sets a different expectation from “Proposal sent”. Small wording changes shift behaviour.
Recalibrate stage probabilities. Once you’ve run the new stages for a quarter, look at what actually closed from each one and update the percentages. Don’t keep the defaults your CRM shipped with.
Add the criteria to the deal record. A short checklist or description on each stage means a rep never has to guess what’s needed.
Why sales leaders push back
The first reaction is usually that the pipeline will shrink. It will. Deals that were sitting at proposal stage because something got emailed will drop back to where they really are. That’s uncomfortable for a month, and then it’s the most useful thing that’s happened to your forecast in years.
The second reaction is that reps will hate the extra fields. Some will. But the questions you’re asking are the ones a good sales manager asks in a deal review anyway. You’re just asking them once, in the system, rather than every Monday.
One pipeline or several?
If you sell very different things, such as a one-off project and a recurring contract, the buyer commits to different things along the way. Forcing both through the same stages usually means the criteria are vague enough to fit either, which defeats the point. In that case, two pipelines with their own exit criteria are better than one compromise. Keep the number small, though. Every extra pipeline is another set of reports to maintain and another place for deals to hide.
How to tell whether it’s working
After a quarter, three numbers will tell you whether the new stages are doing their job. Stage-to-stage conversion rates should become more stable, because each stage now means the same thing for every rep. Time in stage becomes useful, because a deal that sits too long in one place is a real warning sign rather than admin lag. And forecast accuracy, the gap between what you called and what closed, should narrow.
Where to start
Don’t redesign everything at once. Pick the stage where deals pile up and stall, which is usually the one just after the proposal goes out. Write one sentence describing what the buyer must have done for a deal to be there. Then go through every open deal at that stage and ask whether it passes.
You’ll learn more about your pipeline from that hour than from any dashboard.

Adam Foster
Fractional RevOps
ESSAY
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
6 min
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
“A stage should change when the buyer does something, not when we do.”
Ask a sales team what “Proposal Sent” means and you’ll get the same answer every time: we sent the proposal. Ask what it tells you about the chance of that deal closing and the room goes quiet.
That’s the problem with most sales pipelines I look at. The stages describe our activity. Meeting booked, demo done, proposal sent. All of them can be ticked off without the buyer agreeing to anything. So a deal can sit at 60% probability because a rep was busy, while the customer hasn’t opened the email.
Why activity-based pipeline stages break your forecast
Every stage in a pipeline carries a probability, whether you’ve set one or not. When a sales director looks at the pipeline and says “we’ve got £400k at proposal stage”, they’re making an assumption about how much of that will close. If the stage only means a document was emailed, that assumption has nothing underneath it.
Activity-based stages also reward the wrong behaviour. Reps learn that moving a deal forward is about doing the next task, not about getting the buyer to commit. The pipeline fills up with deals that look healthy and aren’t. The weekly meeting then turns into an interrogation, because the sales leader can’t trust what the stages say and has to ask about every deal one by one.
The result is a forecast that depends on the sales leader’s gut feel, and a CRM that nobody really believes.
Define pipeline stages by buyer commitments
A better test is to ask what the buyer has agreed to at each point. Not what they said on the call, but what they did. Did they introduce you to the person who signs off the budget? Did they share their current numbers? Did they agree a date to review the proposal together?
Each of those is a small commitment, and each one is evidence. When a deal moves stage because the buyer did something, the stage starts to mean something. When it moves because we did something, it’s just a log of effort.
This is sometimes called defining exit criteria: the specific things that must be true before a deal can leave one stage and enter the next. The important word is “true”. An exit criterion should be something you could prove to a sceptical sales manager, not a feeling that the call went well.
Example sales pipeline stages and exit criteria
Every business is different, but for a typical B2B sale I’d expect something like this:
Qualified: the buyer has confirmed a problem worth solving and roughly when they need it solved. Evidence: the problem and timescale are written on the deal record in the buyer’s words.
Discovery complete: we’ve spoken to the person who owns the budget, or the buyer has agreed to set that meeting up. Evidence: the decision maker is a named contact on the deal.
Solution agreed: the buyer has confirmed what they’d buy, in their own words, before any price is on the table. Evidence: a short summary sent to the buyer and acknowledged.
Proposal reviewed: we’ve walked through the proposal with them, live, and know what’s left to resolve. Evidence: a dated review meeting and a list of open points.
Contracting: the paperwork is with their side and there’s a date for signature. Evidence: contract sent, signatory named, target date agreed with the buyer.
The names matter less than the exit criteria. Write them down, put them where the team can see them, and make the CRM ask for the evidence before a deal can move.
How to build exit criteria into your CRM
Writing the criteria down is half the job. The other half is making the system support them, so the process holds up when the sales leader isn’t watching.
Make fields required at the right stage. If a deal can’t move into Discovery complete without a decision maker, make that contact association required when the stage changes. Don’t make it required when the deal is created, because the rep won’t know yet.
Rename stages to match the criteria. “Proposal reviewed” sets a different expectation from “Proposal sent”. Small wording changes shift behaviour.
Recalibrate stage probabilities. Once you’ve run the new stages for a quarter, look at what actually closed from each one and update the percentages. Don’t keep the defaults your CRM shipped with.
Add the criteria to the deal record. A short checklist or description on each stage means a rep never has to guess what’s needed.
Why sales leaders push back
The first reaction is usually that the pipeline will shrink. It will. Deals that were sitting at proposal stage because something got emailed will drop back to where they really are. That’s uncomfortable for a month, and then it’s the most useful thing that’s happened to your forecast in years.
The second reaction is that reps will hate the extra fields. Some will. But the questions you’re asking are the ones a good sales manager asks in a deal review anyway. You’re just asking them once, in the system, rather than every Monday.
One pipeline or several?
If you sell very different things, such as a one-off project and a recurring contract, the buyer commits to different things along the way. Forcing both through the same stages usually means the criteria are vague enough to fit either, which defeats the point. In that case, two pipelines with their own exit criteria are better than one compromise. Keep the number small, though. Every extra pipeline is another set of reports to maintain and another place for deals to hide.
How to tell whether it’s working
After a quarter, three numbers will tell you whether the new stages are doing their job. Stage-to-stage conversion rates should become more stable, because each stage now means the same thing for every rep. Time in stage becomes useful, because a deal that sits too long in one place is a real warning sign rather than admin lag. And forecast accuracy, the gap between what you called and what closed, should narrow.
Where to start
Don’t redesign everything at once. Pick the stage where deals pile up and stall, which is usually the one just after the proposal goes out. Write one sentence describing what the buyer must have done for a deal to be there. Then go through every open deal at that stage and ask whether it passes.
You’ll learn more about your pipeline from that hour than from any dashboard.

Adam Foster
Fractional RevOps
ESSAY
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
Sales Pipeline Stages: Define Them by Buyer Commitments
6 min
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
Most forecasts go wrong at the stage definitions. If a deal moves forward because your rep sent something, the stage tells you nothing about whether it will close.
“A stage should change when the buyer does something, not when we do.”
Ask a sales team what “Proposal Sent” means and you’ll get the same answer every time: we sent the proposal. Ask what it tells you about the chance of that deal closing and the room goes quiet.
That’s the problem with most sales pipelines I look at. The stages describe our activity. Meeting booked, demo done, proposal sent. All of them can be ticked off without the buyer agreeing to anything. So a deal can sit at 60% probability because a rep was busy, while the customer hasn’t opened the email.
Why activity-based pipeline stages break your forecast
Every stage in a pipeline carries a probability, whether you’ve set one or not. When a sales director looks at the pipeline and says “we’ve got £400k at proposal stage”, they’re making an assumption about how much of that will close. If the stage only means a document was emailed, that assumption has nothing underneath it.
Activity-based stages also reward the wrong behaviour. Reps learn that moving a deal forward is about doing the next task, not about getting the buyer to commit. The pipeline fills up with deals that look healthy and aren’t. The weekly meeting then turns into an interrogation, because the sales leader can’t trust what the stages say and has to ask about every deal one by one.
The result is a forecast that depends on the sales leader’s gut feel, and a CRM that nobody really believes.
Define pipeline stages by buyer commitments
A better test is to ask what the buyer has agreed to at each point. Not what they said on the call, but what they did. Did they introduce you to the person who signs off the budget? Did they share their current numbers? Did they agree a date to review the proposal together?
Each of those is a small commitment, and each one is evidence. When a deal moves stage because the buyer did something, the stage starts to mean something. When it moves because we did something, it’s just a log of effort.
This is sometimes called defining exit criteria: the specific things that must be true before a deal can leave one stage and enter the next. The important word is “true”. An exit criterion should be something you could prove to a sceptical sales manager, not a feeling that the call went well.
Example sales pipeline stages and exit criteria
Every business is different, but for a typical B2B sale I’d expect something like this:
Qualified: the buyer has confirmed a problem worth solving and roughly when they need it solved. Evidence: the problem and timescale are written on the deal record in the buyer’s words.
Discovery complete: we’ve spoken to the person who owns the budget, or the buyer has agreed to set that meeting up. Evidence: the decision maker is a named contact on the deal.
Solution agreed: the buyer has confirmed what they’d buy, in their own words, before any price is on the table. Evidence: a short summary sent to the buyer and acknowledged.
Proposal reviewed: we’ve walked through the proposal with them, live, and know what’s left to resolve. Evidence: a dated review meeting and a list of open points.
Contracting: the paperwork is with their side and there’s a date for signature. Evidence: contract sent, signatory named, target date agreed with the buyer.
The names matter less than the exit criteria. Write them down, put them where the team can see them, and make the CRM ask for the evidence before a deal can move.
How to build exit criteria into your CRM
Writing the criteria down is half the job. The other half is making the system support them, so the process holds up when the sales leader isn’t watching.
Make fields required at the right stage. If a deal can’t move into Discovery complete without a decision maker, make that contact association required when the stage changes. Don’t make it required when the deal is created, because the rep won’t know yet.
Rename stages to match the criteria. “Proposal reviewed” sets a different expectation from “Proposal sent”. Small wording changes shift behaviour.
Recalibrate stage probabilities. Once you’ve run the new stages for a quarter, look at what actually closed from each one and update the percentages. Don’t keep the defaults your CRM shipped with.
Add the criteria to the deal record. A short checklist or description on each stage means a rep never has to guess what’s needed.
Why sales leaders push back
The first reaction is usually that the pipeline will shrink. It will. Deals that were sitting at proposal stage because something got emailed will drop back to where they really are. That’s uncomfortable for a month, and then it’s the most useful thing that’s happened to your forecast in years.
The second reaction is that reps will hate the extra fields. Some will. But the questions you’re asking are the ones a good sales manager asks in a deal review anyway. You’re just asking them once, in the system, rather than every Monday.
One pipeline or several?
If you sell very different things, such as a one-off project and a recurring contract, the buyer commits to different things along the way. Forcing both through the same stages usually means the criteria are vague enough to fit either, which defeats the point. In that case, two pipelines with their own exit criteria are better than one compromise. Keep the number small, though. Every extra pipeline is another set of reports to maintain and another place for deals to hide.
How to tell whether it’s working
After a quarter, three numbers will tell you whether the new stages are doing their job. Stage-to-stage conversion rates should become more stable, because each stage now means the same thing for every rep. Time in stage becomes useful, because a deal that sits too long in one place is a real warning sign rather than admin lag. And forecast accuracy, the gap between what you called and what closed, should narrow.
Where to start
Don’t redesign everything at once. Pick the stage where deals pile up and stall, which is usually the one just after the proposal goes out. Write one sentence describing what the buyer must have done for a deal to be there. Then go through every open deal at that stage and ask whether it passes.
You’ll learn more about your pipeline from that hour than from any dashboard.