Request a quote
Emergency SectorsCareers About us Blog Get in touch
Meeting room with a wall covered in yellow sticky notes and two colleagues at a long table

Business process automation: which processes first

Business process automation does not start with a tool. It starts with the question of which work your people retype, forward or check by hand every day. This is the order we recommend for an SME: pick the right process, map it, choose the lightest approach that works, and sort out the IT side before the first workflow goes live.

7 min read Written by the ITproposal team
Short answer

Automate work that recurs often, follows fixed rules and already arrives digitally. Work full of exceptions and judgement calls comes later, or never.

Choose the lightest approach that works: a feature your software already has beats an integration, an integration beats a workflow, and a workflow beats a robot clicking through screens.

An automation runs under an account, with permissions and an owner. Set that up first, or it stops silently the day its creator leaves.

Which processes to automate first

Business process automation pays off first on work that meets four conditions. The more of them that hold, the better the candidate:

  • It recurs often. Daily or weekly, not twice a year. A task that rarely happens costs more to build and maintain than it saves.
  • It follows fixed rules. If someone has to think or consult at every step, it is judgement work, not rule work.
  • The input is already digital. An invoice as a PDF in a mailbox, a web form, a record in a system. Paper that has to be scanned first is a second project.
  • The process is stable. A way of working that changes next month is one you will automate again next month.

In practice the same kinds of process keep coming up: preparing incoming invoices for the finance team, passing a website enquiry to the CRM, creating and removing accounts when people join and leave, routing a leave or expense request for approval, compiling a recurring report from two systems.

What to leave for now: processes with many exceptions, processes where a mistake reaches a customer without anyone checking, and processes nobody can explain precisely. For that last group the work is not automation but agreement.

Map the process before you automate it

Automating a messy process gives you a fast messy process. So first write down, or stick on a wall of notes, how it actually runs, not how the manual says it runs.

  • The steps: what comes in, what happens to it, where it goes.
  • The decision points: who approves, on what rule, and what happens when that person is away.
  • The exceptions: which cases run differently, and how often. Count them for a few weeks; the exception everyone mentions often turns out to be rare, and the reverse.
  • The systems: which applications hold the data, and who has access.

Mapping often shows that a step is redundant, or that two departments do the same thing. Remove that first. What remains is what you automate, and it is then also clear what the automation should not do.

Four approaches, from light to heavy

There is no single way to automate. The rule of thumb: choose the lightest approach that does the job, because every step heavier means more maintenance.

  • What your software already does. Rules in the accounting package, mail rules, a built-in approval step, a form that writes straight into a list. This is the option most often skipped, and the cheapest to maintain, because the vendor keeps it working.
  • A standard integration. Many applications come with a ready-made connector to each other. It uses an official interface and usually survives updates.
  • A low-code workflow. A platform such as Power Automate in Microsoft 365 links steps between systems without programming. Powerful, but it is software: someone has to maintain it.
  • A software robot (RPA). It operates screens the way a person does. Useful when two systems genuinely have no integration, but it breaks as soon as a screen changes.

So start by asking your vendors which integrations and features already exist. Only when the answer is no does it become a workflow or a robot.

What the IT side has to set up

An automation is a user who never sleeps and can reach everything you give it access to. Treat it that way.

  • Its own account, not an employee’s. A workflow running under its creator’s personal account stops on the day that person leaves or changes their password. Use a service account in the organisation’s name.
  • Only the permissions it needs. Just the folders, mailboxes and systems this process touches. An account with admin rights everywhere is the first thing an attacker looks for.
  • Secrets in a vault. Passwords and keys for integrations do not belong in a workflow or a script, but in a managed vault, with an expiry date that someone watches.
  • Licences. Some connectors and accounts need a licence of their own. Account for that before you start, not when the invoice arrives.
  • A record. What the automation does, under which account, with which permissions and who owns it. That belongs in the same IT documentation as the rest of your environment.

If the automation handles personal data, check where it goes. A step that sends data to an external service falls under UK GDPR and usually needs a data processing agreement.

One owner, and a plan for when it fails

Every automation needs two owners: someone in the business who knows what the process must deliver, and someone who knows how it works technically. In a small team that can be one person, but it must be a name, not a department.

Agree what happens when it fails. An automation that stops silently is more dangerous than an employee off sick, because nobody notices. Write down:

  • who is alerted when a run fails, and how quickly they look;
  • how the work continues by hand while it is broken, and whether anyone still knows how;
  • how you see what has already been processed, so nothing happens twice or not at all.

Also schedule a regular check that the automation still fits. Processes change, and a workflow that still runs but does the wrong thing only shows up at year end.

Four pitfalls in business process automation

  • Shadow automation. Staff build their own workflows under their own accounts, with their own permissions. That is good news in itself, because they see where time goes. But without an overview nobody knows what is running. Keep a list and agree what people may build themselves and what goes through IT.
  • Forgetting the exception. The automation handles nine cases out of ten, and the tenth sits in a folder nobody checks. Every workflow needs a way out to a person for what it cannot handle.
  • Not measuring. Write down beforehand how much time the process takes now and how often it goes wrong. Without that figure you cannot tell afterwards whether it delivered anything.
  • Starting too big. Automating one process end to end beats five processes halfway. The first one teaches you what the second will take.

Where our work stops

What we do. We look after the IT environment an automation runs on: the Microsoft 365 tenant and licences, service accounts with limited permissions, the vault for passwords and keys, monitoring and backup, and what happens to those accounts when people join and leave. We also supply and configure UiPath, and we build integrations and bespoke software for work that no package covers. That is a separate service, software development, and the source code and documentation are yours.

Where it stops. How your business works and who owns which process stays with you. We do not decide which step goes, who approves what or which rule applies: we put forward what we see when the process is mapped, and the choice is yours. That is why an automation always has an owner inside your own organisation. The packages we integrate with stay with their vendors; we do not build a replacement package.

Frequently asked

Questions we get about this

The five that come up most.

What is business process automation?

Business process automation means letting software, rather than a person, carry out work that follows fixed rules: copying data, forwarding it, checking it or routing it for approval. That can be a feature in existing software, an integration between systems, a low-code workflow or a software robot. The lightest approach that works is usually the best.

Which processes are best to automate?

Processes that recur often, follow fixed rules, arrive digitally and do not keep changing. Examples are preparing incoming invoices, passing website enquiries to the CRM and creating accounts for new starters. Processes full of exceptions or judgement calls are better simplified first.

What is the difference between RPA and an integration?

An integration exchanges data through an official interface of the software and usually survives updates. RPA, a software robot, operates the screens the way a person would and breaks as soon as a screen changes. RPA is therefore mainly a solution for systems that genuinely have no integration.

What does IT need to set up before automating?

A dedicated service account in the organisation’s name, with only the permissions the process needs. Passwords and keys in a managed vault, the right licences, an alert when a run fails and documentation of what is running. Without that, an automation stops silently as soon as its creator leaves.

Can you build the automation as well?

Yes, as a separate service: we build integrations and bespoke software for work no package covers, and we supply and configure UiPath. What we do not do is decide how your process runs. Which step goes, who approves what and who owns it is your decision; we set out the options.

Related services

Further reading

What process automation connects to.

Shall we sort out the IT foundation underneath?

Tell us which process you want to automate and with which applications. We will tell you which accounts, permissions and licences it needs, whether an integration already exists or has to be built, and how to run it securely.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call