How to Define Sales Pipeline Stages With Exit Criteria That Actually Hold

Almost every struggling forecast traces back to the same root cause, and it is rarely discipline. The pipeline stages describe what the seller did rather than what the buyer did, and a stage based on seller activity cannot tell you anything you did not already know.

Why most stage definitions fail

Open a typical early-stage CRM and the stages will look something like this:

Lead → Contacted → Demo → Proposal → Negotiation → Closed

Four of those six describe an action the rep took. "Contacted" means a rep sent something. "Demo" means a rep ran a call. "Proposal" means a rep produced a document. None of them describes anything the buyer committed to, which means a deal can sit in Proposal for five months while remaining, in reality, dead.

This is how you end up with a pipeline that looks healthy and a quarter that does not. The deals are all technically in late stages. It is just that "late stage" was earned by seller effort rather than buyer intent.

The one rule: verifiable from outside the deal

Here is the test that fixes most of this. An exit criterion is only valid if someone outside the deal could verify it.

Not "the rep believes there is budget." Instead: "the buyer named a budget figure and the person who controls it." Not "good discovery call." Instead: "we have written confirmation of the problem, the impact, and who else must approve."

Every criterion on the right is a fact. It either happened or it did not, and two people looking at the record would agree. That is the whole standard.

How many stages you need

Five to seven. Below five, the stages are too broad to tell you where a deal actually is. Above seven, reps stop applying them consistently and you get precision without accuracy.

Each stage needs two to four exit criteria. One criterion is a formality; nine is a form nobody fills in honestly.

A worked six-stage example

This is a reasonable default for B2B SaaS selling to a buying group of three to six people, with deal sizes between $10k and $100k ARR. Adjust the criteria, keep the shape.

Every criterion above describes something the buyer did. That is the mechanism: a pipeline built this way cannot be advanced by optimism.

What re-staging a real pipeline looks like

The exercise that makes this concrete: take your open pipeline and re-stage it against the new criteria, deal by deal, with the reps in the room. Here is a representative sample of what comes out.

Two things reliably surprise people in this session. The first is that deals move down more often than up, usually by a factor of three or four. The second is that at least one deal moves up, because a rep had been conservative and nobody had noticed the buyer was further along than the record said.

What happens to the number

In that sample, pipeline went from $444k to $324k, a 27% drop, and one deal left entirely. That range is typical: expect somewhere between 20% and 40% on a pipeline that has never been re-staged against written criteria.

The important part is what the drop is made of. It is not new bad news. Every one of those deals was already in that condition yesterday, and the only change is that the pipeline now says so. A founder who understands that distinction will handle the board conversation fine. A founder who hears "we lost a quarter of the pipeline" will not, which is why the framing needs deciding before the session rather than after.

Three rules that keep the session honest

• The rep speaks first on their own deal. If a manager stages it, the exercise teaches reps to wait for a verdict rather than to apply a standard.
• Every move needs a named criterion. "It feels earlier than that" is not a reason. Pointing at the unmet exit criterion is.
• Close things out. Any deal with no buyer-side activity beyond 1.5 times the median for its stage gets closed lost, with a reason code. It can always be reopened, and almost none of them are.

Five questions that test your current stages

Run these against your own pipeline before changing anything. If you answer no to two or more, the stages are the problem rather than the team.

1. Could a rep advance a deal without the buyer doing anything? If yes, that stage is a status update.
2. Would two reps place the same deal in the same stage? Test it — take five open deals and ask two people independently. Disagreement rate above 20% means the definitions are not shared.
3. Can you name the exit criteria without opening a document? If the team cannot recall them, they are not being applied.
4. Does every stage have a typical duration you would recognise as wrong? Without that, you cannot spot a stalled deal, only an old one.
5. Does your worst-case forecast ever come in above your commit? If commit and best case are always the same number, stages are not doing any work.

Rolling it out without a revolt

The redefinition is the easy part. Getting a team to apply it is where these projects die. Three things make the difference:

• Rewrite the stages with your reps. An hour in a room produces better criteria and removes the entire "this was imposed on us" conversation.
• Re-stage the existing pipeline once, together, and accept the drop. Pipeline will fall — often by 20–40% — because some of it was never real. Tell the board it is a correction before they see it.
• Enforce at the gate, not in review. If the system simply requires the criteria before the stage changes, adherence stops being a management problem. This is what Throughline's stage gates do.

That second point is the one founders underestimate. The first honest pipeline review after a redefinition is uncomfortable. It is also the first time in months the number has meant anything.

The shortest version

Use six stages with two to four exit criteria each, where every criterion is a fact a stranger could verify. Rewrite them with your reps, re-stage the pipeline once, then enforce at the gate.

If you want a second pair of eyes on your current stages, that is precisely what the free GTM teardown looks at first — and you keep the findings either way.

Frequently asked questions

Zachary Mondragon Founder, Arekko Solutions

Zachary works with founder-led B2B SaaS companies between seed and Series B, as a fractional VP of Sales and Marketing and through the team that builds their revenue operation on Throughline.

Get a free GTM teardown