How to choose an AI automation partner: 10 questions to ask before you sign

A good automation partner can tell you, before you pay for a build, how many hours it should save, what it will cost to run, and what happens when it breaks. If a vendor can't answer those three things in plain language, keep looking.

Below are ten questions to ask on the first call, grouped by money, scope, control, and life after launch. Each one comes with what a good answer sounds like and the answer that should end the conversation.

Money

1. What will this save, and how will we know?

Good answer: a number. "We estimate about six hours a week for your office manager, roughly $10,000 a year at your costs, and here's how we'll measure it after launch." The estimate should come with its assumptions, and there should be a way to check it once the thing is running.

Walk away if you hear "efficiency gains," "transformation," or "it depends" with no follow-up. A partner who won't commit to an estimate before the build won't be able to show you results after it.

2. What's the total cost for the first year?

A build price is only part of it. Ask for the whole picture:

• The build itself
• Any monthly support or maintenance fee
• AI usage costs (the per-use fees AI providers charge, usually modest for small-business work)
• Any new software subscriptions the build needs

Good answer: an itemized estimate, with usage costs shown separately and passed through at cost.

Walk away if it's hourly billing with no cap on a small project, or if AI usage is bundled into a monthly fee you can't see inside.

3. Is the price fixed?

Good answer: a fixed price for an agreed scope. If you ask for changes later, they're quoted before any work starts.

Walk away if the scope is vague and the contract is open-ended. That's how a $5,000 project becomes a $20,000 one.

Scope

4. What's the smallest useful first project?

Good answer: one workflow, live in a few weeks, chosen because it has the fastest payback. Something like "file every incoming client document automatically" or "draft replies to your ten most common emails."

Walk away if the first proposal is a company-wide platform or a long roadmap before anything has been proven. Start small, and the second project goes better because of what you learned in the first.

5. Will this work with the tools we already use?

Good answer: specific. "We'll build inside your Microsoft 365 and connect to QuickBooks. Nothing new for your team to log into." If something new really is needed, they say so up front and explain why.

Walk away if the plan requires moving your files, email, or accounting into their platform.

6. What do you need from our team?

Good answer: a short, concrete list: a kickoff meeting, access to the tools involved, and one person who can answer questions.

Walk away if it's vague, or if the answer is "your team will need to learn" a new system before anything gets easier.

Data and control

7. Where will our data live, and who can access it?

Good answer: in your own accounts, with access limited to what each automation needs, and a written list of every permission they hold. You should be able to revoke any of it yourself.

We cover this in more depth, with seven data-specific questions, in the owner's guide to letting AI touch your files.

8. What happens when it makes a mistake?

Every automation gets something wrong eventually: an oddly formatted invoice, an email that doesn't fit the pattern.

Good answer: a person always approves anything that sends money or changes payment details. Customer emails and file deletions wait for a person too, at least until you've seen them work for a while. Every action is logged somewhere you can read, and there's an off switch you control.

Walk away if the answer is "the AI is very accurate." That tells you nothing about what happens when it's wrong.

After launch

9. What happens when something breaks in month four?

The tools your automation connects to will change. A form gets a new field, or a software update renames something, and the automation can stop working without anyone noticing.

Good answer: a monitoring and support plan with a clear monthly price, or a clear per-fix rate if you'd rather not have a plan. Either way, you know who to call and what it costs before it happens.

Walk away if you hear "it won't break."

10. If we stop working together, what do we keep?

Good answer: everything. The automations run in your accounts, you have documentation of what was built, and ending the relationship doesn't switch anything off.

Walk away if the automations run inside the vendor's own account or platform and can't be handed over.

Red flags on the first call

• They show slides but can't show a working example.
• They quote a guaranteed percentage of time saved before they've seen how you work.
• They can't explain what they'd build without jargon.
• They want a long contract before you've seen a first result.
• They ask for administrator access to everything "to make it easier."

Comparing two proposals

Put them side by side. If a proposal can't fill in a row, that's an answer too.

Our answers

We'd rather you ask us these questions than take our word for anything. Our prices are on the pricing page, our process is on how it works, and our data practices are on the security page. If you're comparing proposals, book a free call and bring the table above; we'll fill in our column on the call.