The AI Team Decision: When to Build Internally, When to Stay Fractional, and When to Do Both

Every founder or CEO I speak to about AI capability eventually asks some version of the same question: should we hire our own AI team, or keep working with external people?

It sounds like a binary choice. It isn't. The companies that get this right treat AI resourcing as a progression, one that evolves with their maturity and what they can actually support. The companies that get it wrong tend to make one of two mistakes: they hire too early and burn through expensive talent before they're ready to use it, or they outsource indefinitely and never develop the internal muscle they'll eventually need.

This piece is about how to think through that progression honestly. I'll share what works, what fails, and how to figure out where you stand.

The technology industry loves a clean dichotomy. Build or buy. In-house or agency. But the AI team decision doesn't sit neatly in either camp, because your needs change as your organisation matures.

What I've seen across multiple engagements is a natural progression that looks roughly like this:

Stage 1: Fractional and external. You don't have a clear AI workload yet. You're exploring what's possible, running initial experiments, maybe integrating off-the-shelf AI tools into existing products. At this stage, you need strategic guidance and focused execution bursts, not a permanent team sitting idle between projects. A fractional CTO or AI advisor makes sense here, because they bring pattern recognition from multiple organisations and can prevent the most expensive mistakes before you make them.

Stage 2: Hybrid. You've validated that AI is central to your product or operations. You have recurring AI workload and reasonably clean data. Now you need a small internal core — perhaps a data engineer and an ML engineer — working alongside senior fractional leadership that provides architectural direction and quality assurance. The fractional leader's job shifts over time from delivery toward mentoring and capability transfer.

Stage 3: Internal with selective external support. Your internal team owns the AI roadmap, the infrastructure, and the day-to-day delivery. You bring in external specialists for specific challenges — a novel architecture, a domain you haven't tackled before, an independent review of your approach. The fractional relationship either ends or becomes genuinely advisory: a few hours a month of strategic counsel rather than hands-on delivery.

This progression isn't theoretical. MIT's Center for Information Systems Research surveyed 721 companies and found that only 7% have reached what they call "AI Future-Ready" status, with fully embedded internal teams delivering measurable value. The vast majority (62%) are still in the first two stages, where some combination of external expertise and internal capability-building is exactly the right approach.

The better question is: which stage are you actually in, and are you resourcing accordingly?

Not every company should rush to hire an AI team. In fact, premature hiring is one of the most expensive mistakes I see. But there are clear signals that indicate you're ready to start bringing capability in-house.

1. You have recurring, predictable AI workload. If your AI needs come in sporadic bursts — a model for this product, an experiment for that initiative — external support is more efficient. When you find yourself needing sustained, daily AI work across multiple product areas, that's when internal hires start making financial sense.

2. Your data infrastructure can actually support an AI team. This one catches people out repeatedly. Data scientists spend roughly 80% of their time wrangling data rather than building models. If your data pipelines are fragile, your data quality is poor, or your data lives in disconnected silos, hiring an ML engineer is like buying a racing car before you've built the road. Fix the infrastructure first. That's work a data engineer can do, incidentally, and it's a much better first AI hire than a data scientist.

3. You have a leader who can set direction. A team of junior or mid-level AI engineers without senior AI leadership will drift. They'll build technically impressive things that don't connect to business value. They'll make architectural decisions that create technical debt you won't discover for months. If you can't yet afford or justify a full-time Head of AI, a fractional AI leader working alongside your first internal hires is significantly more effective than leaving them unsupervised. I'll come back to this.

4. You have executive sponsorship that goes beyond enthusiasm. "We should do something with AI" is not sponsorship. Sponsorship means someone senior owns the AI roadmap, can unblock cross-functional dependencies, and will fight for the budget and organisational patience that AI capability requires. Without this, even excellent AI teams get marginalised into a Centre of Excellence that nobody listens to.

These are harder to accept, because they often coexist with genuine ambition and excitement about AI.

1. You're hiring to "figure it out." If your brief to an AI hire is essentially "come and work out what we should be doing with AI," you are not ready to hire. You're asking someone to simultaneously define the strategy, build the infrastructure, deliver projects, and demonstrate ROI, with no institutional support. The average tenure of a Chief Data Officer is 2 to 2.5 years, and a significant reason is exactly this: organisations hire senior data and AI leaders without the readiness to support them. What you actually need at this stage is a short advisory engagement to define the strategy, followed by targeted hiring against a clear plan.

