Most pipeline stages describe what the seller has done, not what the buyer has decided. “Proposal Sent” tells you the rep hit send on an email. It tells you nothing about whether the prospect has read it, evaluated it, or has any intention of responding. That gap between seller action and buyer decision is where pipeline accuracy collapses.

If your pipeline stages are built around seller tasks instead of buyer milestones, your forecast is not a prediction — it’s a record of your team’s recent activity. Redesigning your stages around the buyer’s journey is one of the highest-leverage changes you can make to pipeline data quality.

Why Most Pipeline Stages Are Seller-Centric, Not Buyer-Centric

Look at a typical CRM pipeline: “Initial Outreach,” “First Meeting Scheduled,” “Demo Delivered,” “Proposal Sent,” “Contract Sent.” Every single stage name describes something the rep did. None of them describe a decision the buyer made.

This matters because stage advancement becomes entirely within the rep’s control. A rep can move a deal from “First Meeting Scheduled” to “Demo Delivered” by running a demo, regardless of whether the prospect is genuinely qualified or interested. The stage change is triggered by seller action, not buyer commitment.

When your pipeline stages reflect seller actions, your forecast probability becomes meaningless. If 100% of deals that reach “Proposal Sent” stay there until they’re won or lost, then the stage tells you nothing useful about close probability. Deals should move through stages because the buyer has made a decision, not because the seller has done something.

Buyer-centric stages look like this: “Problem Confirmed,” “Mutual Fit Established,” “Decision Process Agreed,” “Verbal Agreement Received.” Each stage name describes a state the buyer is in — what they’ve acknowledged, committed to, or decided. A deal can only advance when you have evidence that the buyer has reached that state.

How Many Stages Does Your Pipeline Need?

Too few stages and you lose signal. If your pipeline is just “Early,” “Mid,” and “Late,” you can’t tell whether a deal in “Mid” has had one exploratory call or a full technical evaluation. Coaching is impossible and forecasting is a guess.

Too many stages and reps stop updating. If advancing a deal requires clicking through seven sequential stages with separate fields for each, most reps will either skip stages or batch-update deals at the end of the month. Neither behavior gives you accurate pipeline data.

The practical sweet spot is five to seven stages for most B2B sales cycles. Each stage should represent a meaningful buyer commitment that changes what you do next. If two stages prompt the same set of next actions, they might be the same stage.

When your process requires more granularity within a stage — for instance, a multi-step technical evaluation that could take several weeks — use sub-stages or custom fields rather than adding full pipeline stages. This keeps the main pipeline view manageable while preserving the detail you need.

Designing Each Stage with Clear Entry and Exit Criteria

Each stage should have documented entry criteria (what must be true before a deal can enter this stage) and exit criteria (what the buyer must have done before the deal advances). Vague stage definitions invite reps to advance deals based on optimism rather than evidence.

Stage 1: Qualified Opportunity

Entry criteria: The rep has confirmed minimum viability — there is a real need, access to a relevant decision-maker, some indication of budget availability or ability to fund, and a timeframe that makes this a genuine near-term opportunity. This is your BANT or MEDDIC minimum.

Exit criteria: Discovery call completed. The rep has documented the prospect’s specific pain points, current situation, and what a successful outcome looks like for the buyer. These notes exist in the CRM record.

Stage 2: Discovery and Needs Analysis Completed

Entry criteria: Initial qualification confirmed; discovery call has occurred and outcomes are logged.

Exit criteria: The rep and prospect have verbally agreed that the next step is a formal proposal or solution presentation. The prospect has described what they need to see in order to evaluate your solution.

Stage 3: Solution Presented

Entry criteria: Discovery complete; solution or proposal design is ready to present.

Exit criteria: The prospect has reviewed the solution presentation and provided specific feedback. This could be questions, objections, or a request to proceed — but there has been a substantive response, not silence.

Stage 4: Proposal Under Review

Entry criteria: Formal written proposal delivered and confirmed received.

Exit criteria: The prospect has verbally agreed to the proposed scope and investment, or negotiation has begun. The deal advances when the buyer says yes in some form, not when the rep follows up for the third time.

