Pipeline Velocity

A composite of the four variables determining how fast pipeline converts to revenue: number of opportunities, average deal size, win rate, and sales cycle length.

The calculation

Qualified opportunities × average deal value × win rate ÷ average cycle length in days. The result is revenue per day, which is a strange unit to manage against and a useful one to decompose.

Its value is the decomposition

The headline figure is less informative than its parts. When velocity falls, exactly one of four things happened: fewer opportunities, smaller deals, a lower win rate, or a longer cycle. Each has a different cause and a different response, and the composite tells you which to investigate.

Reading a change in velocity
Input movedLikely causeWhere to look
Opportunity count downDemand or qualification changeCreation volume by source
Deal size downSegment mix shiftWon deals by segment
Win rate downCompetitive or qualificationLoss reasons, no-decision share
Cycle longerProcess or buying-committee changeTime in stage, stage where it grew

Source: Diagnostic framing stated here

Why it is a poor target

Each input is separately gameable, and two of them improve when performance worsens. Cycle length shortens if you abandon large complex deals; win rate rises if you disqualify aggressively. A velocity target can be met by pursuing less ambitious business.

Computing it defensibly

  1. Compute per segment and per motion. A blended figure averages populations with structurally different inputs.

  2. Use median cycle length rather than mean — a handful of very long deals distorts the mean badly.

  3. Hold the opportunity creation criterion constant, since it silently determines both the count and the win rate.

  4. Report the four inputs alongside the composite, always. The composite alone cannot be acted on.

RELATED TERMS

COMMON QUESTIONS

How do you calculate pipeline velocity?
Number of qualified opportunities multiplied by average deal value multiplied by win rate, divided by average sales cycle length in days. The output is revenue per day.
What is pipeline velocity used for?
Diagnosis. Its value is that it decomposes — when velocity falls you can see which of the four inputs moved, which is more actionable than the headline number.
Why is pipeline velocity a poor target?
Because it improves when you shorten cycles by pursuing only easy deals, or raise win rate by disqualifying aggressively. Each input is individually gameable, and the composite conceals which one moved.
Should velocity be calculated per segment?
Yes. Enterprise and self-serve motions have different cycle lengths and deal sizes, and a blended velocity describes neither. The segment view is the one that supports a decision.

Learn how to apply this: RevOps 101: Revenue Operations Foundations

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the course