Sales Stage Exit Criteria: The Small Fix That Makes Forecasts Honest
The short answer
Exit criteria are the observable conditions a deal must meet before it moves to the next pipeline stage, written down so "demo completed" means the same thing for every rep. Without them, stages measure optimism and the forecast is fiction. With them, deals advance on evidence, weak deals surface early, and the weekly forecast review takes minutes instead of arguments.
Why stages without exit criteria fail
Most pipelines have stage names and nothing behind them. "Qualified" means the rep likes the deal. "Demo done" means a calendar event happened. The result is predictable: every rep runs a private pipeline inside the shared one, and the manager cannot compare deals because the same stage label covers different realities.
This is the root cause behind the forecasts we dissected in Sales Forecasting Methods: stage-weighted math is only as honest as the stages. Sales methodology researchers at Winning by Design make the same point from the process side: stages should describe the buyer's journey, and moving between them requires a verifiable buyer action (Winning by Design, accessed November 4, 2026). The key word is verifiable.
What good exit criteria look like
Good criteria share three properties. They are buyer-side, describing something the buyer did or said, not something the rep did. They are observable, so a manager can verify them from call notes or a transcript without asking the rep to interpret. And they are short, one or two lines per stage, because a rubric nobody remembers gets used by nobody.
"Rep sent the proposal" fails all three tests. "Buyer confirmed budget range and introduced the decision maker on a call" passes all three.
Example criteria for a standard pipeline
Discovery complete: the buyer stated their problem in their own words and agreed to a demo with a date. Demo complete: the stakeholders who will use the product attended, and the buyer agreed on what a successful evaluation looks like. Evaluation: the buyer is testing against the agreed success criteria with a named owner on their side. Proposal: the buyer has the proposal and a meeting on the calendar to discuss it. Commit: the buyer has confirmed the decision process, the signer, and the expected signature date.
Notice none of these mention what the seller did. The mutual action plan is the natural companion here: exit criteria define where a deal is, and the action plan records what happens next.
How to enforce them without killing velocity
Enforcement fails when it becomes paperwork. The working version is simpler: the weekly pipeline review asks "what did the buyer do" before any stage change is accepted, and the CRM stage cannot be edited without a next step logged. Reps resist this for about two weeks, then start using it, because deals stop rotting quietly in stage three.
Call evidence makes enforcement nearly free. When calls are captured and summarized, checking an exit criterion means reading what the buyer actually said rather than taking the rep's word. From CRM data to conversation data covers why this shift matters, and Boxy, Hintro's real-time AI sales copilot, produces the summaries and speaker-labeled transcripts these checks run on, across English, Hindi and Hinglish calls.
Frequently asked questions
How many stages should a small team have?
Four to six. Fewer hides where deals die; more creates labels nobody can tell apart. If two stages would have identical exit criteria, merge them.
Should criteria ever bend for a big deal?
Never quietly. If a strategic deal skips a criterion, say so in the review and treat it as a known risk, not as a new normal.
How do we roll this out without a big process launch?
Pick next week's pipeline review, apply the buyer-action question to every stage change, and write down whatever criteria the team already agrees on. The document refines itself within a month.
Related reading: how to run a sales call review that actually changes behavior.
Hintro