What is a sales pipeline?

How this page was researched

Every definition and figure below is read directly from Salesforce's, HubSpot's and Pipedrive's own published pages, plus one independent sales-operations source on the pipeline coverage question, all checked on 29 September 2026 and linked in Sources at the bottom. Salestruct is not affiliated with any of the three vendors named here; we use CRM tools across client engagements and are describing what each one actually publishes about the concept, not selling one of them. Where a number could not be traced to a page with a stated method, it is left out rather than repeated from a blog post that repeated it from somewhere else.

What is a sales pipeline?

A sales pipeline is a visual representation of where each prospect sits in your sales process, organized by stage from first contact through to a closed deal. Salesforce's own definition states it plainly: it "is a visual representation of where each prospect is in the sales process," which "helps you identify next steps and any roadblocks or delays so you can keep deals moving toward close." HubSpot describes the same object from the product side: "a visual representation of your deals organized by stage, from initial contact to closed-won," where "effective pipelines match your sales process with clearly defined stages, entry/exit criteria for each stage, and automation that moves deals forward." Pipedrive's definition adds the operational purpose: a pipeline is "a structured system for tracking and managing opportunities from first contact to closed deal," and a working one "helps sales teams qualify opportunities, prioritize next actions, improve forecasting and identify where deals stall before revenue is lost."

Put together, three things are true of every sales pipeline regardless of which CRM renders it:

• It is organized by stage, not by contact or by date. A deal's position tells you what has been proven so far, not just that it exists.
• Each stage carries a value and a count. A pipeline is a list of individual deals, each with an amount and an owner, not a single aggregate number.
• It exists to be reviewed, not just recorded. The point of laying deals out this way is to spot the ones that have stalled and the gaps in what is coming next, before the quarter ends rather than after.

Sales pipeline vs sales funnel

The two terms get used as if they are the same thing, and Salesforce's own page is explicit that they are not: "A sales pipeline is not to be confused with the sales funnel... a sales pipeline focuses on where the prospect is in their buying journey," while "the sales funnel is also a visual representation of the sales process, but from the customer's point of view." In practice: a pipeline is a list of named, live deals a rep owns and works. A funnel is an aggregate shape, usually a set of drop-off percentages from one stage to the next, used to describe the health of the whole process rather than any one deal. You manage a pipeline deal by deal. You read a funnel to see where the process itself is leaking.

Lead vs deal

The other pair worth separating, because CRMs enforce it differently, is lead versus deal. HubSpot's own distinction: "A lead is a contact who has expressed interest but isn't yet in active sales conversations. A deal represents an active sales opportunity with specific stages, associated contacts, and predicted revenue." The pipeline only ever contains deals. A lead becomes a deal, in HubSpot's own framing, once specific criteria are met: budget confirmed, decision-maker identified, timeline established, need validated. Skip that gate and your pipeline count includes contacts that were never actually opportunities, which inflates coverage without changing what closes.

What are the stages of a sales pipeline?

Salesforce's own FAQ lists the pipeline as commonly running seven stages: prospecting or lead generation, lead qualification, a sales call or demo, a formal proposal, objection-handling and negotiation, a closed deal, and post-purchase follow-up. That is the generic shape almost every CRM ships with by default, and it is a reasonable starting point.

It is also, on its own, not enough to run a forecast on. A stage name only tells you something useful if it is tied to a specific, checkable exit condition rather than an activity a rep logged. Pipedrive's own guidance makes this point directly: avoid vague stage labels like "Interested" or "In progress," and instead name stages after observable milestones with objective exit criteria, such as "Discovery call completed" or "Budget confirmed." We built out exactly that version, stage by stage with a binary exit test for each one, in CRM pipeline stages: give every one an exit criterion. If you already have the generic seven stages in your CRM, that is the page for rebuilding them so a stage actually means what you assume it means.

How do you measure a sales pipeline?

A CRM will happily show you a total pipeline value and call it a health check. That number alone tells you almost nothing, because it does not say how likely any of it is to close or how long it has been sitting there. The metrics that actually answer "are we going to hit the number" are:

• Qualified lead count and conversion rate. How many opportunities are entering the pipeline each period, and what share of them clear each stage. Named directly on Salesforce's own metrics list.
• Deal age. How long a deal has sat in its current stage, which is the fastest way to find the ones that are not actually moving, just sitting there being counted.
• Pipeline coverage. Whether the total value in flight is enough to hit the revenue target, covered in full below.
• Sales velocity. How fast a deal moves from entry to close, and how much revenue that pace produces over a period.

