Sales Pipeline Stages and Why Deals Stall at Each | AmpUp

TL;DR: A standard B2B pipeline runs through seven stages: prospecting, qualification, discovery, proposal, negotiation, close, and post-sale onboarding. Most stage-list guides stop at describing what happens in each stage. This guide adds the part that matters, which is why deals stall at each one. Stalls are behavioral, not procedural. A deal parked at proposal usually reflects weak discovery prep or no mutual close plan, not a missing process step. Each stage below carries entry and exit criteria you can verify, so a rep cannot advance a deal on optimism alone. Pipeline and funnel are not the same. A pipeline counts active deals by stage from the rep’s side. A funnel tracks conversion rates as volume narrows over time.

See how AmpUp diagnoses why deals stall at each stage, not just where: watch the 2-minute walkthrough →

What a Sales Pipeline Actually Tracks

A sales pipeline tracks the active deals a rep owns, sorted by how close each one is to closing. Unlike a forecast or a report, the pipeline belongs to the rep. Each deal sits in exactly one stage, and its position reflects a judgment about where the buyer actually is in their decision.

Stages become useful when you define them by entry and exit criteria rather than by the activities happening inside them. “Rep sends proposal” describes an action. “Buyer has confirmed budget and named a decision-maker” describes a condition you can verify. Criteria you can check turn a stage into something auditable, so a manager reviewing the pipeline can tell whether a deal genuinely belongs where the rep placed it.

That auditability matters because most pipeline problems show up as stalls. A deal sits in one stage for weeks without moving forward or dropping out. Clear exit criteria expose the stall, because you can see exactly which condition the deal has failed to meet. The stage-by-stage breakdown below pairs each stage with the criteria that define it and the specific rep behavior that most often causes deals to get stuck there.

The B2B Sales Pipeline Stages, Entry Criteria, and Where Deals Stall

Most B2B teams run a seven-stage arc from first contact to post-sale onboarding. What separates a pipeline you can trust from a wish list is the criteria that govern entry and exit at each stage. The table below defines each stage, states what has to be true to enter and leave it, and names the rep behavior that most often traps deals there.

Stage	Definition	Entry criteria	Exit criteria	Why deals stall here
Prospecting	Identifying and reaching accounts that fit your ideal profile.	Account matches target firmographics and has a plausible trigger.	Prospect responds and agrees to a first conversation.	Reps spray generic outreach instead of researching the account, so replies never come and the stage fills with dead contacts.
Qualification	Confirming the prospect has budget, authority, need, and a timeline worth pursuing.	Discovery call booked with a relevant contact.	You confirm a real problem, a buyer with influence, and a rough budget.	Reps skip disqualifying questions to protect the deal count, and unqualified deals rot in the pipeline for months.
Discovery	Mapping the prospect’s problem, current process, and success criteria in detail.	Prospect confirmed a problem worth solving.	You document the buying process, stakeholders, and what a win looks like to them.	Weak discovery prep means the rep asks surface questions, misses the economic buyer, and builds a proposal on guesses.
Proposal / Solution	Presenting a scoped solution and pricing tied to the problem you uncovered.	Discovery documented and success criteria agreed.	Prospect accepts the proposal as the basis for negotiation.	Reps pitch features instead of the outcomes discovery surfaced, so the proposal reads as generic and stalls in committee.
Negotiation	Resolving pricing, terms, and objections before commitment.	Proposal under active review by the buyer.	Both sides agree on scope, price, and terms.	Poor objection handling turns a price question into a delay, because the rep discounts on reflex rather than reframing value.
Closing	Securing signature and finalizing the agreement.	Terms verbally agreed.	Contract signed and countersigned.	No mutual close plan means the deal drifts. The rep waits on the buyer’s timeline instead of sequencing legal, procurement, and signature dates.
Onboarding	Activating the customer and delivering early value.	Contract signed.	Customer reaches first defined success milestone.	Reps hand off cleanly and disappear, so the customer stalls at setup and the renewal conversation starts from a deficit.

The stall reasons in that last column are not process gaps. They are execution failures, and they cluster at predictable points for reasons a stage list alone never explains. The heaviest concentration sits between proposal and close, where deals that looked healthy in the CRM quietly go quiet. For the full behavioral data on that pattern, see Why Enterprise Deals Stall.

