Decide or repeat: sort your tasks before you automate anything
TL;DR
- Before you automate, split your tasks into two lists: the ones you repeat and the ones you decide.
- Three questions per task: are the steps always the same?, what happens if it goes wrong?, who answers for the result?
- A real case Todd has already told: a med spa owner spent 2 hours a day copying forms into the CRM and sending follow-ups one by one. They automated it in one afternoon.
- This week's one thing: write down ten tasks from your week and mark each one "repeat" or "decide."
The short answer. Automate what you repeat and leave with a person what you decide. To tell which is which you don't need a tool: you need a list and three questions.
The common mistake goes both ways. Some people automate a decision without realizing it, and suddenly a machine is answering things a person should have answered. And others keep doing by hand, every day, what anyone could leave running on its own.
A real case: two hours a day
It's a case Todd already told on our blog. A med spa owner copied the forms into the CRM and sent follow-ups one by one. It took 2 hours a day. They automated it in one afternoon.
None of that called for judgment. The steps were always the same: a form arrives, it's copied into the CRM, a message goes out. That's a task to repeat.
The three questions
For each task in your week, answer:
- Are the steps always the same? If you do it today the way you did it yesterday and anyone could follow the steps, it's one to repeat. If they change by customer or situation, it's one to decide.
- What happens if it goes wrong? A reminder that goes out an hour late gets fixed. A wrong discount or a reply that commits to a price doesn't get fixed the same way.
- Who answers for the result? If someone has to face the customer, that person decides.
Two "yes, no risk, nobody has to face anyone" make a task to repeat. Any other combination stays with you.
What the list looks like
A hypothetical example, to show the format:
| Task | Repeat or decide? | Why |
|---|---|---|
| Copy a form into the CRM | Repeat | Same steps; a mistake is fixable |
| Confirm tomorrow's appointment | Repeat | Same message, low risk |
| Answer the price of a custom service | Decide | Depends on the case and commits money |
| Approve a discount | Decide | Money and the relationship with the customer |
With that list in front of you, what to automate first points itself out: the top rows.
Before you run something AI wrote
If you ask an assistant to write the message, the rule or the workflow, spend ten minutes on three questions before letting it run:
- What does it assume? Read what it wrote and look for what it took for granted without you saying so.
- What happens if it's wrong? If the worst case is small, go ahead. If it isn't, it goes on your "decide" list.
- Did I test it first with one case? Just one, before letting it run on everyone.
Even the people who build these tools separate what they read from what they decide: Anthropic says its finance section in Claude is read-only and that it "can't move, manage, or invest your money." To see what an assistant does when you give it access to your apps, read two assistants can get into your apps.
What this method doesn't solve
- It doesn't tell you which tool to use. That comes after you have the list.
- It doesn't promise savings. The 2 hours in the case belong to that business. Yours is measured with your list.
- It isn't a perfect rule. A task can look like one to repeat and hide exceptions. If one surprises you once a month, review it.
- It doesn't replace looking at your real week. The list works if you fill it with what you do, not with what you think you do.
- If your task is about answering outside business hours, see what your agent answers at 11 p.m..
Who should skip it
- If you already have a list like this and review it every month.
- If what you do changes every day and almost nothing repeats: your work is deciding, and that's fine.
- If you don't yet know what you do in a week: before this, write it down for three days.
This week, one task
A short stretch.
- Write down ten tasks from your week, the ones you do most often.
- Mark each one "repeat" or "decide" using the three questions.
- Pick one from "repeat" and write down its steps. That's the first candidate.
Frequently asked questions
To close
Before you automate, separate what you repeat from what you decide. The first you hand to a machine. The second stays with you.
Thanks for reading, and for making it to the end on a Friday.
Keep reading
- What your AI agent answers at 11 p.m., and what it leaves to a person · when the task is answering after hours
- Your business's first AI agent shouldn't decide anything. It should carry your messages · where to start with an agent
- If your AI tool changes tomorrow, what do you still own? · what you keep if a tool changes
- The map of the five SEO disciplines · how customers find you today
- Introducing Personal Finance in Claude, Anthropic · a tool that reads and doesn't decide
Sources
The example in the table is hypothetical. The med spa case is Hub365's and already published:
- Introducing Personal Finance in Claude, Anthropic, November 5, 2026 · https://claude.com/resources/articles/introducing-personal-finance-in-claude
- Why your CRM is useless without lead capture on your website, Hub365 AI · /blog/crm-useless-without-lead-capture-website
