← Insights
June 8, 20267 min read

Choosing a Dallas AI consultant: 7 questions middle-market operators should ask

A buyer's guide for COOs, CFOs, and VPs of Ops at DFW middle-market businesses hiring an AI consultant. The seven questions that separate operators from slide-deck consultants, plus the red flags to walk away from.

The "AI consultant" market in Dallas-Fort Worth doubled in the last eighteen months. Most of the new entrants have never run an operation, never owned a P&L, and have never shipped a workflow that survived contact with a real team. Some are excellent. Most aren't. If you're a COO, VP of Ops, or CFO at a middle-market business evaluating one, here are the seven questions that surface the difference before you spend a dollar.

1. "Have you actually run operations yourself?"

Implementation is 20% model selection and 80% change management. A consultant who has never had to convince a 55-year-old service manager or a tenured AP supervisor to adopt a new tool will design something that gets ignored. Ask for a specific example of a workflow they personally rolled out inside a real company, not a client's, theirs.

2. "Can I see a real before-and-after?"

Not a case-study deck. The actual workflow: screenshots, the prompt, the integration, the hours-saved number, and which team inside the client uses it today. If they hide behind NDAs for everything, you're paying for their learning curve.

3. "Who owns the workflow after the pilot ends?"

Three answers are acceptable: your internal IT or ops team, a documented handoff to a different vendor, or a clearly-priced ongoing retainer. The unacceptable answer is "we'll figure it out", that's how a middle-market business ends up locked into a five-figure monthly maintenance fee for a workflow your own team could run.

4. "What does failure look like, and how do we roll back?"

Every honest operator has a rollback plan. If the pilot makes things worse, slower, more errors, team revolt, what happens on day 31? A consultant who can't answer this hasn't shipped enough to have failed yet.

5. "What's the total cost in year one, including tools?"

Consulting fees are the small number. Software licenses, API credits, integration platforms, security review, and the half-FTE of internal time during build are the big number. At middle-market scale, year-one total cost of a real pilot typically lands well into six figures across all line items. A good consultant gives you both numbers up front. A bad one quotes consulting and lets the rest surprise your controller.

6. "What won't you do?"

Operators have opinions. They'll tell you which workflows aren't worth automating, which vendors they refuse to work with, and which industries they don't take on. If everything is "yes, we can help with that," you're hiring a generalist who will learn on your dime.

7. "Can I talk to a client whose pilot didn't work?"

This is the question almost nobody asks, and the one that separates real operators from the rest. Anyone who has shipped enough has shipped at least one thing that flopped. How they talk about it tells you everything.

Red flags to walk away from

  • Hourly billing with no scope cap.
  • "Proprietary AI platform" you've never heard of and can't price.
  • Seven-figure annual contracts before a pilot has run.
  • No named individual accountable, just a "team."
  • Refusal to put the deliverables list in writing.

The right consultant for a Dallas middle-market business is almost always the one who answers these seven questions plainly, in writing, in the first call. If that's the bar you're looking for, a Workflow Audit is the lowest-risk way to test it.

Written by
Reilee Williams
Founder, Applied Ops AI · Dallas, TX
Book a Workflow Audit →