A factory owner once said something to me that I have remembered for a long time:
"Hiring people does not scare me. What scares me is that the person who knows the business best is leaving next month."
His factory has just over twenty people. How a quote is calculated, which customer has a temper, when each machine is due for servicing, which step to check first when something goes wrong — none of it is in any document. It all lives in one person's head. When that person leaves, you do not lose one employee. You lose an operating system.
Turnover is falling; the risk is rising
Start with a piece of data that looks like good news.
The "2026 Turnover and Salary Adjustment Survey Report" published by 51job this January shows that the overall employee turnover rate fell to 14.8% in 2025, down 0.5 percentage points year on year, and lower for the third consecutive year since 2023.
But a small-business owner should read it the other way round: fewer people leave, yet the one who does leave usually hurts more.
When a large company loses someone, the process is still there, the system is still there, and three colleagues beside them still know the job. When a small company loses someone, that person may take away an entire body of experience that nobody ever recorded — it was never in a system, only in that person's habits.
The arithmetic does not work either. Gallup research puts the cost of replacing an employee at 0.5 to 2 times their annual salary; a study cited by Harvard Business Review is blunter: the damage from losing one employee can reach 5 times their annual salary, and training a single new hire alone costs about 21% of their pay.
And that is only the cost of swapping people. What has never been put on the books is the knowledge that walks out the door with them.
Why "just ask them to write it down" almost always fails
Most owners react the same way: while the person is still here, have them write their experience down.
I have seen this route taken too many times, and it almost always ends the same way. Three reasons:
First, there is no time to write. Every day they are still here is spent putting out fires, and nobody treats "writing documentation" as more important than the work in their hands.
Second, they do not know how. What is actually valuable is never something copyable like an "equipment maintenance procedure"; it is knowing that "when a customer says this sentence, calm them down first, because what they really want is a refund". Judgements like that feel like common sense to the person making them, and it never occurs to them that it is worth writing down.
Third, nobody reads what gets written. A 60-page Word file dropped on a shared drive is the same as a cabinet at the very back of the warehouse: identical to not writing it at all.
You probably have a pile of knowledge single points of failure
I call this a knowledge single point of failure: one link in the chain is held up by a single person's head, and the moment they leave, that link loses power.
It is like a server room with only one incoming power feed. Nothing goes wrong in normal times; the moment the breaker trips, you find out what a total outage means.
Here is a simple test you can run right now: take a sheet of paper and list the questions in your company that "only one person can answer correctly on the first try".
- At what point in a price negotiation must the owner be consulted?
- When this model makes a particular odd noise, where do you check first?
- Which customer can never be kept waiting, and which one can be negotiated with?
If you have more than 10 questions like these, what you are holding is not a small company. It is a pile of knowledge single points.
3 things you can do yourself (you can give the order today)
You do not have to wait for a system of any kind. These three can be assigned today:
1. Ask for a question list, not a lessons-learned summary. Instead of asking the employee to write a document, ask them to list "the 20 questions I was asked most often this year". A question list is ten times easier to write and ten times more useful. Documents get abandoned half-finished; question lists do not.
2. Record instead of write. Have them talk into a phone for 10 minutes: the traps customers fall into most often, which line items in a quote get cut most easily, which situations require checking with the owner. Ten minutes of speech usually carries more information than an hour of painful writing.
3. A handover needs a checklist plus a read-back. Do not count on a new hire "picking it up after a few weeks of watching". Write a handover checklist, have the new hire repeat it back and then actually do it, and have the outgoing employee sign it off. This step turns "I thought I had explained it" into "they can really do it".
How far we take it
The three things above deal with "keeping it". But there is a more practical question: once it is kept, how do you actually use it the next day?
That stretch is our work: turning recorded interviews, chat logs and scattered documents into a system you can ask questions of. Your staff type a question and the answer comes from your own material with its source marked; if the material does not contain the answer, it says "that is not in the material" instead of inventing something that looks plausible.
For a standard case we deliver in 7–14 days, and every stage has an explicit acceptance rule: the scope document is confirmed → 20 high-frequency questions are answered correctly more than 70% of the time → your own people can add a new document and see it take effect. All three gates must pass before delivery counts as complete; handing over an account is not the finish line.
Who we are:
- We are a "one person + AI" team focused on bringing enterprise knowledge bases and AI customer service into small and micro businesses.
- Scope: inventorying and cleaning your material, building the knowledge base, AI customer service (including handover to a human and a compliance self-check), and training your staff with an operating manual.
- Boundaries: no hardware or motion control, no model training, no managed operations on your behalf. Pricing is quoted per project.
The maturity of a company is not measured by how good its best person is, but by whether things still run as usual after that person leaves.
How many questions in your company can "only one person answer correctly"? Tell me in the comments; I will pick a few and answer them properly.
#enterprise-knowledge-base #AI-customer-service #small-business #experience-retention #employee-turnover