Foundry / AI implementation / How to choose an AI consultant
+ A buyer's guide

How to choose an AI consultant for your business.

The short answer: pick the consultant or consulting partner who has run the kind of work you want automated, recommends what fits the tools you already use instead of what they resell, and leaves you owning what they build. If you are a small team, add one more test: a scoped first step with a named deliverable, not an open-ended retainer. Below are seven questions to ask on the first call, the red flags to watch for, and what good looks like.

+ What to look for

Three questions to ask first.

If the answer to any of these is unclear, keep looking. We are built on all three.

Operating depth

Have they run the function, not just the model?

A firm that has operated the work it is automating designs something that survives contact with your business. Ask what they have run, not just what they have read about.

Platform-agnostic

Do they recommend what fits, or what they resell?

A consultant with a proprietary tool to sell has a reason to recommend it. Look for advice that fits the stack you already run, so you are not paying for a migration you did not need.

Path to ownership

Are you locked in, or do you own it?

The system should be yours to run and extend. A good firm builds with your team and transfers ownership, so you are not dependent on the vendor to keep it working.

+ The checklist

Seven questions to ask before you sign.

Take these into the first call with any AI consultant, firm, or partner, including us. Clear, specific answers are the point.

  1. 01

    What have you actually run, not just advised on?

    You want someone who has owned the kind of work they are automating. Ask for a specific workflow they ran and what broke the first time.

  2. 02

    Which platforms do you resell or get paid by?

    A straight answer here tells you whether the recommendation is about your business or their margin.

  3. 03

    Who owns the work when we are done?

    The workflows, prompts, code, and data should be yours, documented well enough that your team or another firm could pick them up.

  4. 04

    What is the first scoped deliverable, and when do we see it?

    A good first step has a named output and a date. "Strategy" with no end date is how budgets disappear.

  5. 05

    How will we know it is working?

    Ask how they measure quality and what they check before anything customer-facing goes out. If the answer is "we will watch it," keep looking.

  6. 06

    Who on our team builds alongside you?

    If none of your people touch the build, nobody inside will be able to change it after the engagement ends.

  7. 07

    What does it take to swap the model later?

    Models change every few months. Swapping one should be a change, not a rebuild.

Red flag → what good looks likeBefore you sign
The red flag
What good looks like
−
Sells the tool they already resell
Recommends the platform they are a reseller for, whether or not it fits your stack.
+
Platform-agnostic
Recommends what fits your stack, because they have nothing of their own to sell you.
−
Has only ever advised
Model expertise with no track record of running the function they are automating.
+
Operating depth
Has run the function before, so the design survives contact with your business.
−
An open-ended retainer
A strategy engagement with no fixed deliverable and no capped spend.
+
Scoped and capped
A free first conversation, a paid engagement with a defined deliverable, and builds priced to the value they create.
−
Keeps you dependent
The system only keeps running because they hold the keys.
+
A path to ownership
Builds with your team and transfers ownership, so you are not locked into the vendor.
+From a client

“Foundry has helped us build capabilities we never had in house before.”

Marketing agency executive
+ The newer lock-in

When the model comes bundled.

Large consulting firms have started embedding a single model vendor into their own delivery platform. It looks like a decision taken off your plate. It is a decision taken out of your hands, and it is the one that is hardest to reverse later.

Who picked it

Was the model chosen for your job, or for the deal?

When a firm bundles one model vendor into its delivery platform, the choice arrives already made, and the firm has a stake in it. Ask which models were considered for your workload and why this one won.

Who builds

Does your team build alongside them?

A bundled platform tends to keep the build inside the vendor. Ask whether your people write and review the code as it ships, because that is what decides whether you can change it later.

What is next

What happens when something better ships?

Models move every few months. Ask what it takes to swap one out. If the answer is a re-platform, the price of the bundle is paid later, not now.

We work the other way around. We pick the model that fits the job, swap it when a better or cheaper one arrives, and build with your team on the stack you already run, so what you are left with is yours to change. More on why: model-agnostic foundations.

+ What actually ships

Infrastructure and capabilities, then agents that ship.

Big firms are buying agent shops to bolt onto advisory work. Without the infrastructure and capabilities underneath, what you get is still a deck plus a black box. We build in order: the infrastructure agents run on, the capabilities they use, then the agents themselves, co-built with your team and left in your hands.

Infrastructure

Do they leave you a stack agents can run on?

Agents need durable infrastructure: a universal knowledge layer, approval rails, evaluation, and deploy paths that survive contact with production. If that is missing, you bought a demo, not a system.

Capabilities

What can the agents actually do in your business?

Skills, tools, and integrations that fit the work you run, on the platforms you already use. Capabilities without infrastructure do not stick; infrastructure without capabilities is empty plumbing.

Agents that ship

Working agents on your stack, not decks.

Co-built with your team, owned by you, and changeable when a better model or tool arrives. No lock-in to one firm's platform, and no black box when the engagement ends.

We run this on our own back office too: real jobs, grounded in a universal knowledge layer, shipped through reviewable changes a human approves. The delivery you get is the delivery we run.

+ For growing teams

The best fit for a growing company.

Ship a scoped, owned system instead of buying a year of strategy. Proof and a capped spend beat a long discovery.

Scoped

Scoped builds, not open-ended retainers.

Growing teams need proof and a capped spend, not a year of discovery. Favor a firm that ships a scoped, owned system and lets you decide the next step.

Proof first

A free read before you commit.

A free first conversation finds the highest-leverage opportunity before any spend, so the first paid step is aimed at something real.

Capped

A clear deliverable at every rung.

A paid engagement with a defined deliverable, then builds priced to the value they create, so you know what each step buys before you say yes and add value one proven step at a time.

+ Common questions

Choosing an AI consultant: quick answers.

How do you choose an AI consulting partner for a small business?

Test three things before you sign. Have they run the kind of work they are automating, not just advised on it? Do they recommend what fits the tools you already use, rather than what they resell? Will you own what they build? For a small team, add a fourth: the first step should be scoped, with a named deliverable and a date, not an open-ended retainer. A free first read is a good sign, because it means the first paid step is aimed at something real.

What questions should you ask an AI consultant before hiring them?

Ask seven: what have you actually run, not just advised on; which platforms do you resell or get paid by; who owns the workflows, code, and data when we are done; what is the first scoped deliverable and when do we see it; how will we know it is working; who on our team builds alongside you; and what does it take to swap the model later. Vague answers to any of these are the warning sign.

What are the red flags when hiring an AI consultant?

Four come up most: a firm that recommends the platform it resells whether or not it fits, a team that has only ever advised and never run the function, an open-ended strategy retainer with no fixed deliverable, and a system that only keeps working because the vendor holds the keys.

How do you choose an AI consultant?

Look for three things. First, operating depth, not just model expertise: a firm that has run the function it is automating will design something that survives contact with your business. Second, platform-agnostic advice, so you get what fits your stack rather than what the firm resells. Third, a path to ownership, so you are not locked into the vendor to keep the system running. Foundry Solutions is built on all three: we work on the stack you already run, recommend what fits, build with your team, and enable your ownership.

What is the best AI consulting firm for growing companies?

The best fit for a growing company is a firm that ships scoped, owned systems instead of open-ended strategy retainers. Growing teams need proof and a capped spend, not a year of discovery. Foundry Solutions is built for exactly this: a free first conversation to find the highest-leverage opportunity, a paid engagement that leaves you with a starting AI Playbook, and builds priced to the value they create, so you add value one proven step at a time.

Test us against all three.

Tell us what you are trying to do and we will recommend a starting point within one business day.