Sales metrics that predict revenue

Why activity metrics keep rising while pipeline does not

Activity is the part of sales a team controls completely. Nobody outside the company has to agree to an email being sent. That makes activity easy to report, easy to improve on demand, and almost useless as a prediction.

It also creates a specific failure. When a dashboard leads with volume, the fastest way to look like it is working is to do more of the same thing, and a team that reclaims time through better tooling will spend it sending more of a message that was not landing. Doubling the volume of something with no product-market fit produces twice the silence, on a slightly better chart.

This is the same distinction that decides whether AI tooling pays for itself. The tasks it compresses are the visible ones, so the gain appears in activity immediately and in pipeline much later, if at all. That argument is set out in full in best AI BDR software.

One test for whether a metric is worth a dashboard

Ask whether the number can improve without a single person outside the company changing their behaviour.

Emails sent, calls logged, accounts researched, sequences launched and CRM fields completed all pass that test, which is to say they all fail as predictors. Replies, meetings held, opportunities created and deals advanced all require someone outside to act, which is what makes them informative.

Activity metrics still have a use: they diagnose a capacity or discipline problem when output has already fallen. They are inputs to an investigation, not outputs of a business.

The four that carry predictive weight

• Conversion rate between consecutive stages. The single most diagnostic number in a pipeline, because it localises the problem. An overall close rate averages a healthy stage and a broken one into a figure that describes neither.
• SQL to close rate. The real test of qualification. If it falls while SQL volume rises, the definition of qualified has quietly loosened, and the forecast is already wrong.
• Pipeline velocity. Catches deterioration that a close rate hides, because deals slowing down precedes deals being lost by an entire cycle.
• Conversion by lead source. The only way to tell an expensive source from a bad one. A source with a high cost per lead and a high qualification rate can be the cheapest pipeline you buy.

Notice what is missing. MQL count is not on the list, because it is a measure of marketing throughput rather than of sales outcome, and it is the number most vulnerable to being inflated by a definition change nobody announced.

Pipeline velocity, and why it warns earliest

Velocity combines four things a close rate reports one at a time: how many opportunities exist, what proportion close, what they are worth, and how long they take.

Its value is the denominator. Cycle length moves before win rate does, because a deal that is going to be lost usually stalls first. A team watching only win rate learns about a problem one full cycle after a team watching velocity.

Two cautions. Calculate it per segment, because one large slow enterprise deal and thirty fast small ones average into a number that matches nothing you sell. And treat a rise driven purely by shorter cycles with suspicion, since the fastest way to shorten a cycle is to lose deals sooner.

Rep level spread tells you whether it is the system or the person

Report conversion by rep as a spread, not an average. The shape of the distribution answers a question the mean cannot.

When every rep converts within a narrow band and the band is low, the problem is the system: the list, the message, the qualification standard, the handoff. Coaching individuals against a shared constraint is effort spent on the wrong layer.

When one or two sit far below an otherwise healthy group, the problem is individual, and it belongs in the process described in the five lever SDR diagnostic rather than in a process redesign that disrupts the people already performing.

This distinction is what makes scale survivable. Growing a team from 10 reps to 23 only holds output per rep if the constraint was never the individual in the first place, which is the argument in scaling an SDR team.

What to look at daily, weekly and monthly

Frequency should match how fast a number can genuinely move. Reviewing a monthly metric weekly produces noise, and reacting to noise is how teams change direction four times a quarter.

• Daily, and only for the team running it: new meetings booked, replies needing an answer, and inbound leads still unworked. All of these decay within hours.
• Weekly: conversion between the two stages you are currently trying to fix, split by rep and source, plus the count of deals older than two cycles.
• Monthly: pipeline velocity by segment, SQL to close rate, and cost per opportunity by source. These need a month of volume before the movement means anything.

A common mistake is reporting all three at the same cadence in one dashboard, which trains everyone to ignore the whole thing.

Related reading

To locate a specific problem rather than monitor for one, see how to audit a sales pipeline in 72 hours. For the rep level version of the same question, see the five lever SDR diagnostic.

The reporting and dashboard work itself is described on GTM analytics and sales reporting.