What we automate
Pricing
Company
Resources
Contact Book a consultation →
PLENUA
Guide

How to tell whether your company is ready for automation

Most companies ask this question about themselves — which is why they never find an answer. It is not the company that is ready, but a specific process. Below: four conditions, a five-sentence test and a list of situations where it is better to wait.

Andrzej Lubczyński··8 min read

The short answer

A company is ready when it has at least one process that repeats several times a week, has clear rules, runs on digital data and where a mistake can be undone. The size of the company, the budget and the technical set-up are not conditions.

Diagram: five company processes pass through a filter of four readiness conditions; only enquiry handling meets all four and becomes the first to be automated.
It is not the company that is ready or not ready, but a specific process. The filter is the same for everyone; the result is different every time.

Four conditions a process has to meet

All of them have to be met at once. Three out of four is not enough — the missing condition is usually the one that later derails the implementation.

1. It repeats regularly

At least a few times a week. Something done once a quarter rarely pays back the cost of implementing it — even if it takes half a day each time. A simple sum: a process taking 15 minutes, run twice a month, adds up to six hours a year. Automating that will never pay back.

How to check: Count how many times a week somebody does it. Below three — put it off for later.

2. It has clear rules

It can be described in sentences like “if the enquiry is about a quote it goes to the sales lead; if it is a complaint, to customer service”. Automation is excellent with rules and hopeless with judgement. If every case calls for thought, it is not a process — it is expert work.

How to check: Try writing the rules as “if X, then Y”. If you give up after three sentences, the rules don’t exist yet.

3. The data is stored digitally

The information lives in an email, a form, a spreadsheet or a system. It doesn’t have to be tidy or in one place — it simply has to exist in a form a machine can read. If the key data is on paper or in somebody’s head, it has to be got out of there first.

How to check: Check whether the data the process needs can be copied and pasted today. If it can, that is enough.

4. A mistake can be undone

An email sent to the wrong person is a five-minute problem. A wrongly issued invoice or a misdirected payment is a different category of risk and calls for safeguards that raise the cost. That does not rule out automation — it simply changes its scope and price.

How to check: Ask yourself: what happens if the automation gets it wrong ten times in a row?

The five-sentence test

Describe the process in five sentences. If you can, it is suitable for automation. If after the third sentence you start saying “well, it depends, because sometimes…” — it is not a process yet, just a habit shared by a few people who do similar things in different ways. Automating that habit will cement the mess rather than remove it.

A comparison of two tracks: a process follows one path through four stages, while a habit branches into three different ways of doing it by three people.
The difference the five-sentence test picks up. The upper track can be automated. The lower one has to be settled first.

Signs that it is not the moment yet

Honestly, because it will save you money.

Three people run the process three different ways and none of them is official. Automation will cement one of them — not necessarily the best. First somebody has to decide what the process should look like.
Nobody in the company can decide on the details. An implementation needs decisions: who gets notifications, what to do with an unusual case, which fields are mandatory. Without somebody who can decide, the project stalls.
The process changes every month. Automation runs on repetition. With shifting rules, every change means a rebuild and a cost.
The problem is not the process but the people. If the sales team isn’t calling back because they don’t want to, a reminder in a chat app will change nothing. All it does is make visible who isn’t calling.
Nobody has counted what the process costs today. Without a baseline figure you will never prove the implementation was worth it — and after three months nobody remembers how it used to be.

What to do if the process fails the test

Not being ready does not mean “never”. It means “not in this form”.

1

Describe the process in five sentences

Not in documentation — on a sheet of paper. If it works, you have a process. If not, you have a habit shared by a few people, and that is the first problem to solve.

2

Appoint one person who can decide

Somebody who can say “this is how we do it” and have it stick. Without that, every implementation gets bogged down in details.

3

Measure how much time it takes today

Even roughly, over two weeks. That number will later be your only proof that anything changed. To write down the steps and count the time you can use our process map template.

4

Pick the simplest one, not the most important

The first process is meant to show a result, not to solve everything. The best candidate is the one that annoys somebody enough that they bring it up unprompted.

An example: the same company, two different results

