What a healthy sales pipeline looks like. Four checks that matter more than the total value.

The short answer. What "healthy" actually measures.

A healthy sales pipeline is not a big number. It is a pipeline sized correctly for your own win rate, made up of opportunities that genuinely match your ideal customer, and moving through stages at a pace you can predict. Founders who watch only the total value in the CRM tend to feel reassured by a large figure that is mostly unqualified adds and stalled deals that nobody has had the nerve to mark as lost.

The more useful question is not "how much pipeline do we have" but "how much pipeline do we need, given how often we actually win". That reframes coverage from a fixed multiple to a calculation specific to your business.

How it works in practice. The four checks worth running.

Coverage comes first. The old rule of thumb was 3x quota in pipeline at all times, a heuristic popularised by the analyst firm SiriusDecisions, now part of Forrester. It survives as a rough starting point, but it treats every sales motion as identical. The more accurate version divides 1 by your historical win rate: a team closing 25% of qualified opportunities needs around 4x coverage to hit its number, while a team closing 40% needs closer to 2.5x. Enterprise teams with lower, more variable win rates should run higher coverage than SMB teams closing faster and more often.

Stage distribution comes second. A healthy pipeline is naturally weighted toward earlier stages, since not every qualified opportunity survives to close. If the split between early and late stage looks roughly even, either the early stages are under-populated or deals are being advanced before they have earned it, both of which flatter the CRM and hurt the forecast.

Velocity is the third check, and the one most founders skip. It is not enough for deals to exist in a stage; they need to be moving through it. A deal that has sat in "proposal sent" for six weeks with no logged activity is not pipeline, it is a placeholder. Ageing reports that flag anything past double the typical time-in-stage catch this before it quietly drags the whole quarter down.

Source and fit quality is the fourth check. Two pipelines of identical size can have very different health if one is built from inbound leads that match your ideal customer profile and the other from a list-building exercise that technically counts as pipeline but rarely converts. Tagging opportunities by source and reviewing win rate by source, not just in aggregate, usually exposes which channels are actually worth the coverage they occupy.

What good looks like. Benchmarks, and why they only go so far.

Gartner's ongoing B2B buying research is useful context here: the average buying group involved in a significant purchase has grown from around 5.4 stakeholders a decade ago to 6 to 10 today, and every additional person in that group adds internal alignment time that a seller cannot shortcut. That is one of the main reasons pipelines that looked fine three years ago now need to run wider and further ahead of quota than they used to, independent of anything a sales team is doing wrong.

These ranges are a sanity check, not a target. A founder-led team with a genuinely differentiated offer and a short, low-committee sales cycle can run healthily on coverage that would worry a team selling into enterprise procurement. The benchmark tells you where to look. Your own trend, tracked consistently in a proper sales pipeline management process, tells you whether what you are looking at is actually a problem.

Pitfalls to avoid. Where founders get pipeline health wrong.

The most common mistake is counting vanity pipeline: opportunities added to hit an activity target rather than because a prospect has shown genuine buying intent. This inflates coverage on paper while doing nothing for the forecast, and it is usually visible the moment someone checks how many of those opportunities have had a second meaningful conversation.

The second is letting stalled deals sit unmarked. Nobody enjoys marking a deal closed-lost, so it lingers in "negotiation" for months, still counted in coverage, still distorting the average time-in-stage, and still giving false comfort that pipeline is thicker than it really is. A weekly stage review, the same discipline behind a proper sales pipeline review, is the fastest way to catch this before it compounds.

The third is reporting one blended pipeline figure across genuinely different segments. A pipeline that mixes a fast, low-touch self-serve motion with a slow, multi-stakeholder enterprise motion will always look confusing as one number, because the two segments behave completely differently and were never going to average into something meaningful. Splitting the pipeline the same way you would split pipeline stages across different deal types is what turns a confusing dashboard into a decision-making tool.

The fourth is chasing coverage instead of win rate. A team that cannot hit quota at 3x coverage rarely fixes the problem by pushing coverage to 5x. It usually has a qualification problem further upstream, and more unqualified pipeline just buys a few more weeks before the same shortfall shows up again. Fixing win rate, through better qualification and a sharper mid-funnel process, does more for a healthy pipeline than adding volume ever will.

A worked example. Running the numbers for a ten-person team.

Take a ten-person B2B sales team with a quarterly target of 500,000 US dollars and a historical win rate of 22%. Applying the 1 divided by win rate calculation gives a required coverage of roughly 4.5x, meaning the team needs around 2.25 million dollars of qualified pipeline in play to have a realistic shot at the number, not the 1.5 million a flat 3x rule would suggest. That gap, 750,000 dollars of pipeline the flat rule would have missed, is exactly the kind of shortfall that only shows up once win rate is used instead of a generic multiple.

Splitting that same pipeline by stage tells a second story. If 60% of the 2.25 million sits in the earliest qualification stage, 25% in active evaluation, and only 15% in late-stage negotiation, the shape is healthy: plenty of new opportunities feeding the funnel, a natural taper as deals fail to progress, and a realistic amount in the final stage. If the split were reversed, with most of the value sitting late-stage and very little new pipeline behind it, the team would look fine this quarter and be in real trouble next quarter, because nothing is coming to replace what closes.

Velocity closes the loop. If the team's historical median time in the evaluation stage is 18 days, an ageing report that flags anything sitting past 36 days with no logged activity will typically surface three or four deals a month that are not actually progressing, however healthy they look in the coverage and stage numbers. Pulling those out of the working pipeline, or actively working to unstick them, is what keeps the coverage figure honest rather than inflated by deals that were never really moving.

None of these three checks replaces the others. A team could have perfect coverage and a healthy stage split while still carrying six stalled deals that quietly overstate how close it really is to quota. Running all three checks together, on a fixed weekly and monthly cadence rather than only at quarter end, is what turns pipeline health from a guess into a number a founder can actually plan around.

Making the checks routine. Where pipeline health actually gets managed.

None of the four checks above works as a one-off audit. Coverage, stage distribution, velocity and source quality all drift week to week, and a business that reviews them once a quarter is always looking at a picture that is already out of date by the time anyone acts on it. The founders who keep a genuinely healthy pipeline tend to treat the weekly pipeline review as non-negotiable, short, and specific: which deals moved, which stalled, and which need a decision on whether they are still real.

CRM hygiene is what makes any of this possible to measure at all. A pipeline coverage figure is only as accurate as the close dates, stage assignments and deal values a rep enters, and a CRM where reps routinely leave stale close dates or skip stages to look busier will produce a coverage number that flatters reality rather than describing it. This is less a data-entry problem than a management one: what gets reviewed weekly, in front of the team, tends to get kept current; what only gets pulled for a quarterly board deck tends to rot quietly in between.

Forecasting categories add a final layer of honesty. Splitting open pipeline into commit, best case and pipeline, rather than reporting one undifferentiated total, forces a rep to make an actual judgement call on each deal rather than letting everything sit in an ambiguous middle. A pipeline that is healthy by coverage and stage but where every deal sits in the vaguest possible category is usually a pipeline nobody has looked at closely enough to categorise properly, which is itself a useful, if uncomfortable, signal.