Revenue Velocity
How quickly the revenue engine converts demand into recognised revenue, across the whole lifecycle rather than within the pipeline alone.
Wider than pipeline velocity
Pipeline velocity stops at closed-won. Revenue velocity includes time to onboard and time to value, which is where subscription revenue is actually secured or lost.
Instrument the post-sale half
How to find the binding variable
Compute the components separately: opportunity volume, win rate, average deal value and cycle length. Velocity is their product and quotient, and only the components are actionable.
Change each by ten percent on paper and see which moves velocity most. That is your binding constraint, and it is frequently not the one being worked on.
Segment before optimising. The binding variable in enterprise is almost never the binding variable in a transactional motion.
Check cycle length by stage rather than end to end. A single stage is usually responsible for most of the elapsed time.
Re-run it quarterly. The binding variable moves as the business changes, and optimising last year's constraint is a common waste.
Where it misleads
Velocity can be raised by discounting, which shortens cycles and lowers deal value at the same time — the composite can improve while revenue quality falls.
It treats all four variables as independent when they are not: raising deal size usually lengthens the cycle.
It is a rate, so it says nothing about whether there is enough demand entering the system to sustain it.
At low deal counts the average deal value swings enough to make the whole figure noise.
RELATED TERMS
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.
Sales Cycle Length
The elapsed time from an opportunity's creation to its close. The time dimension underneath capacity planning and forecasting.
Average Deal Size
The mean value of closed-won opportunities over a period. An input to pipeline velocity and capacity planning.
Revenue Engine
The connected mechanism — people, process, systems and data — that converts demand into recognised revenue.
Win Rate
The proportion of opportunities that close won, measured against a defined denominator — which is where most of the disagreement lives.
Time-to-Value (TTV)
How long from purchase until a customer experiences the outcome they bought. The early metric that predicts retention.
COMMON QUESTIONS
- What is revenue velocity?
- A composite measure of how quickly the revenue engine converts demand into recognised revenue, usually computed from opportunity volume, win rate and average deal value divided by cycle length. Its value is in decomposition: the composite tells you little, and the four components tell you where to act.
- How do you improve revenue velocity?
- Find the binding variable first. Change each component by ten percent on paper and see which moves the result most — it is frequently not the one being worked on. Then work that one, because effort spent on a non-binding variable produces a rounding error.
- Is faster always better?
- No. Velocity can be raised by discounting, which shortens the cycle and shrinks deal value simultaneously, so the composite improves while revenue quality falls. Read velocity alongside realised price and win rate before treating an increase as an improvement.
- How is it different from pipeline velocity?
- The terms are used almost interchangeably and the formulas usually match. Where they differ, pipeline velocity tends to be scoped to opportunities already created, while revenue velocity is sometimes drawn wider to include demand generation. Define which you mean before comparing two figures.
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