15 Questions to Ask Before Hiring an AI & Operations Consultant

Ask four types of questions: about operator experience (have they run operations inside a company, not just advised?), about methodology (do they start with your real processes or with strategy decks?), about AI specifics (how do they handle errors and human review?), and about outcomes (what metrics define success?). The best consultants welcome these questions. If someone is evasive, that's your answer.

You need help with operations or AI. Your team is stuck. Manual work is piling up. You've tried tools and they didn't stick. Now you're considering hiring a consultant. The problem: you don't know how to tell the difference between someone who will deliver and someone who will give you a deck and leave.

Most 10-100 person B2B companies I talk to have the same worry. They've been burned by consultants who promised transformation and delivered PowerPoints. They want someone who has run operations, not just advised on them. They want practical AI, not hype.

Having built operations and AI systems from scratch at EverFruit, and now advising companies on the same, I know what separates consultants who get results from those who don't. The right questions upfront save you time, money, and frustration. This guide gives you 15 questions to ask before you hire an AI or operations consultant. Use them in your first call or RFP. By the end, you'll know how to spot operator experience, avoid hype, and choose someone who will implement.

QUICK ANSWER: Ask four types of questions: about operator experience (have they run operations inside a company, not just advised?), about methodology (do they start with your real processes or with strategy decks?), about AI specifics (how do they handle errors and human review?), and about outcomes (what metrics define success?). The best consultants welcome these questions. If someone is evasive, that's your answer.

Why Do These Questions Make or Break a Consulting Hire?

Not all consultants are equal. Some have deep operator experience: they've run teams, built processes, and implemented AI in real companies. Others have strategy backgrounds: they've advised many companies but never owned the outcome day to day. For operations and AI work, operator experience matters. Implementation fails when the consultant doesn't know what it takes to get a team to change how they work.

These 15 questions are grouped into four areas: experience and background, approach and methodology, AI and operations specifics, and outcomes and engagement. Ask them in your first conversation. The answers will tell you whether you're talking to someone who can deliver or someone who will hand you a report and walk away.

Experience and Background (Questions 1-4)

Question 1: Have you run operations or AI implementation inside a company, not just as a consultant?

Why it matters: Someone who has been responsible for operations or AI inside a company knows what it takes to get adoption, handle resistance, and fix processes when they break. Strategy-only consultants often miss the messy reality of implementation.

What to listen for: Specific company names, role titles, and time in the role. "I was Head of Ops at X for 2 years" is stronger than "I've advised many companies on operations."

Question 2: What size companies have you worked with? Have you worked with teams of 10-50 or 50-100?

Why it matters: Operations and AI in a 15-person company look different from a 500-person company. You want someone who has scaled (or scaled down) in a similar context. They should understand your constraints: limited budget, no dedicated IT, and teams wearing multiple hats.

What to listen for: References to company size, team size, or "we had no dedicated ops person" type stories. Red flag: only enterprise or only startup experience when you're in the middle.

Question 3: Can you walk me through one project where you implemented a process or AI use case end to end?

Why it matters: You want a concrete story: what was broken, what they did, what changed, and how they measured it. Vague "we improved operations" answers suggest they didn't own the implementation.

What to listen for: Process name, before/after metrics (time saved, error rate, adoption), and their specific role. "I mapped the process, built the automation, and trained the team" is what you want.

Question 4: What went wrong on a past project, and how did you fix it?

Why it matters: Everyone hits setbacks. You want someone who is honest about failure and can describe how they responded. Consultants who claim everything always works are either inexperienced or not being straight with you.

What to listen for: A specific example (tool didn't work, team didn't adopt, scope creep) and what they did next. Willingness to name the failure is a trust signal.

Approach and Methodology (Questions 5-8)

Question 5: Do you start with strategy and decks, or with mapping our current processes?

Why it matters: Operations and AI work should start with reality: how work gets done today. Consultants who lead with strategy and slides often skip the step of understanding your actual processes. That leads to generic recommendations that don't stick.

What to listen for: "We start by mapping your processes" or "We do an audit first." Red flag: "We'll deliver a strategy and roadmap" with no mention of process discovery.

Question 6: How do you decide what to automate or add AI to, versus what to leave as-is?

Why it matters: You want a clear framework, not "we'll add AI everywhere." Good consultants prioritize by impact, effort, and risk. They should be able to say when not to use AI or automation.

What to listen for: References to ROI, time saved, bottleneck analysis, or "we only recommend AI where it clearly beats automation or manual work." Red flag: AI for everything.

