Pipeline Metrics That Lie to You Every Quarter

Pipeline metrics tell you what you want to hear more often than what you need to know. A pipeline that looks healthy in your CRM can mask a sales process that is stalling, a marketing function that is filling the top of the funnel with the wrong prospects, or a revenue forecast that is built on optimism rather than evidence.

The problem is not that pipeline metrics are wrong. It is that most teams read them in isolation, without the context that makes them meaningful. Volume tells you nothing without velocity. Stage distribution tells you nothing without conversion rates. And conversion rates tell you nothing if the deals closing are not the deals you actually want.

This article is about reading pipeline metrics honestly, not just fluently.

Why Pipeline Volume Is the Most Misread Metric in B2B

When I was running agency teams and reviewing commercial performance with clients, the number that came up first in almost every pipeline conversation was total value. “We have £4 million in pipeline.” “Our pipeline is up 30% on last quarter.” These numbers felt reassuring. They were also, in most cases, almost useless without further interrogation.

Pipeline volume tells you how much opportunity has been identified and entered into your CRM. It does not tell you how much of it is real, how much of it is progressing, or how much of it will close within any meaningful timeframe. I have seen pipelines with eight figures of notional value where the actual expected revenue for the next 90 days was a fraction of that, because deals were stacked in early stages with no meaningful movement.

The issue is structural. Sales teams are often incentivised to build pipeline, not to keep it clean. Marketing teams are often measured on leads generated, not on lead quality. When both functions are optimising for volume, the pipeline swells, and the signal-to-noise ratio collapses.

There is a broader principle here that I think about often. If your pipeline grew by 20% while the market for your product grew by 40%, you are not winning. You are losing ground, and doing it with a smile on your face because the absolute number is moving in the right direction. Context is not optional in pipeline analysis. It is the whole point.

This is the same logic that BCG applied when examining competitive advantage through relative growth: absolute performance figures rarely tell the full story. Relative performance, measured against the market and against competitors, is where the real insight lives.

The Four Pipeline Metrics Worth Tracking Together

Pipeline metrics only become useful when you track several of them together and look at how they move in relation to each other. Individually, each metric has a ceiling on what it can tell you. In combination, they start to describe a system.

The four I come back to consistently are: pipeline volume, stage conversion rates, average sales cycle length, and pipeline coverage ratio. Each one answers a different question, and each one changes meaning depending on what the others are doing.

Pipeline volume answers: how much opportunity exists? It is the starting point, not the conclusion. Use it to track trend direction over time, but never use it as a standalone health indicator.

Stage conversion rates answer: where are deals actually progressing, and where are they dying? This is where you find the real story. I have worked with businesses where the top-of-funnel conversion from lead to qualified opportunity looked strong, but the conversion from qualified opportunity to proposal was catastrophically low. That gap told us the qualification criteria were wrong. Deals were being moved to “qualified” before they actually were, which inflated pipeline volume and created a false sense of momentum.

Average sales cycle length answers: how long does it take to move a deal from entry to close? This metric is particularly sensitive to changes in deal mix. If your average deal size is increasing because you are targeting larger accounts, your sales cycle will lengthen. If you do not adjust your forecasting model to account for that, you will consistently over-predict near-term revenue.

Pipeline coverage ratio answers: do you have enough pipeline to hit your revenue target? The standard rule of thumb is 3x coverage, meaning you need three times your revenue target in pipeline to be confident of hitting the number. In my experience, that ratio varies significantly by industry, deal complexity, and sales team maturity. A 3x ratio in a business with a 60% win rate means something very different from a 3x ratio in a business with a 25% win rate. The ratio is a starting point for a conversation, not a universal standard.

If you are building out the broader commercial framework around these metrics, the Sales Enablement and Alignment hub covers the intersection of marketing performance, sales process, and revenue accountability in much more depth.

How Pipeline Velocity Changes the Conversation

Pipeline velocity is the metric that most teams underuse. It measures how quickly deals move through your pipeline and how much revenue that movement generates over a given period. The standard formula combines four variables: the number of deals in pipeline, the average deal value, the win rate, and the average sales cycle length in days.

