Workflow automation

9 signs a process isn't ready to automate (and what to fix first)

Workflow automationBy Fiona Wang8 November 20269 min read
Illustration for Singapore B2B provider matching and regulatory benchmarks
Public sources cited 2026 S$ Fee Benchmarks 1–5 Free Quotes
Illustration of an open book whose pages turn into signal waves

In short: Automation runs the process you already have, faster and more often. If three people describe it differently, every case is an exception, or nobody can tell a bad result, fix that before you connect a tool. A checklist at the end is the go or no-go.

A phrase that shows up in search suggestions is “when not to automate”. It says nothing about how many people search for it. It does match a question owners actually ask after something has already gone wrong: a poster who described themselves as running lean asked whether anyone had a “should never have automated that” moment that moved the line. In the same thread they reported a quote that went out on the wrong terms because nobody paused it. That report is theirs. It was not checked, and it is not a rate of failure.

The myth worth retiring is that automation repairs a messy process. It does not. It runs the process you have, more often, including the part you had been quietly correcting by hand. The work before a tool is to make the process describable, owned, and checkable.

Each sign below is a reason to wait, what to do instead, and the condition that would make a later build reasonable. None of them is a statistic.

Buyer guide illustration for 9 signs a process isn't ready to automate (and what to fix first)
1Tell us the needScope, budget, timing2Concierge callWe confirm requirements3Registry checksACRA, licences, fit41–5 introductionsCompare quotes free5You decideDecline any; nothing owed
How FYAdvisers matching works
Checklist before you hireEntity is live on ACRA BizFile+ (check the UEN)Relevant licence or registration: ACRA PAC, MAS, IPOS, MOM or Law Society as applicableNamed person who will do the work, and their qualificationWritten scope and fee, with what counts as out-of-scopeProfessional indemnity insurance and engagement letterDeadlines mapped: AGM, Form C, GST, licence renewals
Singapore B2B Vetting & Concierge WorkflowHow we verify and match 1 to 5 providers for your brief
01
Registry & Licence CheckACRA, MAS, CSRO, BCA, MOM & ISO status verified
02
Scope & 2026 Fee AuditItemised S$ benchmarks with hidden traps flagged
03
1 to 5 Vetted QuotesCompare proposals from matched Singapore firms
04
100% Free for BuyersZero obligation; providers fund the service

1. Three people describe three different processes

Ask the person who starts the work, the person who finishes it, and the person who gets shouted at when it fails. If the steps do not match, you do not have a process to encode. You have a negotiation.

Automation makes this worse because the software picks one version and applies it to every case. The other two versions survive in people’s heads and in side spreadsheets. Fix it by writing the current path, including the exceptions, in the shape a pilot checklist asks for: trigger, inputs, the system that is authoritative, outputs, owner, escalation. It is ready when those three people can point at the same page and say what happens on a Tuesday exception, not only on the happy path.

2. Every case is “it depends”

Some work is judgement wearing the costume of a process. Credit for a long-standing customer, a discount that is really an apology, a reply to an angry email. If the useful step is the judgement, a workflow can gather the file and stop. It should not take the decision.

The fix is a template or a checklist the person still completes, which is the “keep manual” rung of the approval ladder. It becomes ready to automate only for the slice that does not depend: filing the email, creating the task, reminding the owner. The decision stays put.

3. It happens a few times a year

A rare task can still be painful. The build, the test and the remembering-how-it-works six months later are a standing cost. A one-page checklist beside the calendar reminder is often the whole design. This is a judgement about effort, not a formula and not a payback period. Nobody has established a number of runs that “repays” a workflow.

It is ready when the rare task is actually a monthly one you had been batching, or when the rare task is so dangerous that the checklist itself needs an audit trail. Even then, start with the record, not with a large platform.

4. The inputs are not in a system

If the facts arrive as a voice note, a WhatsApp paragraph or a photo of a whiteboard, the workflow has nothing stable to read. People then build a brittle parser and call the parser the process.

Fix the intake first. A form with required fields, a shared mailbox used only for that work, or a photo that is attached to a job id. The first-automation list puts structured filing early for this reason. It is ready when a new item can be pointed at without someone retyping a chat.

5. Nobody owns the outcome

A workflow without an owner is a machine that fails into a void. A reply visible only as a search excerpt, on a thread whose opening poster was building a tool rather than running one, said that when something breaks weeks later it is often hard to tell what failed. That is one person’s report. The design response does not need it to be universal: name the person who receives the exception, and write where a failed item waits.

Zapier’s own help, updated 29 May 2026, says error emails go to the account email by default, and that a frequency of “Never” is available and not recommended. It also says Zapier will not send an error email when an error handler runs. So “we turned notifications on” can still mean silence. The maintenance guide is where failure types and replay belong. The process is ready when that named person can show you last month’s exceptions without opening a vendor console.

6. The process is about to change

A new accounting file, a new price list, a new legal entity, a warehouse move. Building against the old shape creates a workflow you will throw away, or worse, one that keeps applying the old rule after the business has moved.

Wait. Write the future steps only when someone can sign them. If you must bridge the gap, limit the workflow to a copy that does not write back into the system that is about to be replaced.

7. You cannot tell when it is wrong

