A good AI consultant understands your business before pitching a tool, can show real shipped work, proposes a small pilot with clear metrics, protects your data, and leaves you owning what they build. Run them through the 11-point checklist, ask the eight questions, and watch for the red flags — chiefly hype over substance, no real deployments, and a push toward a big build before proving value. The simplest rule: hire whoever gets you a small, useful result fast, then builds from there.
A practical companion to Why We Tell Half Our Clients They Don’t Need AI (Yet) and Process-First AI Adoption.
How do you vet an AI consultant?
You vet an AI consultant by checking that they understand your business before pitching any tool, can point to real shipped projects like yours, propose a small pilot with clear success metrics, and let you own what they build. The best ones will even tell you when not to use AI — and start small instead of selling a big build.
Hiring an AI consultant is a high-variance bet. Get it right and a painful workflow quietly starts running itself; get it wrong and you burn a budget on a system nobody uses. The odds aren’t comforting: MIT’s Project NANDA found 95% of enterprise generative-AI pilots delivered no measurable return — and concluded the cause was mismanaged adoption, not weak models (Fortune). The single biggest factor in which side of that line you land on is who you hire to do the work.
The good news: you can tell a lot in the first conversation. A consultant who creates value behaves differently from one who sells hype — they ask about your business before they talk about models, they reach for the smallest thing that works, and they’re honest about limits. Use the checklist below to make that difference impossible to miss.
The 11-point vetting checklist
Run any prospective consultant against these eleven criteria. You don’t need a perfect score — but a string of weak answers, especially on proof, pilots, and ownership, is your cue to walk.
Business understanding
Can they explain your industry, customers, and workflow back to you in plain language — before they mention a single tool?
Relevant proof
Have they shipped real AI projects like yours — in production, with results — not just demos, slide decks, or pilots that never launched?
Clear use cases
Do they name the specific problems AI should solve for you, instead of claiming “AI can help with everything”?
Measurable ROI
Can they estimate the payoff — time saved, revenue gained, cost or risk reduced — and tie it to a number on your P&L?
Data readiness
Do they ask what data you have, where it lives, and whether it's actually usable — before promising anything?
Security and privacy
Can they explain how they'll protect your customer data, employee data, and confidential business information?
A pilot-first plan
Do they propose a small pilot first, with a clear timeline and success criteria — rather than a big build up front?
Ownership
When the project ends, do you own the outputs, the documentation, and the workflows — or are you locked in?
Handover and training
Will they teach your team to use and maintain the solution, so you're not dependent on them forever?
Who actually does the work
Is the senior person you met the one doing the work — or does it get handed to juniors after you sign?
Communication style
Can they explain tradeoffs and limitations without hiding behind jargon?
A good AI consultant talks about your workflow first and the model last.
What questions should you ask an AI consultant?
Ask questions that force specifics: what problem they’d solve first and why, what a 30-day pilot looks like, what data they need, how they’ll measure success, what could make it fail, and who actually does the work. Vague, tool-centric answers are the tell; concrete, business-centric ones are the signal.
Bring these eight to the first call. The content of the answers matters less than their shape — a real operator gets specific fast, a salesperson stays abstract.
- 1
What business problem would you solve first in my company, and why?
- 2
What would a 30-day pilot look like?
- 3
What data would you need from us?
- 4
How will you measure success?
- 5
What are the biggest risks or reasons this might fail?
- 6
What happens after launch?
- 7
Who on your team will actually do the work?
- 8
Can we keep and reuse everything you build?
Good signs and red flags
Beyond the checklist, the overall posture of the conversation tells you most of what you need to know. Here’s what to lean toward — and what should make you pause.
- They ask thoughtful questions before pitching solutions.
- They talk about your workflow, not just the latest AI model.
- They suggest starting small.
- They are honest about what AI should not be used for.
- They offer a clear path from pilot to full rollout.
- They talk more about AI hype than your business.
- They can't show examples of real, shipped deployments.
- They dodge questions about security, costs, or failure cases.
- They promise guaranteed results or fast transformation — without understanding your operations.
- They push a large custom build, or a big contract, before proving value on something small.
- They won't name a single past failure or project that didn't work.
What’s the simplest rule for choosing?
The simplest rule: choose the consultant who can get you a small, useful result fast — then build from there. A real pilot that moves one number beats a six-figure roadmap every time, because it proves value before you commit budget and leaves you with something that actually works.
This is the same discipline we apply to the tools themselves: start with the lightest thing that fully solves the problem, prove it, and scale only what earns the right to be scaled. (It’s why we tell half our clients they don’t need AI yet, and why our whole method is process-first, not tool-first.)
Choose the consultant who helps you make a small, useful result fast — and then builds from there.
FAQ
What should I ask an AI consultant before hiring them?+
Ask what problem they'd solve first and why, what a 30-day pilot would look like, what data they need, how they'll measure success, what could make it fail, what happens after launch, who actually does the work, and whether you keep everything they build. Specific answers signal a real operator; vague ones are a warning.
What are the biggest red flags when hiring an AI consultant?+
The loudest red flags: they talk more about AI hype than your business, can't show real shipped deployments, dodge questions about security and cost, promise guaranteed results or fast transformation, and push a large custom build before proving value on anything small. Any one of these is a reason to slow down.
Should an AI consultant start with a pilot?+
Yes. A good consultant proposes a small, time-boxed pilot with clear success criteria before any large build — usually around 30 days. A pilot proves value on a real workflow at low cost and low risk, and gives you the evidence to decide on a full rollout. Insisting on a big upfront contract is a warning sign.
Who should own the AI system after the project ends?+
You should. Make sure the contract gives you the outputs, the documentation, and the workflows, plus training so your team can run and maintain the solution without the consultant. If you'd be stranded the day they walk away, you don't have a solution — you have a dependency.
How can an AI consultant prove ROI before I commit?+
By estimating the payoff up front — time saved, revenue gained, cost or risk reduced — then proving a slice of it in a pilot measured against a baseline number on your P&L. A consultant who can't or won't put a number on the outcome is asking you to buy on faith.