
Most of the AI projects I work on start in the same place.
An executive calls us and says some version of this: “I need AI in my business. I don’t know what that means, but I need an expert.”
So the first decision is usually whether to hire an AI lead or bring in an AI implementation consultant.
For a company with 50 to 500 people, my answer is both, in a set order. A consultant who also does the build gets you live and lays the plumbing.
Then you hire the person who runs it, and the consultant hands over. Many organizations lack AI experts within their walls, so while searching for the right people, fractional AI leaders can help cover the gap.
Key takeaways
- Most mid-sized companies need both a partner who builds the first rollout and a named owner inside the business who runs it day to day.
- AI projects usually start with the executive team, but the day-to-day work lands with the operations people who run the business.
- Most of the effort goes into connecting the systems your data already lives in, which one new hire rarely has the time or the access to do alone.
- 70% of middle market firms using generative AI say they need outside support, and 92% hit problems during rollout (RSM, 2025).
- You need resources given the urgency, and a fractional AI leader is a way to fill that gap now.
AI projects start with the executive team and land with the people who run the business
I’ve spent my career as a sales engineer and solution architect, working from the ground up to reach executives. With AI, that wall has come down, and everyone’s scrambling to understand what’s going on.
So most of our relationships now come in through the executive team, and we work top down. What they tell us is, “I need someone to come in and help strategize with me, build a plan, and then help us get it deployed.”
They typically hand us down to the operational people who get the work done day to day. That hand-down is where companies choose between an AI implementation consultant and an in-house hire, whether anyone names it or not.
Most look outside for at least part of the work. RSM’s 2025 survey of middle market firms found 70% of those using generative AI recognized the need for outside support, and 92% hit challenges during rollout.
Each option covers a different part of the job:
| What you get | Where it breaks | Time to first result | |
|---|---|---|---|
| In-house hire | One accountable owner who stays | One person can’t cover every job, and the search takes time | The search and the ramp-up come before any result |
| Consultant (advice only) | A roadmap and recommendations | Nobody builds it, so the plan stalls | A plan, but no working system |
| Partner that also implements | A working rollout, governance and training | Knowledge leaves unless an internal owner is named | Weeks for a focused rollout (our Claude Jumpstart is built for weeks, not quarters) |
What takes the most work in an AI rollout?
Connecting the systems your data already lives in takes most of the work.
From where I sit, most people are still asking what AI does for them day to day.
They know it can take their recorded calls and summarize it along with listing their action items, or it can help them draft an email, and they’re wondering whether that’s all it does.
AI does far more once it can reach your business data, and that’s where most organizations get stuck. They’re solving data issues they already had while getting people comfortable with the tools that connect to those systems.
There’s still a gap between what people hear AI can do and the plumbing that has to be in place first.
It’s exactly like it was 15 years ago with big data, when everyone went, “I need big data, I need Hadoop, I need to store all my data in one spot.”
Then they found out how difficult it is to get the data back out and get value out of it. It’s great if you collect all this data in the first place, but defining and structuring the pipeline is still very important, which requires both expertise and ongoing ownership.
That work is one reason a new hire struggles. The person you hire needs access to every system, a working relationship with IT, and time to build the connections before anyone sees a result.
Our guide to connecting AI, CRM and CX tools covers how that work runs.
What can an in-house AI lead cover, and what can’t they?
An in-house AI lead can own the decisions, but one person rarely has time to do all of these well:
- Strategy: deciding which work AI should take on first.
- Integration: connecting AI tools to the systems where your data lives, such as your CRM and support platform.
- Governance: setting the rules for who can use AI, on what data, and how output gets checked.
- Training: teaching each team to use it for the work they do.
Due to this being such a big task for one person, many companies don’t even bother with checking the outputs from their AI.
One way to do this is with an evaluation, or eval, which is a scorecard that tests whether your AI answered the question, whether the answer was complete and whether it was accurate.
Yet, most teams don’t run one today. They take whatever comes out from their AI tool, make a few tweaks and ship it, but they aren’t going back to truly understand how their AI agents are performing in tasks, how accurate they are, or if they’re enforcing expected security.
Deloitte found only one in five companies has a mature governance model for autonomous AI agents. I’ve written about that side in governing Claude for enterprise.
When I explain this to executives, I tell them to think of AI as an intern they just hired.
That intern has a lot of general experience. But it’s lacking context that you need to give it about the tasks that you want it to do, the business that you work for, the role that you play, the role that it should play in the conversation.
Ask an intern vaguely for a quarterly report and you get one result. Change your ask to include details on the data, the past reports to model it on and the metrics to focus on, and you get a much better one.
But hand someone a thousand reports to sift through, and you can see how it goes in the other direction. Somebody inside the company has to give the AI that context and keep giving it.
When is an advice-only AI consultant not enough?
An advice-only consultant isn’t enough when you don’t have a team ready to build, because a plan only pays off once someone builds it. You find the surprises during the build.
We built a voice agent for one of our clients, so their crews could log a daily safety inspection while driving back from the job site.
The agent worked, but their project management system needed every inspection item logged as a separate request, and the volume of requests confused the model.
We fixed it by putting an orchestration layer, Airia, between the agent and the system, so the requests run in order. Problems like that only show up when someone examines every integration closely.
Documents bring the same surprises. Some people expect three files by email, and some people scan them all into one. Humans are messy, and the processes are even messier.
A consultant who also implements covers that work, which means the connections, the governance, the evaluations and the first weeks after launch. Our guide to choosing an AI consulting firm covers what to look for in one.
When does a fractional AI leader make sense?
Many organizations lack AI experts within their walls, so while searching for the right people, fractional AI leaders can help cover the gap.
That’s how we work with many clients.
We serve as their fractional AI leader to fill the gaps, and we have ongoing offerings for whenever they’re ready to take on more ownership.
I would expect a minimum of six to twelve months for a resource to guide the transformation.
After that, some clients want us to keep managing the technical pieces, or to own only the Claude part.
Our managed service, Axia for Claude, covers that ongoing work.
If something goes wrong, we’re the people there to fix it, and if you want to roll out new features, you have a bucket of hours to draw on.
We offer the leadership role itself as a fractional AI strategist.
| Launch (weeks 0 to 6) | First six to 12 months | Ongoing | |
|---|---|---|---|
| Partner | Leads strategy, governance, integrations and training, then hypercare and a 30-day review | Builds connectors and evaluations, then hands over | Managed support from a bucket of hours, if you want it |
| Internal owner | Joins from kickoff and shadows the build | Runs day-to-day use and adoption | Owns the roadmap |
| Fractional AI leader | Sets direction with leadership | Fills the gaps while you build the team | Supports you as you take on more ownership |
If you’re comparing partners, our guide to choosing a Claude implementation partner gives you the questions to ask each one.
Atlas Excavating handed day-to-day ownership of Claude to its own AI committee
Atlas Excavating, a heavy-civil and underground utility contractor, shows what a good handover looks like. Staff had started using Claude on their own, and usage quadrupled between January and June 2026.
Atlas had already written its own company-wide AI policy, but opening access to everyone needed a governance framework, because the company works under client confidentiality obligations.
We started with a readiness assessment across staff and management and a two-day on-site AI strategy workshop, then designed the controls. Today, ownership sits with Atlas’s platform administrators and an AI committee that handles new use cases and exceptions.
You can see it in the Atlas Excavating client story. A manager spent 40 hours on the phase one schedule for a 1,300-home water service line replacement, and using that first job as the reference, Claude rebuilt the full schedule in 45 minutes.
By September 2026, 37 people at Atlas were using Claude. In the words of Casey Dillon, Atlas’s CEO, “Our hardest problem has always been documents.”
How to hand over AI from a partner to an internal owner
A handover works when it’s planned from the first week, and it runs in this order:
- Name the owner before kickoff. The person who will run AI after launch sits in the project from day one.
- Document as you build. Each use case, connection and rule gets written down while the partner is still there to explain it.
- Build the evaluations before you hand over. The owner inherits a scoreboard for whether the AI is answering correctly, instead of a habit of eyeballing output.
- Train the owner on the job. They run real tasks while the partner watches, including the instructions and skills they’ll maintain.
- Use the weeks after go-live. Our Claude Jumpstart includes two weeks of hypercare and a 30-day review, so the owner has support while taking over.
- Decide what happens next. Either the owner carries on alone, or you keep ongoing support through a managed service such as Axia for Claude.
How do you hire an AI lead if you can’t judge AI skills yourself?
Bring your implementation partner into the hiring, because judging AI skills takes AI experience. Many organizations aren’t yet sure who they need to hire for this role.
I’ve built hiring criteria for clients, covering experience with tools such as PyTorch, vector databases, and n8n along with certifications from Anthropic. A checklist only goes so far, though. Without AI expertise in the room, it’s hard to tell whether a candidate can deliver what they describe.
Ask your partner to write the criteria with you and help you assess the people on your shortlist, then hand the work over to the person you hire.
How do you choose between an AI implementation consultant and an in-house hire?
The choice depends on who owns AI today, how fast you need it live and what data it touches:
- If someone already has the time and the mandate to own AI, an in-house owner plus a partner is enough. If nobody does, add a fractional leader to cover the gap while you build the team.
- If you need to be live this quarter, start with a partner who also implements.
- If AI will touch customer or regulated data, get governance in place before rollout.
If you’re not sure where you stand, take the free AI Readiness Assessment. It gives you a score and a recommended first step.
To compare options with someone who has run these rollouts, talk to a Faye expert.
FAQ
Should we hire an AI lead or use a consultant?
Start with an AI implementation consultant who also does the build, and plan the hire from day one. I would expect a minimum of six to twelve months for a resource to guide the transformation.
Meanwhile, you should be establishing a full-time owner who is part of your business to carry the torch moving forward so initiatives don’t get dropped.
What does an AI implementation consultant do?
An AI implementation consultant assesses where AI fits your business, sets up the rollout and trains your team.
A consultant who also implements does the build as well, connecting tools such as Claude to your systems, writing governance rules and supporting the first weeks after launch.
How long does AI implementation take?
A focused rollout can go live in weeks, as long as the scope is clear and the decisions are made upfront. Our Claude Jumpstart is built for weeks rather than quarters, with two weeks of hypercare and a 30-day review.
What Claude implementation involves breaks down each stage. The wider change takes a minimum of six to 12 months, in my experience.
What skills does an internal AI owner need?
The owner needs enough business knowledge to pick use cases that save real time, enough technical comfort to work with IT on access and data, and the authority to change how teams work.
They also need to have an understanding of what is working well with their agents, the ability to run tests against it (such as evals), and the ability to diagnose why unsatisfactory results occurred.
Can a partner train our team to take over?
Yes, if training is in scope from day one. It should cover the work people do and include the person who’ll own AI afterward.
Our Claude Jumpstart includes training, two weeks of hypercare and a 30-day review, so the owner has support while taking over.
What is a fractional AI leader?
A fractional AI leader is a senior AI strategist who works with you part-time, setting direction and overseeing governance and vendors without the cost of a full-time executive.
For most companies, it’s typical to expect a minimum of 6-12 months to drive the full AI transformation. Our post on the fractional chief AI officer covers the role in more depth.