What Is a Sales Pipeline? Stages, Examples and Mistakes

It's Monday morning, and Rachel's team pipeline shows $1.2 million. One deal, a $90,000 order at a regional hospital supplier, has sat at "Proposal" for six weeks. She asks the rep when he last spoke to the buyer. He checks his phone. Five weeks ago.

Rachel (an invented manager, but you've met her) doesn't have a pipeline problem. She has a definition problem. If you've ever asked what is a sales pipeline and got back a funnel diagram and a list of stage names, you know the gap. Drawing stages is easy. Agreeing what must be true before a deal moves, and keeping it true while reps are out in the field, is the hard part.

Below: a plain definition, seven stages with exit criteria written from the buyer's side, one field deal from first visit to signed order, how a pipeline differs from a funnel and a forecast, and the mistakes that quietly inflate it.

A pipeline is only as good as the notes behind it. If your reps would rather talk than type after a visit, ParrotNotes turns a two-minute spoken debrief into a summary and action items.

What is a sales pipeline?

A sales pipeline is the list of open deals a team is working, each placed at a stage of the sales process, with a value, an expected close date, and a next step. It shows where every opportunity stands, what has to happen next, and which deals are stuck, so reps know what to do and managers know what's real.

Salesforce calls it "a visual representation of where each prospect is in the sales process", and IBM says almost the same. The visual part is the board in your CRM. The useful part is three fields on every deal:

• Stage: how far the buyer has actually moved
• Value and close date: what it's worth and when it should land
• Next step with a date: the specific thing that happens next, and when

A deal missing any of the three isn't in the pipeline. It's on a wish list.

The seven sales pipeline stages, with exit criteria

Most sources list six or seven stages with similar names. Salesforce runs from prospecting to post-purchase, LinkedIn's version ends with retention, and IBM stops at closing.

The names matter less than the exit criteria. A stage should describe what the buyer has done, not what the rep has done. "Quote sent" tells you the rep hit send. "Buyer reviewed the quote and named who else signs" tells you the deal moved. Here's a version for field teams; copy it and adjust the wording.

Discovery and negotiation do the most damage when they're loose. For discovery, our discovery questions guide covers what to ask, and MEDDPICC maps neatly onto stages 2 to 4. For negotiation, a mutual action plan shows both sides who signs and how.

A sales pipeline example: one field deal, stage by stage

Definitions stick better with a deal attached. This one is invented, but it runs the way field deals do.

Leah is an outside rep for a packaging equipment distributor in Ohio. On a service call at Brookfield Foods, a regional food distributor, she notices the night shift wrapping pallets by hand. Here's how that became a signed order.

Look at May 9. Nothing was lost, but the exit evidence for negotiation was: the decision-maker's yes had turned back into an open evaluation. So Leah moved the deal back a stage and pushed the close date a month.

That honest edit is the whole point. Left at "Negotiation, May 31," her manager would have counted $48,000 for May, and May would have missed. And every note is specific: names, numbers, dates, the buyer's own reason. Not "great meeting, very interested."

Sales pipeline vs sales funnel vs sales forecast

These three get used as if they were one thing. They answer different questions.

Salesforce frames it as the seller's view (pipeline) against the buyer's view (funnel). LinkedIn adds that a forecast "estimates how much revenue a business can potentially bring in." Because the forecast is built from the pipeline, a loose pipeline makes a bad forecast; the method is in our guide on how to improve sales forecast accuracy.

Four numbers that describe a pipeline

Pipeline value is the sum of open deals. On its own it flatters everyone, since a deal at Prospect counts the same as one at Negotiation.

Coverage is pipeline value divided by quota. Many B2B teams aim for three to four times, a rule of thumb ZoomInfo cites, but your win rate is the better guide.

Stage conversion is the share of deals moving from each stage to the next. A drop after Proposal often means discovery never found the person who signs.

Deal age is how long a deal has sat in its stage. At twice your normal time, treat it as stalled.

None of these beats the notes underneath. Try ParrotNotes free: every recording gets an AI summary, and 100 free minutes a month covers plenty of two-minute debriefs.

Common sales pipeline mistakes

Dev manages eight reps selling building supplies to contractors. Half his pipeline sat in a stage called "Demo scheduled," because booking a demo was easy and the stage rewarded it. He renamed it "Buyer confirmed fit," with the exit rule above, and many of those deals dropped back to Qualified that week. The pipeline shrank. His forecast calls got shorter.

That's the first mistake. The full list:

1. Stages named after seller activity. "Called" and "Quote sent" measure effort. Name stages after what the buyer did.
2. No written exit criteria. Without them, "Qualified" means one thing to your best rep and another to your newest.
3. Next steps without dates. "Follow up" isn't a next step. "Anita answers by Apr 29" is.
4. Close dates that move quietly. A date pushed three times with no note explaining why is the warning sign.
5. Deals that never die. A deal untouched for 60 days inflates coverage. Close it as lost and record why.
6. Stages that never go backward. Leah's May 9 edit feels like failure. It's accuracy.
7. Updates written from memory, days later. Friday's CRM entry for Tuesday's visits produces "good meeting" notes. Salesforce's State of Sales 2026, a survey of 4,050 sales professionals, found 79% of high performers prioritize data hygiene, against 54% of underperformers.

The first two are definition fixes for this week. The rest are habits, built through your field sales management cadence, a 15-minute pipeline stand-up, and a quarterly sales QBR.

Where field pipeline evidence comes from

For a field team, the evidence is said out loud in a warehouse or a site office, and it's gone by the next visit unless someone captures it. The fix is a spoken debrief after every meaningful visit, before the rep drives off:

• Who was there, and did we meet anyone new who signs?
• What did they say, in their words, about problem, budget, or timing?
• What changed against this stage's exit criteria? Forward, or back?
• What's the next step, who owns it, and by when?

Leah's notes above are exactly that, trimmed. Two minutes of talking gives a manager a record they can read in 30 seconds.

Conclusion

So, what is a sales pipeline? It's your open deals, each at a stage that describes what the buyer has done, each with a value, a close date, and a dated next step. Write the stage definitions down, let deals move backward when the evidence says so, and treat the notes behind each move as the real asset.

Rachel's six-week "Proposal" deal wasn't a lazy rep. It was a stage with no exit rule and a visit with no record. Download ParrotNotes free, give your reps the four debrief prompts, and let the next pipeline call run on what buyers actually said.