Sales pipeline metrics: 8 numbers that predict revenue
The eight sales pipeline metrics worth tracking — coverage, win rate, velocity, stage conversion, cycle length, deal size, slippage, and follow-up latency — with formulas.
Pipeline metrics exist to answer three questions: is there enough pipeline, is it healthy, and is it actually being worked? Most dashboards answer the first question and stop. The eight metrics below cover all three — what each one tells you, how to compute it, and the trap each one sets for the unwary.
1. Pipeline coverage
Qualified pipeline value ÷ quota for the period. The classic rule of thumb is 3x, but your real target is 1 ÷ win rate — a team that wins a quarter of its deals needs 4x. The trap: coverage is only as honest as the qualification underneath it. Padded pipeline produces beautiful coverage and missed quarters, which is why honest disqualification is a core practice, not housekeeping.
2. Win rate
Deals won ÷ deals that reached a decision. Measure it from qualification onward, not from first touch, or prospecting noise will swamp the signal. Watch it by segment and by loss reason — a falling win rate against one competitor or in one segment is actionable; a blended number is just weather.
3. Average deal size
Revenue won ÷ deals won. Most useful as a trend and as a denominator in velocity. The trap is letting one outlier swing the average — track the median alongside it if your deal sizes vary widely.
4. Sales cycle length
Average days from qualification to close. The metric that most directly reflects how much dead time lives in your process. Split it by stage to find where deals sit still — the diagnosis that drives shortening the cycle. Watch won and lost cycles separately: lost deals that drag on for months are a qualification problem wearing a cycle-length costume.
5. Stage-to-stage conversion
Deals advancing from each stage ÷ deals that entered it. This is the bottleneck-finder: the stage with the worst conversion is where your process leaks, and improving it lifts the whole funnel. It only works when stages have buyer-defined exit criteria — vague stages produce vague conversion data, which is why this metric and process optimization are two halves of one practice.
6. Pipeline velocity
(Qualified opportunities × win rate × average deal size) ÷ cycle length in days. Revenue per day, in one number — and more usefully, a model of your four levers. Most teams instinctively pull the first lever (more pipeline) when the cheapest gains are usually in the denominator: the same deals, won at the same rate, closing three weeks sooner.
7. Slipped-deal rate
Deals that pushed past their expected close date ÷ deals due in the period. The forecast-honesty metric. Chronic slippage almost always traces to one of two roots: close dates set by hope rather than by a buyer-confirmed event, or deals that quietly stopped being worked. Both are fixable; neither shows up in coverage or win rate until much later.
8. Follow-up latency
Time between buyer activity and your response — and between any two consecutive touches on a live deal. The leading indicator everything else lags. Deals stall in the gaps between touches; this metric measures the gaps directly. It is also the number a team can actually move this week, and when it drops, cycle length and stage conversion follow within a quarter. The fastest way to move it is structural rather than motivational: a system where every live deal always has its next touch drafted and queued. That is the job Ember does — reading every thread, noticing the moment a deal needs attention, and presenting the follow-up in your voice for approval — and it is also what keeps the record underneath all eight of these metrics current without anyone typing, since activity logs itself as it happens.
Reading them together
No single metric survives being targeted in isolation — coverage can be padded, win rate can be gamed by sandbagging, cycle length by disqualifying slow deals. Read them as a system: coverage and velocity for "enough," win rate, deal size, and conversion for "healthy," slippage and latency for "worked." Review the trio weekly at the deal level, as part of the rhythm described in improving sales team performance, and the dashboard stops being theater and starts being a steering wheel.
Frequently asked
- What are the most important sales pipeline metrics?
- Pipeline coverage, win rate, average deal size, sales cycle length, stage-to-stage conversion rates, pipeline velocity, slipped-deal rate, and follow-up latency. Together they answer the three questions that matter: is there enough pipeline, is it healthy, and is it actually being worked?
- How is pipeline velocity calculated?
- Pipeline velocity = (number of qualified opportunities × win rate × average deal size) ÷ sales cycle length in days. It expresses how much revenue your pipeline produces per day and shows which of the four levers most improves it.
- What is a good pipeline coverage ratio?
- The common rule of thumb is 3x — three dollars of qualified pipeline for every dollar of quota — but the right number depends on your actual win rate. Coverage only means anything if the pipeline underneath it is honestly qualified; padded pipeline inflates coverage while predicting nothing.
- Why track follow-up latency?
- Because it is the leading indicator the others lag. Deals stall in the gaps between touches, and follow-up latency measures those gaps directly. When it drops, cycle length and stage conversion typically improve within a quarter — it is the earliest signal that the pipeline is being worked well.
More guides
Better numbers come from better follow-through.
Ember keeps every deal moving and every record current — so your pipeline metrics reflect a pipeline that is actually being worked.