A marketing agency, eight people. Enquiries arrive through the website form, by email and on Messenger. Around fifty a month. They land in a shared inbox that somebody checks once a day. Some go missing.

Repeatability: fifty times a month, that is a dozen or so a week. Condition met.
Rules: “campaign enquiries go to the campaign lead, website enquiries to the web lead, everything else to the owner”. Three sentences, clear. Met.
Data: all of it in email and the form. Met.
Reversibility: a wrongly assigned enquiry means one hand-off. Met.

Four out of four. The process is suitable for automation, and the implementation will pay back in a few months on the recovered hour a day alone.

The same agency, a different process: preparing the monthly client report. Done once a month, it calls for interpreting the data and deciding what to highlight. Repeatability too low, rules unclear. Two out of four — not this process.

This is a typical result: in the same company one process passes the test without reservation and another fails outright. That is why “is the company ready” is the wrong question. The right one is: which process is ready.

How many Polish companies are genuinely ready

Two independent studies from the first half of 2026 show the same thing from two sides. Research by YouGov for the IONOS Group, published in the report “The Digital Pulse of Polish SMEs 2026”, found that 44% of Polish SMEs already use AI solutions, and 42% are planning further implementations in 2026. That is the highest figure among the nine European countries surveyed.

In parallel, the EFL AI Barometer for H1 2026 shows that only 7% of companies describe their readiness for implementation as high or very high — against 24% six months earlier. 43% describe it as low or very low, and 50% as moderate.

A threefold drop in declared readiness over six months does not mean companies went backwards. It means they began assessing themselves more honestly — after the first attempts the difference becomes visible between “we tried ChatGPT” and “we have a process that runs without us”. This is precisely the point at which the readiness question stops being a curiosity and becomes a purchasing decision.

The gap between the two figures says more than either does alone. Most companies don’t have a problem with the technology — they have a problem knowing where to start and whether their process is suitable at all. That is the question this article answers, and the first question we ask in every consultation.

A third figure from the IONOS study is worth knowing: the largest group of companies reports a monthly budget for AI tools in the range of EUR 21–50, roughly PLN 90–215. That is a budget for a subscription, not for an implementation. If you are looking for a solution at that price you probably need an off-the-shelf tool rather than an implementation service — and it is better to know that up front.

Sources: YouGov Deutschland research for the IONOS Group, based on a sample of almost 5,000 decision-makers at companies of up to 250 employees across nine European countries (report “The Digital Pulse of Polish SMEs 2026”, June 2026), and the EFL AI Barometer for H1 2026 (May 2026). Both concern the Polish market, on which we work. The data covers the use of AI; process automation without models was not measured separately.

Frequently asked questions

Yes, if it has a process that repeats at least a few times a week. The size of the company matters less than the frequency of repetition — a five-person agency handling 60 enquiries a month has more to gain than a thirty-person company with five.

No. It is enough that the data is stored digitally — in a spreadsheet, an inbox or a form. A CRM helps, but it is not a condition. You can start without one and add it later.

One. Implementations that begin with five processes at once most often end with a system the team doesn’t use — because it was built before anyone understood how the process actually works.

It shouldn’t. Good automation connects the tools a company already has. If a supplier starts by telling you to buy something, it is worth asking why.

That is a sign it is not ready yet. Automation runs on rules — if the rules keep shifting, every change means a rebuild. It is worth stabilising the process first.

Somebody who can settle what the process should look like — usually the owner or a department head. Implementations mostly drag on when there is nobody to ask about the details.

Not sure whether your process passes this test?

30 minutes, an online call, no obligation. We will go through one process in your company and tell you whether it is worth automating — including when the answer is “not yet”.

Book a free consultation →
Andrzej Lubczyński, founder of AIROX
Andrzej Lubczyński

He spent five years building operations at WebWave: from creating a support department from scratch to the role of Head of Operations and leading the integration after the company was acquired. While putting those processes in order he noticed how much time is taken up by work that develops nobody — and that the tools capable of taking it over already exist. A graduate in corporate finance from the SGH Warsaw School of Economics.

LinkedIn profile →