Which Business Tasks Should You Automate? Three Failure Patterns to Check First

The problem nobody scores

This is the story behind The 6-Question Automation Check. If you just want the worksheet, it is at the end.

If you run a small business and you already use Zapier, Make, n8n, or an AI agent, you have probably asked yourself some version of this question: which of my recurring tasks should I actually automate?

Most advice answers it with one number: time saved. Count the minutes, multiply by the weeks, automate the biggest number. That is how the free checklists work, and it is how most paid "automation ROI" toolkits work too.

We spent a week reading what operators say after they followed that advice. About 130 first-hand quotes and incidents from 64 public threads and posts across twelve places: r/smallbusiness, r/Entrepreneur, r/automation, Indie Hackers, the Zapier, Make and n8n community forums, and X. Not vendors. Not consultants. People describing what happened to their own business.

Three patterns showed up again and again, and none of them are about time saved.

Pattern 1: the automation that quietly stops

One freelancer's n8n lead-capture workflow for a client's website simply stopped working, and nobody noticed for three days. About 40 leads were lost. The client, worth about $2,500 a month, terminated the contract.

The workflow did not crash. It did not send an error. It just stopped, and nothing in the setup was designed to notice absence.

"A Zapier automation dropped a handoff between two bases. No alert. No error. Three weeks later a customer called asking where her order was. The product had an 8-week lead time."

"My automation broke last month and it took four days to notice. A source went quiet and the system stopped including it instead of flagging it."

"Every automation I've built that failed silently failed the same way. It alerted on errors and never on absence."

In our collection, at least seven different people described a silent failure that ran for somewhere between three days and three weeks before anyone noticed. A green dashboard is not evidence that work is happening.

Pattern 2: the automation that does the wrong thing, confidently

One operator's automation ran clean for six days, then sent an email to the wrong person on day seven — confidently, with nothing in the setup flagging the mistake.

"One mistake: I over-automated client emails at first and sounded robotic. Lost one small deal before I added a human edit step."

"Stripe webhook fires, workflow runs, charge executes. Then Stripe retries the webhook, workflow runs again, charge executes again. Customer gets charged twice."

"One workflow tagged a lead 'hot.' Another one quietly removed the tag two steps later. They'd been fighting each other for weeks."

These are the failures that touch a customer, a client, or money. They are not caught by asking "how much time will this save me". They are caught by asking, before you build, what happens if this sends the wrong thing, and who checks before it does?

Pattern 3: the automation that should never have been built

"Just spent 3 hours rebuilding a Zap that should've taken 10 minutes. The original was 'automated' but broke every time a lead filled a form with a slightly different company name."

"I Spent 6 hours automating a 5 minute task. WHY DO I KEEP DOING THIS TO MYSELF."

"Confession: I once spent 3 hours building a slick automation for a task that took 4 minutes a week because it was way easier than sending one overdue email."

"I was automating ops for a tutoring business. Zapier, Airtable, scheduling plugin, payment integration, WhatsApp plugin. About $800/month total. Worked fine until the logic got complex."

"AI broke my workflow last week. I didn't fix it. I cut it. Cost me 6 hours and $200."

At least ten people in our collection described spending three to six hours, sometimes days or weeks, building or repairing an automation for a task that was small, irregular, or needed human judgment at exactly the step they automated.

What it costs

We tried to put numbers on this using only what people reported themselves. Many posts describe hours or days but no dollars, so the table is deliberately conservative.

None of these people lacked tools. They lacked a five-minute check before building.

What already exists, honestly

Free worksheets for choosing what to automate do exist, and some are decent. One well-known small-business AI guide scores use cases on five criteria and includes a readiness checklist that mentions human review. Vendor community forums publish good rules of thumb: automate what is frequent, rule-based, and end to end in software. Paid toolkits on Gumroad in the $19 to $27 range add ROI calculators and priority scoring.

What we could not find is a tool that treats safety as a hard gate: one that refuses to say "go" when you admit a wrong send or a silent stop would cause real harm and you have no human check in place. In every worksheet we looked at, safety is a consideration. In none of them is it a score that can block the decision.

