A Chicago company offered me $8,000/month for ongoing AI consulting last year.

I said no.

Not because the money wasn't good. Because I knew I couldn't deliver the results they deserved from 300 miles away.

Here's why proximity matters more than most people realize—and why it might matter for your business too.

The Zoom Call Problem

On video calls, clients tell me what they think I need to know.

In person, I see what's actually happening.

Last spring, I shadowed a receptionist at a Creve Coeur medical practice. On our discovery call, the office manager had described their appointment process as "pretty smooth, just high volume."

What I saw in person: sticky notes everywhere. A physical binder the receptionist consulted for insurance questions. Three different browser tabs open to check availability across two doctors and one nurse practitioner. A paper calendar on the wall that contradicted the digital one.

The "high volume" wasn't the problem. The fragmented system was.

No video call would have revealed that. The staff had worked around these issues for so long they'd become invisible.

When I built their AI system, I accounted for every workaround. The result worked on day one because it matched how people actually worked, not how the documentation said they should work.

Speed Compounds

Remote agencies work in sprints. Discovery call this week. Requirements doc next week. First draft the week after. Feedback. Revision. More feedback.

A simple implementation takes 6-8 weeks if you're lucky.

When I work locally, I can sit with your team and iterate in real time. Something not working? We adjust it while I'm still there. Questions from staff? We address them immediately before confusion becomes frustration.

What remote agencies do in two months, I typically do in two weeks.

That speed advantage compounds. The sooner your automation is working, the sooner you're seeing ROI, and the sooner we can tackle the next bottleneck.

Accountability You Can't Fake

Remote agencies have dozens of clients. When something breaks, you submit a ticket and wait your turn.

I run into my clients at the St. Louis Bread Company. At Cardinals games. At networking events in Clayton. My kids go to school with their kids.

That changes how I work.

When the dental office chatbot I built gave wrong parking directions (I'd entered an old address during setup), I was there the next morning to fix it. Not because of an SLA. Because my reputation depends on your results, and in a city this size, word travels.

A Chicago agency might deliver competent work. But they won't lose sleep if your system goes down during your busiest week. I will.

Context That Compounds

After working with a dozen St. Louis restaurants, I know things that would take months to learn remotely:

  • Which POS systems integrate well and which are nightmares
  • Seasonal patterns specific to the local market (Mardi Gras weekend isn't just New Orleans)
  • How St. Louis customers expect to communicate (more phone calls than the coasts, more text than email)
  • Local vendors who can support the systems I implement

My tenth St. Louis client benefits from everything I learned with the first nine. That accumulated context makes implementation faster and results better.

A remote consultant starts from zero with every engagement.

The Network Effect

When you work with me, you get access to connections I've built across St. Louis:

  • Introductions to complementary service providers (I know the best local web developers, accountants who understand tech businesses, marketing agencies that won't waste your money)
  • References from businesses similar to yours (you can actually call them)
  • Insights from what's working for similar local companies (I see patterns across my client base)

A NYC agency might have more prestige. They can't introduce you to the Kirkwood business owner who solved the exact problem you're facing.

When Remote Actually Makes Sense

I'll be honest: local isn't always better.

Consider a remote consultant when:

  • You need extremely specialized expertise that doesn't exist locally (rare for small business AI)
  • Your operations are primarily digital and location-independent
  • You've done AI projects before and just need execution
  • Budget constraints make local consulting genuinely unaffordable

But for first-time AI implementations? For businesses with physical locations and local customers? For situations where discovery requires actually seeing how work gets done?

Local wins.

What to Look For

If you're evaluating AI consultants—local or otherwise—here's what matters:

Track record with similar businesses. Not just "AI experience." Experience with businesses your size, in your industry, with your types of challenges.

References you can actually call. Ask for three clients similar to you. Call them. Ask what went wrong, not just what went right.

A defined process. Good consultants have a methodology. They don't make it up as they go.

Transparent pricing. You should understand exactly what you're paying for before signing anything.

Cultural fit. You'll be working closely with this person. Make sure you actually want to.

The Real Question

I turned down that Chicago contract because I knew something they didn't: the implementation would have struggled, they would have been frustrated, and my reputation would have suffered.

The question isn't whether to hire an AI consultant. It's whether the consultant you're considering can actually see your business clearly enough to help.

Sometimes that requires being there in person. For most small businesses, I think it does.

Want to test that theory? Let's grab coffee and walk through your biggest operational bottleneck. Thirty minutes, no pitch, no pressure.

If I can help, I'll tell you how. If I can't, I'll tell you that too—and probably know someone who can.