There’s a version of this conversation happening in a lot of companies. Someone built the tool that runs scheduling, or claims, or inventory. They built it 14 years ago. They’ve maintained it since the start, mostly alone. And they’re leaving in 30 days.
The panic usually arrives as a staffing question: who takes it over? That’s the wrong question, and answering it wastes the time you have left.
Why hiring doesn’t solve it
A team of 10 engineers can still have a system only one of them can touch. The industry calls this the bus factor, the number of people who’d have to vanish before work stops. A 2016 study of 133 popular open-source projects found 46% had a bus factor of 1 and another 28% sat at 2. Another read of the same dataset puts 65% at 2 or lower, with fewer than 10% above 10.
Knowledge generally concentrates around the person who can move fastest and knows the system inside out, and they can move fastest because they built it, and they built it in a way that made sense to them and the business at the time.
The 5-question triage
Ask these about your system, and you can answer them out loud with the person who owns it in the room.
- Can someone else deploy a change to production this week without asking them?
- Does a written explanation exist of why it works the way it does, not just what it does?
- If it broke on a Sunday, could a competent outsider find the cause from logs and code alone?
- Is the logic in the code, or is it in spreadsheets, scheduled tasks and 1 person’s habits?
- Could you hire for the stack it’s written in, at a normal salary, in your city?
Reading your answers
- 4 or 5 yesA people problem. Pair the person leaving with a successor, write things down, and you’ll be fine. You don’t need an agency for this.
- 2 or fewerA system problem, and no amount of handover meetings will fix it. The knowledge isn’t transferable because the artifact isn’t transferable.
What untransferable actually costs
A German engineering firm described a client issue where onboarding a successor took 6 months because the knowledge lived in one person’s head, and put the cost of reverse-engineering long-adapted custom software at several times the original build, using an example where a €200,000 system ran past €500,000 to reconstruct. The pattern matches what we see: reconstruction costs more than construction, because the archaeology is the expensive part and the original builder did it once in their head.
What we’d actually do
The window before a departure is the easiest this work will ever be. The person is still there to answer questions that would otherwise take an agency 3 weeks to reconstruct. This is what we would do to help.
The handover, in order
- Weeks 1–2
- Sit with the team and map what the system actually does, including the processes that never made it into the code.
- Weeks 3–4
- Turn that behaviour into tests, so the rules and logic patterns don’t concentrate in one person’s head.
- Then
- Rebuild what can’t be maintained, keep what can, and simplify the parts where 14 years of patches have piled up.
- Handover
- Documentation for the next person who has to work on it, in a simple and understandable manner.
- Post
- We maintain it and handle any transition pain points.
The simplification step is where most of the value sits. Systems that grow around one person accumulate workarounds for problems that stopped existing years ago.
When to start
Twelve months out is comfortable. Six months is workable; 3 is a pinch, but it’s still worth doing, because a rebuilt system with a maintenance contract beats a working system no one can change.
The failure case is waiting until the leaving date, then hiring someone to “document the existing system”, and it answers none of the questions you’ll functionally have.
Got a system and a resignation date? Book a call. We’ll learn what they know while they’re still here, rebuild what needs rebuilding, straighten out what’s grown crooked, document it properly, and keep maintaining it afterwards if need be. Because “Dave knows how it works” is not good planning.




