Ask yourself one question: if the person who knows how your ERP actually works took a two-week vacation, could your finance team close the month?
For a distributor doing tens of millions in revenue, the answer was no. Every critical process was undocumented and lived in one person's head. How inventory moves. How orders flow. How month-end actually closes. None of it was written down, and none of it was safe.
We walked into that situation at the worst possible time. The company was growing fast, and it was in the middle of acquiring another business. That is exactly when undocumented systems break loudly.
The single point of failure you cannot see
Every business has tribal knowledge. The difference is how much of it is load-bearing.
In a healthy company, the critical processes are documented, tested, and owned by the business. If someone leaves, the work does not leave with them. In this distributor, the entire operation ran on the memory of one person. When that person was out, work slowed to a crawl. When that person made a call, nobody could challenge it, because nobody else knew the process well enough to have an opinion.
The scary part is how invisible this is from the outside. The software looks fine. The screens load. The reports run. But underneath, the business is one vacation away from a crisis, and the people running it have no idea because nothing has ever gone catastrophically wrong yet.
The data nobody trusted
Then there was the inventory. Hundreds of thousands of product records across the system, and nobody trusted the numbers.
Inventory data was unreliable in the way that quietly costs money: buyers could not plan around it, sales promised what might not be on the shelf, and month-end required manual reconciliation because the system's numbers never matched the warehouse's reality. The finance team had learned to do the close with workarounds instead of the system, which meant the ERP was not running the business. A handful of people were running the business on top of the ERP.
That works until it does not. And it cannot scale. You cannot onboard a new hire into a process that lives in someone's head. You cannot integrate an acquisition into a system nobody can explain. You cannot hit a growth target with a finance team that has to hand-check everything.
What it takes to fix it
The fix is unglamorous, and that is why most businesses avoid it.
First, document the real process. Not the process in the training manual, not the process the ERP vendor designed, the process that actually happens, with all the workarounds and patches that keep it alive. That documentation is the map. Without it, every change is a guess.
Second, stabilize the data. Inventory you cannot trust is a liability, not an asset. Until the numbers in the system match the numbers in the warehouse, nothing built on top of them will be reliable.
Third, make the business run without the key person. Not by firing them, by transferring what they know into something the whole company can use. The goal is that the person holding the business together can finally take a vacation, and the business does not notice.
The worst time to find this out
The moment that forces this conversation is usually unpleasant: an acquisition, an audit, a departure, a missed close. That is when a hidden single point of failure announces itself.
You do not have to wait for one of those moments. The dependency is probably already there. The question is whether you find it on your own schedule, or it finds you.
Book a discovery session if your business depends on one person's memory and you want to find the hidden dependencies before they break. Our $7,500 System Assessment documents what actually runs your business and gives you a plan you keep either way.