Blog
When a salesperson leaves, do customers?
A salesperson resigns. Two weeks later three deals have gone quiet, and a customer who used to reply the same day is talking to a competitor. The owner concludes that the rep took the customers with them.
Usually that’s not what happened. The customers didn’t move. The record of the relationship did. It was never in the company in the first place. It was on a phone that walked out the door.
Why customers leave with the salesperson who resigns
Long-cycle B2B means project work, installation, factory supply. In that kind of business a deal is mostly conversation history. What they asked for. What was quoted, and on what basis. Which spec got rejected and why. Almost none of that is in your accounting system. Most of it is in a chat thread on one person’s personal phone.
So when the phone leaves:
- The new rep restarts a conversation the customer finished three months ago.
- The customer re-explains everything, and quietly concludes the company doesn’t know them.
- A fresh quote goes out on different terms, because nobody knows what was already promised.
- The rep who left is the only person alive who knows the deal. Same industry, new employer.
That last point isn’t disloyalty. It’s convenience. The customer goes where the memory is.
A simple test: if your best rep resigned tomorrow, how many days to hand the work over?
Ask it without warning. Take your strongest salesperson and time two things.
- How many days until someone else can list every one of their open deals, with value, next step, and date?
- How many days until someone else can answer “what exactly did we promise this customer?” without phoning the person who left?
In most B2B companies of 20–200 people the honest answer is “we don’t know” or “a month, maybe.” If the number is more than about three working days, you don’t have a people problem. You have a storage problem.
That number is checkable, and you can drill it when nobody is resigning. It measures one thing: whether the company can continue a relationship an employee started.
The standard advice at this point is “get a CRM.” That answers a different question. Software decides where the record lives; it doesn’t decide what has to be in it, or who writes it, or when. Get those wrong and you’ll buy a system and still be at “a month, maybe.”
Four things that must live with the company, not on a personal phone
This is not “put everything in a system.” Four items per open deal:
- The contact. Who the person is, their company, their role, and how to reach them. Kept at an address the company controls, not in one phone’s contact list.
- What was promised. Quote version, what the quote was based on, lead time, any spec exception. All in a document anyone authorised can open.
- The last conversation and the next step. One or two lines, dated, with a name attached. “Waiting for their engineer to confirm panel size. Follow up 12 Aug, Ake.”
- Where the deal stands. A stage everyone in the company reads the same way.
If those four exist for every open deal, a handover is admin. If they don’t, a handover is archaeology.
None of this requires buying anything this week. Four honest columns in a shared sheet beat the finest system nobody updates. The tool question comes afterwards, and it gets much smaller once you’ve agreed what has to be in there.
How to talk about personal chat with your team without making it about trust
This is where most owners stall. The conversation sounds like an accusation. Two things make it easier.
First, don’t ban the personal channel. Customers will keep messaging the person they know, on the app they already have open. A rule saying “customers must use the company account” mostly produces lost messages.
Second, separate the channel from the record. The rule isn’t don’t chat on your phone. The rule is: anything that changes the deal gets written into the company record the same day. A new requirement, a number, a date, a decision. Chat is where talking happens. The record is where the company remembers.
Frame it as cover, not surveillance. If someone is on leave, sick, or on site all day, a colleague can answer their customer without embarrassing them. Good reps like this. It means they stop being on call at 9pm for a question the record could have answered. Say out loud that you are not counting anyone’s messages.
Make deal handover a step in the process, not an emergency
Right now, handover happens once, badly, in someone’s final week, while they’re already mentally gone. Make it routine instead:
- Weekly. Every open deal has a next step, a date, and an owner. Fifteen minutes, not a report.
- On leave. Anyone away more than two days names a cover for their live deals. So the team rehearses handover several times a year, with no emotion in the room.
- On resignation. A written checklist, not a meeting: walk the open-deal list, confirm the four items, transfer the contact, then tell the customer who they’re speaking to next. In that order.
- Two weeks after. The new owner reads the deals back to you. Anything they can’t explain is a hole in the record. Fix the record, not the person who left.
Handover done four times a year is a habit. Done once, under stress, it’s a loss.
Start with the deals running right now, not with everything you’ve ever sold
The reason this never gets fixed is that owners picture a data-entry project: years of history, thousands of contacts, someone typing for a month. Don’t.
Scope it to open deals only. That’s usually 20–60 of them in a company this size, not thousands. One working session per rep, deal by deal, four items each. A day of work, two at most.
Closed customers can stay where they are until they come back. When one does, capture them then. The record fills up as the business runs, not before it.
If you want to know your own number, book a 45-minute pipeline call. We’ll walk through your live deals as they exist today, and you’ll leave with two things: how many days it would really take to hand your best rep’s work over, and the list of what’s missing to make that number smaller. Both are yours whether or not we end up working together.