GTM Engineering
Momentum Over Volume
Start with a question the pipeline total cannot answer
A larger pipeline does not tell you how much of it is likely to close, at what value, or how long that might take. Pipeline velocity brings those questions into one calculation. Use it to compare assumptions and decide where to investigate.
The useful question is not simply “How do we add more opportunities?” It is “Which part of this sales process deserves attention, and what evidence supports changing it?”
Calculate one consistent baseline
Pipeline velocity = qualified open opportunities × win rate × average deal value ÷ sales cycle days.
Choose a defined segment, such as one product and customer size. Record the snapshot date for open opportunities and the historical period used for the other inputs. Keep the currency and deal-value basis consistent.
Qualified open opportunities: count opportunities that meet your documented qualification rule and remain open on the snapshot date.
Win rate: divide wins by wins plus losses for the stated historical period and segment. Record the inclusion rules; open opportunities do not belong in this denominator.
Average deal value: use the mean closed-won value for that segment and period. State whether the value is annual contract value or another measure. If you exclude outliers, document the rule and apply it consistently.
Sales cycle days: use the median elapsed days from qualification to close for the stated historical population. Record whether that population includes wins, losses, or both, and use the same definition in comparisons.
Illustrative example: 48 qualified open opportunities, a 24% historical win rate, $11,000 average deal value, and a 58-day median sales cycle.
48 × 0.24 × $11,000 ÷ 58 = $2,184.83/day.
This is an illustrative pipeline flow estimate under those assumptions. It combines current pipeline with historical averages, so changes in the mix or maturity of opportunities can make the estimate less representative. It is not booked revenue, recognized revenue, or collected cash. Multiplying it by 30 does not establish a monthly revenue forecast.
Change one input at a time
Keep the baseline fixed while comparing scenarios. Each example below changes only the named input; the other three remain unchanged. The scenarios are independent, not a sequence of improvements.
Win rate: 24% to 27% produces $2,457.93/day, a 12.50% increase in the model.
Sales cycle: 58 to 52 days produces $2,436.92/day, an 11.54% increase in the model.
Average deal value: $11,000 to $12,000 produces $2,383.45/day, a 9.09% increase in the model.
Qualified open opportunities: 48 to 52 produces $2,366.90/day, an 8.33% increase in the model.
These numbers show arithmetic sensitivity. They do not prove that a particular intervention will improve win rate or shorten the cycle. They also say nothing about implementation cost, capacity, or return on investment.
The largest percentage in this list is not automatically the best decision. The scenarios use different-sized changes. Compare plausible changes and their costs, then look for evidence that your team can influence the relevant input.
Inspect the process behind the number
Start with stage entry and exit dates, aging opportunities, recorded next steps, and the people responsible for those steps. A slow stage can be a useful place to investigate, but its age alone does not establish why deals are delayed.
For example, if opportunities spend a long time in commercial review, inspect the actual handoffs and missing information before choosing a change. Write down the problem you observed, the proposed change, its owner, and the evidence that would support or challenge the hypothesis.