What work should you hand to AI first? A simple way to pick

You know AI can do things. You do not know where to start, and the wrong first pick burns a week and makes you think it does not work. The first job you hand over should be boring, repeatable and easy to check. This guide gives you a test to pick it.

The four-question test

Run each task on your list through four questions.

1. Does it repeat? Weekly beats one-off. If you do it again and again, the setup pays back.
2. Is there a clear finished state? "Board updated" is clear. "Make the client happy" is not.
3. Can you check it fast? If reviewing takes as long as doing, skip it for now.
4. Is a mistake cheap? Pick work where a wrong answer is a ten-minute fix, not a lost client.

Score each task. Anything that gets four yeses is a starter job.

Good first jobs

• Meeting follow-ups. Pull action items out of a transcript and assign them.
• Task board upkeep. Update statuses and add notes from what happened.
• Drafting documents and slides from notes you already have.
• Sorting transactions in your bookkeeping tool. See automate bookkeeping with AI.
• First-pass replies to common support questions. See automate customer support with AI agents.
• Customer research and lead matching. See AI agents for sales and marketing.

Jobs to keep with a person for now

• Anything that moves money without a second check.
• Sensitive conversations with clients or staff.
• Legal, medical or tax judgment.
• Work where you cannot tell a good result from a bad one.

You can move these later, in small steps, once you trust the loop.

A day in the life: handing off meeting work

Here is the day Tomi describes for automating a computer-based job.

You join a meeting. A tool records and transcribes it. Tomi uses Wispr Flow for this. If your workplace has an approved meeting note taker, use that instead. Tell participants and get any consent you need.

When the meeting ends, you tell an AI assistant to look at the to-dos and action items from the meeting and start working on them. It reads the notes and pulls out what you said you would do. Then it starts on the things it can handle. If a task board needs updating, an AI browser such as Aside opens the site and updates the board. Tomi uses Aside for this because it can actively control websites. He also uses ChatGPT.

Then you go to the gym, take the dog out, or spend time with your kids. At the end of the day, you come back and review what got done. That review is the job. If it is all good, your work is done.

Two notes. First, "review" means real review, not a glance. Second, do this only in a way your employer permits. Check your model provider's data settings, such as OpenAI's data controls. Turning training off does not delete saved chats.

Make the first job small

Tomi's advice for building an AI employee is to start with one job you actually need help with. Give it relevant information, useful memory and only the access its job needs. Not your whole inbox, not every tool.

Write the job as a short brief:

1. What it is for, in one sentence.
2. What it may read and what it may change.
3. What "done" looks like.
4. What it must hand to you.
5. When you will review.

How we do it at SupaKid Studios

Our whole approach rests on one idea Tomi repeats: your job, and your team's job, is to define the input and review the output. The loop between the two has to be fast and small. If the result is not what you expected, you improve the input.

That is how we pick first jobs for clients. Blockwise, a small accounting firm run by two brothers, let their bookkeeper go and was categorizing transactions by hand. The first thing we showed them was how to hand their QuickBooks bank feed to an AI bookkeeping agent. It was repeated, rule-based and easy to check, which is the exact profile in this guide.

If you want agents to run a set of jobs for you, our managed AI agent team is built for that. Our studio team sets up, runs and manages the agents, and you approve anything that goes out.

What goes wrong

• Starting too big. "Automate my business" is not a job.
• No review. Small errors become big ones.
• Too much access. Give the minimum.
• Judging by one run. Run it a week before you decide.
• Hiding it from your team. Tell people when an agent is involved.

Your next step

Write down ten tasks you did this week. Score them with the four questions. Pick the highest score. Spend one hour writing the brief and one week running it with review.

If you want a second opinion on your list, book a 30-minute call with SupaKid Studios. We will help you pick the first job and say plainly what to leave alone.