Chat with us

Process automation: what to automate and what not to

Three gears next to a chain of linked tasks, process automation

Automation Process automation is no longer just a question of saving time. Since August 2026, if the process includes artificial intelligence and talks to people, you also have to say so.

What really gets automated in a small business

Forget the headline cases for a moment. What pays off most is usually boring and repetitive, which is exactly where the time goes:

  • The data typed in twice because the shop and the management software do not talk to each other.
  • The confirmation email someone writes by hand every time, always the same.
  • The invoice that is classified by eye and saved in a different folder every month.
  • The warehouse alert that depends on someone remembering.
  • The weekly report put together by copying and pasting from three places.

None of these things needs artificial intelligence, by the way. Many are solved with a well-built systems integration, which is cheaper and more predictable.

Process automation without coding

Many tasks can be automated with tools you already pay for. For example, email rules or your CRM’s workflows.

When you do need AI

AI comes in when the process requires interpreting something: reading a document with no fixed format, classifying a request by what it says, drafting a text or answering an open question.

In other words, the practical rule is simple. If you can write down the rule (“when X arrives, do Y”), you do not need AI. If the rule depends on the content and not the format, then you do.

The new part: mandatory transparency

Since 2 August 2026 the transparency obligations of Article 50 of the European AI Act have been fully in force. In plain English: when a person interacts with an automated system, they have to know.

This fully affects automations that touch the customer. An assistant answering questions on the website, a system that replies to emails or one that qualifies requests all fall under it.

Say it where it can be seen

The notice goes in the conversation itself, not hidden in the privacy policy. One line is enough.

Leave a way out

Make sure a person can be reached. An assistant that cannot hand over is a dead end.

Log what happens

Keeping a record of what came in and what went out is not red tape: it is the only way to correct things when something answers badly.

How to choose which process to automate first

Start with what repeats every day and has few exceptions. That way the saving shows from the first week.

The most expensive mistake

Automating a broken process. If the current workflow has exceptions nobody has written down, automating it only makes the errors happen faster and in more places at once.

That is why the first step is always to write down how it is done today, exceptions included. It is usually the most revealing part of the project, and often half the saving appears there without touching a line of code.

How to measure whether it was worth it

Before starting, note how much time that task takes today and how many errors it produces per month. Without that baseline, nobody will know afterwards whether the project worked.

And also measure what you cannot see: how often something the system did wrong has to be undone. An automation that is right ninety per cent of the time but forces you to check everything saves nothing.

Process automation and people

Automating is not taking work away from the team. On the contrary, it frees up time for what needs judgement.

How we do it

We set up automation and artificial intelligence connected to the systems you already use, not as a separate island. When a tool of your own is needed, we build it as bespoke software for businesses, and if it has to be used out on the road or in the warehouse, with its own mobile app.

All in layers and without redoing what came before, which is how the never-ending project is avoided.

Three process automation cases that almost always pay off

If you have to start somewhere, these three usually repay the effort sooner than any other, because they tackle daily, low-risk tasks.

The order typed in twice

The shop writes to the management software without anyone copying anything. And typing errors disappear, which are what cause the most returns.

The document classified by hand

Invoices and delivery notes read, named and filed automatically. This is where AI does come in, because the format changes with each supplier.

The alert that depends on memory

Low stock, a delayed order or a contract about to expire. The system alerts the right person, and it no longer depends on someone checking.

All three have something in common: if they fail, nothing serious breaks. That is the property that defines a good first process automation.

Process automation that breaks

When a supplier changes its API, the automation fails. That is why it should send an alert when something does not work.

What it costs to maintain

An automation is not a one-off purchase, it is one more part of the system. When the supplier changes its invoice format or the platform changes its API, it has to be adjusted.

That is why process automation should be part of the same maintenance plan as everything else, instead of being left as a quick fix nobody knows how to touch when it stops working.

In short

Process automation starts by understanding the process, continues by connecting what you already have and only then brings in AI, if it is really needed. And from this year on, when it talks to a customer, you have to say it is a machine.

Want to see what can be automated in your case? The first call is free.

Process automation: where to start tomorrow

If you want a concrete first step, do this: for a week, write down every task you repeat more than three times. You need no tool other than a notebook.

At the end of the week you will have the real list, which almost never matches the one you imagine. And from there, process automation stops being an abstract idea and becomes three or four concrete, measurable jobs.

What to document for each automation

What it does, which systems it touches and who it alerts if it fails. That way anyone can maintain it.

Sources

Keep reading

Start your project
We reply within one business dayMon–Fri 9:00–18:00 CET