Stuart Totterdell
Technical Director
There is a person in your business - maybe more than one - who holds the operation together. They know how the invoicing process actually works, as opposed to how it is documented. They know which supplier needs a phone call instead of a purchase order. They know that the CRM data is only reliable if you filter by a specific field that nobody else knows about. They know where the spreadsheet lives, how the formula works, and what to do when it breaks.
They are not on your risk register. But they are your biggest risk.
Every SME has these people. They are usually experienced, diligent, and deeply embedded. They are often the most valued members of the team - and they should be, because without them, things stop working.
But that is exactly the problem. When your operation depends on individuals - their knowledge, their workarounds, their habits - you do not have a system. You have a dependency. And dependencies break.
The knowledge that lives in people's heads
Ask yourself a simple question: if your three most operationally critical people resigned tomorrow, what would happen?
Not in six months. Tomorrow. Could someone else pick up their work? Do you know what they do, exactly? Not their job description - their actual work. The steps they take, the decisions they make, the data they access, the workarounds they use.
In most mid-market businesses, the honest answer is: no. We would figure it out eventually, but it would be painful, slow, and expensive.
That is not a staffing problem. That is a systems problem - and usually an IT and process strategy one. It gets worse over time, because every day that person continues to operate without documentation, without automation, without structured processes, the knowledge gap between them and the rest of the organisation grows.
Why this happens
It happens because building proper systems takes time and effort that feels unnecessary when the person is there. Why document the process when Sarah knows it? Why automate the workflow when James does it every week? Why build a dashboard when Michelle can produce the report?
The answer, of course, is that Sarah, James, and Michelle are human beings with careers, ambitions, health considerations, and lives outside your business. They will not be there forever. And when they leave - not if, when - they will take your operations with them.
It also happens because the tools most businesses use are not designed for process capture. Your ERP records transactions, not workflows. Your CRM records contacts, not decisions. The actual logic of how your business runs - the sequence of steps, the rules, the exceptions - lives nowhere except inside the people who execute it, and without development and build that reflects how work actually flows, it stays that way.
The automation opportunity nobody is talking about
When people talk about automation, they usually mean efficiency: doing things faster, cheaper, with fewer errors. And that is true. But the more important benefit of automation is something else entirely: externalising knowledge.
When you automate a process through business automation, you are not just making it faster. You are capturing it. You are turning implicit knowledge - the stuff in people's heads - into explicit logic - steps, rules, triggers, and exceptions that are documented, repeatable, and transferable.
That is not an efficiency gain. That is a resilience gain. It means your operation no longer depends on a specific person being present, available, and willing. It means you can onboard new people faster. It means you can scale without proportionally adding headcount. And it means you can actually see how your business works, instead of relying on tribal knowledge and hoping for the best.
Start with the critical paths
You do not need to automate everything. You need to automate the things that matter most - the processes that, if they broke, would cause real damage.
Map your critical workflows. Not the ones in your process documents - the real ones. The ones your team actually follows. Identify where decisions are being made by individuals based on experience rather than data. Identify where handoffs depend on someone remembering to do something. Identify where the same data is being entered into multiple systems by the same person.
Those are your automation targets. Not because they are the easiest, but because they are the most dangerous. Every one of them is a single point of failure disguised as a competent employee.
This is not about replacing people
Let me be clear about something, because this is where the conversation usually goes wrong. Automating processes is not about replacing the people who currently run them. It is about freeing them from work that should not require human judgement in the first place.
Your best people should not be spending their time on data entry, reconciliation, status chasing, and report building. They should be spending their time on the things that actually require their experience and judgement - exception handling, relationship management, strategic decisions.
When you automate the routine, you do not lose your people. You unlock them. And you protect your business from the inevitable moment when they move on.
The question you should be asking
Every business owner should be asking: what happens to this operation without me in the room? Not as an ego exercise - as a genuine operational stress test.
If the answer is "it keeps running, because the systems carry it" - you have built something durable. If the answer is "it falls apart, because only specific people know how it works" - you have built something fragile, regardless of how successful it looks today.
Build the systems. Capture the knowledge. Automate the critical paths. Because your best people will not be there forever, and your business needs to be.
