When and How to Let Go of an Underperforming Rep
Firing a rep is a last step, not a first reaction. A process with real documentation, timelines, and a performance plan that protects the team and the company.
, 3 min read, Sales leadership
Key takeaways
- Confirm quota, territory, onboarding, and coaching were actually in place before assuming underperformance is the rep's failure and not the system's.
- A performance improvement plan needs specific, measurable targets and checkpoints the manager actually keeps, not just a document to justify a decision already made.
- How an exit is handled, both with the departing rep and with the team left behind, shapes trust in every review and PIP that follows.
A firing decided in a single bad forecast call almost always means the process before it was skipped, and the decision, however necessary, will look arbitrary to the rest of the team.
Underperformance is a process failure until proven otherwise
Before any conversation about exit, confirm the basics were actually in place: a clear quota, a defined territory with enough addressable opportunity, onboarding that hit its milestones, and regular coaching documented over time. Skipping this check and moving straight to a performance plan risks punishing a rep for a system failure that was never theirs to fix.
Run a real performance improvement plan
A PIP that exists mainly to create a paper trail for a decision already made helps no one and is usually obvious to the rep receiving it. A real one sets specific, measurable, achievable targets over a defined window, with checkpoints the manager actually keeps.
| Phase | Duration | What happens |
|---|---|---|
| Diagnosis | 1-2 weeks | Confirm root cause (see the skill/will/territory framework), document with data |
| Plan | Set at kickoff | 2-4 specific, measurable targets with weekly checkpoints |
| Execution | 30-60 days | Weekly coaching against the targets, written notes each time |
| Decision | End of window | Targets met: exit the plan. Not met: proceed to separation, with documentation ready |
Recognize when the conversation is coming
The signs are usually visible weeks before the decision: targets missed for two consecutive checkpoints with no material change in approach, or a root cause that the plan can't actually fix, a territory problem masquerading as a performance issue, for instance. Prepare the logistics, the final pay and equity questions, and the exact language before the meeting, not during it.
What to say to the rest of the team
Silence invites speculation that's usually worse than the truth. Without disclosing personal details, tell the team what changed structurally (territory reassignment, headcount plans) and reaffirm that the same clear standards apply to everyone, which is the message that actually protects morale, not a vague reassurance that nothing else will happen.
Protect the exit itself
Give the person a clear, factual reason in the room, avoid ambiguity that leaves them guessing, and handle logistics (final pay, references, any transition support) with the same care you'd want if the roles were reversed. A rep who leaves believing the process was fair is far less likely to leave a negative account of the company behind, and the rest of the team is watching how this is handled more closely than any all-hands meeting.
Document as you go, not at the end
The single most common failure in a difficult exit isn't the decision itself, it's the paper trail behind it. Managers who coach informally for months, then decide to formalize a PIP only once they've mentally committed to letting someone go, end up with a file that reads as thin and after-the-fact, which is a legal and a fairness problem at once. Write a short note after every coaching conversation where performance comes up, even the ones that don't feel serious at the time: date, what was discussed, what was agreed, and what happened by the next check-in.
This habit protects the rep as much as the company. A contemporaneous record shows whether a genuine effort was made to help someone improve, which is the fairest possible basis for any eventual decision, and it also surfaces, sometimes surprisingly, that a rep who looked like a clear PIP candidate from memory actually turned a corner three months ago and the file simply wasn't updated to reflect it. Memory is a poor substitute for notes, in both directions.
Keep the documentation factual and behavioral rather than characterological. "Missed two of three commitments made in the July 12 and July 19 check-ins" is documentation a manager can stand behind under any scrutiny. "Doesn't seem motivated" is an impression that will not hold up, and worse, it tells the rep nothing they can act on even if the conversation happens in good faith.
Frequently asked questions
- How long should a performance improvement plan last?
- Thirty to sixty days is typical for a sales role, long enough to see a genuine trend but short enough that the rest of the team and the business aren't carrying an unaddressed performance gap indefinitely.
- Should HR be involved before the PIP starts?
- Yes, always. Involving HR at the point the pattern is first documented, not after the decision is already made, protects both the company and the rep and ensures the process is actually followed rather than assembled after the fact.
- What should you tell the team after someone is let go?
- State what changed structurally (territory reassignment, hiring plans) without disclosing personal performance details, and reaffirm that the same standards apply to everyone. Vague reassurance without any real information tends to increase anxiety, not reduce it.