top of page
Obsidian Logic

When to Hire an AI Consultant (And When You Don't Need One)

Writer: Keith Mortier
Keith Mortier
Sep 14
6 min read

Updated: Sep 15

Hire an AI consultant when AI decisions are being made in your business and nobody on your team has the time or the authority to own them. Skip one when the AI you want already comes built into software you run, or when someone on your team has the time and judgment to own a single, well-defined project.


Most small and midsize businesses don't have a CTO. So AI arrives without an owner. An employee signs up for a tool, a vendor pitches an add-on, a manager builds an automation over a weekend. Nobody makes a formal decision, and a lot gets decided anyway.


Here's how to tell which situation you're in, and what to do about it.


Four tiles labeled tool sign-ups, vendor add-ons, weekend automations and data access, each with a line running into an empty owner box marked with a question mark, showing AI decisions being made in a business with no one owning them.

Who owns AI in a company with no CTO?


Often nobody. Without a CTO, AI ownership tends to fall to whoever is closest: the CEO, the most enthusiastic employee, the managed IT provider, or the vendor. Each of them can handle part of the job. None of them is set up to decide what gets built, what data AI tools can touch, and who answers for the results.


AI is already in your business either way. Microsoft and LinkedIn's 2024 Work Trend Index, a survey of 31,000 people in 31 countries, found that 78% of people who use AI at work bring their own AI tools, and the figure rises to 80% at small and medium-sized companies. Those are tools individual employees chose, holding company data, under whatever AI policy you have, if you have one.


Bar chart from Microsoft and LinkedIn's 2024 Work Trend Index showing that 78 percent of people who use AI at work bring their own AI tools, rising to 80 percent at small and medium-sized companies.

The usual defaults each break in a predictable place. The CEO can own it, but only by taking time from everything else. The enthusiast has no authority over budget or process. The IT provider owns the infrastructure, and your workflows usually sit outside its contract. The vendor's job is to sell you more of its product.


Bottom line: AI already has a place in your business, and the open question is whether anyone owns it.


When do you actually need an AI consultant?


You need outside help when the decision is bigger than anyone inside can evaluate. That usually means a meaningful budget is on the table, the project touches several systems or departments, a previous attempt failed and nobody knows why, or the data involved carries security or compliance risk.


Leadership uncertainty is common. In the same Microsoft and LinkedIn survey, 60% of leaders said they worry their organization's leadership lacks a plan and vision to implement AI. A consultant is useful when that uncertainty is holding up a real decision, and the business needs an answer it can act on.


The strongest signal is a large spend you can't evaluate. If a sizable vendor proposal is sitting on your desk and nobody in-house can say whether it fits your systems or your problem, an outside read before you sign costs less than finding out afterwards. For a tool that costs a few hundred dollars a month, just run a trial.


Bottom line: bring in help when a wrong decision would cost more than the help does.


When don't you need one?


You don't need a consultant when the AI you want is a feature inside software you already pay for, when one person has the time and judgment to own one clear project, or when you haven't found a problem worth solving yet. In those cases a consultant mostly adds cost and delay.


Built-in AI in your CRM or help desk comes with vendor documentation and onboarding, and that covers most of what you need. A single, contained project, such as summarizing support tickets, can be run by a capable operations lead with a few hours a week set aside.


If you can't name the problem yet, start there. The Tab Test puts a cost on manual work in an afternoon, and the five components of AI readiness give you a way to check whether you're ready for the project you have in mind.


Bottom line: if the vendor's help docs can answer the question, don't pay a consultant to answer it.


Consultant, fractional Chief AI Officer, or neither?


It depends on whether you have a question or a gap. A consultant answers a defined question within a fixed scope, such as whether AI will pay off in your operation and where. A fractional Chief AI Officer fills an ongoing gap: someone at the executive level who owns AI decisions month after month. If you have neither, wait.


A stop-at-the-first-yes list for whether a business needs an AI consultant. If the AI is a feature in software you already pay for, use the vendor's onboarding. If you can't yet name the problem, put a cost on the manual work first. If someone inside has the time and judgment to own one clear project, run it internally. A defined question with a budget and an end point points to an AI consultant, and AI decisions that keep coming with no owner point to a fractional Chief AI Officer.

The question tends to come first. An AI Operational Assessment is our version of a fixed-scope engagement: ten to fourteen business days, five readiness components scored across your workflows, and a written roadmap you keep whether or not you work with us.


The gap shows up once AI touches several parts of the business and decisions keep coming. That's when a part-time executive owner makes sense. Our fractional Chief AI Officer page compares a consultant, a fractional CAIO, and a full-time hire side by side, so we won't repeat that comparison here.


Bottom line: hire for the question you have now, and don't sign a retainer to answer a one-time question.


What should you actually ask before you hire one?


Ask these on the first call, before any proposal arrives. The answers tell you whose interests the advice serves and what you're left holding when the engagement ends. Any consultant worth hiring answers all five without hedging, and a vague answer to any one of them is reason enough to keep looking.


  1. Do you earn anything from the tools you recommend? Referral fees and reseller margins are common. Vendor-neutral advice has to be stated plainly, because you can't assume it.

  2. Do you build what you recommend, or hand it to someone else? The handoff between strategy and build is where projects stall. If they don't build, ask who does and how the handoff works.

  3. What exactly will I have at the end? Get a written deliverable with a defined scope. A promise of "insights" gives you nothing to hold them to.

  4. Who owns the work after you leave? You need documentation and a named person on your side who can run it. If the system stops working when they stop working on it, you've bought a dependency.

  5. How will we know it worked? Agree on a number before the work starts, the same test you'd apply to any AI project.


The pattern underneath all of it


Every good reason to hire an AI consultant comes back to ownership. Somebody has to decide what AI does in your business and whether it's working. Hire outside help when nobody on your team can do that yet, and plan from the first week for who owns it after the consultant leaves.


Businesses that get this wrong tend to miss in one of two directions. Some wait until an employee's tool choice becomes a data problem. Others hire a consultant for a question a vendor's help page could have answered. Both come from buying AI before anyone owns it.


Bottom line: the consultant is temporary and the owner is permanent, so decide who that owner will be before you sign anything.



Related: AI Operational Assessment. The fixed-scope way to find out whether AI will pay off in your operation, and where to start.


Not sure whether you need outside help? A Find the Leaks call is 20 to 30 minutes and free. We'll look at where your time is actually going and put a number on the biggest leak. You keep the finding either way.






FAQ

What does an AI consultant actually do?

An AI consultant answers a defined question within a fixed scope, such as where AI would pay off in your operation, which vendor fits your systems, or why a past project failed. The good ones leave you a written deliverable and a plan someone in the business can own.

Someone with authority over both process and budget, often an operations leader or the CEO with time deliberately set aside. If nobody in-house can take it on, a fractional Chief AI Officer can hold the role part-time until someone can.

They can handle the infrastructure side, such as access, security, and uptime. Decisions about which workflows to automate and whether the results are worth it usually sit outside their contract, so someone still has to own those.

A consultant fits a one-time question with a clear end point. A fractional Chief AI Officer fits an ongoing need, when AI decisions keep coming and someone has to own them at the executive level. Starting with the first is usually how you find out whether you need the second.

Below roughly $1 million in revenue, usually yes. Built-in tools and a clear internal owner cover most needs at that size. The case for outside help gets stronger as the business grows, because a wrong AI decision then wastes more money and more people's time.


 
 
bottom of page