How Many SDR Calls Do Your Managers Actually Hear?
Cale Owen, Co-founder & CEO · Reviewed by Samuel Esserman, Co-founder & CTO ·
TL;DR
- At public medians, one SDR leader manages 6.4 reps who hold about 131 quality conversations a week. That's before counting dials.
- The common advice is to review two calls per rep per week. That covers about 1 in 10 conversations and under 1% of phone activity.
- A 10% sample can tell you a problem exists. It can't reliably tell you which problem costs the most meetings. That takes every call, graded against one standard.
Your coverage = reviews per rep per week ÷ conversations per rep per week.
Most sales managers coach off the few calls they had time to hear. That isn't a knock on managers. It's arithmetic. This piece works through the arithmetic with public benchmarks, so you can run it on your own team in about two minutes.
If you already know your coverage is low and want to see what full coverage looks like, that's what AI call grading for SDR teams does: every call scored against your rubric, and every rep handed the one fix that books more meetings.
01. The short answer
How many calls should a sales manager review per rep? The most common advice is two calls per rep per week: one the rep picks and one the manager picks. Meetbook's call-review playbook recommends exactly that ("Not five. Not every call. Two.") [1].
That's a sound habit for a coaching conversation. The trouble is what it covers. Two calls a week is a coaching cadence, not a quality check. To see why, look at the volume a typical SDR leader is responsible for.
02. The coverage math
The Bridge Group's 2025 sales development report surveyed 351 B2B companies (median revenue $47M) [2]. Three of its medians are enough to size the gap:
| Input | Median | Source |
|---|---|---|
| SDRs per first-line leader | 6.4 | Bridge Group 2025 [2] |
| Quality conversations per SDR per day | 4.1 | Bridge Group 2025 [2] |
| Phone activities per SDR per day | 44 (of 112 total daily activities) | Bridge Group 2025 [2] |
Multiply across a five-day week:
- Quality conversations per team per week: 6.4 reps × 4.1 × 5 days ≈ 131
- Phone activities per team per week: 6.4 reps × 44 × 5 days ≈ 1,408
Phone-heavy teams run higher. The same report puts phone-centric teams at an average of 56 dials and 4.6 quality conversations a day, against the 4.1 median for all teams [2]. That's about 147 conversations and 1,792 dials a week for a 6.4-rep team.
Your mix will differ. The report skews B2B SaaS (83% of respondents). Inbound setter and front-desk teams can run very different volumes, so use your own numbers in section 07.
03. What two reviews per rep actually covers
| Reviews per rep per week | Calls reviewed per team | Share of quality conversations (≈131) | Share of phone activity (≈1,408) |
|---|---|---|---|
| 1 | 6.4 | ~4.9% | ~0.45% |
| 2 (common advice) | 12.8 | ~9.8% | ~0.9% |
| 3 | 19.2 | ~14.6% | ~1.4% |
Illustrative arithmetic on Bridge Group medians [2]. "Share of phone activity" counts every phone touch, including unanswered dials, so it understates coverage of connected calls. "Share of quality conversations" is the fairer comparison.
So even a disciplined manager who never misses a review session hears roughly one conversation in ten. And review time is often the first thing cut when schedules get compressed [1].
04. What review time costs
At Meetbook's suggested pace of about ten minutes per review [1], two reviews per rep is roughly two hours a week of session time for a 6.4-rep team (12.8 reviews × 10 minutes ≈ 128 minutes). That's affordable, which is why the advice is popular. It also buys about 10% coverage.
The cost climbs fast once a manager tries to hear more than that. Session time is only part of it: managers also have to find the right call, scrub to the moment that matters, take notes, and prep the 1:1. Compound's operating estimate, based on typical manager review hours, is 15 to 20 hours a week of manual review for a sales manager who is actually trying to keep up. Over a year, removing that work gives a manager back 750+ hours.
To put that in budget terms, here's an illustration using the Bridge Group's median SDR manager OTE of $146K [2]:
- $146,000 ÷ 2,080 working hours ≈ $70 an hour in OTE alone
- 15 to 20 hours a week ≈ $1,050 to $1,400 a week
- 750 hours a year ≈ $52,600 a year per manager
Illustrative. It's OTE only, before benefits, payroll tax, and overhead, so the fully loaded cost is higher. It also doesn't count the opportunity cost: those hours aren't going into coaching, hiring, or pipeline.
So most teams choose between cheap coverage that misses about nine conversations in ten and fuller manual coverage that eats a large share of a manager's week. Neither is a good trade.
05. Why a sample misses the leaks
A sample would be fine if the calls were chosen at random and each rep made the same mistake every time. Neither is true.
1. The sample isn't random, by design. The common advice is one call the rep chooses (often one they're proud of) and one the manager chooses (often a deal in the pipeline) [1]. Both are good coaching choices. Neither is a typical call. The everyday not-booked call, where meetings are actually lost, is the one least likely to get pulled.
2. Two calls can't rank problems. Suppose a rep has a habit that shows up in 30% of their calls. That's a hypothetical rate, used only to show the math. With two random calls a week, there's a 49% chance neither call shows it (0.7 × 0.7). Over a month of eight reviewed calls, you'd expect to see it two or three times, alongside several other issues that each show up once or twice. A handful of examples per rep can show you that a problem exists. It can't show you which problem costs the most meetings, and that's the question that tells a manager what to coach first.
3. Without one standard, every manager grades differently. Two managers listening to the same call can coach two different things. Meetbook makes the same point: without a written scorecard, "reviews devolve into opinions" [1]. Then "coverage" isn't even one standard. It's several people's opinions applied to a small slice.
The result: a recurring leak can cost meetings week after week without anyone being able to say which one it is. It looks like a lead problem or a headcount problem. Often it's a coverage problem.
06. How to close the gap
You don't close the gap by asking managers to listen harder. You close it by changing what they listen for and letting a system do the first pass.
Step 1: Write one rubric. Six to eight observable moments that decide whether a call books a meeting: the opener, the reason for the call, discovery, the response to an objection, the ask, and confirmation. Make every criterion observable ("proposed a specific time"), not a vibe ("sounded confident"). Have your managers grade the same 10 calls against it and argue until they agree.
Step 2: Grade every call against it. This is where AI call grading earns its place. Every recorded call is scored against the rubric, and each score is tied to the line in the transcript that earned it. Coverage of recorded calls goes from roughly 10% to 100%.
Step 3: Coach from a ranked list, not raw recordings. Each rep gets their single biggest fix for the week, ranked by how often it shows up on calls that didn't book. The manager's two review slots now go to the calls that show that fix. The cadence stays the same; the targeting gets much better.
Step 4: Check the same behavior next week. Coaching that isn't checked wears off. Because every call is graded, you can see whether the fix showed up across all of next week's calls, not just the next one you happened to hear.
The manager still does the coaching. The system's job is to tell them what to coach and give back the hours they were spending hunting for it.
07. Your coverage in three numbers
Run this for your own team:
- A = calls each manager reviews per rep per week
- B = conversations per rep per day (from your dialer or CRM, connected calls only)
- C = selling days per week
Coverage = A ÷ (B × C)
At the Bridge Group medians and two reviews per rep, that's 2 ÷ (4.1 × 5) ≈ 10%. If your number is around 10% or lower, a sample is unlikely to show you your team's biggest leak.
FAQ
How many calls should a sales manager review per rep each week?
The common advice is two calls per rep per week: one the rep chooses and one the manager chooses. That's a good coaching cadence. At public medians, though, it covers only about 1 in 10 of a team's quality conversations, so it works for coaching but not for finding which problem costs the most meetings.
What percentage of sales calls do managers actually review?
It depends on volume. At the Bridge Group's 2025 medians (6.4 SDRs per leader and 4.1 quality conversations per SDR per day), two reviews per rep per week covers about 10% of quality conversations and under 1% of phone activity. Teams with more conversations per rep get lower coverage from the same review habit.
How do you coach SDRs when you can't review every call?
Agree on one rubric, have every call graded against it (AI call grading makes that practical), and coach each rep on the single fix that costs them the most meetings. Use your manual review time on the calls that show that fix, then check whether it shows up in the following week's calls.
How long does manual sales call review take?
A focused review session runs about ten minutes per call, so two reviews per rep is roughly two hours a week for a 6.4-rep team. Keeping up with more than that takes far longer once you count finding calls, listening, taking notes, and preparing coaching. Compound's operating estimate for a sales manager trying to keep up is 15 to 20 hours a week, or 750 or more hours a year.
Is AI call grading the same as conversation intelligence?
Not quite. Conversation intelligence tools record, transcribe, and search calls. AI call grading scores each call against your team's own rubric and ranks what each rep should fix first. Many teams already have recordings. What they lack is a consistent standard applied to every call.
08. Find out what your calls are actually saying
Related:
If you own the P&L: what AI can do for margin without adding headcount →
Sources
- [1] David Rodriguez, "Sales Call Review: A Manager's 8-Week Playbook," Meetbook, Feb 24, 2026. https://meetbook.app/blog/sales-call-review-manager-playbook
- [2] The Bridge Group, SDR Models, Motions & Metrics: 2025 Research Report, published Feb 6, 2025. https://www.bridgegroupinc.com/research/2025-sdr-models-metrics-report-the-bridge-group
- Compound figures (15 to 20 hours a week of manual review; 750+ hours saved a year per manager): Compound operating estimate based on typical manager review hours, as stated on compoundoperators.com.