# Should I automate this task, delegate it to AI, or just stop doing it?

- URL: https://www.agentskillpacks.com/guides/automate-or-delegate-a-task
- Updated: 2026-10-21
- Book: The Leverage Stack by İsmail Günaydın (https://www.agentskillpacks.com/books/the-leverage-stack)

## Short answer

Every task has only four options: delete it, automate it, delegate it, or do it yourself. Ask in that order and stop at the first yes. Would anything break if it stopped? If not, delete it. Is it the same every time with no taste needed? Automate it with a rule. Does it need a head, but not yours? Give the first draft to AI and review it. Only what is left is yours to do. The order matters because each option is cheaper than the next.

**The four things you can do with any task, from cheapest to most costly**

| Option | Ask this | What it costs you | Example from the book |
| --- | --- | --- | --- |
| Delete | Would anything break if it stopped? | Nothing, and it lasts forever | A mood board no couple ever opened |
| Automate | Is it the same every time, with no taste needed? | One setup, then it runs free | The gallery delivery email |
| Delegate | Does it need a head, but not mine? | A brief, plus a quick review each time | The first draft of a new inquiry reply |
| Do | Is it still here after the first three? | You, every single time | Deciding if a couple is the right fit |

## How to read the four options

The table runs from cheap to costly, top to bottom. That is the whole trick.

A deleted task costs nothing and never comes back. An automated task costs one setup and then runs for free. A delegated task costs a brief once and a short review every time. A task you do yourself costs you, the scarcest thing in your business, on every single repeat.

So you want each task to fall out at the cheapest row it can. Ask the four questions in order, top to bottom, and stop at the first yes.

Most owners run it the other way. They treat every task as a Do until proven otherwise. That is how the pile stays on your desk. Flip it. A task has to earn its place there.

## The order matters more than any single call

Say you skip the first question. You take the weekly report nobody reads and build a smart system that writes it for you. Now it is worse. It still wastes the reader's time, it cost you a setup, and it is harder to kill because it looks like a system.

That is the most costly mistake in the chapter, and it feels like progress while you make it. Faster waste is still waste.

One more rule makes the calls quicker. If you write "well, it depends on the client," look hard at the "depends." Is it your judgment, or a rule you never wrote down? Often it is a rule. That makes it a Delegate with a good brief, not a Do.

## When should you not automate a task?

Most advice says automate anything that repeats. The book adds a second question before you build: what happens the day this rule fires wrong? Rank each task by how often it happens and by what a mistake would cost.

|                    | Mistakes cost little                                                                             | Mistakes cost a client                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Happens often**  | Automate first. Adding a booked client to the calendar, filing an entry, a standard confirmation | Automate, but with a check on top, or keep it by hand until the rule has proven itself for weeks |
| **Happens rarely** | Leave it by hand. A rule for something that fires twelve times a year is rarely worth the build  | Keep your finger on it. Do not start here                                                        |

Two plain tests help you sort the bottom-right box. Could you write down how you make the call, so a stranger would do it the same way? And can you name the exact harm a rule would cause? If you can write it down, it is a procedure, and procedures can be automated. If you cannot name a harm, you may just like doing it yourself.

The book's sharpest example: wiring the final gallery delivery to send on its own, and one day it ships the wrong couple's photos with your name on it. A final send like that earns a human check, even when the rest of the process runs by itself.

## Some tasks are three tasks wearing one coat

A monthly newsletter does not fit one row. It is three jobs. Deciding what is worth saying is a Do. Drafting it is a Delegate. Sending it on a schedule is an Automate. Cut a task at its seams first, then sort the pieces.

And some tasks fit the Do row today only because no brief exists yet. Mark those "Delegate, pending." They are yours until you write the instructions, not forever.

The reverse case matters too. A refund request has a real human call inside it. Do not automate the call. Automate everything around it, and leave the decision as a clean, fast Do.

## Sunday night, a list of twelve

Nadia, the wedding photographer in the book, sat at the kitchen table with twelve tasks she had marked as habit. Twelve things to fix, and seven months of albums still owed. The list had named the problem. It had not shrunk it.

So she ran each one down the four rows. One pass, no agonizing. Two went to Delete. Four went to Automate. Three went to Delegate. Three stayed as a Do: editing the gallery, building the shot list, and deciding if a couple was the right fit.

She killed the mood board that night in about four minutes. Then she did the step most people skip. She deleted the reminder that told her to build the next one. A delete is not done until the trigger is gone, or the task crawls back within a month.

It cost her zero bookings and gave back an afternoon a week.

I like this chapter best of all because the biggest win in it uses no tech at all.

## Where The Leverage Stack takes this next

This is the problem [The Leverage Stack](/books/the-leverage-stack) was written for.

Chapter 2, **The Inventory**, gives you the Task Triage Sheet, more before-and-after cases, and the four ways people sort the pile wrong, including cutting a quiet task that was actually holding things up.

Chapter 1, **The Bottleneck**, builds the list you sort here. Chapter 8, **The Human Layer**, guards the Do row, so it stays small but never empty. If you fear handing off too much, read [what work should stay yours](/guides/what-work-should-i-never-hand-to-ai).

Why bother sorting at all? The [NBER study of AI at work](https://www.nber.org/papers/w31161) found AI help lifted the least experienced workers the most, up to 34% per hour. And the [Census Bureau](https://www.census.gov/library/stories/2025/07/nonemployer-business-growth.html) shows how many of us now run with no staff to hand work to. The triage sheet is in the [free workbook](/workbook/the-leverage-stack).

## Where this is in the book

- The Inventory
- The Bottleneck
- The Human Layer

Kindle: https://www.amazon.com/dp/B0H6MP1WG9
Paperback: https://www.amazon.com/dp/B0HKG9KJJZ

Links go to Amazon. I wrote this book and earn a royalty on every sale.

Part of The Solo Operator Series, five short books that can be read in any order.

## Is the book for you?

- Yes, if You have a long list of tasks and freeze when you try to decide what to hand off
- Yes, if You suspect some of your work does not need doing at all
- Yes, if You keep calling everything 'only I can do this'
- Skip it if You want a list of apps to automate things with
- Skip it if You already know exactly which tasks you will hand off

## FAQ

### How do I decide what to automate in my small business?

Use the index-card test. If you could write the steps on one card and a stranger would get it right every time, with no 'it depends', it can be automated. Turning a paid invoice into a bookkeeping entry passes. Choosing which client to call back first does not.

### What is the difference between automating and delegating?

Automating is a rule that runs the same way every time and needs no taste. Delegating is handing a task to a head that is not yours, like an AI drafting the first version of a reply, which you then review. Automate costs one setup. Delegate costs a brief and a quick look each time.

### Which tasks should a solopreneur stop doing?

The ones where nothing breaks if they stop. The weekly report nobody reads. The 'just checking in' email that brings three more emails. If you have done a task for over a year and cannot remember who asked for it, lean toward deleting it.

### What tasks can AI do for a small business?

Tasks that need a head but not your head. A first draft of a reply. Research on three options so you only choose. A rough set of captions you then edit. AI does the first 80% and your judgment touches the last 20%.

### Should I automate a task I only do four times a year?

Usually not yet. A rule on a weekly task pays you 52 times a year. The same setup on a quarterly task pays four. Sort the task by type first, then let how often it happens decide if it is worth building now.

### When should you not automate a task?

When a wrong run would cost you a client, and when the task is too rare to be worth the build. Ask what happens the day the rule fires wrong. High-stakes sends, like a final delivery going out under your name, should keep a human check on top. Rare, low-stakes tasks can simply stay by hand. Start with frequent, low-stakes tasks, where a mistake teaches you cheaply.