7 Questions to Ask Before Hiring an Automation Agency in 2026
Before hiring an automation agency, ask seven things: who owns what they build, what happens when you cancel, how they scope before quoting, what their process-first approach looks like, which of your existing tools they keep, how they hand over, and what proof they have in your business shape. The answers separate system builders from dependency renters.
The fastest way to evaluate an automation agency is not their portfolio. It is watching how they answer seven specific questions, because the answers reveal the business model behind the pitch. Some agencies build systems you own and walk away. Others build dependencies you rent forever. Both look identical in a sales call until you ask.
I run an agency, so read this knowing where I stand. But these are the questions I would ask anyone, including us, and I have included what a good answer sounds like and the red flag version of each.
1. Who owns what you build?
The only acceptable answer is: you do, fully, including logins, documentation and the right to change anything without us. Automation work lives inside your CRM, your accounting platform and your inbox. If the agency holds the master accounts or builds in a workspace you cannot access, every future change routes through their invoice.
Red flag: "We manage the infrastructure for you so you do not have to worry about it." Translated, that sentence means the off switch is in their pocket.
2. What happens when I cancel?
A good answer is boring: the systems keep running, you keep everything, and the documentation is already in your drive. We put this in writing as "cancel us, keep everything" because the question deserves a contractual answer, not a reassuring tone. Ask for it in the agreement, not the call.
Red flag: a retainer that bundles "maintenance" without which things mysteriously stop working. Well-built automation does not need a babysitter. It needs an owner, and the owner should be you.
3. How do you scope before you quote?
Good agencies diagnose before they prescribe. That means mapping how your business actually runs, putting a dollar figure on each leak, and only then proposing what to build. The quote should name your workflows, your systems and your numbers, not a package tier with a seat count.
Red flag: a price in the first conversation. If someone can quote you before seeing your operation, they are quoting their template, not your problem. In the builds we have done, the first scoped assumption survives contact with real data about half the time. The other half, the diagnosis changes the plan, which is the point of doing one.
4. Are you process-first or tool-first?
Ask what they would do if the best fix involved no new software at all. A process-first agency redesigns the workflow, then automates what remains. A tool-first agency sells you their preferred stack and bends your workflow around it, because their margin lives in the stack.
A useful tell: ask them to describe a project where they removed software instead of adding it. We have had engagements where the honest recommendation was connecting the systems the client already ran rather than adding anything new. Any agency that has been operating for a while should have a story like that. If every story ends in a new subscription, you have your answer.
5. Which of my existing tools do you keep?
The default answer should be: all of them that work. Your team already knows your CRM, your accounting platform and your field or inventory system. Replacing tools your team knows is a cost measured in months of retraining and data migration, and it should need a strong reason, not an agency preference.
Red flag: a proposal that begins with a migration to the agency's favourite platform. Sometimes that is right. It is suspicious when it is always right.
6. How do you hand over?
The deliverable is not the automation, it is your team running the automation without the agency. Good answers include written documentation, recorded walkthroughs, a named owner on your side trained during the build, and a defined support window after go-live. Ask to see a handover document from a past project with the client details removed.
Red flag: "You will not need to touch anything." That line sounds like service and functions like lock-in. Independent cost comparisons put inventory platform implementations at $5,000 to $30,000, and the number one reason that money gets wasted is a handover that never happened, a pattern we covered in the Cin7 Core vs Unleashed vs Katana comparison.
7. What proof do you have in a business shaped like mine?
Ask for numbers from a comparable operation: team size, revenue band, industry shape. Not logos, numbers. Across our own work that means things like 200+ hours a month returned to a fleet operator and 250+ SKUs live in one connected system in 5 days for a logistics client, published on our results page. Whoever you talk to should be able to match that specificity for a business that looks like yours.
Red flag: case studies with impressive brand logos and no numbers attached. A logo tells you someone paid them once. A number tells you what happened next.
What these seven questions are really testing
Every question above is the same question wearing different clothes: does this agency make money when you succeed, or when you stay? Builders get paid for outcomes, document everything, and are comfortable being cancelled. Renters get paid for access, hold the keys, and are very interested in your renewal date.
A logo tells you someone paid them once. A number tells you what happened next. Ask for the numbers.
If you want to run these seven questions against us, that is what the free strategy session is: thirty minutes on your operation, a straight answer on whether an engagement makes sense, and the same ownership terms in writing either way.
Frequently Asked Questions
What should I ask an automation agency before hiring them?
Seven things: who owns the build, what happens on cancellation, how they scope before quoting, whether they are process-first or tool-first, which existing tools they keep, how handover works, and what numbers they can show from businesses shaped like yours.
Should an automation agency own the accounts and infrastructure?
No. You should hold every login, workspace and document, with the agency working inside access you grant. Agency-held infrastructure means every future change routes through their invoice, and cancellation can turn the systems off.
Is a monthly retainer with an automation agency a red flag?
Not by itself. A retainer for new work or genuine improvements is normal. The red flag is a maintenance retainer without which the existing automations stop working, because well-built systems do not need a babysitter to keep running.
How much should automation agency work cost?
Scoped project work for $1M to $10M businesses typically runs from a few thousand for a diagnostic to five figures for a full build. Anyone quoting a precise price before mapping your operation is quoting a template, not your business.
What does a good automation agency handover include?
Written documentation, recorded walkthroughs, a named owner on your team trained during the build, and a defined post-launch support window. The test of a good handover is that the client can change and extend the systems without calling the agency.
Ready to cut the admin?
Want to put the seven questions to us? Book a free strategy session. Thirty minutes, your numbers, our answers in writing, including who owns everything we would build. That one is easy: you do.