
July 1, 2026
When someone asks what automation costs, they usually blur two very different things: the monthly cost of the tools, and the one-off cost of building the system. They move in opposite directions. Cheap tools with a badly built system will cost you more in breakage than good tools built once, properly. Let me separate them with real 2026 numbers.
For local context I have added rough Kenyan shilling figures at about KES 130 to the dollar.
Most small-business automation runs on one of three platforms. They price very differently, and the difference is not marketing, it is the billing unit.
| Platform | Entry paid plan | Billed by |
|---|---|---|
| n8n (self-hosted) | Free software, about $5 to $7 a month for the server (KES 650 to 900) | Nothing per run. Unlimited. |
| n8n Cloud | About $20 a month, 2,500 runs (KES 2,600) | Per whole workflow run |
| Make | About $11 a month, 10,000 operations (KES 1,400) | Per step (operation) |
| Zapier | About $20 a month, 750 tasks (KES 2,600) | Per action step (task) |
Here is the part that decides your bill. Zapier charges for every single step in an automation. A five-step workflow run 150 times burns 750 tasks, your entire entry plan, from one automation. Make charges per operation, cheaper per unit but the same idea. n8n charges once per whole workflow run no matter how many steps are inside it, which is why the same job that maxes out a Zapier plan barely registers on n8n.
n8n has a free, open-source version you host yourself. You pay only for a small server, roughly $5 to $7 a month, and you get unlimited runs and every feature that matters for a small business. Compared to a cloud plan that stops your workflows the moment you hit a limit, self-hosting is the single biggest saving available.
The catch is real: someone has to set up the server, the reverse proxy, the SSL and the backups, and keep an eye on updates. That is where I spend a lot of my time, running self-hosted n8n on providers like Hostinger, Render, Railway and Google Cloud. For a business without in-house technical staff, the honest maths is to pay a builder once to set it up correctly, then run it for the price of a coffee a month, rather than pay a platform a premium forever.
Two more line items, both usage-based, both easy to forget.
You have two routes. Build it yourself, where the tools are cheap but the time and the debugging are yours. Or pay someone to build it, where you pay once for a system that is set up to survive contact with real customers.
A single, well-scoped automation, say a website chat agent that captures leads, or an email classifier that routes and answers enquiries, is a one-off build, not a subscription to a person. What you are buying is that it works when a customer hits an edge case at midnight, and that it does not silently stop three weeks later without anyone noticing.
For a small business running two or three solid automations:
Most small businesses I work with run their core automations for well under $50 a month in tooling once they are set up on self-hosted infrastructure. The build is where the real investment sits, and it is a one-time one.
The most common way people overpay is a polling workflow that checks for new data every few minutes on a per-step platform. One of those can quietly eat an entire monthly plan. It is exactly the kind of thing a proper build avoids and a rushed one does not.
If you want a straight answer on what your specific automations would cost to build and run, tell me what you are trying to automate and I will give you a real number, not a range designed to keep you guessing.