What Automation Consulting Actually Costs

Why Two Quotes for the Same Job Differ Tenfold

Send the same brief to four automation consultants and the spread will be wide enough to make you suspicious of all of them. It usually isn't dishonesty. They're quoting for four different jobs, because your brief left room for four readings.

"Automate our lead follow-up" can mean a form that triggers a templated email, which is a couple of hours. It can also mean routing by territory, deduplicating against an existing CRM, sending across email and SMS, handling replies, logging outcomes, and alerting a human when something fails. That's a fortnight. Both are honest quotes for the sentence you wrote.

The Pricing Models You'll Meet

Per project. A defined scope for a fixed number. Best for a first engagement, because your risk is capped and you find out how the consultant works before committing to more. Watch how change requests are handled, since scope always moves a little.

Hourly or day rate. Common with solo implementers and dev shops. Fine when the work is genuinely exploratory, uncomfortable when it isn't, because you're carrying the risk of their learning curve.

Monthly retainer. Ongoing builds plus maintenance and monitoring. Makes sense once you have several workflows running and something breaking occasionally matters. Makes no sense before you have anything to maintain, and paying a retainer from month one is the most common way small businesses overspend here.

Per workflow. Some shops price by the automation. Clean and comparable, though it encourages splitting one sensible workflow into three billable ones, so ask what counts as one.

What Actually Drives the Number

Five things, roughly in order of impact.

How many systems it touches. One tool talking to itself is cheap. Four tools, each with its own auth, rate limits and data quirks, is where hours go. Every boundary crossed is a place things can fail and therefore a place that needs handling.

Whether your data is clean. This one surprises people and it's frequently the biggest line item. If the same customer exists three times in your CRM with different phone formats, somebody has to sort that before any sync will behave. We've had projects where cleaning and keying the data took longer than building the automation on top of it, and there's no way to skip it. Why your spreadsheet sync keeps creating duplicates explains why.

How much the process varies. "Send a confirmation email" is one path. "Send a confirmation email, unless it's a repeat customer, or the booking is within 24 hours, or they came from the partner channel" is four paths, each needing testing.

Error handling and monitoring. A workflow that works on the happy path is maybe a third of the total effort. The rest is what happens when it doesn't, and it's the part cheap quotes leave out. Ask explicitly whether failure alerting is included, because "yes" and "no" are very different products at the same price.

Documentation and handover. Skipping it makes a quote look better and makes you dependent. Worth paying for.

How to Tell Cheap From Overpriced

A quote that's suspiciously low usually excludes the same things. No audit before building, so they're building what you described rather than what you need. No error handling. No monitoring, so failures are silent. No documentation. Credentials on the builder's personal account, which becomes your problem the day they stop answering.

A quote that's overpriced usually has a different signature. A discovery phase measured in weeks for a business with 12 staff. Custom development for something Make does natively. A retainer attached before anything exists to maintain. Licensing for an enterprise platform when your volume would fit comfortably on a small self-hosted instance.

The useful question on a first call is what happens when it breaks. The answer tells you more about the price than the price does. If they haven't thought about failure, you're buying the cheap version regardless of the number.

Judging It Against Your Own Costs

The only figure that makes a quote meaningful is what the manual version costs today, and most businesses have never worked it out.

Take the task, count the minutes it takes each time, multiply by frequency, multiply by the loaded hourly cost of whoever does it. Two hours a day of copy-paste is roughly a quarter of a full-time salary spent on something software does for a fixed fee. Then add the costs that don't appear on a timesheet: the leads that went cold because follow-up was slow, the invoice entered wrong, the appointment nobody confirmed.

If a build costs less than a year of that, it's usually worth doing. If it costs more than three years of it, it usually isn't, regardless of how good the demo looked. How to calculate automation ROI before building has the longer version, and how much you can save automating has worked examples.

The Costs After the Build

Quotes cover building. Three things cost money afterwards and belong in your budget.

Tool subscriptions, which scale with volume. Zapier bills per task and gets expensive quickly at high record counts, while self-hosted n8n trades that for a server you maintain. Self-hosted n8n server requirements covers what that actually needs.

Maintenance. APIs change, tokens expire, someone renames a field. Budget for a few hours a quarter even on a well-built workflow.

Changes. Your business will change and the automation will need to follow. That's just the normal cost of having one.

A Sensible Way to Start

Buy one small project, not a programme. Pick the workflow with the clearest manual cost, get it built with error handling included, and run it for a month. You'll learn more about whether the consultant is any good from one delivered workflow than from any proposal, and if they're not, you've lost one project fee rather than a retainer year.

If you're still working out which kind of consultant you need, what an automation consultant actually does breaks down the four types, and how to vet an automation consultant covers the questions to ask.

Book a free 60-minute call and we'll scope the actual job, tell you what it should cost, and tell you if the numbers don't justify building it.