That gap is the whole reason this toolkit exists.

Our approach

One task at a time. Four scores. Two yes/no questions. One decision.

1. Pick one recurring task you are actually considering automating.
2. Score it 1 to 5 on value, repeatability, input consistency, and safety. Safety means the residual risk of a silent stop, a wrong send, or irreversible harm, given the controls you would actually put in place.
3. Answer two questions. Would a silent stop or wrong send cause material harm? Is there a human confirmation before anything external happens?
4. Read the decision. The worksheet returns GO, NO-GO, INCOMPLETE, or CONTRADICTION. It will not return GO if any score is missing. It will not return GO if you scored safety as fine while admitting harm is possible and no human checks first. That contradiction is the exact mistake behind the wrong-recipient email and the double charge above, and the worksheet is built to catch it.
5. If GO, write down the human checks that stay in place before and after the automation runs. Absence alerts, not just error alerts. A confirm step before the first send to a new recipient. A volume or cost ceiling.

The decision rules are formulas in the spreadsheet, not advice in a paragraph. Two people scoring the same task get the same answer.

Try it on one task now

You do not need the worksheet to run the check once. Take one recurring task you are thinking of automating and answer these six questions honestly.

1. Value (1 to 5): if this were automated well, how much would it matter?
2. Repeatability (1 to 5): does it happen often, the same way, on a schedule you could describe?
3. Input consistency (1 to 5): after you write down any clean-up rule you would apply, how uniform are the inputs it receives?
4. Safety (1 to 5, where 5 is safe with the controls you would actually put in place): what is the residual risk of a silent stop, a wrong send, or something irreversible?
5. Would a silent stop or a wrong send cause real harm (lost leads, a wrong customer message, a double charge)? Yes or no.
6. Is a human confirming before anything goes out to a customer, a card, or a system you cannot undo? Yes or no.

Then apply the rules in this order:

• Any answer missing: not ready to decide. Go back and answer it.
• Safety scored 4 or 5 and harm is possible and nobody confirms first: contradiction. You have described a safe task and a dangerous one at the same time. This is the most common way people talk themselves into the wrong-recipient email.
• Harm is possible and nobody confirms first: no-go, until a confirmation step or an absence alert exists.
• Value, repeatability and input consistency all 3 or above, safety 4 or above, and either harm is not possible or a human confirms first: go. Write down the checks that stay in place before and after it runs.
• Anything else: no-go for now.

A worked example. Auto-replying to new website leads on WhatsApp, with no human confirmation before the first message. Value 4, repeatability 4, input consistency 3, safety 4 on paper (templated messages, structured lead fields). Could a silent stop or wrong send cause harm? Yes: this is the exact setup behind the "40 leads lost in three days" story above. Is a human confirming first? No. Result: contradiction, not go. The fix is not a better template; it is a confirmation step before the first send to a new contact and an alert when no leads arrive for a day. Re-score with those in place and the same task becomes a go.

That is the whole method. Two people scoring the same task with these rules get the same answer.

The worksheet, if you want it done for you

The 6-Question Automation Check is the same method as a spreadsheet: the rules above are formulas in the cells, so it refuses to say go on a missing score or a contradiction, prints the reason, and gives you a one-page decision with the human checks written down. It comes with a short guide, a before-and-after review checklist, and two completed examples (one go, one no-go). It does not build the automation, pick a vendor, or promise a return.

Get it here: The 6-Question Automation Check.

Who made it

We are 4NLab, a boutique technology partner: a team of developers, designers and strategists who believe technology should serve the business, not the other way around. With many decades of combined experience we have helped startups launch and enterprises modernize, and along the way we have built AI and automation tools for many enterprise clients. That work is where this toolkit comes from: we have watched automations run green while quietly failing, send the wrong thing to the wrong person, and cost more to maintain than the task they replaced. We share what we learn through guides and documentation; the scoring method here is the same judgment we apply before we automate anything for a client, reduced to four scores and two questions so a business owner can apply it in one sitting. The research behind it is public, first-hand, and traceable: every quote above maps to a row in the product's claims ledger.