That clustering has a behavioral cause. Early stages fail on volume and preparation, and a rep who under-researches accounts simply generates fewer conversations. The damage there is visible because the pipeline stays empty. The proposal-to-close band fails differently. Deals arrive at that band looking qualified, then stall because the rep never confirmed the economic buyer during discovery, never surfaced the real objection during negotiation, or never built a dated close plan the buyer agreed to. Each gap is invisible in the stage field. The deal still reads as “proposal sent,” even as three separate execution mistakes quietly compound.

Read this way, the pipeline stops being a tracking artifact and becomes a diagnostic one. When you see deals piling up at negotiation, the stage tells you where. The stall reason tied to that stage tells you what to coach. A rep whose deals consistently die between proposal and close does not have a pipeline problem. That rep has an objection-handling problem or a closing-discipline problem, and no amount of CRM hygiene fixes a skill gap. The value of clean entry and exit criteria is that they force the honest question. Not “how many deals are at this stage,” but “why do mine keep dying here.”

Sales Pipeline vs. Sales Funnel: What Actually Differs

A sales pipeline counts your active deals by stage, and a sales funnel measures the rate at which volume narrows as prospects move toward a purchase. The pipeline answers a rep-side question about individual deals. You have 40 open opportunities, 12 sit in proposal, and each carries a dollar value and a close date. The funnel answers an aggregate question about conversion. Of 1,000 leads that entered last quarter, 300 reached discovery and 45 closed, so you can see where the biggest drop-off happens.

The same deal data looks different depending on which view you take. Picture 100 opportunities that entered your pipeline this quarter. In the pipeline view, you track each one as a discrete deal with a name, an owner, and a stage, and you forecast revenue by summing their weighted values. In the funnel view, those same 100 opportunities become percentages. Sixty percent advance past qualification, thirty percent reach proposal, and fifteen percent close, which tells you your qualification-to-proposal step leaks half your deals.

Both views draw on identical records, but they serve different jobs. Reps and managers work the pipeline to move specific deals forward. Sales leaders read the funnel to find the stage where conversion collapses across the whole team. Confusing the two leads you to forecast with conversion averages or diagnose team-wide leaks by staring at one rep’s deals. For the math that connects pipeline volume, win rate, deal size, and cycle length into one number, see Sales Velocity Formula: How to Calculate It and Improve Each Input.

Building a Pipeline Your Reps Can’t Fudge

Your pipeline data is only as honest as the exit criteria that govern it. When a rep decides whether a deal moves from discovery to proposal, subjective judgment invites optimism. A deal “feels close” or the buyer “seems interested,” so the rep advances it. Weeks later that deal sits untouched in a late stage, inflating your forecast and hiding the fact that nothing verifiable ever happened.

The fix is to define each exit criterion as an observable event, not a feeling. A deal leaves qualification when the buyer confirms a budget range, not when the rep senses one exists. It leaves proposal when a mutual close plan carries a signed date, not when the rep expects a signature. A signed document, a scheduled procurement review, and a written budget approval either exist or they do not. Anyone auditing the pipeline can check.

Reps advance deals prematurely because activity metrics reward motion over truth. When a leader tracks proposals sent or opportunities created, a rep hits the number by pushing weak deals forward. The pipeline fills, the dashboard looks healthy, and the close rate quietly collapses two quarters later. Objective exit criteria remove that incentive, because a rep cannot claim a stage transition without producing the artifact that proves it.

Enforce this at the stage gate, not in the forecast review. Configure your CRM so a deal cannot progress until the required field or attachment exists. Once every stage change points to something verifiable, your pipeline reports where deals actually are. For the 30-minute weekly cadence that runs on this kind of verifiable data, see Pipeline Review Meeting Template (30 Minutes, Signal-Driven).

---

Want to see which stage is quietly eating your team’s pipeline? Book a demo → Bring a quarter of closed-lost deals and we will show you exactly which stage they died at, which behavioral gap killed them, and what Sales Brain would have flagged weeks earlier.

---

Why Stage Tracking Alone Doesn’t Explain the Stall

A pipeline stage tells you a deal has sat at “proposal” for three weeks. It does not tell you the rep sent a generic quote without confirming the buyer’s evaluation criteria, or skipped the multi-threading that would have reached the actual economic buyer, or never surfaced the objection now killing the deal in silence. The stage field records position. It says nothing about the behavior that produced that position.

