
TL; DR
Picture a pipeline where 40% of deals sit in Proposal, and half of them haven’t heard from the buyer in three weeks (an illustrative example). The stages say the deals are moving, but the buyers have gone quiet.
Sales pipeline stages only work when each one has exit criteria based on buyer evidence, not seller activity. Below are the seven stages, the buyer evidence that should move a deal through each one, and a template you can copy into your CRM.
What Are Sales Pipeline Stages?
Sales pipeline stages are the steps a deal moves through from first contact to closed-won or closed-lost, such as qualification, discovery, proposal and negotiation. Each stage should have exit criteria based on buyer evidence, like the economic buyer joining a call, so the pipeline reflects real progress rather than rep optimism.
- Prospecting: the buyer engages for the first time.
- Qualification: the buyer states a problem you can solve.
- Discovery: the buyer describes the pain, its impact and how they decide.
- Solution and validation: the buyer confirms technical fit.
- Proposal: the economic buyer engages and budget is discussed.
- Negotiation and procurement: procurement or legal is engaged.
- Closed-won / closed-lost: a signed agreement, or a recorded loss reason.
Pipeline stages vs sales cycle stages
Pipeline stages describe a deal’s current status in the CRM. Sales cycle stages describe the full process a buyer goes through and how long it takes. Your pipeline is a snapshot; your cycle is the timeline.
The 7 Sales Pipeline Stages (With Buyer Evidence)
A stage is a claim about the buyer, so make it prove itself. Each stage below names the buyer evidence required to exit, not a task the seller completed.
1. Prospecting
Goal: get a real response. Exit evidence: the buyer replies or accepts a meeting. Sending ten emails is activity. A reply is evidence. Until the buyer acts, the deal belongs in a prospect list, not the pipeline.
2. Qualification
Goal: confirm there’s a problem worth solving. Exit evidence: the buyer states the problem in their own words and confirms basic fit. Frameworks help here; see qualification with BANT. Keep it short. You’re confirming fit, not running discovery.
3. Discovery
Goal: understand the pain and how the buyer decides. Exit evidence: the buyer describes the impact of the problem and their decision process, and a second stakeholder is named. As Gartner’s Delainey Kirkwood put it, “Buying groups are more diverse than ever.” One contact is a conversation. Two are the start of a deal, which is why multi-threading matters early.
4. Solution and validation
Goal: prove the fit. Exit evidence: technical validation is passed and the buyer agrees on evaluation criteria. A demo you held is a seller task. A buyer-side technical lead confirming it works is evidence.
5. Proposal
Goal: get the decision-maker involved. Exit evidence: the economic buyer is engaged, the buyer raises budget themselves, and the decision process is known. If the economic buyer has never joined a call or replied to an email, the deal isn’t at Proposal, whatever the CRM says.
6. Negotiation and procurement
Goal: get from decision to signature. Exit evidence: procurement or legal is engaged, redlines are received, and the paper process is mapped. MEDDICC describes the paper process as the steps from decision to signature and calls it “the number 1 reason deals slip.” That’s their view rather than a statistic, but it matches what most teams see. Forrester’s 2026 buyer research found that procurement is a decision-maker in 53% of business buying cycles.
7. Closed-won / closed-lost
Goal: record the truth. Exit evidence: a signed agreement, or a loss reason in the buyer’s words. “Went dark” is not a loss reason. It’s a sign the deal left the funnel earlier than the CRM shows.
Exit Criteria Table: Evidence, Source, Owner
To define deal stages in your CRM, write one row per stage: the buyer evidence required, where that evidence shows up, and who confirms it. The same table works in any CRM, whether yours calls them opportunity stages or deal stages.
A copyable exit-criteria template
| Stage | Buyer evidence required | Where it shows up | Who confirms |
| Prospecting | Reply or accepted meeting | Email, calendar | SDR or AE |
| Qualification | Problem stated by buyer; fit confirmed | Call, email | AE |
| Discovery | Impact and decision process described; second stakeholder named | Call, email, calendar | AE, manager review |
| Solution and validation | Technical validation passed; criteria agreed | Call, email, ticket | AE, sales engineer |
| Proposal | Economic buyer engaged; budget raised by buyer | Call, email, calendar | AE, manager |
| Negotiation and procurement | Procurement or legal engaged; redlines received | Email, CRM | AE, deal desk |
| Closed-won / closed-lost | Signed agreement or recorded loss reason | CRM, email | AE, RevOps |
Notice the third column. Most of the evidence lives in calls, emails and calendars, not in CRM fields.
Why Deals Sit in the Wrong Stage
Deals sit in the wrong stage for three reasons: target pressure, stages that never move backward, and evidence that lives outside the CRM.
Optimism under pressure. HBR notes that under target pressure, teams “become more susceptible to wishful thinking.” Deals get advanced on hope.
Stages that never regress. Deals move forward easily and almost never move back. A deal that stalls in Proposal stays in Proposal, weighted as if it were alive. Stalls are common: research by Matthew Dixon and Ted McKenna, published in HBR in 2022, found that 40% to 60% of deals end up lost to customers who intend to buy but fail to act.
Missing evidence. The buyer’s budget comment was on a call. The procurement email went to one inbox. None of it reached a CRM field, so the stage can’t reflect it.
Stage aging: an example
Illustrative: a deal has been in Proposal for 23 days. The last buyer reply was 19 days ago, and the economic buyer has never joined a call.
The evidence-based reading is that this deal never met the Proposal exit criteria. It belongs in Discovery, with a clear next step: get the economic buyer engaged.
How to Keep Stages Honest
Keeping stages honest takes four habits: define evidence, capture it, compare it, and route mismatches to the deal owner.
- Write exit criteria as buyer evidence. Use the table above.
- Capture evidence where it happens. That means calls, emails and tickets, not just CRM fields. Keeping the CRM current matters, but the evidence has to be found first.
- Compare evidence to the stage every week. Ask whether the buyer actually did what the stage claims.
- Send each mismatch to the deal owner, with the source. The owner updates the stage.
This matters for the forecast. In Gartner’s 2020 survey, only 45% of sales leaders and sellers had high confidence in their forecasting accuracy. Probability weights are only as good as the stage definitions underneath them.
Revenue AI Signals helps with steps 2 to 4. It can detect buyer evidence from calls and emails and tickets, flag when what the buyer said and what the stage says disagree, and email the mismatch to the deal owner with the source attached. For example (illustrative), a deal is marked Negotiation, but the buyer’s latest email says the budget review moved to next quarter. The owner sees the line and updates the stage.
Metrics to Track by Stage
Track metrics that show whether stages reflect reality, not just volume.
| Metric | Formula | What it tells you |
| Stage conversion rate | Deals exiting a stage forward ÷ deals entering it | Where deals stall or drop |
| Stage aging | Days in current stage vs the median for that stage | Which deals are stuck |
| Pipeline velocity | (opportunities × win rate × average deal size) ÷ sales cycle length | Revenue throughput per day |
| Weighted pipeline | Sum of (deal value × stage probability) | Expected value, if stages are honest |
| Forecast accuracy | Actual closed revenue ÷ forecast revenue | Whether stage weights hold up |
What’s a good stage-to-stage conversion rate? It varies by motion, deal size and segment. Benchmark against your own history and watch the trend, rather than chasing someone else’s number.
FAQs
Q1: How many stages should a sales pipeline have?
Most B2B teams use somewhere between five and eight stages, as a matter of common practice. A few well-defined stages beat many vague ones. If nobody can name the buyer evidence for a stage, delete it.
Q2: What is the difference between pipeline stages and sales cycle stages?
Pipeline stages show a deal’s current status in the CRM. Sales cycle stages describe the full buying process and how long it takes from start to finish.
Q3: What are exit criteria?
Exit criteria are verifiable buyer evidence required before a deal advances. Examples include the economic buyer joining a call or procurement sending redlines.
Q4: What evidence moves a deal to proposal?
A confirmed need, an engaged economic buyer and a known decision process. Without the economic buyer, a proposal is usually premature.
Q5: Why do deals get stuck in one stage?
Usually because the buyer hasn’t taken the action the next stage requires. Flag stage aging against your median so stuck deals surface early.
Q6: How do stages affect forecast accuracy?
Probability weights are only as good as the stage definitions behind them. Gartner’s 2020 survey found only 45% of sales leaders and sellers had high confidence in their forecast accuracy.
Q7: Should stages match the buyer journey?
Yes. Define each stage by a buyer commitment, not a seller task, so stage progress means buyer progress.