2. Your leadership team treats AI as IT's problem. Research from A.Team found that 84% of companies plan to increase AI investment, but the most common mistake is delegating the entire initiative to the technology function. AI capability that lives exclusively in IT gets disconnected from commercial reality. The models get built, but they don't get deployed, because nobody in the business owns the problem they're supposed to solve. If your board talks about AI but your product and commercial leaders aren't involved in defining what success looks like, you're not ready for internal hires.

3. You don't yet have a problem worth solving with AI. This sounds obvious, but it's remarkably common. RAND Corporation's research — the most methodologically rigorous study on AI project failure — found that the single most common root cause of failure is misunderstanding what problem needs solving. Companies hire AI teams to go looking for problems, rather than hiring AI teams to solve problems they've already identified and validated. If you can't articulate a specific, measurable business problem that AI could address, you need discovery work, not a permanent team.

The numbers on premature AI hiring are worse than most leaders expect.

Start with the direct costs. A senior ML engineer in the UK commands £100,000 to £127,000 in base salary. A Head of AI in London ranges from £111,000 to £269,000. In the US, the numbers are even higher — a VP of AI averages $351,000, and compensation for senior AI engineers runs $150,000 to $280,000. These are competitive market rates, driven by an AI talent demand-to-supply ratio of 3.2 to 1 globally.

Now consider: it takes an average of 142 days to fill an AI role, compared with 44 days for the general market. During that vacancy, you're losing roughly $2,500 per week in productivity. Once hired, a senior technical hire takes 6 to 12 months to reach full productivity — longer in organisations without existing AI infrastructure, because they're building the foundations as well as the product.

If the hire doesn't work out — and in a field where average tech tenure is 2 to 3 years, turnover is a real risk — you're looking at a total cost of 1.5 to 3 times annual salary when you factor in recruitment fees, onboarding, lost productivity, severance, and the cost of starting the search again. For a senior AI engineer on £120,000, that's £180,000 to £360,000 for a failed hire.

Compare this with a fractional AI leadership engagement. A fractional CTO or Head of AI working two days per week typically costs 60 to 80% less than a full-time equivalent at the same seniority level, brings cross-industry pattern recognition from multiple organisations, and can start delivering strategic value within weeks rather than months.

The financial argument for fractional leadership at the early stages isn't even close.

But the financial costs aren't the most dangerous part. The real damage from premature hiring is organisational.

You hire talented ML engineers and data scientists. They build genuinely impressive prototypes. Those prototypes never make it to production. IDC and Lenovo data shows that 88% of AI proofs of concept never reach production — and the primary reason is that they were built in isolation from the business context that would make them useful. Without senior AI leadership connecting technical capability to commercial reality, you end up with a team that publishes internal demos but doesn't ship products.

Your AI team becomes a silo. They sit in engineering, far from the business teams whose problems they're supposed to solve. They build technically correct solutions that nobody trusts, nobody adopts, and nobody asked for. Harvard Business Review documented cases where AI teams in banks were simultaneously flagging customers as too risky for lending while marketing was targeting those same customers for growth — because the AI team had no line of sight into commercial strategy.

You hire a Head of AI or Chief Data Officer. They arrive with energy and ambition. At around 18 months, they hit a wall — the organisation wasn't ready for the change they were hired to drive, they don't have the cross-functional authority to unblock adoption, and they leave. The average CDO tenure is 2 to 2.5 years, and nearly a third of current CDOs question the long-term viability of their own role. When they leave, they take their institutional knowledge with them, and you start again.

All of them are preventable.

For most companies in the middle of this progression — past pure exploration but not yet ready for a fully internal team — the hybrid model is the right answer. But "hybrid" is often used as a vague catch-all. Here's what it looks like in practice when it's structured well.

The most effective hybrid arrangements I've seen pair a senior fractional AI leader (typically two days per week) with a small internal core — one or two engineers who own the day-to-day execution. The fractional leader defines the architecture, reviews code and model decisions, manages technical risk, and mentors the internal team. The internal team builds the domain knowledge, maintains the systems, and gradually takes on more strategic responsibility.

I worked with one early-stage company where the founder had a strong product vision involving AI but no technical leadership to execute it. We established a structure where I worked a set number of fixed days per week alongside a single senior developer. My role covered everything from product architecture and commercialisation strategy to managing the development workflow and quality. Over several months, the developer's capability grew substantially — not because I was formally training them, but because they were working within a structure that demanded good architectural decisions, clear code review processes, and consistent delivery standards.

The key was that the engagement was designed from the start to build internal capability, not to create dependency. Every architectural decision was documented. Every technical choice was explained, not just implemented. The goal was always that the team could eventually operate independently, with my involvement reducing over time from delivery to oversight to occasional strategic advice.

