Six Pipeline Metrics, and the Companion Each One Needs

A pipeline dashboard with twenty metrics on it is a dashboard nobody reads. The number that gets quoted in the review is whichever one moved most, and the number that would have explained the quarter is on the third screen, because it never moves much and nobody put it near the top.

Pipeline metrics are worth a small number of well-chosen figures held together, because each of them is ambiguous alone and most of them become clear in pairs. This page covers the six that carry the load, the pairings that make them readable, and the two ways every one of them can be gamed without anybody lying.

The six that carry the load

Volume and valueHow much is in there

• Open pipeline value: total value of open opportunities in the period
• Pipeline coverage: that value divided by the target
• Pipeline created: new value entering per period, which is the leading indicator

MovementWhether it is going anywhere

• Stage conversion: share of deals entering a stage that reach the next one
• Sales cycle length: median days from entry to closed won
• Win rate: share of qualified opportunities that close won

Notice what is not on that list. Number of opportunities is on almost every default dashboard and tells you very little without value and stage attached. Activity counts belong in activity reporting rather than in pipeline reporting, because a rep can complete every activity without the buyer doing anything at all.

Pipeline created is the one most often missing and the one worth adding first. Open pipeline value is a standing balance and moves slowly, so it disguises a collapse in new business for a full cycle. New value entering per period does not.

The reason a standing balance hides so much is worth being precise about. Open pipeline value falls when deals close and rises when deals are created, and in a period where both happen at similar rates the total barely moves. A team that stopped generating new opportunities six weeks ago and is still closing the ones it had will show a stable pipeline value and a stable coverage ratio for most of a cycle, and the first visible symptom will be a quarter with nothing left to close. Created value has already fallen off a cliff by then, and it fell in the week the problem started.

Segment the six wherever the sales motions genuinely differ. Enterprise and mid-market deals convert at different rates and run at different lengths, so a single blended figure for either conversion or cycle length is guaranteed to be wrong for at least one of them, and usually flattering to the segment doing worse. Splitting is the cheapest improvement most teams can make to their reporting, and it costs one grouping field.

The pairings that make them readable

Almost every pipeline metric is ambiguous on its own and settles when held next to one other figure.

Coverage next to win rate. The famous three-to-one rule of thumb is really a statement about winning roughly a third of what you carry. A team converting one in five needs about five to one, and at three to one it is short while the multiple looks completely normal in the review. The reciprocal relationship, and the reasons both inputs are softer than they look, are worked through in pipeline coverage.

Cycle length next to close dates. If your median cycle is four months, every deal created inside the last eight weeks with a close date in this quarter is a forecasting problem sitting inside a pipeline metric. Comparing accepted close dates against your own measured cycle is a cheap audit almost nobody runs.

Stage conversion next to time in stage. A stage with good conversion and a long dwell time is a bottleneck that eventually resolves. A stage with poor conversion and a short dwell time is a filter working correctly. The same conversion figure means opposite things depending on the companion.

Win rate next to average deal size. Win rate rising while deal size falls usually means the team has drifted down-market, which is a strategy change nobody decided. The two together describe a motion; either alone describes a mood.

Time in stage is the diagnostic

If a team can only add one thing to its reporting, it should be age rather than count.

Count tells you volume. Age tells you where the process breaks. The specific comparison that carries the information is the current median age of deals in a stage against the median age at which deals historically converted out of it. When the first is materially larger than the second, that stage is holding deals which are not going to progress, and the standing count will not show it.

41 dealsCurrently in Proposal

The count a default dashboard reports

12 daysMedian age when converted

From closed-won history

37 daysMedian age of the current 41

Three times the converting age

9 dealsUnder 12 days old

The part of the stage that is actually live

In that invented example the stage reports forty-one deals and contains nine that resemble deals which have historically closed. A forecast built on the forty-one is not slightly optimistic; it is describing a different population.

The two ways every one of these gets gamed

Neither requires anybody to lie, which is what makes them durable.

Definition drift. The metrics are all built on the boundary where an opportunity enters the pipeline. Tighten that boundary and win rate rises, coverage falls, and conversion from meeting to opportunity falls while conversion from opportunity to won rises. Loosen it and every one of those reverses. A dashboard showing all four will look like a team that suddenly got better at closing and worse at generating demand, and the only thing that happened was an edit to a definition document. The defence is a dated definition with readable version history, so the question of whether the population changed or the ruler did has an answer.

Deferred honesty. Nothing in a CRM closes a dead deal. Pushing a close date is invisible and closing one as lost is a visible act, so pipelines accumulate deals that inflate value and coverage while contributing nothing. The metric that catches it is the count of deals whose close date has moved more than twice, which almost no dashboard carries and which takes minutes to build.

Both of these are reasons to clean the pipeline on a fixed schedule that has nothing to do with when the numbers are being presented. A pipeline cleaned the week before a board meeting looks like a business that shrank.

Reading them for an outbound programme

Pipeline metrics are a lagging view of a targeting decision made a full sales cycle earlier, which changes what the honest response to a gap actually is.

If the cycle runs four months and the quarter has eight weeks left, conversations started today are next quarter's pipeline no matter how quickly they are booked. Treating outbound as an in-period repair produces rushed targeting and a set of opportunities that raise the ratio without ever closing, which makes the following quarter worse rather than better.

The two figures that connect outbound to the rest of this are meeting-to-opportunity conversion and the reason distribution for the meetings that do not convert. The first tells you whether the meetings are the right meetings. The second tells you what to change, and only if the reasons come from a fixed list, because free-text reasons cannot be counted. Where the reasons concentrate on seniority or company fit, the instruction is for the targeting; where they concentrate on timing, the instruction is usually for the segment rather than the campaign. What qualified has to mean when money depends on it covers how that definition gets settled in advance, and running discovery so it disqualifies well covers where the reasons get produced.

Our own commercial position is a narrow version of the same discipline. We are paid on attended meetings that meet criteria agreed in writing before launch, and budget, timing and authority are deliberately outside that definition, because they change every quarter and a meeting that happened should not become unqualified retrospectively. That also keeps the meeting-to-opportunity figure meaningful: it measures fit rather than the buyer's mood on the day.

Building the reporting without buying anything

None of this needs a dedicated analytics platform, and starting with one usually delays the work.

Five saved views cover most of it in any mainstream CRM. Open deals with no next step or an overdue one. Deals whose close date has moved more than twice. Deals whose close date is inside a window shorter than the median cycle. Age in current stage, grouped by stage. And created value by period, which is the leading indicator the standing balance hides.

The reason to build these before buying a tool is that each one will expose data-quality problems, and a platform bought before those are fixed will report the same problems more attractively. Where the numbers come from and who owns them is the design question underneath all five.

The short version

Six metrics carry most of the load: open pipeline value, coverage, pipeline created, stage conversion, cycle length and win rate. Each is ambiguous alone, so pair coverage with win rate, cycle length with close dates, stage conversion with time in stage, and win rate with average deal size.

Add age before adding anything else, and compare the current median age in a stage against the age at which deals historically converted out of it. Watch for the two silent distortions: a moved definition, which shifts four metrics in different directions at once, and unclosed dead deals, which inflate value and coverage indefinitely. Date every definition change on the chart it moves, and clean on a schedule divorced from the reporting calendar.

Where the metrics say the constraint is supply rather than execution, that is the half we run: see what a first campaign produces.