All insights
operating-modelsourcingcapability-strategydecision-making

Build, buy, or blend: the false binary that quietly shapes your operating model

Every capability decision gets framed as build versus buy. It's the wrong question. The real variable is how much of a capability you must own versus simply access — a spectrum, not a switch — and the most valuable position is often the one the binary hides: the blend.

Yasir Aheer20 July 20268 min read

Sooner or later every operating decision arrives in the same shape: should we build this ourselves, or buy it? A new finance capability, a data platform, a support function — the debate splits into two camps, someone builds a cost model, and a verdict is reached.

The verdict is often wrong, because the question was miscast before anyone opened a spreadsheet.

Two questions decide it — not one

The build-vs-buy debate usually turns on a single axis: cost. But cost is a consequence, not a cause. Two prior questions actually determine the right home for a capability: how much does it differentiate you, and how hard is it to run well. Explore the combinations.

The Capability Classifier

Where Does Your Capability Belong?

Pick the two answers that fit a real capability you are weighing up

Strategic differentiation

Operating complexity

BlendNot your edge, but hard to run
BlendYour edge, and hard to build
BuyTable stakes, easy to run
BuildYour edge, and you can run it
CommodityCore

Differentiation → · rows: complex (top) / simple (bottom)

Recommended posture

Blend

It differentiates you but building the whole machine is slow and risky. Own the strategy, standards, data, and outcome — blend in operating capacity to get there faster.

Scaled data opsCustomer operations

The classifier surfaces what the binary suppresses: complexity is what makes the blend rational. Something can be central to your advantage and too hard to stand up from scratch on any sensible timeline. Forcing that into "build or buy" gives you a bad answer either way.

Why each pure option fails at the edges

Push the pure options to their limits and their failure modes are predictable.

Pure build looks like control, but a capability is not a purchase — it's an institutional muscle. As McKinsey puts it, a genuine capability is an integrated set of people, processes, and technology that lets you consistently outperform, and it has to be grown deliberately from strategy, not assembled overnight [3]. Build the wrong thing and you've committed years and headcount to a muscle you'll never make world-class.

Pure buy looks like speed, but generic software commoditises whatever it touches. It runs your happy path and stalls on your exceptions — and if a capability is core, buying the same thing your competitors buy quietly erases the difference you were trying to protect.

The market has already moved to the blend

This isn't theory; it's where sourcing is actually heading. Deloitte's survey of more than 500 executives describes a shift to multidimensional sourcing — organisations deliberately combining a retained core, an outsourcing ecosystem, global in-house centres, and a digital workforce, with insourcing rising and outcome-based models growing [1]. The pure play is giving way to the portfolio.

The clearest signal is the rise of models built specifically to sit between the poles. Deloitte describes Build-Operate-Transform-Transfer as "neither in-house nor conventionally outsourced" — a partner stands up and transforms a capability while the organisation keeps control and can pull it back in later [2]. That is the blend formalised: access now, own over time.

Build vs buy vs blend, honestly compared

Build

Own everything

Full control and, if you make it world-class, real differentiation — paid for in time, headcount, and fixed cost.

Speed to capacity
Slow
Control of standards & data
Full
Handles your exceptions
If you build for it
Cost curve
High fixed cost
Protects differentiation
Yes — if world-class
Who owns the outcome
You

Buy

Own nothing

Fast and cheap to start — but generic software commoditises whatever it touches and stalls on your exceptions.

Speed to capacity
Fast
Control of standards & data
Low
Handles your exceptions
Poorly (generic)
Cost curve
Low, then plateaus
Protects differentiation
No — commoditises it
Who owns the outcome
The vendor, implicitly

Blend

Own what matters

Own what matters

Own the strategy, standards, data, and outcome; access the operating capacity. Fast now, yours over time.

Speed to capacity
Fast
Control of standards & data
You keep them
Handles your exceptions
Designed to
Cost curve
Variable, scales with need
Protects differentiation
Yes — you keep the core
Who owns the outcome
You (partner operates)

How to make the call

The blend is powerful but not a default — an unmanaged blend is just outsourcing with extra steps. Decide it deliberately.

Making the Call

How to Decide — and Govern — the Blend

Tap a step to see why it matters and how to run it

  1. Would a customer pay more, or switch to you, because you do this yourself? If yes, it is core. If it merely has to run flawlessly but is invisible to customers, it is context. If anyone can provide it, it is commodity.

    Why it matters

    This screen comes before any cost model. Cost is a consequence of where a capability belongs — not the thing that decides it.

    In practice

    Write the one-line customer test for the capability. If you cannot argue it changes what a customer would pay or choose, treat it as context or commodity.

That fourth step is where blends succeed or quietly fail. Deloitte's own reading is that as the sourcing landscape becomes multidimensional, the binding constraint becomes the maturity of governance — managing the "extended workforce" as one system rather than a pile of contracts [1].

The question that matters

Build versus buy forces a choice between owning everything and owning nothing — and both extremes quietly cost you, one in years, the other in your edge.

The better question is: What must we own to keep our advantage, and what can we simply access to get there faster? Own the outcome, the standards, and the data. Blend the machinery. That's not a compromise between build and buy — it's a more precise answer than either.

Sources

  1. Deloitte. 2024 Global Outsourcing Survey. 2024.Insights from 500+ executives: organisations are adopting 'multidimensional sourcing' — combining a retained organisation, an outsourcing ecosystem, global in-house centres, and a digital workforce — with insourcing rising and outcome-based delivery models growing.View source
  2. Deloitte. Build-Operate-Transform-Transfer (BOTT): shift the risk of outsourcing. 2024.A model that is 'neither in-house nor conventionally outsourced' — a partner stands up, stabilises, and transforms a capability while the organisation preserves control and can transition it back.View source
  3. McKinsey & Company. What's your superpower? How companies can build an institutional capability to achieve competitive advantage. 2023.An institutional capability is an integrated set of people, processes, and technology that lets a company consistently do something better than competitors; it must derive from strategy and, done well, becomes a lasting edge.View source
Y
Yasir Aheer· Founder, OpsTeam

Yasir Aheer is the founder of OpsTeam. He writes about engineered operations, operating-model design, and the business and organisational implications of running People + Engineered Platforms + Production AI as one integrated system.

Ready to put this thinking into practice?

We design and operate integrated operating models for organisations ready to compound efficiency. Let's discuss yours.

Schedule Discovery Call