Which work should you automate first?

Most businesses have a long list of tasks that someone would happily never do again. Choosing which one to automate first decides whether the project pays for itself quickly or drags on.

Start with volume

Pick work that happens many times a week. Entering invoices, copying orders between systems, sending the same follow up emails and building the weekly report are common examples. A task done twice a month rarely repays the effort of automating it.

Prefer clear steps

If you can write the task down as a checklist, it is a good candidate. Where a step needs reading or judgement, such as sorting emails by what they ask for, a language model can now handle it, but the steps around it should still be fixed and checked.

Count the cost of a mistake

Some errors are cheap to fix, like a report sent an hour late. Others are expensive, like a payment sent twice. Begin where mistakes are cheap, and add a review step wherever money, customers or legal records are involved.

Measure before you start

Note how long the task takes today and how often it goes wrong. Without that number, nobody can say later whether the automation worked.

What a first project looks like

A good first project is small enough to finish in a few weeks and visible enough that the team notices the difference. Once it runs reliably, the next task is easier to choose, because everyone has seen what automation can and cannot do.