How to Evaluate a Workflow Automation Consultant Before You Hire
The 12 questions that separate consultants who ship from ones who demo: who owns the system, who fixes a broken integration, what the monthly covers.
The questions that tell you whether a workflow automation consultant can actually ship are not about their tools or their portfolio. They are about ownership, maintenance, and whether they will ever tell you no. Ask who owns the system if you cancel, what the monthly fee covers line by line, and who pays when an integration breaks — three answers that reveal more than an hour of demos.
Here are twelve questions worth asking, in the order that saves you the most time, with the answers that should reassure you and the ones that should not. We answer each on our own behalf as we go, because a page like this is only useful if the person writing it is willing to be held to it.
Start with who owns the system
Question 1: If I stop paying you, do I keep what you built?
Ask this first, before scope, before price. The answer sorts the market in one sentence.
Many retainers are structured so the automation lives in the consultant’s account, on the consultant’s platform licence, and stops working the day you cancel. That is a defensible business model, and it is also a completely different purchase from the one most owners think they are making. You are renting access, not buying an asset, and the monthly fee is permanent by design.
Our answer: you keep the system and its documentation, the agreement is month to month, and the build runs in accounts you own. We would rather you leave with something working than stay because leaving breaks your business.
Question 2: Whose accounts does this run in?
The follow-up that stops a vague answer. If the automation platform, the API keys, and the phone number are all in the consultant’s name, question 1’s answer is “no” regardless of what they said.
What happens when an integration breaks
Question 3: An integration breaks on a Tuesday. Walk me through exactly what happens.
Integrations break. Platforms change their APIs without consulting your vendor, and your vendor finds out the same way you do. This is not a hypothetical to be reassured about; it is a routine event with a response path, and you want to hear the path.
A good answer has three parts: something was monitoring and noticed, a named person is responsible, and the repair is covered. A bad answer is “just email us and we’ll take a look,” which means nothing was watching and the clock starts when you notice — which, for a silent failure, might be three weeks of lost leads later.
Question 4: Is that repair billed separately?
If break-fixes are hourly on top of the retainer, your actual monthly cost is unknowable, and the consultant is paid more when their build is less reliable. Ours are included in the $250.
Ask what the monthly fee covers, line by line
Question 5: What exactly do I get for the monthly fee?
Make them enumerate. A real answer names five things: hosting and platform management, monitoring with error alerts, break-fixes, a defined allowance of changes, and a scheduled check-in. An answer like “ongoing support and optimisation” is a budget rather than a service, and it is where hourly billing reappears later.
Our answer: those five, with the change allowance set at up to an hour a month. The number matters less than the fact that there is one.
Question 6: What is not included, and what will I be billed by someone else?
Platform subscriptions, AI model usage, phone numbers, and carrier registration are real costs that belong to you. Typically $20 to $100 a month for a small build. A consultant who does not raise these is either inexperienced or counting on you not asking. The full list and what we charge against it is in what a workflow automation consultant costs.
Ask to see a workflow map, not a dashboard
Question 7: Can you show me a map of a workflow you built, including the failure cases?
Demos show the happy path. A lead arrives, the system responds, everyone smiles. The interesting part of any automation is what happens when the input is malformed, the API times out, the customer replies something unexpected, or two systems disagree about who the customer is.
A workflow map shows the handoffs and the exception branches. A dashboard shows that something happened. Ask for the former. If the only artefact anyone can produce is a screen recording of the happy path, the exceptions probably have not been thought about yet.
Question 8: What did you learn from a build that went wrong?
Everyone who has shipped more than a handful of systems has one. A consultant with no failure stories has either not built much or is not being straight with you.
Check whether they will tell you not to automate something
Question 9: Give me an example of something you told a client not to automate.
This is the question we would ask first if we were buying. A consultant who automates whatever is requested is selling hours, and the easiest way to sell more hours is to agree with the client about what is broken.
There are four common reasons not to automate a process, and a consultant who knows the work will name some of them unprompted: the process is not settled yet, so automating it locks in a version you are about to abandon; it happens rarely, so the build never pays back; it is a single connection between two apps that you could do yourself in an afternoon; or nobody will own it, which means it will quietly stop working and you will not notice because you have started trusting it.
Our answer: that list is on our main workflow automation consulting page under “when automation isn’t worth it,” and the whole point of a paid discovery is that it is allowed to conclude “don’t.”
Scope and timeline questions
Question 10: What does the first week produce?
A real answer names an artefact — a workflow map, a prioritised list, a working piece of the build. A vague answer means discovery is being billed as progress.
Question 11: What does “done” mean, and who decides?
Done should mean tested against the exceptions, documented, and handed to a named person on your side who has been trained on it. If done means “deployed,” you will be the one discovering the edge cases.
For reference on duration: a single workflow is typically two to three weeks of build once the consultant has system access, after one or two weeks of discovery. Three months for one workflow deserves the question “what happens in weeks three through ten.” Three days deserves “how are you testing the exceptions.”
Pricing transparency
Question 12: What will this cost, roughly, before we book a call?
If the price only exists after a discovery call, that is a signal — not a disqualification, because scope genuinely varies, but a signal. It means you cannot compare two consultants without sitting through two sales processes, and it means the quote can be sized to what the call suggested you could afford rather than to the work.
Ask for a range in writing first. A consultant who has done this work before can give you one in a sentence.
Our answer: $1,200 to build one system, $250 a month to run it, $750 for the two-week audit and credited toward the build. That is on the pricing page, and the reasoning behind each number is in what a workflow automation consultant costs.
The same twelve questions apply if the person you are talking to calls themselves a business process automation consultant — the title varies more than the work does.
The twelve questions
- If I stop paying you, do I keep what you built?
- Whose accounts does this run in?
- An integration breaks on a Tuesday — walk me through exactly what happens.
- Is that repair billed separately?
- What exactly do I get for the monthly fee?
- What is not included, and what will I be billed by someone else?
- Can you show me a workflow map, including the failure cases?
- What did you learn from a build that went wrong?
- Give me an example of something you told a client not to automate.
- What does the first week produce?
- What does “done” mean, and who decides?
- What will this cost, roughly, before we book a call?
If a consultant answers all twelve without hedging, price is the only thing left to compare. If they hedge on one, three, five, or nine, you have learned something more useful than a quote.
Still deciding whether to hire anyone?
The prior question — hire a consultant at all, or build it yourself with Make, n8n, or Zapier — is a real one, and the tools are good enough now that DIY is sometimes the right answer. The honest case for each is in is hiring an AI automation agency worth it.
What a paid discovery should produce
A discovery you pay for should leave you with something you could hand to a different consultant. Ours is the Clarity Audit: $750, two weeks, and it ends in a workflow map, a ranked list of what is worth automating with a dollar figure against each, and a cost estimate per fix. The fee is credited toward the build if you go ahead — and if the honest conclusion is that you should do it yourself, you still keep the map.
Frequently asked questions
What should I ask an automation consultant before hiring them?
Start with who owns the system if you cancel, what the monthly fee covers line by line, and who fixes a broken integration and whether that is billed separately. Those three answers tell you more than a portfolio does, because they reveal whether you are buying an asset or renting access to one.
How do I know if an automation consultant is any good?
Ask them to show a workflow map rather than a dashboard, and ask for an example of something they told a client not to automate. Good consultants have several; a consultant who automates whatever is requested is selling hours. The map matters because demos show the happy path and maps show the failure cases.
Is it a red flag if a consultant will not give a price without a call?
It is a signal rather than a disqualification. Scope genuinely varies. But it also means you cannot compare two consultants without sitting through two sales calls, and quotes produced after a discovery call are often sized to what the call suggested you could afford. Ask for a range in writing before you book.
Should I pay for a discovery or audit before the build?
Yes, if it produces a document you keep and could hand to someone else. A paid discovery that ends in a proposal is a sales call you funded. Ours is $750 for two weeks and produces a workflow map, a ranked list of what is worth automating, and a cost estimate per fix — and the fee is credited toward the build.
How long should a small automation build take?
Two to three weeks for a single workflow once the consultant has access to your systems, after a discovery of a week or two. If someone quotes three months for one workflow, ask what happens in weeks three through ten. If someone quotes three days, ask how they are testing the exceptions.
Want this applied to your business?
The Clarity Audit finds the 2-3 places your business is leaking and what each one is worth fixing. Prefer to talk? Call (719) 314-1500.
No obligation to build afterward. If a fix isn't worth it, the audit says so.
Recommended services and industry hubs
See how Alpenglow AI implements these systems directly inside real operations.
Marketing Agencies
White-label AI tools, client reporting, and internal workflow automation for marketing agencies.
Industry Hub →Workflow Automation Consultant
Custom workflow automation and systems to eliminate manual admin work and accelerate lead response.
Service Hub →AI Clarity Audit
A 2-week deep dive into your operations to find leaks and prioritize high-ROI automations.
Audit Hub →