That gap matters because two deals stuck at the same stage often stall for completely different reasons. One rep never built a mutual close plan. Another handled a pricing objection by discounting instead of reframing value. A third let a champion go quiet and did nothing to re-engage. Your CRM shows both as “proposal, 40% probability.” The root causes stay invisible. For the specific signals that predict a slip before the close date moves, see What Is Deal Slippage? Causes, Signals & Prevention.

Fixing a stall means reading the execution layer under the stage, which is exactly what the pipeline was never built to capture. Behavioral data of the kind Sales Brain produces records what reps actually did in each conversation, so a stalled deal becomes diagnosable rather than just visible. When the diagnosis points to a skill gap, Skill Lab turns it into targeted practice before the next deal hits the same wall. Stage tracking answers where a deal sits. Execution data answers why it stopped moving, which is the only question that changes the outcome.

Frequently Asked Questions

Q: How many stages should a B2B sales pipeline have?

Most B2B pipelines run five to seven stages, from prospecting through post-sale onboarding. AmpUp treats seven as the practical default because it separates discovery from qualification and keeps the proposal-to-close transition visible. Fewer stages hide where deals stall, and more than eight create busywork without adding diagnostic value.

Q: How do pipeline stages differ from deal or opportunity stages in a CRM?

Pipeline stages describe your sales process end to end, while CRM opportunity stages are the specific fields Salesforce or HubSpot use to track a single deal. The two usually map one to one, but CRM stages carry probability percentages and forecast categories that your process definition does not. Align them so a stage change means the same thing everywhere.

Q: How do you calculate pipeline velocity and stage conversion rate?

Pipeline velocity multiplies the number of open deals by average deal value and win rate, then divides by the average sales cycle length in days. Stage conversion rate divides deals that exit a stage by deals that entered it. Track both to find where deals leak. For the full breakdown of each input and how to improve it, see Sales Velocity Formula.

Q: What is the difference between a sales pipeline and a sales funnel?

A pipeline counts active deals by stage from the rep’s side, with each deal carrying a name, owner, value, and close date. A funnel tracks conversion rates as volume narrows over time, turning the same deals into percentages that show where drop-off concentrates. Reps work the pipeline. Leaders read the funnel. Confusing the two leads to forecasting with averages or diagnosing team-wide leaks from one rep’s deals.

Q: What are exit criteria in a sales pipeline?

Exit criteria are the verifiable conditions a deal must meet before it advances to the next stage: a confirmed budget range, a documented buying process, a mutual close plan with a signed date. They replace rep optimism with observable events. A deal either has a scheduled procurement review or it does not, and anyone auditing the pipeline can check. AmpUp recommends enforcing them at the CRM stage gate rather than in the forecast review.

Q: Where do most B2B deals stall in the pipeline?

The heaviest stall concentration sits between proposal and close. Deals arrive at that band looking qualified, then stall because the rep never confirmed the economic buyer, never surfaced the real objection, or never built a dated close plan. Early-stage failures are visible because the pipeline stays empty. Late-stage failures hide behind a healthy-looking stage field while execution mistakes compound.

Q: How does AI help with pipeline stage management?

AI tools like AmpUp’s Sales Brain read the execution layer under the stage field: whether the economic buyer has been engaged, whether objections were surfaced or buried, whether a close plan exists with real dates. That turns a stalled deal from visible into diagnosable. The stage tells you where the deal sits. The behavioral data tells you why it stopped moving and which skill gap to coach.

Conclusion

A stage list tells you where deals sit. Entry and exit criteria tell you whether they belong there. The stall pattern at each stage tells you what to coach. Most pipeline advice stops at the first layer, which is why most pipelines read as healthy right up until the quarter misses.

Build the criteria, enforce them at the stage gate, and read stalls as behavioral signals rather than process gaps. A deal that keeps dying at negotiation is not a pipeline problem. It is a skill gap wearing a stage label, and the fix lives in coaching, not CRM hygiene.

---

See AmpUp Diagnose Where Your Pipeline Actually Leaks

Bring us a quarter of deal data. We will show you which stage concentrates your stalls, which behavioral gap is driving each one, what Sales Brain would flag for coaching this week, and what Skill Lab would build into practice for the reps whose deals keep dying at the same stage.

Book a demo →

Want to explore first? See how Sales Brain works, review the execution loop, or calculate what better execution is worth for your team.