Six Processes You Should Deliberately Leave Manual
A written list of what you refuse to automate is a stronger governance artefact than any AI strategy document — and it buys you organisational trust you will need later.
Michel ZozayaTechnical AuthorityThe list
Low volume with high variance. Under roughly twenty instances a month, each shaped differently, the maintenance burden permanently exceeds the saving. Automate the intake and leave the handling manual.
Anything irreversible and expensive when wrong: outbound client email, invoices and credit notes, contract terms, anything sent to a regulator. Human approval there is permanent policy, not training wheels.
Processes attached to a system you are replacing within six to twelve months — you would be building against an API being decommissioned. Processes that are the relationship, such as the key-account call or a difficult renewal, where automating the touch removes the signal you needed. Processes where the real bottleneck is an unmade decision, because automation will only queue the work faster. And anything nobody will own.
The threshold to apply throughout
Automate for order-of-magnitude gains in time, cost or accuracy. A 20% improvement does not survive its own maintenance cost.
Why publishing it increases adoption
Staff resistance is rarely to automation in general. It is uncertainty about where it stops. Naming the boundary removes that fear far more effectively than reassurance in a town hall.
Write your one-page do-not-automate list, with the reason beside each item, and send it to the whole team before you announce a single project.
Forty years as a Technical Director across shopping malls, offices, hotels and industrial assets.
Meet the team →Questions we get asked
What should never be automated in a services business?
Anything irreversible and expensive when wrong — outbound client email, invoices and credit notes, contract terms, regulatory filings — plus anything that is itself the relationship, and anything nobody will own.
What is the minimum volume that justifies automating a process?
As a rule of thumb, above roughly twenty instances a month with reasonably consistent shape. Below that, maintenance cost exceeds the saving permanently.
Does publishing a do-not-automate list slow adoption?
The opposite. Resistance is usually uncertainty about where automation stops. Naming the boundary explicitly increases adoption of everything else.
Related insight
The AI Assistant That Does Everything Does Nothing
An agent's reliability collapses as you add systems it must be simultaneously correct about. The only agents that reach production…
AutomationYour Software Is Fine. The Gaps Between It Cost You Forty Hours a Week.
The recoverable waste in most operating companies sits in the transfers between systems, not inside any one of them. No vendor is …
AutomationAutomate a Broken Process and You Buy a Faster Broken Process
Automation makes a process permanent. Any step you encode without questioning becomes structurally harder to remove than it was th…
Where is your business still running manually?
We review your processes, identify the highest-impact automation opportunities and estimate their financial impact — before anything is built.