Rethinking how organisations build, buy or embed specialist capability

That distinction is becoming less useful as requirements change more quickly, specialist skills become harder to access and the expertise needed tomorrow looks very different from what is needed today.

For leaders, the question is therefore becoming less about who owns the resource and more about how to build the right capability around the organisation’s needs. There may be no single answer, but there are more options than the traditional build-or-buy choice suggests.

Capability is not the same as headcount

When a new requirement emerges, creating a role is one of the most natural organisational responses and, in many cases, it is absolutely the right one. However, headcount and capability are not interchangeable.

An organisation might recruit an intelligence analyst when the real requirement is broader: stronger geopolitical awareness, regional expertise, better decision support and the ability to respond as circumstances change.

Leadership teams therefore need to start one step earlier. Rather than asking, “What role do we need?”, they should ask, “What outcome are we trying to achieve, and what capability will get us there?” That change in emphasis can lead to a very different answer.

Build, buy or embed?

Broadly, organisations have three ways of accessing specialist capability, each suited to a different type of requirement.

Build it

Developing expertise internally offers control and deep organisational knowledge. Where the requirement is stable, strategically important and likely to remain relatively consistent, building an internal team may be the right long-term decision. But it also requires sustained investment in recruitment, development, leadership and retention.

Buy it

External specialists and consultancy can be highly effective when an organisation needs a defined outcome, project or piece of expertise. It acquires the output without needing to own the capability permanently. The limitation comes when the

requirement becomes ongoing or success depends on deep integration into day-to-day decision-making.

Embed it

A third model sits between the two. Specialist professionals or teams work within the organisation and become deeply integrated into its objectives and ways of working, with the flexibility to adapt as the requirement evolves.

This can make particular sense where the requirement is ongoing but evolving, specialist skills are difficult to maintain internally or the organisation needs flexibility as circumstances change.

None of these models is inherently better than the others; what matters is making a deliberate choice based on the organisation’s needs.

Start with the problem, not the delivery model

Too often, organisations define the solution before fully defining the problem: “We need an analyst”, “We need another security manager” or “We need somebody covering this region.” These describe resources, not necessarily the underlying requirement.

A better capability discussion starts with questions such as:

• What outcome are we trying to achieve, and where are the genuine gaps?
• How important are organisational context and integration?
• Is the requirement stable, or will demand fluctuate?
• Could it expand into other disciplines or geographies?

Only then should the organisation decide how that capability is best delivered. That might mean recruiting, engaging an external adviser, embedding an individual or team, or combining the three.

The future is likely to be more blended

I believe successful organisations will increasingly combine a strong internal core with specialist external capability that can be brought closer to the business and adapted as needs change.

This matters particularly in security, intelligence and healthcare, where risks rarely respect organisational structures. A geopolitical development can quickly become a security problem; a security incident can create a medical issue; and a health event can have operational, reputational and people consequences.

As these risks intersect, organisations need to connect expertise more effectively rather than simply build larger permanent teams.

Flexible capability is not necessarily temporary. One specialist may evolve into a team, a regional requirement may become global, or an intelligence need may

acquire a security or clinical dimension. Equally, capability may need to reduce or shift elsewhere.

The organisations best equipped for this environment will not necessarily have the largest teams, but they will be able to access the right expertise at the right time without redesigning themselves whenever circumstances change.

A leadership decision, not a resourcing decision

Deciding how to access specialist expertise is not simply a recruitment or procurement exercise. Leaders must determine which capabilities are genuinely core, which need to sit inside the organisation and where an external or blended model will deliver the strongest outcome.

This thinking has shaped Healix Embedded Solutions across security, intelligence and clinical expertise, but the principle extends beyond any individual service model: start with the capability the organisation needs, not the mechanism used to provide it.

The question is no longer simply, “Do we build or buy?” but “What capability do we need, where should it sit, and how should it evolve with us?”.