Enterprise DNA

Omni by Enterprise DNA

Enterprise DNA Resources

Insights on data, AI & business. Practical AI operating-system thinking for owners, operators, and teams doing real work.

220k+

Data professionals

Omni

AI agents and apps

Audit

Map the manual work

Stop Hiring for AI Roles Until You Do This First
Blog Business

Stop Hiring for AI Roles Until You Do This First

Every business owner I know is looking for an AI specialist right now. Most of them are making the same expensive mistake before they even post the job.

Sam McKay

There is a conversation happening in almost every boardroom, every small business back office, and every team Zoom call right now. It goes something like this.

“We need to hire someone for AI.”

I understand the instinct. The news cycle has been relentless. Every headline is either about a company deploying AI to replace workers or a company getting left behind because they did not. Salesforce froze more than a thousand engineering positions while simultaneously announcing it was redirecting that budget to AI. Meta cut eight thousand people while posting record revenue and announcing a hundred-billion-dollar AI infrastructure bet. The signal feels clear: the companies winning are the ones going all in.

So you want to hire an AI person. Get ahead of it. Bring in someone who knows what they are doing and let them figure it out.

Here is what I have learned after training 220,000 data and AI professionals and deploying AI agents inside real businesses: that approach fails more often than it succeeds. Not because the people are wrong. Because the sequence is wrong.

The Expensive Mistake

When a business hires for AI before it understands its own AI problem, it creates a very particular kind of mess.

The new hire arrives. They are smart, capable, genuinely excited. They look around and they see a hundred possible places to start. The marketing team wants a content tool. The ops manager wants something for scheduling. Sales wants a lead qualifier. Finance wants automated reporting. Every department has a list.

So the new hire does what any reasonable person would do in that situation. They start working through the list.

Three months later, you have six half-built AI projects, a team that is confused about priorities, and a hire who is drowning because they are essentially doing the strategy work that should have happened before they showed up.

I see this pattern constantly. And I see the aftermath, which is usually a business owner asking me why AI “hasn’t really worked” for them yet, despite the investment.

The Three Questions You Need to Answer First

Before you post any job listing, before you talk to any vendor, before you book any AI demo, there are three questions your business needs to answer clearly. If you cannot answer all three, you are not ready to hire. You are ready to think.

One: What is your single most expensive repeatable problem?

Not your most annoying problem. Not the one that frustrates people the most. The one that costs you the most money when you add up time, error rate, opportunity cost, and the downstream effects of getting it wrong.

In a medical practice, it might be appointment no-shows. In a consulting firm, it might be the time that goes into building proposals from scratch every time. In a trades business, it might be the calls that come in after hours when no one is available to answer.

You should be able to name this problem in one sentence. If you cannot, you do not yet have enough clarity to direct someone else to solve it.

Two: Do you have the data to train or measure an AI solution?

This is where a lot of businesses get surprised. AI agents do not run on enthusiasm. They run on data. Call logs, document templates, CRM records, historical tickets, email threads. The cleaner and more complete your data, the faster and better any AI deployment will be.

If your answer to this question is “we have some stuff in spreadsheets and some stuff in our CRM and some stuff in emails,” you have a data readiness problem that needs to be solved first. Hiring an AI specialist into a data readiness problem is like hiring a chef before your kitchen has appliances. They can still work, but you are making their job much harder than it needs to be.

Three: Who in your current team owns the outcome?

AI deployments fail when they are nobody’s job. Not in the sense that nobody is implementing them, but in the sense that no one person in the business is accountable for whether they actually deliver results.

This is not about technical ownership. It is about business ownership. Someone needs to be the person who wakes up every morning thinking about whether the AI agent is doing what it was supposed to do, whether it is being used correctly, and whether it is actually moving the metric it was built to move.

In my experience, this person almost always already exists in your business. It is usually someone in operations, or a team lead who cares obsessively about process quality. They do not need to be technical. They need to care about the outcome and be empowered to make decisions about it.

What the Answers Tell You

When I work through these three questions with a business owner, one of three things usually happens.

The first is that they realize they do not actually have a clear answer to question one. They think they do, but when they try to articulate it, they end up describing a category of problems rather than a specific one. This is not a failure. It is a finding. It means the next step is not hiring, it is mapping your operations with enough clarity to identify where AI will create the most value. That is advisory work, and it is far cheaper than a mis-hire.

The second is that they have a clear problem, but their data situation is not ready. They know exactly what they want to automate, but the information that AI would need to do its job is scattered, incomplete, or inconsistently formatted. This is also useful to know early. The work to do here is data standardization before anything else. A good fractional AI advisor can help you do this without committing to a full-time hire.

The third is that they have a clear problem, reasonable data, and a natural owner in the business. This is when hiring makes sense. And interestingly, when businesses get to this point before they hire, they hire better. They know what they are looking for. The job description reflects a real problem, not a vague category. And the new hire, whether that is an employee or a partner, has something concrete to work on from day one.

The Sequence That Actually Works

There is a sequence that I have watched work across dozens of businesses, and it goes like this.

Understand first. Map your highest-value processes. Identify where time, money, and risk accumulate. Do not skip this step because it feels slow. It is the only thing that makes everything else fast.

Upskill before you hire. In almost every business I have worked with, the capability to implement AI already exists somewhere in the team. A finance manager who is curious about automation. An ops lead who has been quietly building things in Notion. An account manager who has been using AI tools on the side for six months. These people exist. They just need permission, a framework, and sometimes some structured training to get to where you need them.

Deploy before you scale. Start with one agent, one workflow, one use case. Get it working, measure it, understand what it actually does to the business. Then expand. The businesses that try to deploy AI everywhere at once usually end up with AI nowhere, because nothing ever gets to a finished, reliable state.

Hire into momentum, not into a blank page. If you have done the first three steps, a hire is now a multiplier. They are joining a business that knows what it wants, has some working deployments, and has a team that understands enough to collaborate. That is a completely different environment than the blank-page situation, and it produces completely different outcomes.

What This Means for You Right Now

The AI hiring frenzy is real. The pressure to move is real. I am not suggesting you slow down. I am suggesting you spend two or three weeks doing the thinking that will make every action after it ten times more effective.

If you are a business owner trying to figure out where to start, the most valuable thing you can do right now is answer those three questions. Write them down. Be honest. If the answers are clear, you are ready to move. If they are not, clarity is the work.

If you want help thinking it through, that is exactly what Omni Advisory is for. We sit down with business leaders and map the AI opportunity in their specific context, before anything gets built or bought.

And if your team needs to build the underlying skills to work with AI effectively, EDNA Learn has structured programmes built for exactly that, from data fundamentals to deploying real agents.

The pressure to act on AI is justified. The reflex to hire first and think second is not. Get the sequence right, and the results follow.