Contents
There is no flat rate for automation, and anyone who quotes one without understanding your process is guessing. What it costs depends on the complexity of the work, the systems involved, and whether off-the-shelf tools can handle it or something custom is needed.
So rather than open with a range that would not apply to you, here is a worked example with real numbers, followed by how to check the arithmetic against your own situation.
What a typical automation costs: a worked example
Say an audit finds eight hours a week going into supplier payments, reconciliation across three systems by hand, and a tool doing a job an integration does better.
| What comes back | Each month |
|---|---|
| Time released, 35 hours at R165 | R 5 775 |
| Tool no longer needed | R 900 |
| Errors and rework, estimated | R 800 |
| Recovered each month | R 7 475 |
| What it costs | |
|---|---|
| Build, once | R 24 000 |
| Monthly thereafter | R 2 600 |
| Net each month | R 4 875 |
| Break even | Month 5 |
Round numbers, for illustration. Not a quote. Your figures come out of the audit.
Every figure there is checkable, which is the point of showing it this way.
Eight hours a week is about 35 hours a month. R165 an hour is what a R22 000 salary actually costs an employer once the usual additions are counted, spread over a 40 hour week. That combination is an assumption, not a law, and it is the number to change first if your team is paid more or less than that.
R24 000 divided by R4 875 a month is 4.9 months, so month five is the first one in the black. If the same build only released half those hours, with the tool and error savings unchanged, the net recovery falls to around R1 990 a month and payback stretches to roughly twelve months, a different conversation.
Note what the recovered figure is not. It is not eight hours of pure cash. Time released only becomes money if the person does something else valuable with it, a hire is avoided, or a subscription gets cancelled. The tool line is real money leaving your account today. The error line is an estimate. Keeping the three separate is the difference between a number you can defend to a sceptical partner and one you cannot.
What drives the cost of automation
Complexity of the logic
The simplest automations are linear: something happens in system A, data moves to system B. No decisions, no branching, no transformation.
More complex automations need conditional logic ("if the invoice is above a threshold, route it for approval; otherwise post it"), multi-step workflows, data transformation between formats, and error handling for the cases that do not fit the pattern. Each of those adds build time.
Whether native connectors exist
Platforms like Zapier, Make and n8n have pre-built connectors for hundreds of common tools. If both systems you are connecting have native connectors, setup time is measured in hours.
If one or both do not, someone has to work directly with the API, which takes longer and needs more technical skill. This is common in South Africa, because a good deal of the local stack (bank portals, several payroll and job management tools) was never built with third-party integration in mind.
Production reliability requirements
A workflow that sends a Slack message when a form is filled in can tolerate the occasional failure. A workflow that creates client invoices or moves money cannot.
Anything touching money or customers needs error handling, retry logic, alerting when something fails, and logging so a failure can be investigated afterwards. That adds real build time and it is not optional. Most of the difference between a cheap automation and a reliable one sits here.
Data quality in the source system
If the data in your source system is clean and consistent, the integration is straightforward. If your CRM has half-filled records, inconsistent formats or duplicates, the automation either needs validation logic built into it or the data needs cleaning first. Both take time, and the second is usually the better investment.
Ongoing maintenance
Automations are not built and forgotten. APIs change, authentication tokens expire, banks change a file format, and business rules move. There is an ongoing cost either way: your own time keeping it running, or someone on a monthly arrangement doing it for you.
Do you pay a flat rate or a monthly fee?
Both, and you see both numbers before anything starts.
The build is priced on the work involved and fixed before we begin, so there is no meter running. It is a single figure, agreed upfront.
The monthly is priced on what the automation gives back, not on a tier list. It covers monitoring, fixes when a vendor changes something, a couple of hours of changes each month, and a one page report showing what ran and what it recovered.
Both numbers come out of a free audit rather than a price list, because the honest answer to "what will this cost" depends on what we find when we look at your process. The services page lists the kinds of work these numbers usually apply to.
How long does automation take to pay for itself?
You can work out a rough version yourself before speaking to anyone.
- Estimate the current manual time cost. How many hours a week does the process take, and what does the person doing it actually cost per hour? Use the fully loaded cost (wages plus payroll taxes plus benefits), not the bare salary.
- Turn it into an annual figure. Three hours a week is about 13 hours a month. At the R165 an hour used above, that is roughly R2 145 a month, or R25 700 a year. Substitute your own numbers. The method matters more than the example.
- Be honest about whether it is real money. Hours saved only become money if that capacity gets used for something else, a hire is avoided, or a subscription gets cancelled. Otherwise it is time released, which is still worth having but is not the same as cash. This is the step most ROI calculators skip.
- Add the error cost. Manual data entry produces mistakes. If those occasionally cause billing errors, duplicated records or late payments, they belong in the calculation.
- Compare it to the build. If the annual figure is a multiple of the build cost, the case is obvious. If it is roughly the same, it probably is not worth doing yet.
At low volume, a handful of transactions a month, the answer is often that you should not automate anything and that native features in the tools you already have will cover it. See Xero's built-in automation features before paying for a build, and automating bank reconciliation if that is where the time is going.
Ongoing costs: n8n, Zapier and Make
Beyond the build, most automations carry a platform fee. These vendors price in dollars and euros, so the rand cost moves with the exchange rate.
- n8n cloud starts around €20 a month on annual billing (closer to €24 month to month), which includes a capped number of workflow executions rather than unlimited use.
- n8n self-hosted is free to run for your own business under its Sustainable Use Licence. It is not free of effort: you are responsible for the server, updates, patching and backups, so budget your own time alongside the $5 to $20 a month of hosting. If you want to go that route, deploying n8n on Railway covers a production setup.
- Zapier charges per task.
- Make charges per operation. It often works out cheaper than Zapier at higher volumes, though not always, because the two count usage differently and a workflow with many steps can erode the difference.
Vendor pricing and plan limits change often. Check the current figures on the vendor's own site before budgeting, and treat the numbers above as a starting point rather than a quote.
Can you automate your business for free?
Partly, and it is worth exhausting the free options before paying anyone.
- Xero's native features. Repeating invoices, payment reminders and bank rules handle a surprising number of common cases with no extra automation tool. Xero itself is a paid subscription, and entry-level plans cap how many invoices and bills you can process each month, so check your plan covers your volume.
- n8n community edition. The free self-hosted version handles complex workflows with no execution limits, if you are comfortable running a server.
- Zapier's free tier. Two-step Zaps only, meaning one trigger and one action, with a small monthly task allowance. Enough for a single simple connection, not a multi-step workflow.
A note on HubSpot, which often gets recommended here: the full workflow builder is a Professional-tier feature, not part of the free plan. The free and entry tiers give you very limited automation, so do not plan around it without checking what your tier actually includes.
If one of these solves your problem, use it. We would rather point you at a feature you already pay for than sell you a build you did not need.
Questions to ask before starting
Before engaging anyone, know the answers to these. The clearer you can be, the more accurate any quote will be and the faster the build will go:
- What exactly triggers the automation?
- What data needs to move, and from which fields?
- What should happen when the data is missing or wrong?
- What does success look like, and how would you know it worked?
- How many records does this process each week or month?
- Does it need to be auditable or logged?
If you can answer most of those, you are close to a scoped piece of work already. If you cannot, that is what the free audit is for, and whether you need a developer at all is worth reading first.
Want to know what your specific automation would cost?
Describe what you're working with and we'll come back with something specific, not a sales call.
Get your free audit →Read next