Sales velocity has one published formula worth knowing, because it is the single number that combines volume, value, win rate and speed into one figure: HubSpot states it as Sales Velocity = Number of Opportunities x Deal Value x Win Rate / Length of Sales Cycle. We walk the formula, a worked example and which of the four inputs is actually the easiest to move first in What is pipeline velocity?. The short version, in HubSpot's own words on why it matters: "Every sales manager lives in fear their sales pipeline is a bunch of fluff," and velocity is what "uncovers a slow-moving or, even worse, stagnant pipe" before the quarter proves it the hard way.

What is pipeline coverage, and is the 3x rule real?

Pipeline coverage is the ratio of total pipeline value to the revenue target it needs to produce. Salesforce defines it as "the total value and/or number of deals in your pipeline, which allows you to see if you have enough potential sales to meet your revenue goals." Pipedrive frames the same idea as a planning input rather than a report: managers "work backward through historical conversion rates to estimate how many qualified opportunities should exist in each stage of the pipeline," which "transforms the pipeline from a reporting tool into a planning tool."

Neither vendor page states a target ratio, because there is not a universal one to state. The number most sales teams have actually heard, "you need 3x pipeline coverage," traces to sales-operations folklore rather than to a study.

Kellogg's own account of where the number came from: "So where does the magical 3x coverage ratio come from? I don't know the history, but I can say that long before I saw... my first salesforce automation system, I heard sales managers speak of the rule of three. It makes sense: 2x seems tight and 4x seems rich. So, through the Goldilocks Principle, we ended up with 3x." His argument is not that coverage targets are useless, it is that a flat, universal multiplier is the wrong shape for one. He recommends a ratio that is emergent (calculated from your own historical conversion rate, not handed down), personalized (a rep who closes 40% of qualified opportunities needs less coverage than one who closes 15%), secret (publishing the target as a quota teaches reps to inflate the pipeline to hit the ratio, which defeats the forecast it was meant to protect), and time-varying (based on what is left to close before the period ends, not a static number carried all quarter).

A worked example, using invented numbers to show the arithmetic, not a client result:

1. 1.
   Set the revenue target

   You need $200,000 in new revenue this quarter.
2. 2.
   Know your average deal size

   Your average closed deal is $10,000, so you need 20 wins.
3. 3.
   Know your actual win rate

   Your team's historical win rate on qualified opportunities is 24%, measured over the last four quarters.
4. 4.
   Divide wins needed by win rate

   20 divided by 0.24 is roughly 83 qualified opportunities that need to be in the pipeline over the quarter.
5. 5.
   Read the ratio your own numbers produced

   83 opportunities against 20 wins is roughly a 4.15x coverage ratio, not 3x. Nobody chose 4.15x because it sounds tidy. It is what this team's own win rate requires.

That is the whole method Kellogg is describing: coverage is an output of your win rate and your target, not an input you copy from a blog post. A team closing 40% of qualified opportunities needs roughly 2.5x coverage for the same target. A team closing 15% needs closer to 6.7x. Using a flat 3x for either one either starves the pipeline of deals it actually needs, or has reps chasing a number that was never calibrated to how they sell.

Common mistakes when running a sales pipeline

• Vague stage names with no exit test. "In progress" and "Interested" tell a manager nothing checkable. Pipedrive's own guidance is to name stages after a milestone a buyer produced, not an activity a rep logged. See the full six-stage rebuild in crm-pipeline-stages-exit-criteria.
• Treating the pipeline total as a health signal on its own. A large total pipeline value says nothing about win rate, deal age or stage distribution. Read it against coverage and velocity, not by itself.
• Letting stale deals sit uncounted for what they are. A deal untouched for six weeks still counts toward coverage unless someone removes it or marks it accurately, which quietly overstates how much real pipeline exists. Measuring how fast your own data goes stale is covered in CRM hygiene: measure your decay rate.
• Borrowing a coverage ratio instead of calculating one. Covered in full above: a flat 3x rule was never measured against your win rate, so it either understates or overstates what you actually need.
• Choosing the CRM before the process. A pipeline is a structure you define; the CRM is where you enforce it. Two products can render the identical pipeline very differently once you look at automation, stage limits and reporting. We compared what HubSpot and Pipedrive each actually let a team do with a pipeline, plan by plan, in HubSpot vs Pipedrive.

Frequently confused terms

If your team is past the point of arguing over stage names and into arguing over which numbers the CRM should even be trusted to report, that is usually a sign the pipeline was never the actual problem.

If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.