Is This Task Worth Automating?
A straight framework for deciding whether AI belongs in a workflow, or doesn't.
Not every task should be automated. Most AI advice skips this part and goes straight to the tools. That's how you end up with a complicated workflow that saves you four minutes a week and breaks every time something changes.
Here's how to decide before you build anything.
The three questions worth asking
1. Does this task happen enough to justify the setup?
Automation has a fixed cost: the time it takes to build, test, and learn the workflow. If the task happens twice a month, that cost may never pay off. If it happens every day, it almost certainly will.
A rough rule: if a task takes more than 30 minutes a week and follows a consistent pattern, it's probably worth automating. Under that, be skeptical.
2. Is the output consistent enough that AI can produce a useful first pass?
AI is good at tasks where the structure is predictable even when the content varies. A proposal changes every time, but the sections, the format, the tone, and the questions it answers are usually the same. That's an AI task.
A conversation with a difficult client is different every time in ways that matter. That's not an AI task.
Ask yourself: if I wrote down the instructions for this task clearly enough, could a smart assistant who has never worked in my business produce something I'd be willing to edit? If yes, AI belongs here. If no, it probably doesn't.
3. What happens when it goes wrong?
Every AI workflow will produce a bad output eventually. The question is whether a bad output is a minor inconvenience or an actual problem.
Automated meeting notes that miss something? Annoying, fixable. An AI-drafted contract clause with an error that goes out unsigned? That's a different category of problem.
The higher the cost of a mistake, the more human review you need in the loop. That's not a reason to avoid automation. It's a reason to design the workflow correctly.
A quick scoring method
Score each task from 1 to 3 on each of these:
| 1 | 2 | 3 | |
|---|---|---|---|
| Frequency | A few times a month | Weekly | Daily or near-daily |
| Consistency | Different every time | Similar structure, variable content | Almost identical every time |
| Cost of error | High: hard to catch, expensive to fix | Medium: catchable with review | Low: easy to spot, easy to fix |
Add the scores. 7 or higher: strong automation candidate, start here. 5-6: worth trying, build in a review step. 4 or below: probably not worth it yet.
The tasks that almost always score high
For professional services businesses: first-draft proposals, client intake summaries, follow-up email sequences, meeting notes, contract first drafts, monthly client reports.
For local service businesses: estimate request responses, appointment confirmations and reminders, review response templates, FAQ responses, social media posts, job completion follow-ups.
The tasks that almost always score low
Anything where the relationship is the whole point. Anything where a wrong output creates legal or financial exposure without an obvious review step. Anything that happens so infrequently that building a workflow costs more than just doing it.
What to do with this
If you have a task that scores 7 or higher and you're not sure where to start, the AI Workflow Self-Assessment will help you prioritize across your whole business. If you're ready to build, the AI Workflow Audit is where we take this further together.
Let's find where AI fits your business.
Tell us how the business runs today. We'll find what helps.