Stage 5: Verbal Commitment

Entry criteria: The prospect has expressed verbal intent to move forward.

Exit criteria: Signed contract or purchase order received. For deals that require procurement involvement, this stage may last several weeks, but the buyer commitment is documented and active.

Stage 6: Closed Won and Closed Lost

For Closed Won, document the final contract value, the primary driver of the decision, and the key stakeholders involved. For Closed Lost, require a mandatory loss reason field. Every closed-lost deal should have a reason documented before the record is updated.

Stage Name	Buyer Decision Made	Seller Action Required	Exit Criteria	Typical Duration	CRM Field
Qualified Opportunity	Agreed to explore the solution	Run discovery call; document findings	Discovery notes logged in CRM	1–5 days	Qualification Score field
Discovery Completed	Confirmed the problem is real and worth solving	Present findings; confirm alignment	Prospect confirms proposal is next step	3–14 days	Discovery Status dropdown
Solution Presented	Engaged with solution and responded	Walk through proposal live	Prospect provides substantive feedback	2–7 days	Demo/Presentation Date field
Proposal Under Review	Actively evaluating your proposal	Manage follow-up; answer questions	Verbal agreement or negotiation begins	5–21 days	Proposal Sent Date field
Verbal Commitment	Said yes verbally	Handle procurement; prepare contract	Signed contract received	3–14 days	Verbal Close Date field
Closed Won / Closed Lost	Final decision made	Document outcome, reasons, and learnings	Record updated with close reason	Same day	Close Reason dropdown (required)

The Closed-Lost Stage: Getting Value from Lost Deals

The loss reason field is arguably the most valuable field in your entire CRM — and also the most consistently underfilled. When a rep closes a deal as lost without logging the reason, you lose the data that tells you where your sales process has a systemic gap.

Common loss reasons include: lost to competitor, lost on price, no decision made, timing not right, champion left, project cancelled, or disqualified during late evaluation. Each reason points to a different intervention. If you’re losing 40% of deals “on price,” that’s either a positioning problem or a qualification problem. If you’re losing 30% to “no decision,” your urgency creation and value demonstration need work.

Require loss reason as a mandatory field before the stage can be marked Closed Lost. Brief your reps on why this data matters — not to evaluate them, but to improve the process they work within. When reps see that their loss reason data led to a pricing structure change that helped them win more deals, they’re more likely to fill it in accurately.

When to Update Your Pipeline Stage Design

Your pipeline stages should be reviewed when your close rate at a specific stage drops significantly without an obvious cause, when reps consistently skip a stage or treat two stages as identical, or when a major change in your sales process (like adding a technical evaluation step or a new stakeholder tier) creates a gap in your current stage structure.

Migrating deals to a new stage structure requires care. Map each existing stage to its new equivalent and update deals in bulk. Add a note to each deal record explaining the migration. Keep the old stage names visible in a read-only field for 60 to 90 days so historical reports don’t lose their meaning.

FAQ

Should we have one pipeline for all deals or multiple pipelines? If your sales motions are genuinely different — say, a direct enterprise pipeline and a channel partner pipeline — separate pipelines make sense. If you use different pipelines simply because deal sizes vary, consolidate them. You can filter by deal size within a single pipeline without the overhead of maintaining parallel stage definitions and reporting.

How do we get reps to actually update pipeline stages? Require stage advancement to be accompanied by a note or a completed field. If moving a deal to “Proposal Under Review” requires the rep to log the proposal delivery date and the agreed review date, the field completion becomes part of the action. Make it easier to update correctly than to skip.

What if our sales cycle varies a lot by deal size? Use deal size as a segmentation filter in reporting, not a separate pipeline. Your stages can stay the same while your expected duration per stage varies by deal tier. Document the expected stage durations for small, mid, and enterprise deals separately, and use those as benchmarks in your pipeline reviews.

How do we align pipeline stages with our CRM’s probability settings? Assign probability percentages to stages based on historical close rates, not intuition. If 70% of deals that reach “Verbal Commitment” in your CRM close successfully, set that stage to 70%. Run this analysis on your closed deals from the previous 12 months and let the data set your stage probabilities. Update them quarterly.