Skip to content

Which business processes should you automate first?

How to choose the first processes to automate: score frequency, error cost and rule clarity, count the manual work, and know when integration beats automation.

By AM-IT Solution · Published · 4 min read

Close-up of interlocking metal gears in a machine
Photo: cottonbro studio on Pexels. Illustrative only; not an AM-IT project.

In short

Automate first the process that is frequent, rule-based, error-prone and already well understood, such as re-keying data between systems, sending routine notifications or chasing standard approvals. Leave out anything that still changes weekly or depends on judgement. Count the manual steps before you build, because that count is what justifies the work.

Most organisations have far more candidates for automation than they have budget for. The risk is not choosing a bad idea. It is choosing an interesting one first: a clever process nobody does often, while the dull, daily copying between two systems carries on. This guide gives a plain way to rank the list.

What makes a process a good candidate for automation?

Four qualities matter more than the technology. A process that has all four is worth looking at first.

  1. It happens often. A ten-minute task done every day outweighs a two-hour task done twice a year.
  2. It follows rules you can write down. If a new colleague could do it from a checklist, software can too.
  3. Mistakes are costly. Wrong figures, missed deadlines or forgotten follow-ups create work and damage trust.
  4. It is stable. Automating a process that changes every month means rebuilding it every month.

The reverse is also useful. Work that needs discretion, negotiation or a view on a particular person’s circumstances should stay with a person. Software can prepare the information for that decision, but it should not make it for you.

How do you work out what manual work costs?

You do not need a spreadsheet model. For each candidate, write down five facts, using your own numbers rather than estimates from elsewhere.

  • How often the task happens in a normal week.
  • How long it takes each time, including interruptions and waiting.
  • Who does it, and what they would be doing otherwise.
  • How often it goes wrong, and what putting it right involves.
  • What happens when the person who knows how to do it is away.

Multiply the first two to get the weekly effort. The last three are usually where the real cost sits: the corrections, the delays and the dependence on one person. Two processes with the same weekly effort are not equal if one of them is where invoices, deadlines or customer communications go wrong.

Where do most organisations find their first candidates?

The same few patterns come up again and again, whatever the organisation does:

  • Re-keying: the same details typed into a form, a spreadsheet and an accounting package.
  • Routine messages: confirmations, reminders and status updates written by hand.
  • Chasing: following up on documents, approvals or payments that are late.
  • Hand-offs: a task that sits in someone’s inbox until they remember it.
  • Reporting: a weekly or monthly figure assembled by copying from several places.

None of these needs artificial intelligence. They need a reliable trigger, a clear rule and a place to record what happened.

Should you integrate your systems or automate the process?

They are different jobs, and mixing them up is a common reason for projects to cost more than they should.

Integration compared with workflow automation
AspectIntegrationWorkflow automation
What it doesMoves data between two systems so it is entered once.Runs a sequence of steps, decisions and notifications.
Typical exampleA paid order creates an invoice in your accounts.A new enquiry is assigned, reminded and escalated if untouched.
Best whenPeople copy the same data between systems.People pass work along and forget or delay it.
Main riskData that does not match between the two systems.Rules that nobody has written down or agreed.

Often the first step is integration, because clean shared data makes everything after it simpler. Our API integration work covers connecting the systems you already use, and workflow automation covers the sequences, rules and notifications that sit on top.

What should you do before building anything?

  1. List ten candidate processes and score each one on frequency, error cost, clarity of rules and stability.
  2. Pick one, and write the process as it works today, including the exceptions people handle by hand.
  3. Decide how you will know it worked, in terms you can check: fewer corrections, fewer chasing emails, a shorter wait between steps.
  4. Build the smallest version that handles the common case and sends the exceptions to a person.
  5. Run it alongside the manual process briefly, then switch over and review it.

How does AM-IT approach automation work?

We begin with a paid discovery from £750 that can map and rank your processes, and a first scope can cover a single process, so you can judge the value before committing to a build. A custom booking system and a replacement for a case-tracking spreadsheet are two examples of processes that often rank high.

Common questions

Do we need special software to start?

Not necessarily. Some candidates can be handled with the features of tools you already pay for. We recommend custom work only when the rules or the connections go beyond what those tools allow.

Can a small organisation benefit?

Yes. Small organisations often have the most to gain from removing repeated manual steps, because each person’s time covers several roles.

What if the process changes after we automate it?

Rules change, so the automation should be easy to adjust, and later changes can be covered by a support arrangement.

Want a figure for your own process?

Start with a 30-minute conversation about the operation and the useful next step.

  • Free 30-minute call
  • No obligation
  • Reply within 24 hours
Book a free 30-min call