Automation or another hire? The calculation nobody does
When the team can no longer keep up, the first instinct is to hire someone to help. Before you do, it is worth calculating what a job really costs, what automation costs — and why the two are not a like-for-like comparison.
The short answer
Automation and a new employee do not solve the same problem. Automation takes over repetitive tasks with clear rules: retyping data, confirmations, reminders, reports. A person is needed where you have to talk, judge and decide.
That is why there is only one sensible order: first automate what can be automated, then count how much work is really left. It often turns out the new hire was not needed. Sometimes it turns out they were — but for entirely different work.
Where the question comes from
The story is almost always the same. The company grows, enquiries and clients multiply, the team stays late. The instinct: hire someone to help.
Rarely does anyone check what exactly that person would be doing. Break it down into tasks and a large part turns out to be work you can describe in one sentence: copy the data from the form into the spreadsheet, send a confirmation, remind about a payment, put a report together from three tools.
Hiring a person for that kind of work usually ends the same way. They get bored, make routine mistakes and leave after a year — taking with them the knowledge of how things work.
What a hire really costs
The figure in the job ad is not what the company pays. In Poland, the employer adds its own contributions on top of the gross salary — pension, disability, accident insurance, the Labour Fund and the Guaranteed Employee Benefits Fund — about 20% in total, a little more with an employee capital plan (PPK).
| Gross / month | Company cost / month | Per year |
|---|---|---|
| PLN 5,500 | PLN 6,630 | PLN 79,500 |
| PLN 6,500 | PLN 7,830 | PLN 94,000 |
| PLN 7,500 | PLN 9,040 | PLN 108,400 |
Rounded figures. Employment contract, 1.67% accident insurance rate, no PPK. The exact amount depends on the industry and the employee’s age.
And that is not all. There are costs the table does not show:
- recruitment — job ads, interviews, your time; usually several weeks,
- onboarding — the first months mean reduced output, and someone on the team has to teach,
- the workstation — a computer, licences, a desk,
- absence — 20 or 26 days of annual leave plus sick leave, when the work stops or lands on others,
- turnover — when the person leaves, the whole cycle starts again.
Once holidays and public holidays are taken off, an employee on PLN 6,500 gross costs the company around PLN 50 for every hour actually worked. That figure will come in handy in a moment.
What automation costs
The cost has two parts.
Implementation — one-off. With us, automating a single step costs PLN 3,600 net and a full process PLN 6,900 net. The amount is fixed and agreed before we start.
Tools — monthly. An automation platform, sometimes a language model. In a small company usually PLN 0–500 a month, paid directly to the providers.
Automation does not take holidays, does not fall ill and does not resign. It works the same at 10 pm on a Saturday as on a Tuesday morning. It does have one limitation, though — and that limitation is the heart of the whole comparison.
You buy a job whole, and automation by the hour
You cannot hire someone for ten hours a week of retyping data. You hire a whole job, and the rest of the time has to be filled with something. Automation works the other way round: it takes over specific tasks and nothing else.
So the honest question is not “automation or an employee” but: how many hours a week does the team spend on work that can be described by a rule?
The team spends 10 hours a week retyping enquiries, sending confirmations and reminders. Automation takes over 7 of them — the rest are exceptions that stay with people. That is about 30 hours a month, or around PLN 1,500 at PLN 50 an hour. Take off PLN 300 for tools and you are left with PLN 1,200 a month. A full-process implementation at PLN 6,900 pays for itself in just under six months — and then keeps working.
Those ten hours do not justify a hire — they are a quarter of a job. But in a growing company there will be twenty of them in six months, and then the question of hiring comes back, only louder. You can run the numbers for your own process in our payback calculator.
What automation does better, and what a person does better
The line is simpler than it seems. If you can write down what should happen without the words “it depends”, it is work for automation. If every situation needs judgement — it is work for a person.
| Task | Who should do it |
|---|---|
| Copying form data into the CRM | automation |
| Confirming an enquiry was received | automation |
| Payment or meeting reminder | automation |
| Weekly report from several tools | automation |
| A client question outside the pattern | a person |
| A complaint and an upset client | a person |
| Negotiating price and terms | a person |
| Approving an exception to the rules | a person |
The combination works best: automation prepares the data, watches the deadlines and sends reminders, while a person deals with whatever needs a conversation and a decision. We write more about where that line runs in A rule or an AI agent.
When hiring is the better choice
We will not pretend automation solves everything. Hiring is the better decision in four situations.
The work is mostly conversations and judgement
Sales, handling complaints, looking after key clients. Automation can prepare the data for that person and remind them of a deadline, but it cannot replace them.
There are too few repetitions
A task that happens three times a month does not justify an implementation. It is quicker to do it by hand.
The process is not settled
If everyone on the team does it differently and the rules change every week, automation will lock the mess in place. Someone has to sort it out first — and that can be a good job for a new person.
Nobody owns the outcome
Automation carries out steps, but it does not watch the goal. If the problem is that nobody owns customer service or sales, you need a person, not a tool.
If you are not sure what stage your company is at, take the readiness test. It takes five minutes.
A sensible order
The hiring decision is best made at the end, not at the start.
- Write down one week of tasks. Everyone on the team notes what they did and how long it took. No judging — the point is the picture.
- Mark the repetitive ones. Anything that happens by the same rule at least a few times a week.
- Automate the biggest chunk. One process, not everything at once. After two weeks you can see how much time actually came back.
- Count what is left. Only now do you know whether you are short of hands or were just short of time.
- If you do hire — rewrite the role. The new person goes into work that needs a human, not into retyping. They are easier to find and less likely to leave.
This order has one more advantage. A process written down for automation is a ready-made guide for a new person — so if the hire does turn out to be needed, onboarding will be shorter.
Frequently asked questions
In a small company it rarely replaces a whole job. Most often it gives the existing team back anywhere from a few to a dozen or so hours a week that used to go on retyping data and chasing deadlines. The usual result is no need to hire, or hiring for different work — not a redundancy.
In Poland, an employee on PLN 6,500 gross a month costs the company around PLN 94,000 a year. Automating a full process costs PLN 6,900 net one-off with us, plus usually PLN 0–500 a month for tools. But the comparison is not like-for-like: automation takes over specific tasks, not a whole role.
It depends on how many hours you get back. At 30 hours a month and around PLN 50 per hour of work, a PLN 6,900 implementation pays for itself in roughly six months. If the payback comes out at over a year, it is usually a sign to start with a different process.
Someone in the company should know how the process works and get a notification if something goes wrong. That is a few minutes a week, not a job. If you would rather have someone outside keep an eye on it, there is optional monthly care.
The reverse is usually cheaper. If you hire someone for repetitive work and then automate it, that person is left without half their tasks. If you automate first, you hire for work that genuinely needs a person.
The expected ones — yes, if they can be described by a rule. It should not try to handle unexpected ones: a well-built process recognises a situation outside the pattern and hands it to a person instead of guessing.
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 →