The Day a Rep Leaves: How 189 Days of Revenue Disappears Before You Notice

It starts the moment they accept the offer somewhere else.

Sales rep turnover in B2B SaaS runs at 35% annually — nearly three times the 13% average across all industries. That means on a 30-person sales team, roughly 10 people will leave this year. You already know that. What most revenue leaders miss is what happens in the 48 hours after the exit interview.

That's 189 days. Not 30. Not 60. Six months and change where the territory is either dark, covered by a manager burning time they don't have, or handed off to a rep who is already overloaded. And the revenue math is brutal: divide your annual new business target by 280 working days and multiply by 189. That number — quiet, invisible, never showing up in your board deck — is what a single departure actually costs.

The data problem nobody talks about.

Here's what actually happens in Salesforce the morning after a rep leaves: nothing. The accounts stay in their name. The territories stay assigned. The opportunities sit in their pipeline. The automated sequences keep running from their email address — which bounces. The comp record in Xactly stays active. And nobody gets an alert.

44% of companies estimate they lose over 10% in annual revenue due to poor-quality CRM data — and that's before a single rep departure triggers a cascade of orphaned records.

— Clari / survey of 1,250 companies

The problem compounds. A rep who is mentally checking out — who has already accepted an offer but hasn't told anyone — stops updating their CRM weeks before they announce. Deals go stale. Contacts go cold. And when they finally leave, the last record anyone has of their accounts is weeks out of date.

What 'orphaned account' actually means in dollars.

An orphaned account is any account that was assigned to a departed rep and has not been reassigned, contacted, or updated. On a typical 30-person SaaS sales team with 35% annual turnover, you'll have 10–11 departures per year. If each rep owns an average of 40 accounts, that's 400+ accounts cycling through an ownership gap every year. Even if your team reassigns them within two weeks, that's two weeks of uncontacted accounts — at a time when the prospect's last interaction was with someone who no longer works for you.

• Inbound leads routed to a departed rep's queue go unanswered
• Renewal conversations in-flight stall with no handoff
• Automated sequences bounce from the rep's now-inactive email
• Comp disputes emerge when the departed rep's manager inherits credit questions
• SOX auditors flag unexplained account ownership gaps in financial reporting

The fix is not a process. It's a trigger.

Most RevOps teams respond to rep departures reactively — a manager notices something is wrong, sends a Slack message, and someone spends a Thursday afternoon doing account reassignment in bulk. This works when turnover is low and your team has bandwidth. It stops working the moment you have a bad quarter.

The right model is triggered: when a departure is logged in your HRIS, a cross-system check runs automatically — not on a quarterly schedule, not when someone notices, but within hours. Accounts get flagged. Territory gaps surface. Comp records get suspended. The manager gets an alert with a specific list of actions, not a vague notification that 'something changed.'

That's what OrgDrift was built to do. Drop in a CSV from Workday and Salesforce after a departure. It tells you exactly what broke, what needs reassigning, and what the compensation system still has active that shouldn't be.