Seven jobs worth handing to AI first, and three to keep

Most people pick the most impressive job first. It is the wrong one. The jobs worth handing over first are boring, repeat on a schedule, and have an obvious right answer, because those are the ones where you will notice immediately if something goes wrong.

Here is the order I use, with the reasoning, so you can disagree with it in a specific way.

The seven worth handing over

1. The weekly summary you write from the same sources

Whatever you assemble every Monday from the same three places. It repeats, the inputs are stable, and you already know what a good one looks like, so you can grade the output in ten seconds. That last part is what makes it the right first job.

2. Reading your inbox, not answering it

Sorting, grouping and summarising what arrived is safe. Replying is not. Split them: let it do the reading for a few weeks and keep the sending for yourself. You will learn more about whether you can trust it in those weeks than from any demo.

3. Receipts and invoices into a spreadsheet

Photograph it, forward it, drop it in a folder. Amount, date, vendor, filed where your bookkeeper expects. The thing that makes this work is insisting it flag what it could not read rather than guessing. Three unreadable receipts in a pile beats three invented numbers.

4. The first draft nobody sees

Proposals, listings, job posts, follow-ups. A first draft is low risk by definition because it is not going anywhere without you. This is the highest-value, lowest-danger job on the list and it is the one most people skip because it feels like cheating.

5. Finding things in your own files

Not organising them. Finding them. "Which supplier quoted under four hundred in March" is a question your folders already contain the answer to, and answering it costs you twenty minutes every time.

6. Turning one thing into five

One article becomes an email, three social posts and a page section. The source already exists and you can see at a glance whether each output is faithful to it. Low risk, immediate leverage.

7. Watching for the thing you keep forgetting

A renewal, a filing date, a follow-up that goes cold at day four. A job that does nothing most days and speaks up on the one day it matters is worth more than it looks.

The three to keep, for now

Anything that sends. Email, messages, posts, anything that reaches another human. Not because the writing is bad, but because a mistake here cannot be taken back and the cost lands on someone who did not sign up for your experiment.

Anything that moves money. Payments, refunds, invoices going out. The same logic, with a number attached.

Anything that deletes. Renaming is reversible. Deleting is not. Every setup I build puts deletion behind an explicit approval, and I have never once regretted it.

The pattern underneath

You will notice the three to keep have one thing in common: they all reach outside your own machine. That is the line worth drawing, and it is a better line than "simple versus complex", because it does not change as you get more confident. A job that only reads and writes inside your own files can be wrong and recoverable. A job that sends, pays or deletes is wrong and permanent.

When you do eventually hand those over, hand them over with a stop in front of them, so the work happens automatically and the irreversible step waits for a human. That is the whole design, and it is what the console on the home page demonstrates.