Back to all posts · Guide

What should a small business automate first? Five questions that pick the task.

Most owners who look at automation start in the wrong place. They pick the biggest, messiest problem in the business, the one that has frustrated everyone for years, and ask software to fix it. Six months later nothing is running.

The businesses that get somewhere do the opposite. They pick one small, boring job, hand it off, and watch it work. Then they pick the next one.

So which job? These five questions will find it.

1. What does your team do more than twenty times a day?

Volume is the first filter. A task that happens twice a month is not worth building anything for, however annoying it is.

Walk through the office and count. Typing orders from an email into the system. Checking a customer's insurance in a web portal. Moving a form into a record. Entering supplier invoices. The tasks that come up again and again, all day, are your candidates.

2. Is it done the same way each time?

Ask the person who does the task to explain it. If the answer is a short list of steps, that is a good sign. If the answer starts with "well, it depends", keep looking.

A useful test: could your best employee write the rules on a single page? If yes, the task can be taught. If the rules live in one person's head and change with the day, sort that out first. Automating a process nobody agrees on only makes the disagreement faster.

3. Where does the information come from?

Good first tasks start with something concrete: a faxed form, a PDF, an email, a row in a spreadsheet, a screen in a program you already use. Someone reads it and types it somewhere else.

That reading and retyping is exactly the work software now does well, even when every form looks a little different.

4. What happens when it goes wrong?

Every task has mistakes. The question is who catches them.

Pick a task where a person already reviews the result before it matters. A pharmacist verifies a prescription. A manager approves a bill before it is paid. A front desk confirms coverage with the customer. That review stays in place, so a wrong entry is caught the same way it is today.

Avoid starting with anything that goes straight to a customer with no one looking.

A good first task and a poor one

Good first task

  • Done many times a day, the same way each time
  • Starts from a form, a fax, an email or a screen your team already reads
  • Has rules your best employee could write on one page
  • A mistake is caught by a person before it matters
  • Your team would be glad to hand it over

Poor first task

  • Happens a few times a month
  • Depends on a judgment call that changes case by case
  • Nobody agrees on how it should be done
  • A mistake reaches a customer before anyone sees it
  • It is the part of the job people enjoy

5. Would your team thank you for taking it away?

This one gets skipped, and it matters most. The best first task is the one your staff like least. Nobody took a job at a dental office because they love insurance portals.

When the first thing automation removes is the part of the day people dread, the team helps you make it work. When it removes the part they enjoy, they will not.

What this looks like in practice

Here are first tasks that pass all five questions.

  • A pharmacy: entering new prescriptions from the fax and electronic queue, ready for the pharmacist to verify.
  • A dental office: checking insurance for tomorrow's patients and recording the result.
  • A medical clinic: entering referrals that arrive by fax.
  • An accounting firm: entering supplier invoices and matching them to orders.
  • A med spa: moving completed intake forms into the client record.

Each one is frequent, follows rules, starts from a document, has a person checking the result, and is nobody's favorite part of the job.

How we handle the first task

An agent, as we build them, is software that signs in to the systems your team already uses, with its own login, and does one repetitive job inside them by following rules your team wrote down with us.

We start with one task. We learn it from the person who does it now, write the rules with them, and run the agent beside your current routine until you are satisfied. When something does not match the rules, the agent stops and hands that item to a person with the reason. Nothing changes in the software you already own.

Common questions

How small is too small to automate? If a task takes one person less than an hour a week, leave it alone. Look for something that takes an hour or more a day.

Do we need to replace our software first? No. A good first project works inside the programs you already have.

What if our process is a mess? Then the first step is writing down how the task should be done. That is useful even if you never automate it.

Should we automate several things at once? No. One task, working well, teaches you more than five started and none finished.

If you have a task in mind and want a second opinion on whether it is a good first one, tell us about it. We will tell you plainly.

Tell us the task

This article is general information about automation. It is not legal, financial or technical advice for any particular business.

Book a demo