How do I know if my SDR is the problem or the system is?

Check in order: list quality, dial volume and tooling, conversation skill, then the script. If wrong numbers and dead lines are common, or dials are capped by manual dialling, the system is the problem and no coaching will fix it.

How many dials should an SDR make per day?

40 to 60 with manual dialling, or 200 or more with a parallel dialer — roughly 1,000 dials a week for a dedicated caller. If volume is low, look at tooling before effort.

What is a good cold call connect rate?

Four to eight percent of dials reaching a human is typical in B2B. Below that, look at data quality and local presence numbers before questioning the caller.

Should I put an underperforming SDR on a PIP?

Only after the system is fixed. A performance plan on a broken list or manual dialling is a plan to fail. Fix what is upstream of the rep, give them two to four weeks on a clean system, then evaluate.

When is it actually the rep?

When connect rates are fine but conversations end in seconds, recordings show the opener being skipped, and the rep avoids the phone. The test is recordings after coaching, on a good list, with a working dialer.

How long before an SDR produces consistent results?

Three to four months of ramp before consistent output is normal. On a fixed system, first meetings land in week three and steady state around week six.

My SDR Is Not Performing: How to Diagnose It Before You Replace Them | BizDev Labs

1,000+dials / week per dedicated caller

200+dials / day on a parallel dialer

10–12qualified meetings / month

3–4months ramp before consistent output

A sales development rep missing quota is usually a system problem, not a person problem. Diagnose it in the right order: list quality, dial volume, conversation skill, then script.

Start here: check the system, not the person

If your SDR is not performing, check the system before you check the person. Wrong numbers, disconnected lines and people who left the company are a data problem no script or coaching can fix.

Diagnose in this order: list quality, then dial volume and tooling, then what happens in the conversation, then the script. Most managers debug in exactly the reverse order and conclude the rep is the problem.

In most underperforming SDR programs, the issue is upstream — data, process or tooling — not the rep. Fix the system first, then evaluate the person.

The 5 things to check (in order)

The list

Sample 50 dialled records and count wrong numbers, dead lines and gone contacts. If this is high, nothing downstream can be fixed.

Dial volume and tooling

Manual dialling caps at 40–60 dials a day. A parallel dialer with local presence produces 200+. Check the dialer, not the effort.

The conversation

Normal connects but no bookings is the one stage the rep truly controls — and you can only see it in recordings.

The script

Last, not first. Scripts get rewritten constantly and rarely fix a program. Look here only after the three steps above are healthy.

The job itself

Lists, copy, deliverability, LinkedIn and calling are five different skills. One person covering all five is quietly bad at three.

Benchmarks to know

Based on the calling benchmarks we publish and hold our own pods to.

MetricBenchmark

Connect rate, dials to a human4–8% is typical in B2B

Dials per day, manual dialling40 – 60

Dials per day, parallel dialer200 or more

Dials per week, dedicated caller1,000 or more

Qualified meetings per month, dedicated caller10 – 12 in B2B software

Ramp before consistent output3 – 4 months

Before you put them on a PIP

A performance improvement plan for a rep whose list is broken is a plan to fail. Before the PIP, run the five checks above and fix whatever is upstream of the rep. Then give them two to four weeks on a clean system.

If the numbers move, you had a system problem and you just saved a hire. If they do not move on clean data, proper tooling and a tested script, now you have a fair read on the person.

When it actually is the rep

Sometimes it is the person. The honest signals: connect rates are fine but conversations end in seconds; recordings show the opener being skipped or rushed; the rep avoids the phone and over-invests in channels with softer accountability; activity is reported but not evidenced in the dialer.

The test is recordings. A rep who cannot hold a sixty second conversation after coaching, on a good list, with a working dialer, is a rep problem. Everything before that is a management problem.

Common problems and fixes

Wrong numbers and dead lines. Waterfall five to six data vendors per record and enrich with mobile, email and signal data before a single dial. Verify, do not assume.

Low dial volume. Move from manual dialling to a parallel dialer with local presence. A dedicated caller should be at 1,000 dials a week, evidenced in the dialer, not in a spreadsheet.

Meetings that do not hold. Define a qualified meeting in writing — account fit, seniority, held attendance, complete handoff — and measure held meetings, not booked ones.

One person doing five jobs. Split the work. Strategy, list building, email, LinkedIn and calling each belong to a specialist. This is the entire reason the pod model exists.

How long before results?

On a fixed system, expect first meetings in week three and a steady state around week six. A reliable read on whether the rep can do the job takes about a month of clean data. A full rebuild of the function — new data, new tooling, new message — takes a quarter to prove.

If you need pipeline faster than that, the answer is usually not a better rep. It is more specialists. A five-specialist pod — strategy, lists, email, LinkedIn and a dedicated caller at 1,000 dials a week — can be live in 7 days, which is faster than any PIP cycle.

Key takeaways

Diagnose the system before the person: list, volume, conversation, script, in that order.
40–60 manual dials a day is a tooling ceiling, not an effort problem. A parallel dialer produces 200 or more.
Recordings are the only honest way to evaluate conversation skill.
A PIP on a broken system is a plan to fail. Fix upstream first, then evaluate.
One SDR doing five jobs will be bad at three of them. Specialists beat generalists at every stage.

Frequently asked questions

How do I know if my SDR is the problem or the system is?: Check in order: list quality, dial volume and tooling, conversation skill, then the script. If wrong numbers and dead lines are common, or dials are capped by manual dialling, the system is the problem and no coaching will fix it.
How many dials should an SDR make per day?: 40 to 60 with manual dialling, or 200 or more with a parallel dialer — roughly 1,000 dials a week for a dedicated caller. If volume is low, look at tooling before effort.
What is a good cold call connect rate?: Four to eight percent of dials reaching a human is typical in B2B. Below that, look at data quality and local presence numbers before questioning the caller.
Should I put an underperforming SDR on a PIP?: Only after the system is fixed. A performance plan on a broken list or manual dialling is a plan to fail. Fix what is upstream of the rep, give them two to four weeks on a clean system, then evaluate.
When is it actually the rep?: When connect rates are fine but conversations end in seconds, recordings show the opener being skipped, and the rep avoids the phone. The test is recordings after coaching, on a good list, with a working dialer.
How long before an SDR produces consistent results?: Three to four months of ramp before consistent output is normal. On a fixed system, first meetings land in week three and steady state around week six.
Is it better to replace the SDR or use an agency?: If the issue is one person doing five jobs, replacing the rep changes nothing. A five-specialist pod — strategy, lists, email, LinkedIn and a dedicated caller — can be live in 7 days and costs less than a fully loaded hire.