Before you let an underperforming SDR go, rule out the system: the list, the message, deliverability, coaching, the comp plan, and whether they got a real ramp. Most underperformance we get asked to diagnose is a system problem wearing a rep's name. Fire the rep and keep the broken system, and the next hire fails the same way. The honest test is simple: fix the inputs, give one clean cycle, and see who is left standing.
This is for founders and managers staring at an SDR's weak numbers and wondering whether to coach, wait, or part ways. It covers how to tell a rep problem from a system problem, when it genuinely is the rep, and how to act cleanly either way. It is deliberately opinionated, because the default reflex, blame the rep, is usually wrong and always expensive.
Why is underperformance usually a system problem?
Because an SDR sits at the end of a chain they do not control. Someone else builds the list, sets up the domains, writes the core message, defines the ramp, and designs the comp. If any of those is broken, the rep's numbers are bad through no fault of their own, and the numbers look identical to a genuine rep problem. That is what makes this hard: the symptom is the same, the cause is not.
So the manager's job is to be a fair diagnostician before being a judge. The reps you most want to keep are often the ones a broken system fails first, because good people leave a situation they cannot win, and you are left with whoever tolerates dysfunction. The full list of reasons good SDRs walk is in why SDRs quit.
How do you tell a rep problem from a system problem?
Read the symptom, then check the input behind it. Each weak number points at a likely cause upstream of the rep. Only after those come back clean should you conclude it is the person.
| Symptom | Usually | The check |
|---|---|---|
| High bounces, 'wrong person' replies | System (list) | Is the data verified and the ICP tight? |
| Good delivery, very low reply rate | System (message or list) | Is the message specific, and are these the right people? |
| Mail in spam, low open and reply | System (deliverability) | Are domains warmed and authenticated? |
| Never ramped, still weak past month one | System (onboarding) | Did they get a real, structured ramp? |
| Books meetings but they no-show | Mixed | Is it a qualification bar or a confirmation gap? |
| Ignores coaching, low effort, honesty gap | The rep | Have you coached the same thing twice with no change? |
The bottom row is the only one that is clearly the rep. Everything above it is fixable without changing the person. This is the same diagnostic ladder a good manager runs weekly, covered in how to coach SDRs weekly.
What system problems get blamed on reps most often?
- A bad list. The single most common one. A rep dialing and emailing the wrong people cannot win, and their activity looks fine while their outcomes do not. Fix targeting first; a filter is not an ICP.
- No real coaching. A rep left to figure it out alone plateaus, and that plateau gets read as a ceiling. It is usually just an absence of coaching.
- A comp plan that rewards the wrong thing. Pay on booked meetings and you get no-shows; pay on activity and you get spam. The rep is responding rationally to the plan. Fix the plan, in SDR compensation plans.
- No ramp protection. A rep judged on quota in week two, before they know the product or the buyer, looks like a failure and often quits before they were ever given a chance. A structured 30-day ramp prevents it.
- Burned domains. If the mail is in spam, the rep's best email is invisible. That is infrastructure, not effort.
When is it genuinely the rep?
When the system is sound and the problem is the person, in ways a better list cannot fix. Three patterns are real rep problems: they do not apply coaching (you correct the same thing repeatedly and nothing changes), the effort is not there (activity is low and excuses are high), or there is a trust or honesty issue (inflated numbers, meetings that were not real). None of those are system problems, and none improve with a better setup.
The trait that matters most here is coachability, which is exactly what a good hiring process screens for and why the wrong hire is so costly to unwind. What good looks like, and how to screen for it, is in what makes a great SDR and SDR interview questions that predict performance.
How should you actually make the call?
Fix the system, give one honest cycle, then decide, and act cleanly whichever way it goes. Rushing to fire while the list is broken just resets the problem with the next hire. Dragging it out for months past a corrected cycle is unfair to the rep and a drain on the team.
- Fix the inputs first. List, message, deliverability, coaching, comp, ramp. Whatever the diagnostic flagged, correct it.
- Reset expectations clearly. Tell the rep exactly what changed, what good looks like now, and the timeframe. No ambiguity.
- Coach hard for one cycle. Four to six weeks, with the weekly rhythm actually happening, not skipped.
- Then decide. A coachable rep with real effort usually turns the corner once the system is fixed. If they do not, part ways quickly, respectfully, and without dragging it out. Slow, unclear exits hurt everyone.
How MarginSales thinks about this
MarginSales provides sales outreach services for companies that want to extend their outbound capacity without building the entire sales development function internally, and we place and coach reps through our hiring and enablement work. When a rep is struggling, we run the diagnostic before we run the exit: check the list, the message, the deliverability, the coaching, the comp, and the ramp, because most of the time the fix is upstream of the person. We hold the honest line too: when the system is sound and the rep is not coachable, the kindest thing for everyone is a clean, quick decision.
If you have a rep whose numbers are down and you cannot tell whether it is them or the setup, we are happy to run the same diagnosis on your motion that we run on ours.
Frequently asked questions
How do you know if an SDR is underperforming or if it's the system?
Walk the funnel before you judge the rep. If the list is wrong, the domains are burning, the message is generic, or the rep was never coached or given a real ramp, the numbers will look like an SDR problem when they are a system problem. Rule those out first. If the inputs are genuinely sound and a coachable, hardworking rep still cannot produce, then it is the rep.
When should you actually let an SDR go?
When the system is sound and the problem is the person: they do not apply coaching, the effort is not there, or there is a trust or honesty issue. Those are not fixable by a better list. Give one honest cycle with the inputs corrected and clear expectations; if a coachable rep with good effort still cannot get there after that, part ways cleanly and quickly.
How long should you give a struggling SDR before deciding?
One honest cycle after the system is fixed, usually four to six weeks. If you fire a rep while the list is broken, you just repeat the problem with the next hire. Fix the inputs, reset expectations clearly, coach hard, and then judge. Dragging it out past a corrected cycle is unfair to the rep and expensive for you.
Not sure if it's the rep or the setup?
Tell us the rep's numbers and what their list, message, and coaching look like. We will help you tell a rep problem from a system problem before you make an expensive call, whether or not you work with us. Book a 20-minute review.