Most pipeline stages are fiction. They have names — Prospect, Qualified, Proposal, Closed — but those names mean different things to different people on the team. That ambiguity is the root cause of the forecast problem, the pipeline review problem, and the coaching problem. You can't fix any of them until the stages are real.
Real stage definitions have four components. They can be written down. They can be tested against a specific deal. They don't require a manager's interpretation. And when someone moves a deal into a stage, everyone on the team knows what that means.
What Pipeline Stage Definitions Actually Need to Do
A stage definition needs to answer two questions for every deal in that stage: what had to happen for this deal to get here, and what has to happen before it moves forward? Those are entry criteria and exit criteria. Without both, a stage is just a label.
Stage definitions also need to be actionable for the rep. If a rep can't look at a stage definition and immediately know whether their deal belongs there, the definition has failed. The purpose isn't bureaucracy — it's giving reps a shared language that makes pipeline reviews faster and forecasting cleaner.
The Components of a Usable Stage Definition
Entry Criteria
Entry criteria define what must be true before a deal can enter this stage. They should be verifiable — not "rep feels like this is a good opportunity" but "discovery call completed, budget confirmed, decision-maker identified and on record in the CRM." If you can't verify it, it's not a criterion.
Exit Criteria
Exit criteria define what must happen before the deal can advance to the next stage. "Proposal accepted" is an exit criterion. "Customer asked for a proposal" is not — that's an activity, not an outcome. The distinction matters because activities can happen without momentum. Exit criteria should require the customer to do something.
Required Fields at Each Stage Gate
Translate your exit criteria into required fields in the CRM. If a deal can't advance from Proposal to Negotiation without a signed NDA and a confirmed budget number, those are required fields at that gate. HubSpot, Salesforce, and most modern CRMs support required fields at stage transitions. Use them — they're the enforcement mechanism that keeps your definitions honest.
Typical Duration
Every stage should have a typical duration based on your historical data. If deals typically spend 7–14 days in Proposal, a deal that's been in Proposal for 45 days is flagged as a risk — not because the rep is lying, but because the data says this deal is behaving abnormally. This is how you catch stuck deals before they die quietly in your pipeline.
How Many Pipeline Stages Is Too Many?
The answer is usually fewer than you have. Most B2B businesses need five to seven stages. When I audit CRMs with 10, 12, or 15 stages, it's almost always because stages were added reactively — someone wanted to track a specific situation and added a stage instead of using a field.
The test: can every active deal be unambiguously placed in exactly one stage? If you have stages that overlap — if a deal could reasonably be in "Demo Scheduled" or "Qualified" at the same time — you have too many stages.
Example Stage Definitions (B2B SaaS)
1. Prospect — Entry: company identified as ICP match, contact in CRM. Exit: discovery call scheduled.
2. Discovery — Entry: discovery call completed, pain confirmed. Exit: qualified on budget, authority, need, and timeline (BANT or equivalent). Required fields: decision-maker name, estimated budget range, use case documented.
3. Evaluation — Entry: qualified, demo or trial started. Exit: customer has seen solution applied to their specific use case. Required fields: demo date, champion identified.
4. Proposal — Entry: formal proposal submitted. Exit: proposal reviewed by economic buyer, questions answered. Required fields: close date, contract value, economic buyer name.
5. Negotiation — Entry: customer actively negotiating terms. Exit: verbal agreement on deal structure. Required fields: final contract value, expected close date confirmed within 14 days.
6. Closed Won / Closed Lost — Required fields for Lost: loss reason (required, no "other"), competitor if applicable.
Example Stage Definitions (Professional Services)
Professional services pipelines work differently — relationship-driven, longer cycles, often no formal RFP. A five-stage model that works: Relationship Active → Opportunity Identified → Scoping → Proposal Submitted → Engagement Confirmed. Each stage needs criteria that reflect how decisions actually get made, not how a SaaS pipeline assumes they work.
The Five Stage Definitions Every Mid-Market Team Gets Wrong
- Discovery defined by the rep's action, not the customer's. "Sent intro email" is not Discovery. Discovery requires a conversation where pain was confirmed.
- Proposal defined by sending, not receiving. A proposal that's been sitting in a prospect's inbox for three weeks with no response is not a live deal.
- No stage for deals stuck in legal. "Contract Review" is not Closed Won. Deals that sit in legal limbo need their own stage so they don't inflate your late-stage pipeline.
- Close date not required at Negotiation. If you don't require a close date before a deal enters late stages, you'll have deals in Negotiation with no close date that are impossible to forecast.
- No stage for "churned before close." Deals that ghost after proposal need to go somewhere. Create a "Stalled" or "Ghosted" stage so reps have somewhere to put them without closing them immediately lost.
How to Roll Out New Stage Definitions Without Blowing Up Your Pipeline
Don't migrate every existing deal at once. First, define and agree on the new stages. Second, apply new definitions to deals created going forward. Third, audit existing deals over a two-week period and re-stage them using the new definitions. Fourth, train the team on entry/exit criteria before the first pipeline review under the new system.
The CRM cleanup guide covers the broader process for handling existing data. And if you're working across both mid-market and growth-stage SaaS motion, the stage definitions will need to reflect the differences in how those deals actually move.
Are your pipeline stages doing what they're supposed to?
Take the free RevOps Scorecard — one of the nine questions is specifically about pipeline stage governance.
Take the Free Scorecard →