What makes velocity useful is that it forces you to think about pipeline as a flow, not a stock. A pipeline snapshot tells you what exists at a point in time. Velocity tells you how productively that pipeline is moving. Two businesses with identical pipeline volumes can have dramatically different revenue trajectories depending on how quickly deals progress.

I spent a period working with a client whose pipeline had been largely static in volume terms for three quarters. The headline number was not growing, which made leadership nervous. But when we looked at velocity, it had actually improved significantly. Deals were moving faster, win rates were up, and the average deal value had increased. The pipeline was not growing because deals were closing more efficiently, not because the business was struggling. Volume was the wrong metric to be watching.

Velocity also surfaces problems that volume hides. If your pipeline volume is growing but velocity is slowing, that is a warning sign. It typically means deals are entering the pipeline faster than they are progressing, which often points to qualification problems, resource constraints in the sales team, or deals that are being held open long past their natural close date.

The Marketing-Sales Gap in Pipeline Interpretation

Marketing and sales teams often look at the same pipeline data and reach entirely different conclusions. This is not a communication failure. It is a structural problem rooted in how each function defines success.

Marketing typically owns the top of the funnel. The metrics that matter to marketing are lead volume, lead quality scores, cost per lead, and MQL-to-SQL conversion rates. Sales typically owns from SQL onwards. The metrics that matter to sales are qualified pipeline, win rates, average deal size, and quota attainment.

The gap between these two sets of metrics is where most forecast errors originate. Marketing can hit every MQL target and still generate a pipeline that sales cannot close, because the quality criteria used to define an MQL do not match the reality of what converts into revenue. I have been in rooms where marketing was celebrating record lead numbers while sales was quietly noting that the leads were not converting. Both were right. Neither was looking at the same data.

The fix is not to merge the functions or to give one ownership over the other’s metrics. The fix is to agree on a shared definition of pipeline quality and to measure both functions against outcomes that are further down the funnel than either is currently comfortable with. Marketing needs to be accountable for pipeline quality, not just pipeline volume. Sales needs to be accountable for how they work the pipeline marketing creates, not just the deals they close from their own prospecting.

Forrester has written thoughtfully about the challenges of building models that both sides trust, and the pipeline interpretation problem is a good example of why shared models matter more than technically correct individual ones. A model that marketing trusts and sales ignores is not a functional model. It is a political document.

What Stage Distribution Tells You About Pipeline Health

If you map the distribution of deals across pipeline stages and plot it over time, you get one of the most honest pictures of pipeline health available. A healthy pipeline has a natural shape: more deals in early stages, progressively fewer as you move toward close. The exact shape varies by business, but the principle holds.

What you are looking for in stage distribution is unusual concentrations. A pipeline that is heavily weighted toward late stages might look exciting in the short term, but it signals a future problem. If you are not continuously replenishing early-stage pipeline, you will hit a cliff. I have seen this happen in agencies when a large pitch cycle consumes the whole team’s attention. Deals close, revenue comes in, and then there is nothing behind them because nobody was building pipeline during the pitch.

Equally, a pipeline that is heavily weighted toward early stages, with very little in late stages, suggests a conversion problem. Deals are entering but not progressing. This could be a qualification issue, a sales capability issue, or a product-market fit issue. Stage distribution does not tell you which, but it tells you where to look.

The other thing to watch in stage distribution is deal age. A deal that has been sitting in the same stage for twice the average sales cycle length is not a pipeline asset. It is a liability. It occupies mental bandwidth, distorts your coverage ratio, and creates false confidence in your forecast. I have a rule of thumb from years of reviewing pipelines: if a deal has not moved in 90 days and the next step is not clearly defined, it should be moved to a separate category or removed entirely. Clean pipeline is more useful than large pipeline.

Benchmarking Pipeline Metrics Against Something That Matters

One of the most common mistakes I see in pipeline analysis is benchmarking exclusively against prior periods. Quarter-on-quarter comparisons are useful for spotting trends, but they tell you nothing about whether your performance is actually good relative to the opportunity available.

