What automating a small business really costs, and how to know if it will pay off
“How much does it cost?” is the first question we get, and the wrong way to ask it. An automation does not have a price. It has a build cost, a running cost and a failure cost. And on the other side, a gain you can calculate before spending a single euro. Here is how we run the numbers, for our clients and for ourselves.
Start with the cost of the task, not the tool
Before talking tools, put a number on what the task costs today. The formula fits on one line: time per occurrence, times occurrences per month, times the loaded hourly cost of the person doing it.
An example
Copying bookings into the team schedule: 30 minutes per working day, about 11 hours a month. At €35 per loaded hour, the task costs €385 a month, over €4,600 a year. And that figure counts neither the copying mistakes nor the time spent fixing them.
That amount is your ceiling. An automation that costs more than the task it replaces is not an investment, it is a hobby. Our free calculator runs this calculation for all your repetitive tasks.
The four items of the real cost
1. The tool licence
The visible part, and the least decisive. Mainstream tools bill by volume: each operation consumes a unit of your plan, and an automation handling many small events gets expensive fast. n8n can be self-hosted, and the cost then becomes that of a server rather than that of the volume.
2. Hosting
A small server for n8n costs from a few euros to a few tens of euros a month. The real cost is not the machine: it is the updates, backups and monitoring that come with it. Handle them in-house or hand them over.
3. The build
The item that varies most, and it depends less on the tool than on how clear the process is. A written, stable process with known edge cases is quick to build. A fuzzy process gets built three times, because the rules are discovered while building. That is why we always write the process before automating it.
4. Maintenance
The item nobody budgets, and the one that kills automations. APIs change, credentials expire, a vendor changes its response format. An automation with no maintenance budget always ends up degrading in silence.
Hidden costs
- The silent failure. An automation that stops without warning costs the task it was meant to do, plus the time to work out what was not done. That is why we never deliver anything without monitoring.
- Dependency on one person. If only one person knows how the system works, their departure costs you the system.
- Double entry. An automation that requires someone to check its output by hand every day has not automated anything. It has moved the task.
- Adoption. A tool the team works around costs its licence and its build for nothing.
Free 30-minute audit
We look at your real processes and tell you what is worth automating, and what is not. Pick a slot →
The payback calculation
Once both sides have a number, the maths is simple: the build cost divided by the net monthly gain (task cost minus running cost) gives the number of months to break even.
In the example above, a €385-a-month task replaced by an automation that costs a few tens of euros a month to run frees up over €300 a month. A build of a few days pays for itself in under a year, and everything after that is gain.
Our rule: if payback goes beyond eighteen months, we do not start with that task. There is almost always a more profitable one right next to it.
The most common calculation mistakes
- Counting the owner's time as zero. It is often the most expensive time in the company, and the scarcest.
- Picking the cheapest licence. The licence weighs little next to the build and maintenance.
- Automating an unstable task. A task that changes every month gets rebuilt every month.
- Leaving maintenance out of the budget. It always comes; the only question is whether it was planned.
Frequently asked questions
How much does it cost to automate a task in a small business?
The real cost has four items: the tool licence, hosting, the build and maintenance. The licence is often the smallest. The build depends mostly on how clear the process is, and maintenance, often forgotten, must be budgeted from the start.
How do I know if an automation will pay off?
First put a number on the task: time per occurrence, times occurrences per month, times the loaded hourly cost. Then divide the build cost by the net monthly gain to get the payback period. Beyond eighteen months, start with another task.
What are the hidden costs of an automation?
The silent failure discovered too late, dependency on the one person who knows the system, the daily manual check that cancels the gain, and poor adoption by the team.
Is n8n cheaper than Zapier or Make?
At high volume, often yes, because n8n can be self-hosted and its cost becomes that of a server rather than the number of operations. In return, hosting means updates, backups and monitoring to handle in-house or hand over.
Read next
Where to start automating your businessThe four-step method to pick the right first task. Monitoring n8n workflowsWhy a “success” status proves nothing.Want the calculation on your own tasks? The free audit takes thirty minutes: we put a number on your repetitive tasks and tell you which one pays most to automate, including when the answer is none.