The short answer
Most small-business automation builds land between $2,500 and $8,000, depending on how many workflows are in scope. A paid audit of $500 to $1,500 comes first and is credited in full against the build. As a rule of thumb, expect the build to cost around 10% of the annual saving it can be shown to produce.
What the price is actually based on
Automation is not priced by the hour or by the tool. It is priced against the saving, because that is the only number that tells you whether the thing is worth buying.
So the sequence runs backwards from the money. Count the hours a process currently eats. Multiply by a loaded rate. That gives you an annual figure. The build should cost roughly a tenth of it, which means the system pays for itself several times over inside the first year and keeps paying after that.
If a process costs you $40,000 a year in staff time and someone quotes $30,000 to automate it, the arithmetic has stopped working in your favour — regardless of how good the system is.
Why the audit is paid, and what it costs
The audit is $500 to $1,500, and it is credited in full against the build if you go ahead.
Paid audits are unpopular to explain and worth insisting on. A free audit is a sales meeting with a document attached: nobody who is paid only when you buy is going to spend a week discovering that you should not. Paying for the finding means you can be told the honest answer, including the one where automation is the wrong tool and you have paid $500 to avoid spending $6,000.
What you get is a written picture of where the hours actually go, which processes are worth automating, which are not, and what each would cost.
What moves the number
- How many workflows. One process end to end sits near the bottom of the range. Three or four connected ones sit near the top.
- Whether the process is written down. If nobody has ever documented it, the first part of the work is discovering what the process actually is, which is frequently different from what everyone believes it is.
- How your systems talk. A stack with real APIs is cheap to work with. Older software with no integration points changes the shape of the build.
- How many exceptions there are. A process with four edge cases is straightforward. One with forty is really forty processes.
- Whether a model is genuinely needed. If a rule and a scheduled job solve it, that is cheaper to build and far cheaper to run than putting a language model in the middle of it.
What you should not be paying for
A monthly retainer to keep a working system running. If the system needs its builder on call permanently, it was built wrong, or it was built that way deliberately.
Ongoing licence fees you were never told about at quote time. Model and platform costs are real, they are yours, and they belong in the quote — not in a surprise invoice in month three.
Access to your own system. Nobody external should be holding the credentials to a process your business depends on.
How to sanity-check any quote
Ask three questions of whoever is quoting.
- What annual saving is this number derived from, and how did you measure it?
- What does it cost me to run per month once you have gone?
- Who on my side will be able to change it, and how do they learn that?
A quote that cannot answer the first question is a guess. One that cannot answer the third is a subscription.
Last updated 18 August 2026 by Hugo, founder of Hugo Signal.
Bring me the process that wastes the most time.
A first call takes thirty minutes. You will leave it knowing whether automation is worth doing at all in your case.