Pipeline stages are checkpoints a deal passes on its way to closed — and the entire value of the concept rests on one discipline: each stage must have an exit criterion, a fact that's true or false. "Proposal sent" is a stage. "Feeling good about it" is a mood. Most broken pipelines are broken here, not in the software.
Here's the standard six-stage model, the exit criteria that make it honest, and when to deviate.
Sales pipeline vs. sales funnel vs. sales process
Three terms get used interchangeably and shouldn't be. Your sales process is the sequence of things a rep does to take a buyer from stranger to customer: prospecting, discovery, proposal, negotiation, close. Your sales pipeline is the deal-by-deal view of where each of your open sales opportunities sits in that process right now. The sales funnel is the aggregate view: how many leads entered at the top and what share came out the bottom.
So a sales pipeline tracks individual deals and a sales funnel measures conversion in bulk. Stages are the bridge: breaking the sales process into a sequence of stages gives each deal an address, and counting deals at each address gives you the funnel.
Stage definitions matter more than stage names, then: stages that reflect how deals are really worked beat stages copied from a template, because the deal view and the funnel view only agree when the stages are real.
The standard six stages
1. Lead / New
Someone entered your world — form fill, list import, referral, reply. Nothing is known yet beyond contact info.
Exit criterion: qualified against your bar (fit + intent) → advance; otherwise nurture or disqualify. This is the MQL/SQL line, and speed matters most right here.
2. Qualified
A real potential buyer: right profile, plausible need. Worth a rep's calendar.
Exit criterion: a discovery conversation happened and confirmed a problem you solve (your BANT-style checklist, applied as judgment).
3. Discovery / Meeting
You've talked. You understand their problem, stakeholders, and rough timeline.
Exit criterion: a concrete solution discussion is scheduled or delivered — demo done, scope agreed, or the prospect asked for numbers.
4. Proposal
A specific offer — scope and price — is in their hands.
Exit criterion: verbal or written intent ("yes, pending X"). Deals rot here more than anywhere; this stage needs the tightest follow-up cadence and the strictest aging alarm.
5. Negotiation / Commit
They want it; you're closing terms, legal, security review, signatures.
Exit criterion: signed, or dead. Nothing lives here longer than your contracting process actually takes.
6. Closed (Won / Lost)
The outcome — with a required reason code either way. Lost isn't failure; unlabeled lost is. Those codes are your win/loss report, which is your roadmap.
What to measure at every stage of the pipeline
Stages exist so you can measure movement. Four numbers per stage of the sales pipeline tell you most of what you need about pipeline health: how many deals are in it, what they're worth, how long they've been there, and what share advance from one stage to the next. The rest of your pipeline metrics are derived from those four.
| Stage | Metric to watch | What a bad number usually means |
|---|---|---|
| Lead | Time to first touch; lead-to-qualified rate | Slow response, or a lead source that doesn't fit |
| Qualified | Qualified-to-discovery rate | Qualification bar too loose; meetings booked that never happen |
| Discovery | Discovery-to-proposal rate; dwell time | Discovery isn't surfacing a real problem, or scope keeps drifting |
| Proposal | Dwell time; proposal-to-commit rate | Pricing surprises, a missing decision-maker, weak follow-up |
| Negotiation | Dwell time against your contracting norm | Legal or procurement bottleneck; a verbal commit that wasn't real |
| Closed | Win rate; reason codes on losses | Wrong-fit deals surviving too long; budget or competitor losses clustering |
If the entire pipeline converts at a rate you can live with but one stage leaks, that stage is your bottleneck, and fixing it beats putting more leads in the pipeline. A sales team that adds volume to a leak just leaks faster.
Dwell times added up are your cycle length. Knowing the average sales cycle length by segment is what makes aging alarms meaningful: twenty days in Proposal is normal in enterprise and alarming in a transactional motion. Track it per stage, because a long cycle is almost always one or two slow stages rather than uniform slowness.
Pipeline value is the sum of open deal sizes; the weighted version multiplies each deal by its stage probability. Pipeline coverage compares that total to your sales targets for the period. Sales velocity (pipeline velocity, in some tools) folds deal count, deal size, win rate and cycle length into a single rate of revenue per day, which is the cleanest one-number read on pipeline performance. Coverage and win rate are the two to learn first.
Stage probabilities: an illustrative example
A stage probability is the historical share of deals that reached that stage and eventually closed won. Suppose a team looks back over a year of closed deals and finds that of everything that reached Qualified, 15% eventually won; Discovery, 30%; Proposal, 50%; Negotiation, 80%. Those figures are an example, not a benchmark; yours will differ by segment and by rep.
What matters is where they come from. Probabilities computed from your own closed deals are a forecasting tool; probabilities set by a manager's gut are a mood stage in disguise. Recompute them each quarter, and treat a rep who consistently beats or misses the stage average as feedback about that rep's qualification, not a reason to change the average.
When to deviate from six
- Add a stage only when a distinct exit criterion exists. A security-review or pilot stage earns its place if it's a real, dated checkpoint in your motion. "Strong interest" does not.
- Transactional sales: collapse to four. Lead → Qualified → Proposal → Closed fits short cycles; more stages than conversations is theater.
- Enterprise: split Negotiation. Legal/procurement often deserves its own stage because its dwell time and owners differ from commercial negotiation.
- Never model the customer journey as your pipeline. Stages track your selling checkpoints; awareness/consideration language belongs to marketing funnels, not deal management.
How sales pipeline stages vary by B2B, B2C, and agency
The six-stage model is the common sales pipeline for a reason: it fits most business-to-business selling with a human rep in the loop. But the right sales pipeline follows your sales complexity, and three patterns cover most teams.
B2B sales with a long sales cycle
Multiple stakeholders, a budget cycle, security review, procurement. B2B sales at this end usually justifies 7 stages, because certain stages that are a single checkpoint elsewhere split into distinct ones here: a technical evaluation or pilot after Discovery, and Legal/Procurement separated from commercial Negotiation. Each has a different owner, a different dwell time, and a fact that ends it, such as a signed pilot agreement or a returned redline.
B2C and transactional sales
One decision-maker, one or two conversations, a decision measured in days. Fewer stages is correct: Lead, Qualified, Quote, Closed. Discovery and Negotiation collapse into the conversation where the offer is made, and the metric that matters most is response time from lead to first contact.
Agencies and productized services
Agencies usually need a Contract stage between Proposal and Closed, because the gap between "yes to the scope" and "signed with deposit paid" has its own failure mode: the proposal is accepted verbally and the contract sits unsigned while the client's budget quietly moves elsewhere. Onboarding is not a pipeline stage; it belongs to delivery, and putting it there pollutes the forecast with deals that are already revenue.
Stage design mistakes that make pipelines lie
- Mood stages. Any stage a rep can enter or leave based on feel will be gamed at forecast time. Facts only.
- No aging rules. Every stage needs a normal dwell time and an alarm past it — otherwise stage four becomes a hospice (the zombie math is in our coverage guide).
- Skipping backwards silently. Deals do move backwards — a champion leaves, scope reopens. Track regressions explicitly; they're your best early-warning signal.
- Percent-complete as probability. Stage 4 of 6 isn't 66% likely to close. Use historical per-stage close rates — or per-deal ML probabilities, which is the same idea with the guesswork removed.
How to build a sales pipeline (or refine the one you have)
Building an effective sales pipeline is mostly deciding what each stage means. Build a pipeline on paper first; putting it in software is the last step.
- Write down the steps in your sales process as they actually happen. Pull the last twenty closed-won deals and list the events each passed through: first reply, discovery call, demo, proposal sent, verbal yes, contract signed. The pipeline should reflect this record, not an org chart or a template.
- Define stages from the recurring events. An event that appears in nearly every won deal with a clear before and after is a stage. This is where teams create pipeline stages they don't need: if two events always happen together, they're one stage.
- Write each exit criterion as a yes/no fact, then test it. Hand the list to a sales rep and ask them to place five live deals. If any placement takes more than a few seconds of debate, the criterion isn't factual yet.
- Set a normal dwell time and an alarm for every stage. Use your own history for the baseline. Anything past the alarm gets a decision at the next review: advance, regress, or close lost.
- Assign stage probabilities from history. No history yet? Use a conservative placeholder, label it as one, and replace it after a quarter of real closes.
- Put it in the CRM and remove the escape hatches. Required fields on stage change, a required reason code on Closed Lost, no free-text stage names. Consistent pipeline management is won or lost in the configuration, not the pep talk.
- Refine your pipeline on a schedule. Once a quarter, look at where deals stall, where they regress, and which stage explains any gap in sales performance. A well-designed pipeline changes a little every quarter and a lot never.
If you'd rather start from a worked layout than a blank board, the sales pipeline template lays out stages, exit criteria and dwell times you can edit, and this guide to process steps covers the sales activities that belong inside each stage.
Pipeline design also decides what your software has to do. Every stage change is an event, and a CRM that acts on events (starting the follow-up sequence, flagging a deal past its dwell time, asking for the reason code) does the maintenance reps otherwise skip. AutomateNexus CRM, as one example, runs unlimited contacts on every plan from $49/mo, so the stages, not the contact count, are what you're paying for.
Pipeline reviews: keeping pipeline data accurate
Stages only stay honest if someone looks. Effective pipeline management comes down to a weekly pipeline review, and its job is narrow: for every deal past its dwell alarm or sitting in a late stage, confirm the exit criterion is actually met, then advance it, regress it, or close it.
Run it by exception. Sales managers who walk every deal in order run out of time before they reach the deals that matter. Sort by stage age and deal value first and the review spends its minutes on what's overdue or at risk. A good sales pipeline review of forty deals takes twenty minutes because thirty of them need no discussion.
Ask every flagged deal the same two questions: what fact moved it here, and what fact moves it next. If the rep can't answer the second, the deal is stuck or misplaced. Regressions get logged with a reason, the same way losses do.
The review is also where you keep pipeline data accurate. Deals with a blank amount, a missing close date, or a stage that contradicts the last logged activity get fixed in the meeting, not noted for later. Sales leaders who let this slide end up with a board that looks full in week one and empties in the last two weeks of the quarter, which is the pattern behind most missed sales targets. Cadence, roles and reporting are covered in the sales pipeline management guide; the stage-level rule is that no deal sits past its alarm without a decision.
Pipeline visibility is the payoff. When every deal carries a factual stage, a dated last activity and a probability drawn from history, the sales forecast falls out of the pipeline instead of being assembled from rep opinions, and anyone in the sales organization can see where the quarter's revenue actually stands.
Keeping stages honest, automatically
Stage discipline is another practice that decays under busyness: criteria blur, aging alarms get snoozed, reasons go uncoded. The systematic fix is making the pipeline maintain itself — in AutomateNexus CRM, Karrie nudges stage updates from actual activity (a sent proposal moves the deal; silence past dwell time flags it), keeps every stage's follow-up sequence running, and the daily brief surfaces exactly which deals sit past their welcome. The six stages stay six facts.
Pipeline stages FAQ
How many stages should a sales pipeline have?
As many as you have verifiable checkpoints — for most B2B teams that's five to seven. Fewer beats more: every stage must earn its exit criterion.
What's the difference between a pipeline and a funnel?
Same journey, different lens: the funnel is the aggregate conversion view (marketing's tool); the pipeline is the deal-by-deal management view (sales' tool). Stages belong to the pipeline; percentages belong to the funnel.
What should trigger a stage change?
An event, not a feeling: meeting completed, proposal delivered, verbal commit received. If you can't name the event, the deal doesn't move.
Should lost deals stay in the pipeline?
They leave the active pipeline but stay in the system with a reason code — feeding win/loss analysis and the quarterly re-engagement sequence that revives the "not now" cohort.
What are the 5 stages of a sales pipeline?
The common five-stage version is Lead, Qualified, Proposal, Negotiation, Closed: the six-stage model with Discovery folded into Qualified. It works when your qualification call and your discovery call are the same conversation. If they're separate meetings with separate outcomes, keep them as separate stages.
What are the 7 stages of the sales cycle?
The seven-stage version usually adds Prospecting before Lead and either a Pilot or a Contract stage before Closed: Prospecting, Lead, Qualified, Discovery, Proposal, Negotiation or Contract, Closed. The extra stages reflect longer cycles with more real checkpoints, not a better model.
What are the 5 stages of the sales process?
Described as activities rather than checkpoints, the five are usually given as prospecting, qualifying, presenting, handling objections, and closing. Pipeline stages are the checkpoints between those activities: the process says what the rep does, the stage records what has been proven true about the deal so far.