If “correct” is a feeling, you cannot test the workflow and you cannot alert on it. Define a check a stranger could apply: the invoice number matches, the quantity is not above the order, the recipient is on the approved list, the task has an owner. Until that sentence exists, do not connect the last step.

The maintenance guide assumes you can tell a bad item from a good one. A missing-run is a separate problem from a wrong run. Both require a definition of expected behaviour. Ready means you can write three test cases: an ordinary item, a duplicate, and one that must stop.

8. The first version touches money or a customer

Bank details, payment release, a quote, a renewal, a chaser to a customer who is already in dispute. These can be automated later, around a person. They are a poor first build because you have not yet learned how the tool fails.

Put a draft in front of a named approver. The supplier bank-detail control and the approval ladder are the patterns. Ready means the approver can reject, the rejection sticks to that version, and a timeout does not send the item anyway.

9. The team does not trust the system, so they keep a second copy

Double-keying is a sign, not a character flaw. On a HardwareZone thread in June 2025, a poster who described themselves as in charge of process and projects complained that a colleague still keyed every invoice into both the accounting system and Excel three years on. A reply suggested the system might not make totals easy, so the spreadsheet was the working report. That is one workplace, paraphrased, not a portrait of Singapore SMEs. Use it as a question: what does the spreadsheet calculate that the system does not show?

Do not automate a third copy on top of the two they already keep. Find the missing total, the missing exception, or the fear of being blamed when the system is wrong. The rollout plan is the sequence. It is ready when the person who kept the sheet agrees the screen replaces the reason they kept it, not when a manager bans the file.

Myths that push teams into these nine

“AI will handle the exceptions.” A model can draft or classify. It does not own the exception queue unless you build one and staff it. Ask for the path and the test, as in the pilot checklist.

“Once it is built it runs itself.” Credentials expire and fields move. Zapier documents that you can switch error mail off. Other products differ. Read the maintenance guide before you believe a set-and-forget claim.

“The tool is cheap, so the automation is cheap.” The subscription is one line. The design, the exceptions and the person who watches it are the rest. Compare quotes on the cost worksheet. How tasks and credits accumulate is the billing explainer, which is not a price list.

A yes-or-no list you can print

Answer for one process, not for “automation” in general.

# Ready only if you can say yes
1 The people who do it agree the steps, including the usual exception
2 Judgement is either removed from this slice or explicitly left to a person
3 It happens often enough that a checklist alone is getting painful, or the risk justifies a record
4 New items arrive as fields, not only as chat
5 A named person owns exceptions
6 The process will still look like this in three months
7 You can describe a wrong output in one sentence
8 This version does not move money or contact a customer without a person
9 The team’s parallel spreadsheet, if any, has a known reason you are willing to fix

Two or more “no” answers means fix those items first. Do not buy a platform to resolve them.

A thin slice is still allowed

Failing the list does not mean the team must keep doing every click by hand. It means you may not call the whole process automated. Take sign 4 and sign 8 together. Messages still arrive as chat, and the tempting build would reply with a price. The allowed slice is a form that creates an internal task. The reply stays on the manual rung. Write that boundary in the pilot so a builder does not “helpfully” close it. The same move works for sign 2: gather the file automatically, leave the judgement on a checklist a named person completes. If you cannot describe the slice in two sentences, it is not thin enough.

Illustrative scenario

Illustrative scenario, not a clinic we work with and not an outcome. An administrator wants online booking because the phone keeps ringing. Walked against the list, the process fails the input test: patients still describe the need in a free-text message, and the diary rules are about to change because a doctor is joining. It also fails the “about to change” test. The useful step is a short form that captures who, what and when, reviewed by the administrator, with automation limited to putting that form on a task. The booking rules are revisited after the new doctor’s hours exist. No reduction in calls is claimed.

What this list will not do

It will not tell you the percentage of projects that fail. That number is not established here. It will not rank tools. If the nine answers are yes, go back to what to automate first and pick one slice. If staff are the reason a good system sits idle, use the rollout. If the spreadsheet is the system, use outgrown spreadsheets.

The same stop applies before a model: an AI readiness assessment should be allowed to say no, and a trial needs the AI pilot acceptance checklist.

To walk one process through the nine rows, use the workflow service or WhatsApp +65 9071 3976 (chat). This is operational guidance, not a guarantee that a process is safe to automate.

Frequently asked questions

Is it always a mistake to automate a broken process?

It is a mistake to automate the broken part and then trust the output. You can still automate a thin, stable slice beside it, such as filing a document, while the judgement stays manual. Name that slice. Do not describe the whole messy process as automated.

Can I automate only part of a process?

Yes. That is often the right scope. Copy the fields, remind the owner, and stop before the step that changes money or a customer promise. The human-approval guide is the line between those parts.

Who decides the process is ready?

The person who owns the outcome, after the people who do the work agree the steps and the exceptions. A vendor can show a demo. They cannot declare your process ready.

What if a vendor says the AI will handle the exceptions?

Ask for the exception path in writing: where an unsure item goes, who sees it, and the test pack that includes an exception. A pilot checklist is the format for that question. A slogan is not an answer.

Chat on WhatsAppConcierge · +65 9071 3976
Get Free QuotesWhatsApp Us