Most CRM pipelines have stage names but no stage definitions. One rep moves a deal to Proposal after sending a price over email; another waits until the buyer has agreed the scope. The result is a pipeline report that adds together deals at very different levels of progress, a forecast nobody trusts and stage conversion rates that mean little. Exit criteria fix this. They state, for each stage, the conditions that must be true before a deal can move forward. This article explains how to write them, gives a template for a typical B2B sales pipeline, shows how to enforce them in the CRM and covers how to keep them in use once the novelty wears off.
Why stage definitions matter
Every pipeline metric depends on stages meaning the same thing for every deal. Win rate by stage, pipeline coverage, weighted forecasts, sales cycle length and pipeline velocity all assume that a deal in Evaluation in one rep's book is comparable to a deal in Evaluation in another's. Without shared definitions, those numbers describe how optimistic each rep is rather than how close deals are to closing. Clear exit criteria also improve coaching, because a manager can see exactly what is missing from a stuck deal, and they improve handoffs between SDRs, account executives and solutions engineers, because each knows what has been confirmed before they take over. The work is mostly agreement, not software: sales leadership, RevOps and, where relevant, marketing need to sit down and agree what each stage means.
Write criteria as buyer actions, not seller activities
The most common mistake is defining stages by what the seller did: sent a proposal, held a demo, followed up twice. Seller activity says little about whether the buyer is moving. Better criteria describe what the buyer has done or confirmed: agreed that a specific problem is worth solving, named the people involved in the decision, shared a budget range, agreed evaluation criteria, accepted a proposal in principle, or started their procurement process. Each criterion should be verifiable from evidence in the CRM, such as a note, a field value, a meeting with a named stakeholder or a document. If a manager cannot check a criterion by looking at the record, it is a feeling, not a criterion.
A template for a typical B2B pipeline
Adapt the stage names and criteria to your sales motion. The principle is that each exit criterion is something the buyer has done and the rep can show.
| Stage | Enters when | Exit criteria (all must be true) | Required CRM fields |
|---|---|---|---|
| Discovery | Qualified meeting booked and held | Problem confirmed by the buyer; fit with ICP checked; next meeting agreed | Problem statement, ICP fit, next step date |
| Qualification | Problem confirmed | Decision process and people identified; budget range or funding route discussed; timeline stated | Decision makers, budget range, target close date |
| Solution / evaluation | Decision process known | Evaluation criteria agreed; solution demonstrated against them; technical or security questions logged | Evaluation criteria, stakeholders met, competitors |
| Proposal | Buyer confirms solution fits | Proposal or quote sent and reviewed with the buyer; scope agreed in principle | Amount, products, proposal date |
| Negotiation / commit | Proposal accepted in principle | Mutual close plan agreed; procurement, legal or approval steps known with dates | Close plan, paperwork status, confirmed close date |
| Closed won / lost | Contract signed or deal ended | Signed contract or recorded loss reason | Close reason, loss reason, competitor won |
Shorter sales cycles may merge Qualification and Evaluation. Enterprise cycles may add a separate Security or Procurement stage.
How many stages you need
Use as few stages as the sales process allows while still separating steps where deals behave differently. Five to seven open stages is common for B2B sales. Too few stages hide where deals stall. Too many create stages reps skip, because the difference between them is not meaningful to the buyer. A useful test is to look at historical deals: if almost every deal passes through two adjacent stages within days of each other, merge them. If deals often sit for weeks in one stage for very different reasons, it may hide two separate steps. Keep closed won and closed lost as separate stages, and record a loss reason every time, because loss reasons are some of the most useful data in the CRM.
Enforcing criteria in HubSpot and Zoho
Definitions written in a document fade unless the CRM supports them. In HubSpot, you can make specific properties required when a deal moves into a stage, so a rep cannot move a deal to Negotiation without, for example, a close plan and a confirmed close date. Zoho CRM supports mandatory fields and layout rules, and its Blueprint feature can model stage transitions with required fields and actions at each step. Salesforce uses validation rules and path guidance for the same purpose. Whichever system you use, enforce a small number of fields per stage, the ones that truly prove progress, rather than making every field required. Heavy enforcement leads reps to type placeholder values to get past the screen, which is worse than an empty field because it looks like data.
Stage probabilities and forecasting
Many CRMs attach a default win probability to each stage, used for weighted pipeline. Do not leave these at the defaults. Once exit criteria have been in use for a few quarters, calculate the actual historical win rate for deals that reached each stage and use those figures. Revisit them each quarter or half-year. Even then, stage-weighted pipeline is only one input to a forecast. The article on B2B sales forecasting methods compares it with rep commits, historical run-rates and statistical approaches.
Rolling out new definitions
Introduce the definitions in a working session with the sales team rather than by email. Walk through each stage with real deals from the current pipeline, and ask reps to move deals back where they do not meet the new criteria. Expect pipeline value to fall in later stages when you do this. That is the point: the report becomes more honest. Agree a date from which the definitions apply, set up the required fields in the CRM, and add a short version of the criteria to the deal record or a pinned note so reps can see them while working. Managers should use the criteria in pipeline reviews from the first week, asking what evidence supports a stage rather than how a deal feels.
Keeping the definitions honest
Review the criteria each quarter with sales leadership. Look at stage-to-stage conversion rates and time in stage: a stage where most deals stall may need clearer criteria or may reveal a real bottleneck in the sales process. Spot-check a sample of deals each month for evidence of the criteria. Look for patterns of deals that skip stages or jump backwards often. And involve marketing, because the first stage definition, what counts as a qualified opportunity, connects directly to marketing's targets and to the MQL-to-SQL handoff. When definitions change, record the date, because historical comparisons across a definition change need care.
Common objections from sales teams
Reps sometimes push back on exit criteria, and the objections are worth answering directly. That this is admin for its own sake: show how the criteria improve the forecast the rep is judged on and reduce time spent defending deals in reviews. That every deal is different: agree, and keep the criteria to the few conditions true of every won deal, leaving room for judgement elsewhere. That moving deals backwards makes the pipeline look worse: explain that leadership would rather see an honest smaller pipeline than be surprised at quarter end. That the fields take too long to fill: reduce the number of required fields to those that prove progress, and pre-fill what the CRM already knows. Involving a few respected reps in drafting the criteria usually does more for adoption than any rule.
FAQ
Verifiable conditions a deal must meet before moving to the next stage, such as a confirmed problem, identified decision makers or an agreed close plan. They make stages mean the same thing for every deal.
Buyer actions. What the buyer has confirmed or done shows real progress. Seller activities such as sending a proposal do not.
Commonly five to seven open stages plus closed won and closed lost. Merge stages deals pass through together and split stages where deals stall for different reasons.
Yes. HubSpot can require properties when a deal enters a stage, Zoho CRM supports mandatory fields and Blueprint transitions, and Salesforce uses validation rules. Enforce only the fields that prove progress.
Later-stage pipeline usually falls as deals are moved back to where the evidence supports. The pipeline becomes smaller but more accurate.