BoteamOperations
Operations that do not live in one head, so the work runs whether one person is on holiday or the project is on fire.
In most small businesses the operating system is one person’s memory. Pricing rules, supplier quirks, which client needs what, all of it lives in the owner’s head. It works right up until that person is on site, on holiday, or flat out — and then threads drop quietly. A quote is not sent. A follow-up slips. Nobody notices until the customer has gone elsewhere.
The cost of those dropped threads rarely shows up on a profit and loss statement, which is why it gets ignored. But it is the reason most owners describe their week as firefighting rather than running the business. Deloitte’s SMB research found the single biggest barrier to getting value from AI is not cost or fear — it is not knowing where to start. The fix for that is not a tool. It is writing down what the business actually does.
Once the repeatable work is written down, it can be handed over in a controlled way: a defined role, a stated capacity, an approval line, and a reporting rhythm so you can see what happened without chasing it.
Below: how to choose the first role, what a role should own versus what stays human, and how to keep the standard visible once the work has moved.
Track a normal week and write down every task that arrived in the same shape and was answered the same way.
What an AI employee should own, and what it should never
The first decision in any AI role is not which tool to use. It is where the line sits between work that repeats and judgement that stays human.
Choosing the first role: pick the work that repeats
Most small businesses have one or two tasks that eat the week in a predictable pattern. That pattern is where the first managed role belongs.
Operations that do not live in one head
In most small businesses the operating system is the owner’s memory. It works right up until that person is unavailable, and then things quietly fall apart.