Sales KPIs: what to track, and how to calculate each one.

What are sales KPIs?

Sales KPIs are the specific, formula-backed numbers a sales team tracks to judge whether its process is working, as opposed to the broader set of sales metrics, which includes anything measurable regardless of whether it ties to a goal. Pipedrive draws that line directly in its own guidance: "Sales metrics track sales activities and performance data, while sales KPIs measure progress toward specific business or sales goals." The number of calls made is a metric. Win rate, tied to a target, is a KPI.

The four groups, and why grouping by measurement beats grouping by funnel stage

Most published lists sort KPIs by category label: "activity," "pipeline," "revenue," "customer." The labels vary by vendor and the same KPI often lands in two different categories on two different lists. A cleaner sort is by what the number is actually counting:

• Volume counts things: opportunities, pipeline value, leads.
• Conversion counts a ratio: how many of one thing became another.
• Speed counts time: days, hours, minutes.
• Value counts money: what a deal, a customer, or a rep is worth.

Every KPI in this post fits one of those four, and the formula for each group follows a predictable shape once you know which group you're in: volume is a sum, conversion is a fraction times 100, speed is a total divided by a count, and value is a dollar figure divided by a count or a rate.

Volume KPIs: how much is moving

Coverage ratio is worth a second look, because the single number most people quote for it, "3x," is not actually a constant. Salesloft states the real relationship as the inverse of your win rate: "Required Coverage = 1 ÷ Win Rate." At a 25% win rate that's 4x. At 50%, it's 2x. A flat 3x target only happens to be correct for a team whose win rate is close to a third, and applying it to a team with a lower win rate understates how much pipeline they actually need.

Conversion KPIs: how much of it turns into revenue

Read the first two rows again and notice they measure different things despite the similar names. HubSpot's win rate divides by opportunities. Pipedrive's lead conversion rate divides by leads. If your leads and your opportunities are not the same count, and they almost never are once a qualification step sits between them, the two percentages describe different parts of the funnel. Neither vendor is wrong. The mistake is comparing a number you calculated one way against a benchmark somebody else calculated the other way, and assuming they're the same measurement.

On quota attainment specifically, Salesforce's own published figure is a useful gut check before you set a target off a benchmark: "Only 24.3% of salespeople exceed their yearly quota." A quota-attainment dashboard where most reps sit below 100% most of the time is not automatically a sign the team is underperforming. It may be a sign the quota itself is calibrated the way most companies' quotas already are.

Speed KPIs: how long it takes

Two independent vendors publishing the identical formula for cycle length is a good sign it's genuinely a settled calculation, not a house convention. Response time deserves more room than a formula and a row: how a slow first reply drags on every downstream number, including cycle length itself, is its own post. Speed to lead covers it in depth.

Value KPIs: what it's worth

A worked example, with round numbers

Take a team of six reps in a single quarter. 90 qualified opportunities sit in the pipeline, valued at $2,700,000 total. Their quarterly team quota is $900,000. They close 27 deals for $540,000 in revenue, at an average sales cycle of 52 days.

Nothing in that table is a good or bad result on its own. What makes it useful is that all four numbers came out of the same CRM export, on the same day, from the same set of 27 closed deals and 90 open ones. That's the entire point of grouping the formulas this way: every number in a group is built from the same underlying records, so a single pull answers all of them at once.

Common mistakes when tracking sales KPIs

1. Comparing a KPI you calculated one way against a benchmark calculated the other way. HubSpot's win rate divides by opportunities. Pipedrive's lead conversion rate divides by leads. Publishing "our conversion rate is 30%" without saying which denominator you used invites a reader to compare it against the wrong published number.
2. Treating a metric as if it were a KPI. By Pipedrive's own distinction, "calls made" is a metric and "win rate" is a KPI because it ties to a goal. A dashboard full of metrics with no goal attached measures activity without measuring whether the activity is working.
3. Using a flat coverage multiple instead of the one your own win rate calls for. A "3x rule" is only correct at a win rate near 33%. Salesloft's formula, 1 ÷ win rate, gives a 20%-win-rate team a real target of 5x, not 3x.
4. Reporting quota attainment without segmenting it. A blended team average can sit near 80% while half the team clears 120% and the other half sits under 40%. The average hides exactly the split a manager needs to see.
5. Tracking every KPI on a published list instead of the ones tied to a decision this quarter. Pipedrive's own guidance is direct on this: "Tracking too many KPIs can make reporting harder and distract teams from the metrics that drive decision-making."

The KPIs your CRM cannot calculate on its own

Every formula above runs on fields a CRM already has: deal value, deal stage, close date, quota. A separate group of commonly listed KPIs, customer acquisition cost, lifetime value, LTV to CAC, and payback period among them, needs cost data that lives in ad accounts and payroll systems instead. No CRM will ever hold that data natively, and reporting one of these numbers without saying where the cost side came from is reporting a figure nobody can check. Revenue operations KPIs your CRM cannot calculate covers that group and what it actually takes to compute each one correctly.

FAQ

If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.