5 Questions to Ask Before Hiring an AI Consultant (And What Good Answers Look Like)

# ai# consulting# business# startup
5 Questions to Ask Before Hiring an AI Consultant (And What Good Answers Look Like)Midas Tools

AI consulting is booming. So is AI consulting that overpromises and underdelivers. Before you hand...

AI consulting is booming. So is AI consulting that overpromises and underdelivers.

Before you hand over $5,000–$50,000 to an AI firm, ask these five questions. The answers will tell you everything.


1. "Can you show me something you've built that's live in production?"

The only right answer: yes, with a link.

AI consulting is full of people who can talk about GPT-4 architecture and RAG pipelines but have never shipped something a real customer uses. "We're working on a client project" or "we can't share due to NDA" are yellow flags. One real, live example outweighs ten case study PDFs.

What you're testing for: Do they build, or do they present?


2. "What happens when the AI gets it wrong?"

Every AI system makes mistakes. The quality of an AI consultant is largely determined by how they design for failure — not how they demonstrate success.

Good answers include:

  • Human review workflows for high-stakes outputs
  • Confidence thresholds and fallback paths
  • Logging and feedback loops to improve over time
  • Explicit guardrails for your industry (medical, legal, financial)

Bad answers: "The model is very accurate" or "we'll fine-tune it."

What you're testing for: Do they think like engineers, or like demo builders?


3. "Who owns the system after you're done?"

AI projects can create hidden dependency. You pay for the build, then discover you need the consultant forever for every change.

Ask specifically:

  • Will we have access to all prompts, configs, and code?
  • Can our internal team modify it without your help?
  • What does handoff documentation look like?
  • Are we locked into any proprietary tools you're reselling?

A good consultant builds for your independence. A bad one builds for recurring dependency.

What you're testing for: Are they building for you, or for their retainer?


4. "What's the smallest version we could test in 2 weeks?"

Any serious AI consultant should be able to answer this instantly.

If the answer is "we need a 4-week discovery phase" before touching anything, that's a process-heavy firm that moves slowly and bills by the hour. If the answer is a specific, scoped prototype — "we could have an AI handling your inbound inquiry emails with human review in 10 days" — that's someone who's done this before.

What you're testing for: Speed of learning vs. speed of billing.


5. "What AI tools are you actually using, and why?"

The space moves fast. A consultant using the same stack they used 18 months ago is probably not keeping up.

Good consultants have opinions: "We use Claude for long-context reasoning tasks, GPT-4o for structured outputs, and Whisper for voice transcription because..." They can explain tradeoffs, not just name-drop models.

Red flag: "We use ChatGPT" with no further specifics.

What you're testing for: Do they have real depth, or surface-level familiarity?


The Underlying Pattern

Every question above tests the same thing from a different angle: does this person actually build AI systems, or do they sell the idea of AI systems?

The market is flooded with the latter. They have good slide decks, confident pitches, and impressive vocabulary. They will charge you $20,000 to learn on your project.

The builders are quieter, more specific, and slightly less impressive in the first meeting. They'll say "that might not work because..." instead of "absolutely, we can do that."

Hire the ones who push back.


At RooxAI, we start with a working prototype before asking for a significant commitment. If you're evaluating AI consultants, we're happy to be one of the options you vet — questions and all.