By Nazreen Daud, Malay web consultant and marketer in Singapore, founder of Mulacan · Originally shared on LinkedIn, 9 October 2026
The short answer: the most expensive automation in your business might be the one nobody remembers building. Before your next long weekend, check four things: does someone own each automation, how many hand-offs between apps could quietly break, does your customer data live in one place, and will anything tell you when it stops?
What can go wrong with "set and forget" automations?
I read a story this week that every small business owner should hear: 14 automations, one expired login, three days of silence.
A small team ran social media for two brands. Their setup was 14 Zapier automations, a Google Sheet acting as the posting queue and, in their own words, "a webhook nobody remembers writing".
Over a long weekend, one login connection expired. Nothing posted for three days. Nobody noticed until it was already done.
That's the painful part. Not the outage itself, but the silence. Everything looked fine because nothing complained.
How do automation setups get so messy?
It rarely starts as a mess. One automation solves one problem. Then another. Then someone adds a sheet to hold it together. Each step makes sense at the time.
A few years later, the business runs on a chain of hand-offs that nobody fully understands, and nobody owns.
Swap "social posts" for "enquiries" and you can see why this matters for any service business. If the automation that sends new website enquiries to your inbox breaks quietly, you don't lose a few posts. You lose clients who think you ignored them.
Should small businesses stop using automation or AI agents?
No. Automation and AI agents genuinely help small teams do more with less. The answer isn't to give up on them. The answer is to set them up properly, with clear ownership and a way to know when something stops.
The four-question automation check
Save this and run it before every long weekend or holiday.
| Question | Why it matters | A good answer looks like |
|---|---|---|
| 1. Does someone clearly own each automation? | Unowned automations break and nobody feels responsible for fixing them | A simple list: automation name, what it does, owner |
| 2. How many hand-offs between apps could quietly break? | Every connection between two tools is a login, a token or a format that can change | As few hand-offs as possible for the critical paths |
| 3. Does your customer data live in one place? | Data scattered across sheets and apps is hard to check and easy to lose | One system holds contacts, enquiries and bookings |
| 4. Will anything tell you when it stops? | Silent failure is the real cost | An alert, a daily summary, or a person who checks |
1. Give every automation an owner
Write a short list. For each automation, note what it does, which apps it connects, and who looks after it. If the answer is "the person who left last year", that's your first job.
2. Count the hand-offs
Trace your most important flow, usually the path from a new enquiry to a reply. How many apps does the data pass through? Each hand-off is a place where an expired login or a changed field can break things without warning.
3. Keep customer data in one place
When enquiries, contacts, bookings and follow-ups live in one system, there's less to connect and less to break. It's also much easier to see at a glance whether today looks normal.
4. Make failure noisy
The 14-automation team didn't suffer because something broke. Things break. They suffered because nothing told them. Turn on error notifications where your tools offer them, and pick one simple daily check, such as "did today's enquiries arrive?".
Not sure what's quietly holding your business together? Book a call with me and we'll map your enquiry-to-booking flow together.
Why I prefer one business system over a patchwork of tools
That's why I lean towards one practical business system over a patchwork of tools. With Mulacan, the CRM and marketing automation platform I founded for service businesses, enquiries, contacts, booking and follow-up sit in one place, so there are fewer hand-offs to quietly break.
That doesn't mean one tool must do everything. It means the path your clients take, from first enquiry to booked appointment, shouldn't depend on a webhook nobody remembers writing.
Be honest: if one login expired tonight, how long before you'd notice? Hours, days, or "what login?"
FAQ
What is the biggest risk with Zapier or other no-code automations? Silent failure. A login or connection expires, data stops flowing, and nothing alerts you. The automation itself may be fine; the problem is that nobody owns it and nobody is told when it stops. Clear ownership and error notifications reduce that risk a lot.
How many automations is too many for a small business? There's no magic number. The real question is whether each one has an owner, whether you know what it connects, and whether you'd notice if it stopped. Fourteen well-documented automations can be fine; three undocumented ones on your enquiry path can be risky.
Should my enquiries and bookings be in one system? For most service businesses, yes. Keeping enquiries, contacts, bookings and follow-up in one place means fewer hand-offs between apps, fewer logins to expire and an easier way to check that nothing has been missed.
How do I know if an automation has stopped working? Turn on error notifications in each tool where available, and add one human check for your most important flow, such as confirming that today's enquiries arrived. A daily or weekly summary is better than finding out from an unhappy client.
Next step
If you want a business system that doesn't need babysitting, book a call with me. Read more about me, browse the tools I use, or see all my ventures, including Mulacan.