Before the engagement starts, agree on what "ready for internal leadership" looks like. Specific, measurable indicators: the internal team can independently architect new features, they can evaluate and manage external technical resources, they can make infrastructure decisions without senior oversight. When those triggers are met, the fractional engagement scales down. If you don't define these upfront, engagements drift into comfortable dependency, which is a failure of the model even if the work is good.

Hybrid models fail when the boundaries get blurred. If the fractional leader ends up doing all the strategic work while the internal team only executes, no capability transfer happens. If the internal team makes architectural decisions without review because the fractional leader isn't available that day, quality drifts. The structure needs fixed touchpoints: regular sessions where decisions are made together, code reviews that are genuinely educational, and a clear escalation path for urgent issues that respects the fractional leader's committed hours.

Most AI consultancies won't say this, so I will: the goal of any external AI engagement should be to make the external person unnecessary.

This isn't how the consulting industry typically works. The major firms have invested billions in AI practices — Accenture's $3 billion Data & AI investment, Deloitte's $4 billion AI services plan — and their business model depends on long-term, high-value engagements. Research from HFS and IBM found that 65% of enterprises now say traditional consulting models no longer deliver value, and 73% of consulting buyers want fundamentally different pricing models. There's a reason for that frustration: many consulting relationships are structured around dependency.

The fractional model, done well, is structurally different. You're not buying a team of junior consultants managed by a partner who appears at the steering committee. You're working directly with a senior practitioner who has built and shipped the things they're advising you on. And that practitioner's success is measured by how effectively they transfer knowledge and make themselves redundant.

When I think about the engagements I'm most proud of, they're the ones where the client eventually said: "We don't need you for this anymore." That's the whole point.

This doesn't mean the relationship necessarily ends completely. Companies that have built strong internal AI teams still benefit from occasional external perspective — an independent architecture review, strategic advice on a new technical domain, a sounding board for a hire they're considering. But the nature of the engagement shifts from delivery to advisory, and the cost drops accordingly.

If you're a founder or CEO trying to work out where you are in this progression, here's a simplified diagnostic:

You're at Stage 1 (Fractional) if:

• AI is one of several strategic priorities, not the core of your product
• You don't have dedicated data infrastructure or a data engineering function
• Your AI workload is project-based rather than continuous
• You haven't yet validated specific, measurable AI use cases
• Right move: Engage a fractional AI leader to define strategy, validate use cases, and build a roadmap for capability development

You're at Stage 2 (Hybrid) if:

• You have validated AI use cases delivering measurable value
• You have functional data pipelines and reasonable data quality
• Your AI workload is recurring and growing
• You need someone working on AI daily, not just in project bursts
• Right move: Hire your first internal AI engineers, paired with fractional senior leadership for architectural direction and mentoring

You're at Stage 3 (Internal with selective support) if:

• Your internal team can independently architect, build, and deploy AI features
• You have established code review, deployment, and monitoring processes
• Your AI leaders participate in commercial and product strategy, not just engineering
• You bring in external expertise for genuinely novel challenges, not routine delivery
• Right move: Transition fractional leadership to a light advisory relationship; invest in growing your internal team's seniority and breadth

Most companies I work with are somewhere in the transition between Stage 1 and Stage 2. And that's fine: 62% of companies sit there, according to MIT's enterprise AI research. Being early in the progression is fine. Pretending you're further along than you are is where the damage happens.

Two things in the current market are worth considering before you commit to a resourcing model.

First, we're in what Gartner calls the "Trough of Disillusionment" for generative AI. The initial hype has cooled. Only 5% of companies are capturing significant value from AI, and 60% are generating no measurable value at all. MIT found that internal AI builds succeed only about a third of the time, compared with roughly two-thirds for purchased or externally supported solutions. Which doesn't mean you shouldn't build internal capability. It means you should build it carefully, with senior guidance, rather than hiring aggressively and hoping for the best.

Second, the economics of AI teams are shifting. AI coding tools are genuinely changing the calculus. Over 75% of developers now use AI coding assistants, and they're cutting onboarding time nearly in half. This means smaller, more senior teams can achieve what previously required larger groups. The emerging model is a strong architectural leader supported by a smaller number of capable engineers, amplified by AI tooling. This makes the fractional-to-hybrid progression even more relevant: you need strategic leadership more than you need headcount.

The AI team decision is an ongoing calibration between your ambition, your maturity, and what your organisation can actually support. The companies that navigate it well are honest about where they are, and they invest in capability that progressively builds independence.