What a real engagement covers, what automation consulting services cost in 2026, and how to tell a consultant who ships workflows from one who leaves a slide deck.
The tools are not the shortage. The shortage is a person who will look at last week's work and name the three jobs that should stop being done by hand. Proposals blur together. Discovery. Roadmap. An AI layer. Change management. Here is the version worth paying for, what it costs, and the pages you can cross off.
You are buying a decision, then a build that still runs on a Tuesday when nobody is presenting. Four pieces, and no more than that unless you ask.
A short map of repeating work: who does it, how long, where it breaks. Readable in ten minutes, not a 40-page process bible. A rank of the first three jobs, by hours and by money, not by demo appeal. The joins between systems you already pay for, meaning the CRM, the inbox, the form, invoices, Slack or Teams, and the sheet the ops lead actually opens. Then a handover you can watch: one real lead, invoice, or ticket goes through while you sit there.
Leave out the CRM migration, the custom app, the new site, and any "AI strategy" that never names a workflow. If the proposal cannot say which job stops being manual, you are buying a workshop. The jobs small teams usually pull off the pile first are listed in what small businesses automate first.
Plain automation copies a field from one screen to another. AI automation consulting covers the step that used to need someone reading the message. Sorting inbound mail. Drafting a quote from a messy form. Tagging a ticket. Writing a first reply a human still approves.
That is the product. A shorter queue. The model name is not the product. A consultant who opens with the model, and has not asked what the queue is, is selling a demo. Where agents pay for themselves, and where they stall, is in AI agents for business.
Anything a customer will read stays a draft until someone on your team has agreed the tone. After that, the boring send can run. Complaints, a discount promised on a call, a blank field: those come back to a person. That split is what the system still feels like six months later, when the buyer is no longer the daily user.
Three conditions, all at once. The task happens at least 10 times a week. Someone is copying between two tools you already pay for. A miss costs a lead, a payment, or a customer left waiting. That is when an AI automation consultant earns the invoice.
One Zapier zap does not need a consultant. Forty zaps, with nobody sure which still fire, and a new hire afraid to edit them, does. That is an operations mess wearing a software logo.
"We should do more with AI" is not a brief. Write five repeating jobs down first. If the page stays blank, you are early, and a straight consultant will say so on the first call instead of selling a six-week discovery.
Week 1 is last week's real jobs. Not the org chart. The Friday CSV export, because the CRM report is wrong, pasted into a sheet, then dropped in Slack for sales.
Week 2 is a short plan. Three workflows. Tools you already have. One new tool only if you need it. And a number: hours back, or cash recovered. No number means they have not looked. Do not build on adjectives.
Weeks 3 to 5 are the build on your data. You sign off anything a customer will see. Nothing customer-facing sends itself on day one. Week 6 is handover. A named owner. A log of runs. A way to hear about a failure before the customer does.
Call it business automation consulting or a done-for-you build. The name is less important than week 6 existing. A lot of proposals die on "phase 2 discovery". If you are choosing a firm rather than one freelancer, the differences that matter are in how an AI automation agency is set up.
You can skip the 30-slide deck, the RACI, and any recommendation that starts by throwing out the CRM the team just learned. The test: if they vanished on Friday, could your team open the workflow on Monday? If not, you are renting a black box.
Keep it on tools you can keep. The stack agencies actually run is compared in Zapier alternatives for agencies. The difference between a build and a workshop is in business process automation as a service.
Ranges we see quoted to small and mid-size firms in the US and the UK. Not a rate card. The fair number moves with how many systems the workflow has to touch.
Open hourly blocks with no cap and no definition of done drift. Fix the price per workflow. Hourly is for repairs after handover, not for the first build.
Payback is arithmetic, not a case-study percentage. Six hours a week from someone who costs $40 an hour fully loaded is about $960 a month. A $5,000 build returns in about five months, before the leads you stopped losing. If their maths is worse, make them rerun it on your numbers.
They lead with a model name when you asked about missed leads. The proposal opens with a migration because they will not use your tools. The login is theirs. Stop paying and the workflow stops. The proposal has no number. "Improved efficiency" is not a result.
The case study is logos and no before and after. Ask what the client stopped doing by hand, and how many hours. They want six months before a single workflow is live. The discovery call is a pitch, and they never ask to see the queue. That is a package. Fine for a newsletter tool. A bad fit for the spreadsheet your ops lead built in 2019, which is usually where the time sits.
Do it yourself for one trigger and one action, if you like the tinkering. Form to Slack. New row, send email. Give it a weekend. If you are still debugging on Sunday night, that is the signal to hire, not to buy another course.
A freelancer fits when the workflow and the stack are already chosen. You have the spec. You need someone faster in n8n or Make. Pay for the build, keep the login. Do not expect them to choose which job matters. That choice is the consulting, and most hourly builders will not make it unless the brief says so.
A firm fits when several tools, several people, and customer-facing words are in play, and you want the order picked by someone who has shipped it. You are paying for sequence and handover, not for a smarter zap.
The common miss: hire someone to "do AI" with no map. Six weeks later, a chatbot nobody opens, and invoices still chased on Sunday. Start with Sunday. The chatbot can wait.
Five repeating tasks. Times per week, minutes each, and what a slip costs. Take that page to the first call. A good consultant prices the first workflow from it. A weak one books a workshop before they will say a number.
Want a second look before you hire? We will say which line is worth paying to remove, and which lines to leave alone.
Ready to price the first job? book a free 20-minute walkthrough →