If your market is contracting and your pipeline is flat, you are outperforming. If your market is growing at 30% and your pipeline is growing at 15%, you are losing ground, regardless of how the internal trend line looks. The number that matters is not the absolute value of your pipeline. It is your pipeline as a proportion of the addressable opportunity.

This is harder to measure than it sounds, because market size data is often imprecise and competitor pipeline data is unavailable. But the discipline of asking the question is valuable even when the answer is approximate. BCG’s work on developing new metrics to measure competitive efficiency makes the same underlying point: the metrics you choose shape the conclusions you reach, and internal metrics alone create a closed loop that can mask external weakness.

Proxy benchmarks help here. Win rates against named competitors. Average deal sizes relative to market average contract values. Sales cycle lengths compared to industry norms. None of these are perfect, but they provide an external reference point that internal metrics cannot.

When I was at iProspect, growing the team from around 20 people to over 100, one of the things that kept us honest was tracking our new business win rate against the broader agency market. We were not just asking whether we were winning more than last year. We were asking whether we were winning more than we should be, given the size and quality of the opportunities we were pitching. That framing changes the conversation considerably.

The CRM Data Problem Nobody Wants to Talk About

Pipeline metrics are only as reliable as the data behind them, and CRM data quality is one of the most consistently underestimated problems in B2B commercial operations. The issue is not that CRM systems are bad. The issue is that CRM data reflects human behaviour, and humans in sales teams are not primarily motivated by data hygiene.

I have reviewed pipelines where deal values had not been updated in months, where stage progression had been recorded based on activity rather than buyer signals, and where close dates had been rolled forward quarter after quarter with no substantive change in deal status. The pipeline looked substantial. The underlying data was largely fiction.

This is not a technology problem or a training problem. It is a leadership and incentive problem. If sales managers review pipeline by asking “what is the total value?” rather than “what has moved since last week and why?”, the team learns that data accuracy is not what gets rewarded. The pipeline becomes a reporting artefact rather than a management tool.

The practical fix requires two things. First, pipeline reviews need to be structured around movement and evidence, not volume. Second, the definition of what constitutes a valid pipeline entry needs to be specific enough that it cannot be gamed. A deal is not in pipeline because someone had a conversation. It is in pipeline because a specific next step has been agreed with the buyer, a timeline has been established, and a decision-making process has been confirmed.

That level of rigour feels uncomfortable at first, particularly in teams that have been rewarded for building large pipelines. But it produces forecasts that are actually useful, which is the whole point of tracking pipeline metrics in the first place.

The broader alignment work that supports pipeline discipline, including how marketing and sales define shared standards and accountability, is covered across the Sales Enablement and Alignment hub. Pipeline data quality is in the end a function of how well the two teams have agreed on what pipeline actually means.

Reading Pipeline Metrics as a System, Not a Scorecard

The shift I would encourage any commercial leader to make is from reading pipeline metrics as a scorecard to reading them as a system. A scorecard tells you whether you hit a number. A system tells you why, and what is likely to happen next.

When you read pipeline as a system, you are looking for the relationships between metrics rather than the metrics themselves. Volume is rising but velocity is falling: something is entering the pipeline that should not be there, or deals are getting stuck. Win rate is improving but average deal value is declining: you are getting better at closing smaller deals, possibly at the expense of larger ones. Stage conversion is strong in early stages but drops sharply at proposal: your qualification is good but your commercial proposition is not landing.

Each of these patterns tells a different story and points to a different intervention. None of them are visible if you are looking at a single metric in isolation.

The other thing that reading pipeline as a system requires is a willingness to act on what you find, even when the finding is uncomfortable. I have sat in forecast reviews where the data was clearly signalling a problem and the response was to adjust the assumptions rather than address the underlying issue. That is not analysis. That is wishful thinking with a spreadsheet attached.

Pipeline metrics are most valuable when they are used to make decisions: to reallocate sales resource, to revisit qualification criteria, to challenge a pricing model, to invest more in a particular segment or pull back from one that is not converting. If your pipeline reviews end with everyone feeling informed but nothing changing, the metrics are decorative rather than functional.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions