Sales rep productivity metrics: what to track and how to read them

What sales rep productivity metrics measure

Productivity is output divided by input. For a sales rep, the input is time and the output is revenue, so a rep's productivity is the revenue produced per unit of working time. Sales rep productivity metrics are the numbers that let you see that ratio and the machinery inside it: how many hours a rep spends selling, what those hours produce in conversations and proposals, and what the proposals turn into.

That makes them a specific slice of the broader family of sales performance metrics. Performance metrics judge the whole operation. Productivity metrics assess the trade-off between one person's time and money, which is why they matter so much on a small team. When you employ two salespeople, or when the main salesperson is you, there is no averaging to hide behind. Every unproductive hour belongs to someone with a name.

One distinction saves a lot of confusion later: activity counts are inputs. A rep who logs 300 calls has spent effort, and the effort may or may not have produced anything. Counting the calls tells you the engine is running. Productivity metrics tell you whether the car is moving.

Start with selling time

The first number to establish is how much selling time there is, because every other metric is divided by it. Salesforce's 2026 State of Sales research found reps spending 60% of their time on work that is not selling: CRM updates, internal meetings, hunting for information, and assembling quotes. On an eight-hour day, that leaves barely three hours of actual selling, and most owners I have compared notes with guessed their own number far too high.

Measure it once with a one-week audit. Have each rep, yourself included, tally hours spent talking with prospects and customers or writing directly to them. Everything else lands in the other bucket. No stopwatch and no software, just an honest calendar review on Friday. Repeat it quarterly.

The split matters because it is usually the cheapest thing to fix. Raising a win rate takes coaching and time. Giving a rep back five admin hours a week takes a template, an automation, or a decision to stop requiring a report nobody reads. The payroll stays the same while the sales grow.

Sales activity metrics and their limits

Sales activity metrics count effort: calls made, emails sent, meetings booked, demos or site visits delivered, proposals out the door, and new opportunities opened. They are the easiest numbers to collect and the first to move when something changes, which makes them useful as early warning signs. A quiet activity week shows up in revenue one full sales cycle later, by which point the cause is weeks old and hard to remember.

The question owners ask most is how many calls a rep should make in a day, and published dial counts are a poor answer because they describe somebody else's business. Derive yours instead. Suppose you need four wins a month, you win about 40% of proposals, 60% of first meetings lead to a proposal, and 15% of real conversations lead to a meeting. That works back to 10 proposals, 17 meetings, and roughly 110 conversations a month, call it five a day. Now the daily target is arithmetic from your own funnel, and when a rep hits it, you know the inputs are there.

Two limits. Activity counts measure motion, and motion can point at the wrong prospects all month. And the moment activity numbers decide pay or standing, they get manufactured: calls get shorter, and contacts get logged twice. Keep them as a floor, and read them only next to the ratios below.

Conversion ratios, where activity becomes progress

Between activity and revenue sit the ratios that show what each rep's effort converts into. Four cover most small teams: conversations to meetings, meetings to proposals, proposals to wins, and the speed of the first reply to a new inquiry. Response speed has the strongest evidence behind it of any input in sales; we cover the research in our guide to sales pipeline metrics, which handles win rate, velocity, and coverage at the pipeline level.

Ratios are diagnostic in a way that totals never are. Each rep tends to have one leak. Plenty of conversations and few meetings usually mean the wrong list or a weak opening. Plenty of meetings and a few proposal points at discovery, or chasing buyers who were never going to buy. Plenty of proposals and few winning points at pricing, the proposal itself, or follow-up.

That last leak is bigger than it looks. Matt Dixon and Ted McKenna analyzed 2.5 million recorded sales conversations for their book The JOLT Effect and found that 40% to 60% of qualified pipeline is lost to no decision at all: the buyer simply never chooses, as they wrote in Harvard Business Review in 2022. For a rep, every hour spent on a buyer who will never decide is an hour of selling time producing nothing. Qualifying for intent, asking early whether a decision is coming this quarter at all, protects the scarcest input a rep has.

Output metrics: revenue per sales rep and quota attainment

Output metrics are the totals that the previous numbers exist to explain. Revenue per sales rep is the plainest one: revenue closed in the period, divided by the number of people carrying a number, tracked per quarter. Count the owner's own book as its own line if you sell too, because mixing it into a rep's total flatters everyone and informs no one.

Quota attainment is the percentage of the target a rep closed, and at the team level, the share of reps who reached 100% of their targets. For SaaS companies, SaaStr's Jason Lemkin treats 70% to 80% of reps hitting quota as healthy and anything under half as a structural alarm, with revenue per rep landing between $500,000 and $1 million a year at scale. Those figures come from venture-backed software, so treat them as an orientation, and treat attainment on a small team as a reading on the quota as much as the rep does. When one rep misses, coach the rep. When everyone misses, the number was fiction, and quiet sandbagging follows if it stays fiction.

