Most statements about automation are not wrong. They are half right — and the missing half is exactly where projects go wrong. Here are five we hear regularly.
Five half-truths, and what is missing
“Once it’s built, it runs by itself.”
Systems around it change every month — APIs, data, people. Every automation needs an owner and monitoring.
“No-code means no developer is needed.”
No-code removes typing, not thinking. Logic, error handling and testing still need someone who understands them.
“Automation saves headcount.”
It mostly saves time and errors. The people are still needed — for exceptions, for customers and for the system itself.
“The cloud is always available.”
Cloud services fail, change and get discontinued. Availability is a design goal, not a property of a provider.
“We’ll add monitoring later.”
Later usually means after the first silent failure. Monitoring belongs in the first version.
Each of these half-truths is convenient in a sales pitch. Each of them costs money when it meets reality.
Why half-truths are so persistent
Half-truths survive because the first months confirm them. The new workflow runs, the dashboard is green, the saved hours are real. The missing half appears later — when the original builder has moved on, when an interface changes, when a job stops without telling anyone.
The full truth in one sentence
Automation is a system like any other: it needs an owner, tests, monitoring and maintenance. Planned that way from the start, it pays off for years. Treated as a one-off shortcut, it becomes one of the most expensive pieces of software in the company — precisely because nobody sees it.
Read more on each point: The Automation Nobody Owns · The Silent Failure: When Automations Stop Without Telling Anyone · When an API Changes Overnight: Dependencies You Don’t Control.
If it runs your business, treat it like a system — not like a shortcut.
Want automation that is planned as a system from the start? We build, run and monitor systems ourselves — and we know where automation pays off and where it becomes a risk.