One rep is a single point of failure. Plan for it.

The resignation lands on a Tuesday. Two weeks of notice, a polite exit, and then a one-rep outbound program is a zero-rep outbound program. The list goes quiet, the follow-ups expire, the accounts that were three touches deep go cold, and by the time a replacement is dialing, the pipeline has a hole in it the exact shape of one quarter. None of this is dramatic. It is Tuesday.

The numbers say to plan for it. SDR turnover runs 34 to 40 percent a year, roughly triple the all-role average, and about one in five new hires is gone inside ninety days. A single-rep program is therefore not a small version of a team. It is a system with no redundancy running a component with the highest failure rate in the building. You cannot buy your way out of the odds. You can design so that a departure costs you weeks instead of a quarter.

Continuity is written down, or it does not exist

The playbook lives outside the rep's head. Call track, objection responses, the qualification bar, the cadence structure: current versions, in a shared place, updated as they change. Most one-rep programs have all of this as tribal knowledge, which means the program's intellectual property walks out with the person. A successor who inherits documents starts executing in days. One who inherits a login starts archaeology.

Calls are recorded and kept. A library of real calls is the fastest possible onboarding for a replacement: this is how our buyers talk, these are the objections, this is what good sounds like here. It is also the only honest record of message iteration. The recordings cost nothing to keep and are irreplaceable the week you need them.

The company owns the list. Accounts, contacts, signals, tiering logic, and every touch logged in company systems, never in a personal spreadsheet. The five-field logging discipline we laid out in the CRM post is a continuity asset as much as a reporting one: dated next steps and verbatim notes are exactly what lets a successor pick up mid-conversation instead of starting over with every account.

Someone else can run the desk for two weeks. Not well, just adequately: a manager or founder who knows the system can keep tier-one follow-ups alive while the seat is empty. Coverage that degrades beats coverage that stops.

The clock is the expensive part

Even with perfect documents, the in-house replacement math is slow. Recruiting an SDR takes weeks in the best market, and the hiring seasons do not schedule themselves around your resignation. Then a ramp measured in months starts, even with the scripted first week in hand. Stack those and an unplanned departure in a one-rep program costs a quarter of pipeline at the fully loaded seat price of roughly $10,000 a month, paid the whole way through.

This failure mode is one of the reasons CommandVA exists in its current shape. Your rep is one named person, but the system around them, the documentation, the recordings, the list, the management layer, is institutional. It is all standard practice on every account, and it is a large part of what you are buying at the published price: not just a rep, but a program that survives the loss of any single person, ours included. If your outbound currently lives in one head, book a strategy call. The best week to build the continuity plan is any week before you need it.