How to hand your AI its first real job (start with something small and boring)
Last time I argued that AI becomes useful the moment you stop chatting with it and start handing it real work. The obvious next question is where to begin. The answer is not your biggest headache. You begin with something small and boring, so that if it goes wrong nothing breaks and you can see at a glance whether it did the job.
Pick something boring
A task you do often where a mistake costs you nothing serious.
Put it all in one place
Gather the files or data together so it can actually see them.
Say what you want
Tell it the end result and show one finished example.
Check the first few
Lay them next to the originals, like a new hire's first batch.
Four steps to hand off your first task.
Pick the right first task
A good first task is one you do again and again, where a mistake costs you nothing serious and you can tell at a glance whether it came out right. Sorting a folder of documents, pulling figures out of a stack of receipts, tidying up an export from one of your systems. Dull work, the kind nobody misses if it wobbles the first time.
Let's take a real one. You've got a folder full of supplier receipts and you need them as a simple list: date, supplier, amount. Normally you'd type that out by hand on a quiet afternoon. This is a perfect first job, because every receipt is a bit different but the thing you want out is always the same.
Put everything in one place
The coworker can only work with what it can actually see. So before you start, gather the inputs into one spot. Drop all the receipts into a single folder, or paste the data into one sheet. You're not doing anything clever here, you're just laying the work out on the desk so it can get started.
Tell it the outcome, and show one example
Here's the part most people get wrong. They explain how to do the task, step by step, as if writing a manual. You don't need to. Tell it what you want at the end instead: "Go through every receipt in this folder and give me a table with the date, the supplier and the amount." Then, if you can, show it one row you've filled in yourself. That single finished example does more than a paragraph of instructions, because now it knows exactly what good looks like.
The result
| Date | Supplier | Amount |
|---|---|---|
| 03-05-2026 | Van der Berg Kantoorartikelen | € 84,15 |
| 07-05-2026 | Tankstation De Brug | € 71,40 |
| 12-05-2026 | Drukkerij Snelder | € 312,00 |
| 19-05-2026 | Café De Hoek | € 48,60 |
| 24-05-2026 | Groothandel De Vries | € 156,75 |
Want to try it on the exact example above? Use this prompt:
Go through every receipt in this folder and give me a table with the date, the supplier and the amount.
Five sample receipts (fictional suppliers and amounts) so you can run it yourself.
Download the receipts (.zip)Check the first few yourself
Treat the first run like a new hire's first batch of work. Don't wave it through. Take the first handful and check them against the original receipts. If it misread a total or put the wrong supplier, just say so plainly, and it will correct itself. After a run or two comes back clean, you can trust it with the rest and only spot-check now and then.
The real win is next month
The point was never this one afternoon. It's that the next time the receipts pile up, the job is already worked out. You keep the instruction you wrote the first time, hand over the new folder, and what used to be an afternoon is now ten minutes and a quick check.
So don't go looking for the perfect, impressive task to start with. Start with the boring thing nobody would notice if it wobbled, get one clean result, and you'll spot the next ten places it fits on your own.