If your best person leaves, what leaves with them?
TL;DR
People leave. That part is normal and expected.
The risk is when customer history lives only in their phone and memory.
Then a new person starts from zero and the customer feels it fast.
Keep the chat, promise and next step in one place the business owns.
Test it now, while the person is still here to fill the gaps.
Your best person resigns. Two weeks later a customer calls and asks about the promise they were given last month. Nobody else knows what was said.
That is the real loss. Not the resignation letter. The history that walked out with one phone, one inbox and one memory.
What actually leaves when a key person leaves?
What leaves is context. The customer history, the small promises, the price that was quoted, the reason a deal stalled and the date someone said to call back.
In many small firms that context lives in personal chats. The chat is quick. It is also private to that phone. When the person changes phones, goes on leave or leaves the firm, the firm loses the thread. A new person can change the owner name in a sheet. That does not transfer what was actually discussed.
This is why we say on the BaseEngine page that the work should live in the business, not in one person. One place. One owner at a time. But the history stays when the owner changes.
Why does a customer feel a staff change so fast?
A customer feels it because they have to repeat themselves. They explain the same need again. They forward the same file again. They hear a new person ask a question that was already answered.
Research on sales handovers shows why that moment matters. A study covered in Phys.org looked at 2,040 B2B customers over four years. It found resale revenue fell by 28.1 percent after a relationship change. Earlier work cited in the same report put total customer revenue loss at up to 17.6 percent after a disruption. You can read the summary in the Journal of Marketing study report.
Those are large firms. In a small firm the same break is sharper. There is often only one person who knows the customer well. If that knowledge is not written where others can read it, there is no second chance to get the handover right.
How common is this risk, really?
It is common because people move. The same study report notes at least 20 percent annual turnover in sales, rising to 34 percent when both voluntary and involuntary moves are counted.
Data also moves with people, often without bad intent. A Tessian survey of 2,000 UK workers, reported by Infosecurity Magazine, found 29 percent of employees said they took data with them when they left a job. Many said they believed the work was theirs because they had worked on it.
Read that plainly. This is not only a bad actor problem. It is a placement problem. If the only copy of a customer note is on a personal device, the business has already decided who owns that history. It just has not admitted it yet.
Why does buying a CRM not fix this on its own?
Buying a CRM does not fix it because a tool only holds what people put into it. If the real chat still happens on a personal phone, the CRM stays empty and the history stays private.
Published CRM failure estimates range from 30 percent to 70 percent, depending on how failure is defined, with poor use by the team as the recurring cause. That summary is set out in this CRM statistics review, which also notes that buying is easy and daily use is the hard part.
So do not start with a bigger tool. Start with a smaller rule. Every customer promise gets written in one business owned place on the same day it is made. No promise lives only in a chat. That rule is boring. It is also the whole fix. We use the same thinking in our AI automation work. Put the record where the work already happens, then let the system do the reminding.
Personal phone and memory. Nobody else can find the thread. They repeat everything from zero
Shared sheet with short notes. Others can read the last step. Handover is rough but possible
One business owned record. Owner can change, history stays. They are known, not restarted
What should live in the business, not in one phone?
Five things should live in the business. Keep them short. Long notes that nobody writes do not help anyone.
Who the customer is and who owns them today.
What was promised, in one line, with a date.
What file or quote was last shared and when.
What is stuck and who is waiting on whom.
When the next step is due and who will do it.
That is enough for a new person to pick up the phone with respect for the customer time. They may not know everything. They will not start with a blank face. That alone changes how the call feels.
I wrote about a close cousin of this problem in Your AI tools sit next to the work, not in it. That piece was about tools sitting beside daily work. This one is about history sitting inside one person. Different seat, same leak.
How do you test your risk before someone resigns?
Test it this week. Pick your five most important customers. For each one, ask if a second person could answer three questions in two minutes.
Could they say what was last promised? Could they find the last quote or file without calling the owner? Could they say what the next step is and when it is due?
If the answer is no for three or more customers, you do not have a people problem. You have a memory problem with a date on it. You just do not know the date yet.
Write the missing lines now, while the person who knows is still here to correct them. That is cheap. Doing it after they leave is guesswork, and customers can hear guesswork.
Start narrow. Five customers. One shared place. One short format your team will actually use on a busy day. You can see how we think about this shape on the BaseWorks homepage and on the About page. The full set of notes like this lives on the Insights page.
What is the first move if you find a gap today?
The first move is a handover note written before you need it. Sit with the person who holds the customer. Write the five lines together. Check that a second person can read them and make the next call without help.
Do one customer a day for a week. By Friday you will know if your business can survive a sick week, a long leave or a resignation without starting customer talks from zero.
That is the conversation I want this piece to start. If your best person took two weeks off tomorrow, what would stop, and what would a customer have to repeat?
Want to think it through for your business? Start with the BaseEngine overview and check whether your customer history would stay if the owner changed.
Frequently Asked Questions
What leaves when a salesperson leaves a company?
What leaves is customer context if it was never written in a shared place. That includes chat history, quoted prices, promises made on calls, reasons a deal stalled and the next step date. A new owner can be named in minutes. The context takes much longer to rebuild.
Why do customers repeat themselves after a staff change?
Customers repeat themselves because the new person cannot see what was already said and shared. They ask for files again, ask about needs again and miss promises made earlier. The customer reads that as the business not remembering them, even when the new person is trying hard.
Is this only a problem when someone resigns?
No. The same gap shows up on leave, on a sick day or when a phone is lost or changed. Resignation is just the most final version. Any day the one person who knows is not reachable, the business finds out how much history it actually owns.
Do I need a new CRM to fix this?
No. You need one business owned place for customer history and a rule that promises are written there the same day. A new CRM with no daily habit stays empty. A simple shared record that your team uses every day will beat a large tool nobody opens.
What should a handover note include?
Keep it short so people will write it. Include who owns the customer today, what was promised and when, what was last shared, what is stuck and when the next step is due. Five lines are enough for a second person to continue the talk with care.
How often should we update customer records?
Update them on the day a promise, quote or next step changes. A weekly cleanup helps, but it cannot fix a month of chats that were never written down. The habit that matters is same day writing, in the place the whole team can read when they need it.
By Aravind Bhati, Founder, BaseWorks