Deals closed per month and average deal size per rep round out the set. Deal size drifting down usually means discounting, and one rep discounting harder than the rest is worth a conversation about confidence in the price list.

How to measure sales productivity

The formula is short: sales productivity = output ÷ selling hours. Wins per 100 conversations if you want an efficiency read, revenue per selling hour if you want the truth in dollars. A rep who closed $38,400 on 64 selling hours produced $600 an hour. The point is comparison over time, so pick one version and keep the definition still.

If searching for sales productivity benchmarks brought you here, one caution from someone who reads them for a living: published numbers disagree because their definitions do. One vendor counts dials, another counts conversations; one divides by total hours, another by selling hours. Your own trailing 90-day share your market and your definitions, and beating it is the only comparison that pays.

The tracking itself stays light. Five numbers per rep per week: selling hours, conversations, meetings, proposals, and wins, with revenue attached. Fifteen minutes on a Friday. Which of these gets promoted to targets is a separate decision, and our guide to KPI meaning in sales covers how to choose without drowning the team in dashboards.

A worked example: two reps, one month

A two-rep team sells commercial cleaning contracts worth about $9,600 a year each. Both reps logged 64 hours of selling last month. Maya made 130 calls that became conversations, booked 13 meetings, sent eight proposals, and won two deals: $19,200, or $300 per selling hour. Dev had 90 conversations, 14 meetings, nine proposals, and four wins: $38,400, or $600 an hour.

On an activity dashboard, Maya is the hardest worker, 40 conversations ahead. On a productivity read, Dev turned conversations into meetings at 16% against Maya's 10%, and proposals into wins at 44% against her 25%. Effort explains none of that. The leak lies in who gets called and which deals earn proposals, so the fix is specific: Maya borrows Dev's list criteria and his habit of asking about budget in the first meeting, and drops the dial target that rewarded volume. Without the ratios, the obvious advice would have been to make more calls, which was the one thing that was already working.

That is the pattern worth stealing from this example: totals identify who is ahead, ratios identify why, and only the why is coachable.

Reading rep metrics without souring the team

Rep-level measurement fails socially before it fails mathematically, so a few rules keep it useful. Publish the definitions so nobody learns mid-review that a call only counts if someone answers. Let reps see their own numbers first, and review them together as a diagnosis. The metrics exist to identify friction, and the moment they become a leaderboard, people manage the counter rather than the customer.

Respect small samples too. When eight deals reach a decision in a month, one unlucky buyer moves that rep's win rate by 12 points, with nothing about the selling changed. Read counts weekly, ratios over a trailing quarter, and compare each rep to their own trailing average before comparing reps to each other. Territories and lead sources rarely deal even hands.

And keep paying off the activity counters. Compensate outcomes; use the input and ratio numbers for coaching. The counters stay honest only while nothing is riding on them.

How to improve the numbers, in order to

Improvement has a natural order, and it starts with subtraction. Give hours back before asking for more output: quote templates, auto-logged calls and emails, one shared record instead of three, fewer tools rather than more. The same Salesforce research finds that sellers juggle an average of 8 tools, and sellers who report being overwhelmed by their tools are 45% less likely to hit quota. An hour of admin removed is a selling hour gained, and it arrives without a single coaching session.

Then fix the leakiest ratio, one rep and one leak at a time. A month is a fair test, a week is noise. Only after the hours are back and the worst leak is patched does more activity make sense, because volume added to a leaky funnel mostly buys more leaks. New hires follow the same logic with one extra number: time to first deal, which tells you whether your onboarding teaches the job or just points at a desk.

Where the tracking should live

A spreadsheet can hold the five weekly numbers, and it works for a single rep. It starts lying at the ratios, because ratios need every call, meeting, and stage change recorded with a date, and hand-typed logs go stale the first busy week. This is the honest case for a CRM on a small team: the counting happens as a side effect of working.

Here is where we declare an interest: Bigin is our product, built for exactly this size of problem. It is a pipeline-first CRM where calls, emails, and meetings log against the deal as they happen, stage moves carry timestamps, and the dashboards chart activity and conversion per rep on their own. The free plan covers one user, one pipeline, and 500 records, and paid plans start at $7 per user per month, billed annually. Both numbers sit on our pricing page as of September 2026; pricing claims age quickly, so check ours the way you would check anyone's.

A quick summary

Sales rep productivity metrics track how a rep's hours are used. Establish selling time first, because 60% of the week is going elsewhere. Count activity as a floor, read the four conversion ratios as the diagnosis, and judge output by revenue per rep and quota attainment against your own trailing quarter, not somebody's benchmark deck. Measure the week, coach the leak, and subtract admin before demanding volume. If you want the numbers to assemble themselves while everyone sells, try Bigin free for 15 days, no card required.