Sales KPI examples. The ones worth putting on a live dashboard.

Why this matters. A list is not a dashboard strategy.

Search for sales KPI examples and most results hand you a list of thirty metrics with a one-line definition each, which is not actually useful. The real question isn't which KPIs exist, it's which ones earn a place on a dashboard someone actually looks at every week. This guide groups the examples that matter into five categories, with how to apply each one and where teams typically get it wrong.

This sits alongside our work on sales reporting and dashboards and the discipline of sales pipeline management more broadly. The metrics below are the raw material; a working dashboard is what turns them into something a founder or sales lead can act on in a five-minute Monday review rather than a spreadsheet nobody opens.

The list, with how to apply each. Five categories, ten examples.

Pipeline health

Pipeline coverage ratio. Total open pipeline value divided by the remaining revenue target for the period. Most B2B teams I work with aim for a ratio between three and four times target, since not every open deal closes and the ratio has to absorb that attrition. Calculate it weekly, not monthly, so a shortfall shows up while there's still time to build more pipeline.

Pipeline velocity. Number of qualified opportunities, multiplied by average deal value, multiplied by win rate, divided by average sales cycle length. It's a single number that captures how fast revenue is actually moving through the funnel, and it's more useful for spotting a slowdown than any one input metric on its own, because it shows whether a drop in one area is being offset elsewhere.

Conversion

Lead-to-opportunity conversion rate. The share of qualified leads that become a real, worked opportunity. Track it by source, since a channel with high lead volume but low conversion is usually generating noise, not pipeline, and that distinction changes where marketing spend should go.

Win rate. The Ebsta and Pavilion 2025 GTM Benchmarks Report, based on an analysis of hundreds of thousands of B2B opportunities, found the average new-logo win rate fell to 19 percent in 2025, down from 29 percent the year before. Track win rate by deal size and by stage separately, not as one blended figure, because a blended number hides whether deals are being lost early on fit or late on price.

Activity and response

Lead response time. The gap between a lead's first inbound action and the first human reply. A landmark 2011 Harvard Business Review study by Oldroyd, McElheran and Elkington, auditing 2,241 US firms, found the average firm took 42 hours to respond to a new lead, a figure that hasn't meaningfully improved at most companies since. This is one of the few sales KPI examples where the target is genuinely simple: minutes, not hours.

Meetings booked per rep per week. A leading indicator, not a target in itself. Its value comes from pairing it with conversion rate: a rep booking plenty of meetings that rarely convert has a qualification problem, not an activity problem, and the two require completely different coaching.

Revenue

Average deal size. Track it by segment or product line rather than as one company-wide average, since blending a large enterprise deal in with several small self-serve ones produces a number that describes neither well.

Quota attainment distribution, not just the average. The Ebsta and Pavilion 2025 report found just 14 percent of sellers now drive 80 percent of revenue, an elevenfold gap between top and bottom quartile performers. Looking only at average attainment across a team hides that spread entirely, and it's the spread that usually points to where coaching or hiring needs attention.

Efficiency

Sales cycle length by segment. The same Ebsta and Pavilion dataset found opportunities that closed within 50 days converted at a 47 percent win rate, against 20 percent or lower once a deal stretched beyond that window. Cycle length isn't just a speed metric, it's a leading indicator of a deal's health.

CAC payback period. How many months of gross margin from a new customer it takes to recover what was spent acquiring them. It's the metric that connects sales performance back to whether the business model actually works at the growth rate being chased, which makes it worth a place on a founder's dashboard even if it rarely appears on a rep's.

Where teams go wrong. The mistakes that make a KPI list useless.

The first mistake is tracking everything at once. A dashboard with fifteen metrics gets reviewed thoroughly exactly once, in the week it's built, and glanced at or ignored every week after. Pick four to six, tied to the team's current stage, and add more only once those are genuinely being used to make decisions.

A related version of the same mistake is picking metrics that look impressive in a board deck rather than ones that change a manager's actual behaviour week to week. A metric worth keeping on a live dashboard should pass a simple test: if the number moves in the wrong direction, is there a specific action someone takes in response, or does it just get noted and forgotten. If nobody can answer that question for a metric, it belongs in a monthly report, not a weekly dashboard.

The second is treating activity metrics as targets rather than diagnostics. Call counts and emails sent are useful for working out why a rep is missing their number, an activity problem versus a conversion problem, but rewarding activity directly encourages low-quality volume over real progress.

The third is leaving every metric without a named owner or a review cadence. A number nobody is accountable for reviewing drifts into background noise within a month, whatever it's measuring. For a narrower, process-focused look at the handful of metrics that diagnose whether the sales machinery itself is healthy, rather than this broader set of examples, see our guide to sales operations metrics that matter.

The fourth is confusing a leading indicator with a lagging one, and coaching against the wrong one. Our guide to leading versus lagging indicators covers this distinction in full, but the short version here is that revenue tells you what already happened, while pipeline created and response time tell you what's about to happen, and it's the second group that a weekly team meeting should actually be built around.