How to hire an AI automation consultant.
Fifteen questions to ask, what a good answer sounds like, and the red flags worth ending a conversation over. We have printed our own answer under every question, so you can use this checklist against us as easily as against anyone else.
- 15 vetting questions
- Our answers included
- 9 red flags
- Deal-losing questions
Know what you are buying first.
The hardest part of hiring for automation work is that you are buying something you cannot inspect. A demo looks the same whether the workflow behind it is well built or held together with string, and the difference only shows up months later when an API changes.
So vet the process rather than the output. Everything below is designed to reveal how someone works: whether they scope before quoting, whether they hand over what they build, and whether they will tell you no. Get a written scope from at least two people before choosing - a free written audit is a reasonable thing to expect from any of them, and comparing two written reports tells you more than comparing two calls.
It also helps to know roughly what the work should cost before anyone quotes. Our 2026 cost breakdown gives market-typical figures per workflow so you can tell an unusual number from a normal one.
Do the cheapest preparation first: write down what you want automated before you talk to anyone. The automation audit template scores your recurring tasks and picks the top three, and the proposal template gives every bidder the same brief so the quotes you get back are actually comparable. Both are free and neither depends on hiring us.
It also helps to arrive knowing what good looks like in your trade. The workflows worth building first differ between a dental practice, an HVAC or plumbing firm, a cleaning company, a salon, and an accounting firm. A consultant who cannot talk fluently about the ones on your page has not worked in your world.
15 questions, with our answers underneath.
- 1
Who will actually build this, and will I speak to them?
- Why it matters
- The most common small-business complaint is that the person who sold the work is not the person who did it, and detail was lost between the two.
- What a good answer sounds like
- A named individual, available on calls, with the authority to change scope. If it is a team, you should still be told who owns your build.
- Our answer
- One person. You talk to the person who does the building on every call, including the first one. There is no account manager layer, which is also the main limitation of hiring us - see the honest version of that on our comparison page.
- 2
Have you automated something like my process before?
- Why it matters
- Domain shape matters more than industry. A consultant who has done invoice chasing understands ledger edge cases regardless of whether it was for a clinic or a builder.
- What a good answer sounds like
- A specific description of a comparable workflow, including what went wrong in it. Vagueness here usually means the answer is no.
- Our answer
- We work on lead capture and follow-up, invoicing and payment chasing, support and email triage, reporting, document and data entry, and scheduling. If your workflow is outside that, we will say so rather than learn on your budget.
- 3
What will you need from me, and how many hours of my time?
- Why it matters
- Automation projects stall on client availability far more often than on technical difficulty. A consultant who has not thought about your time cost has not run many projects.
- What a good answer sounds like
- A concrete number of hours and a list of what they need: access, example records, decisions about edge cases.
- Our answer
- Expect roughly two to five hours of your time across a single-workflow project: the consult, one or two review sessions, edge-case decisions, and the handover walkthrough. We ask for access only to what the workflow needs, when it needs it.
- 4
Will you quote a fixed price, and what is in scope?
- Why it matters
- An hourly arrangement transfers all estimation risk to you, and you cannot supervise the estimating.
- What a good answer sounds like
- A written fixed price per scoped workflow, with an explicit list of what is included and what would be a change request.
- Our answer
- Fixed price per workflow, in writing, agreed after the free consult. Scope, exclusions, and what counts as a change request are written down before anything starts.
- 5
What happens to the price if it turns out to be harder than you thought?
- Why it matters
- This separates people who mean 'fixed price' from people who mean 'opening price'.
- What a good answer sounds like
- Some version of 'that is our risk, unless you change the scope'. Then ask what counts as a scope change.
- Our answer
- Our estimating error is our problem. The price moves only if you ask for something that was not in the written scope, and we tell you the new number before doing the work, not after.
- 6
Do I own what you build? What exactly do I receive at handover?
- Why it matters
- This is the question that most cleanly separates a consultant from a vendor renting you a process.
- What a good answer sounds like
- A specific list: workflow source or export, credentials in your accounts, documentation, and a walkthrough. 'You'll have access' is not the same as ownership.
- Our answer
- You own all of it. Handover is the workflow source and configuration, every account and credential in your own name, written documentation of how it works and how to change it, and a recorded walkthrough video. Nothing stops working if you stop working with us.
- 7
Whose accounts will the tools and subscriptions live in?
- Why it matters
- If the automation platform account belongs to the consultant, you do not control your own process and you cannot leave cleanly.
- What a good answer sounds like
- Your accounts, your billing, your ownership, with the consultant added as a collaborator you can remove.
- Our answer
- Your accounts, billed to you directly at list price. We do not resell subscriptions or mark them up, and you can revoke our access at any time without anything breaking.
- 8
What happens when it breaks at 2am?
- Why it matters
- Automations fail. APIs change, credentials expire, a vendor ships a breaking update. What matters is whether failure is silent.
- What a good answer sounds like
- Error handling, alerting to you, and a documented fallback to the manual process. Plus a stated response expectation.
- Our answer
- Every workflow logs what it did and alerts on failure, and anything customer-facing or financial degrades to the manual path rather than doing something wrong. We agree a response expectation in writing; we are one person, so we tell you honestly what that is rather than implying 24/7 cover.
- 9
What will you refuse to automate?
- Why it matters
- Any consultant who will automate anything you ask has an incentive problem. The good ones have a list.
- What a good answer sounds like
- A real answer: low-frequency work, processes with no stable rules, anything where the exception rate exceeds the happy path, decisions with legal or safety consequences.
- Our answer
- Work that runs a couple of times a month, processes still changing weekly, judgement calls with real consequences, and anything where the payback maths does not clear roughly twelve months. We would rather say no on the call than deliver something you switch off in a quarter.
- 10
How do you handle my customer data?
- Why it matters
- Automation projects usually touch customer records. You are responsible for that data regardless of who built the workflow.
- What a good answer sounds like
- Least-privilege access, credentials in your accounts, no unnecessary data copies, and a clear statement about what is sent to which AI provider.
- Our answer
- We ask only for the access a specific workflow needs, keep credentials in your accounts, and avoid exporting data where the workflow can read it in place. We tell you which model provider processes what, before you approve it.
- 11
What are the ongoing costs after handover?
- Why it matters
- A build fee that ignores running cost hides the real total. Subscriptions and model usage continue forever.
- What a good answer sounds like
- An itemised monthly estimate covering platform subscriptions, AI usage, and any support arrangement, with support optional.
- Our answer
- We itemise expected monthly subscription and usage cost as part of the quote. Support afterwards is optional and priced separately; the automation keeps running whether or not you buy it.
- 12
What could go wrong, and where does a human stay in the loop?
- Why it matters
- A consultant who cannot name failure modes for your workflow has not thought about it properly.
- What a good answer sounds like
- Specific failure modes for your process, plus a proposal for where approval steps sit and when they can safely be removed.
- Our answer
- We map the risky points during scoping and default to a human approving anything that sends to a customer, moves money, or deletes. Once you have watched it behave for a few weeks, you decide which approvals to drop.
- 13
Can you show me how it works, or only that it works?
- Why it matters
- A demo proves nothing about maintainability. Being walked through the logic proves the consultant understands what they built.
- What a good answer sounds like
- Willingness to open the workflow and explain the branches in plain language, before you have paid anything.
- Our answer
- We will screen-share the internals of a comparable workflow on the consult and explain each step. If we cannot explain it in plain English, it is too complicated to hand over.
- 14
What is the smallest useful thing we could start with?
- Why it matters
- A consultant reaching for a large first project either does not understand small business cashflow or is optimising for their own revenue.
- What a good answer sounds like
- An eagerness to shrink the first build, prove value, and expand from there.
- Our answer
- One workflow, the one with the shortest payback, shipped before we discuss anything else. The written audit ranks candidates so you can pick the small one deliberately rather than by accident.
- 15
What would make you tell me not to do this?
- Why it matters
- The single most revealing question on the list. Everyone claims honesty; few can produce an example on demand.
- What a good answer sounds like
- A concrete scenario in which they would decline the work and what they would advise instead.
- Our answer
- If the payback is beyond a year, if the process is not stable enough to encode, if your existing tools already do it and nobody switched the feature on, or if the real problem is a staffing or pricing decision rather than an admin one. All four happen, and all four end with us not invoicing you.
Nine things that should slow you down.
The course-grad reseller
Finished a six-week AI agency course, bought a template pack, and is selling the same three workflows to everyone. Tell: cannot answer question 12 about failure modes for your specific process, and describes the tooling rather than your business. Not disqualifying on its own - everyone starts somewhere - but the price should reflect it, and you should never be their first invoice-chasing build at a premium rate.
Guaranteed results
'Guaranteed 40% time savings' or 'we guarantee 10 extra leads a month'. Nobody can guarantee an outcome that depends on your data quality, your team's adoption, and your market. A guarantee that specific is either meaningless in the contract or is going to be met by redefining the measurement.
No source-code or workflow handover
The workflow lives in their account, and you get a dashboard. Ask what you receive on the last day of the engagement. If the answer does not include the workflow itself and the credentials, you are renting a process your business depends on.
Mandatory retainer to keep it running
Support you can buy is fine and often sensible. Support you must buy or the automation stops is a lock-in with a friendly name. Ask directly: if I stop paying you, does it keep working?
Marked-up subscriptions
Software resold to you at a margin, billed through them, in their accounts. You lose price transparency and the ability to leave. Tools should be in your name at list price.
Proprietary platform lock-in
'We build on our own platform' usually means the automation cannot be exported, and no other consultant can ever maintain it. Sometimes justified; it should be stated openly and priced as a trade-off, not discovered at handover.
Discovery-free quoting
A price given before anyone has asked what systems you use or how often the task runs. Either the number is padded to cover the unknown, or it will be revised upward once the unknown appears.
Pressure tactics
An expiring discount, a 'we only take two clients a month' scarcity line, or a contract sent before the scope document. Good automation work does not need urgency manufactured around it.
AI-first, problem-second
The proposal leads with the model, the framework, or the agent architecture rather than with your process. If they cannot describe your workflow back to you in your own words, they have not listened to it.
None of these are automatically disqualifying on their own. A specialist platform choice can be right, and everyone selling automation was new to it at some point. Two or more together, or any one of them plus reluctance to answer question 6 about handover, is a reason to keep looking.
The platform answer is the one worth probing hardest, because it decides whether you can ever change supplier. Ask which workflow platform they build on and why - Make, Zapier, and n8n compared is enough background to tell a considered answer from a habit, and the stack picker will suggest a shortlist from your own constraints so you have something to hold their answer against.
Questions that should make any consultant lose the deal.
Ask these late in the conversation, when the pitch is over. The wrong answer to any one of them is worth more than every case study you were shown.
A losing answer: it stops, or you keep paying a hosting fee, or 'we would migrate it for you' at an unspecified cost. Ownership either exists on day one or it does not.
A losing answer: an inability to produce one. Everyone who has run real projects has turned work down. Someone who never has is either very new or is selling regardless of fit.
A losing answer: a package tier, or an industry benchmark. A real estimate references your number of systems, your exception rate, and your data quality.
A losing answer: theirs, bundled, or 'we handle all that'. Convenience that costs you control and price transparency.
A losing answer: they cannot show a redacted example, because it does not exist yet. Documentation written after the project is documentation that never gets written.
A losing answer: 'it doesn't go wrong'. Every automation fails eventually. The right answer is about logging, alerting, and the fallback to manual.
Use this list on us too
Structure the first engagement to limit your downside.
- Start with one workflow. Preferably the one with the shortest payback, not the one that annoys you most. You are buying information about the consultant as much as you are buying the automation.
- Get the scope in writing, in your words. If the scope document does not describe your process in language you would use, they have not understood it.
- Set up the accounts yourself. Create the tool subscriptions in your own name and invite them in. Five minutes now, no migration project later.
- Agree the handover contents before work starts. Source, credentials, documentation, walkthrough. Written down, not assumed.
- Keep the manual process alive for a few weeks. Run both in parallel until you trust the automation. Cheap insurance.
For what the engagement itself should look like week by week, see what an AI automation consultant actually does. If you are still deciding between an independent, an agency, and doing it in-house, the side-by-side comparison covers that choice honestly, including when not to hire us. Our own version of the engagement, from scoping through to handover, is on the automation services page.
One last calibration exercise, and it is free: read a full build end to end before you commission one. The missed-call text-back guide and the quote follow-up guide show the guards, the failure modes, and the compliance steps a competent builder handles without being asked. If a quote you receive skips them, you now know what to ask about.
Hiring an AI automation consultant: FAQ
What should I ask an AI automation consultant before hiring them?
Start with ownership and scope: who actually builds it, will they quote a fixed price in writing, what exactly do you receive at handover, and whose accounts the tools live in. Then ask what they would refuse to automate and what would make them tell you not to do the project. The last question is the most revealing, because it cannot be answered convincingly by someone selling regardless of fit.
How much should I expect to pay an AI automation consultant?
For a single well-scoped workflow, market-typical build fees sit roughly in the low-to-mid four figures, with tool subscriptions on top. Multi-step pipelines across several systems commonly reach the high four or low five figures. Ask for a fixed price per workflow rather than an hourly rate, so estimation risk sits with the builder.
Is a solo consultant or an agency better for a small business?
For a small business with one or two workflows to automate, a solo consultant usually gives more of your budget to actual building and gives you direct access to the person doing it. An agency is worth the overhead when you need several workstreams in parallel, guaranteed continuity if one person is unavailable, or a formal procurement process.
What are the biggest red flags when hiring an automation consultant?
Guaranteed results, no source-code or workflow handover, a mandatory retainer for the automation to keep running, software subscriptions resold at a markup in the consultant's accounts, and a price quoted before anyone asked what systems you use. Any one of these is a reason to slow down; two together is a reason to walk.
How do I check that a consultant is technically competent?
Ask them to open a comparable workflow and walk you through the branches in plain English before you have paid anything. Competence shows up as a willingness to explain the logic and to name the specific ways it could fail with your data, not as a polished demo.
Should I hire someone who only does one automation platform?
Specialisation is fine and often produces better work, but it becomes a problem when the tool is chosen before the problem is understood. The test is whether they can explain why that platform suits your particular workflow, and whether they will tell you when a feature you already pay for would do the job instead.
What should be in the contract?
The scoped workflow described in your own words, the fixed price, what counts as a change request, what you receive at handover including source and credentials, who owns the resulting work, data handling terms, and any support arrangement stated as optional rather than as a condition of the automation continuing to run.
How long should hiring take?
Usually under two weeks. A first conversation, a written scope or audit, and a fixed quote. If someone needs longer than that to tell you what they would build and what it would cost, the project is either genuinely complex - in which case they should say so - or they have not scoped it.
Keep reading
- Free AI automation auditTest us against this checklist. A 30-minute call and a written report, no obligation.
- AI automation cost in 2026Market-typical build and running costs so you can judge a quote.
- Consultant vs agency vs DIYWhich type of help fits your budget, timeline, and appetite for maintenance.
- AI automation servicesHow we scope, build, and hand over automations.
Ask us all fifteen.
Book the free consult and run the checklist live. If our answers on the call differ from the ones printed on this page, do not hire us.
