What are the 12 questions to ask before hiring an AI automation agency?
Ask these in the first conversation, not after a proposal arrives. A vendor who cannot answer most of them plainly has not scoped your project yet, whatever the deck says.
| # | Question | What a good answer sounds like | Red flag |
|---|---|---|---|
| 1 | What exact process are we automating, start to end? | Names the trigger, the steps, and the system it lands in | "AI for your business" with no named workflow |
| 2 | What does the agency need from us to start? | A short list: access to systems, a data sample, one point of contact | Vague, or "just sign and we'll figure it out" |
| 3 | Who owns the workflow and the code after launch? | You do, in writing, on a standard stack | Locked into the agency's proprietary platform |
| 4 | What happens to our data, and where does it live? | Named systems, named retention policy, no training on your data without consent | No clear answer, or "trust us" |
| 5 | How is this priced: fixed project, subscription, or hourly? | A number tied to defined scope, not a vague monthly fee for an undefined amount of work | Pressure to sign a long subscription before scope exists |
| 6 | What is explicitly out of scope? | A written list | No list, because everything becomes a change order later |
| 7 | Who maintains this after launch, and what does that cost? | A named support tier with a price | "We'll take care of it" with no defined cost |
| 8 | What happens if the automation gets something wrong? | A defined escalation path and a human fallback | No fallback, or "it won't happen" |
| 9 | Can you show a live example you built, not a demo script? | A real, working system, even a small one | Only slide-deck mockups |
| 10 | What is the realistic timeline, including your team's time? | A range with what could push it later | A single confident number with no caveats |
| 11 | If we want to leave, what do we take with us? | The code, the data, the documentation | Nothing portable; you start over with anyone else |
| 12 | Why this workflow, and not a different one first? | A specific answer about where the labor cost or error rate is highest | No prioritization, just enthusiasm |
Two decide most outcomes: question 3 (who owns it) and question 6 (what's out of scope). Everything else can be renegotiated after launch; those two cannot.
Why do most AI automation projects fail to show a return?
Because most of them are not automating a workflow, they are adding a chat window next to one. The MIT NANDA study drew a sharp line between the roughly 5% of deployments that worked and the 95% that did not: the successful ones were narrow, embedded inside a single real process, and built to learn from that specific context over time. The failures tended to be general-purpose tools layered on top of existing work without changing who does what.
For a small business this translates directly into question 1 above. "We'll add AI to your business" is the pattern that fails. "We'll take the phone call → form → CRM → calendar chain that currently needs a person watching it, and make it run on its own" is the pattern that has a chance, because it replaces a specific, measurable piece of manual work rather than sitting beside it. If an agency cannot name the workflow in one sentence, the project is at risk before it starts.
What should an AI automation agency's pricing actually look like?
Pricing structure is itself a signal. Compare two shapes:
A subscription with no defined scope ("$997 a month for AI automation") asks you to commit before anyone has looked at your process, and it is priced to keep charging whether or not the automation ever ships. A project priced against a defined scope, with a support tier after launch priced separately, tells you the vendor has actually looked at the work.
As a reference point, GoodFirms' 2026 Software Development Cost Survey (100+ companies, updated May 29, 2026) found that 71.4% of AI-focused development companies charge $50,000 to $125,000 for a small to mid-scale AI build, a figure that includes integration and testing, not just a chatbot license. Against that backdrop, a realistic small business AI automation project runs $2,500 to $6,000 for one process fully wired up (phone, forms, CRM, calendar), $6,000 to $15,000 for a connected system with multiple integrations or a private document search, and from $15,000 for a full custom build. A free audit before any of that is a reasonable ask; a paid audit is not, and a locked-in monthly fee before scope exists is a bigger flag than the price itself.
Who should own your data and workflow after the project ends?
You should, and the agreement should say so before work starts, not after a dispute. Three things to nail down in writing:
- The code and configuration sit in accounts in your name (or are handed over on delivery), on standard, documented technology, not a proprietary no-code platform only the agency can edit.
- Your data stays yours, is not used to train a model for other clients without your explicit consent, and has a stated retention and deletion policy.
- The workflow logic (what triggers what, what the fallback is) is documented somewhere you can read without the agency in the room.
This is not a hypothetical concern. An agency that owns the platform your automation runs on effectively owns your workflow: leaving means rebuilding, not migrating. Ask question 11 from the table above and get the answer in the contract, not the sales call.
What red flags mean you should walk away from an AI agency's pitch?
A few patterns show up often enough to name directly:
- A guaranteed percentage improvement with no baseline defined ("cut costs by half," "triple your leads"). Without a measured starting point, the number cannot be verified, and it should not be signed as a promise.
- No named workflow, only "AI for your business." Revisit question 1.
- Pressure to commit to a subscription before scope exists. Scope should come first, price second.
- No answer on data, or an answer that dodges where the data lives and who can see it.
- No live, working example, only a slide deck or a generic demo unrelated to your industry.
None of these mean the agency is acting in bad faith; a lot of it is just an incomplete process. But your project is the wrong place to find that out.
When should you build in-house instead of hiring an agency at all?
Sometimes the honest answer to "how do we pick an agency" is "we don't need one yet." If the automation is a single, well-defined integration your existing developer can build in a week, or your team already has the skill and just needs the time, in-house can be the cheaper and more accountable path. The tradeoff between in-house, agency and offshore, with real wage and rate data rather than a rule of thumb, is covered in in-house vs. agency vs. offshore. For most small businesses without a developer on staff already, an agency scoped against the questions above is the faster route to something that actually runs.