Question 7: Will you hand off implementation to us, or will you stay until it's live and adopted?

Why it matters: Many engagements end at "here's the plan." Implementation is where most value is created. You need to know if they will build and train, or leave that to you.

What to listen for: Clear scope: "We'll run the pilot and train your team" or "We'll hand off after design." Either can work, but it must be explicit. Red flag: vague "we'll support you" with no defined handoff.

Question 8: How do you work with our team? Do you need a dedicated project lead on our side?

Why it matters: You need to know who on your side needs to be involved and how much time they'll spend. Small teams can't spare a full-time project manager. Good consultants are clear about dependencies.

What to listen for: Specifics: "We need 2-4 hours per week from someone who knows the process" or "We need access to the team doing the work for workshops." Red flag: "We're flexible" with no concrete ask.

AI and Operations Specifics (Questions 9-12)

Question 9: How do you handle AI quality, errors, and human review?

Why it matters: AI makes mistakes. You need someone who builds in guardrails, human-in-the-loop checks, and error handling. Consultants who don't mention this are either inexperienced or overselling AI.

What to listen for: Guardrails, human review, quality checks, pilot-and-measure, clear boundaries for where AI is and isn't used. Red flag: "AI is reliable" with no discussion of errors or review.

Question 10: Do you recommend specific tools, or do you help us choose based on our stack and budget?

Why it matters: You want recommendations tailored to your context, not a standard vendor list. They should ask about your current tools, budget, and constraints before naming solutions.

What to listen for: "We assess your stack first" or "We recommend based on your use case and budget." Red flag: Pushing one tool or partner without asking about your situation.

Question 11: How do you measure success? What metrics do you track?

Why it matters: You need defined success criteria before you start. Time saved, error rate, adoption rate, or throughput are examples. If they can't name metrics, they may not be focused on outcomes.

What to listen for: Concrete metrics (hours saved per week, error rate, % of team using the new process). Red flag: Only "efficiency" or "transformation" with no numbers.

Question 12: What do you do when our team is skeptical or resistant to change?

Why it matters: Adoption is the hardest part. You want someone who has dealt with resistance: training, clear ownership, quick wins, and addressing trust and job-security concerns.

What to listen for: Training, communication, quick wins, involving the team early, addressing concerns about AI or automation. Red flag: "We'll present the plan and they'll adopt it."

Outcomes and Engagement (Questions 13-15)

Question 13: What does a typical engagement look like? Timeline, deliverables, and cost range?

Why it matters: You need to compare options and plan budget. They don't have to give a fixed price on the first call, but they should be able to describe a typical scope and range.

What to listen for: Phases (e.g. audit, design, pilot, scale), duration (e.g. 4-8 weeks for first phase), and ballpark cost. Red flag: "It depends" with no structure at all.

Question 14: Can you provide a reference from a company similar to ours?

Why it matters: References from companies of similar size and industry are more relevant than Fortune 500 case studies. You want to hear about implementation and results from someone like you.

What to listen for: Willingness to share 1-2 references after an NDA or with permission. Red flag: No references or only very large companies.

Question 15: What's the one thing you'd want us to have in place before we start?

Why it matters: This reveals how they think about readiness. Good consultants are clear about what they need: sponsor commitment, access to the team, data, or a clear problem statement. It also shows whether they set you up for success or blame you later.

What to listen for: Something specific (e.g. "someone who owns the process," "we need 2-4 hours per week from your side," "clear success criteria"). Red flag: "Nothing, we'll figure it out" (often means scope creep or misalignment).

How to Use These Questions

You don't need to ask all 15 in one call. Pick the ones that matter most to you. For example:

• If operator experience matters most: Focus on questions 1, 2, 3, and 4.

• If you care about implementation: Focus on 5, 7, 8, and 12.

• If AI is the priority: Focus on 6, 9, 10, and 11.

• If you're comparing proposals: Use 13, 14, and 15 to compare structure, references, and readiness.

Write down the answers. Compare consultants on the same criteria. The goal is not to catch anyone out, but to find someone whose experience, approach, and engagement model fit your company and your problem.

Conclusion

Hiring the right AI or operations consultant comes down to three things: they have done the work themselves, they start from your reality (processes and constraints), and they stay until something is implemented and adopted. The 15 questions in this guide help you check for all three.

Use them in your first conversation or in your RFP. The best consultants will answer clearly and welcome the scrutiny. If someone is evasive or defensive, that's useful information too.

Frequently Asked Questions