Operations & Sourcing method guide

Make / Buy / Partner / Build

This tool frames sourcing choices through strategic importance, internal capability and credible alternatives.

Beginner-friendly guide · 4 min read

What Make / Buy / Partner / Build does

This tool frames sourcing choices through strategic importance, internal capability and credible alternatives.

Make, buy, partner or build analysis helps an organisation decide how to access an activity or capability. The choice affects more than immediate cost: it shapes knowledge, control, flexibility, dependency, speed and future strategic options.

Begin with a clearly defined activity and its importance. Then compare realistic routes, including developing the capability internally, purchasing a service or asset, and forming a relationship in which risks and knowledge are shared.

Cambridge make-or-buy research treats sourcing as a strategic decision with multiple factors, not a simple cost comparison. The wider sequence links market needs, success factors, activities and option evaluation.[1][2]

Method schematicMatch sourcing posture to importance and internal strength

The matrix frames the first discussion. Detailed option evidence is needed before commitment.

Strategic importance: low to high

Buy or monitor
Make and protect
Partner or build
Use selectively

Internal strength: low to high

InnovationFlow explanatory schematic, synthesised from the method sources[1][2].

Understand the method

The parts in plain language

1

Strategic importance

Assess how the activity contributes to differentiation, critical knowledge, customer access, risk and future options.[1][2]

Illustrative example

Diagnostic logic may be strategically important even if cloud hosting is not distinctive.

2

Internal capability

Examine current strength, capacity, learning potential and the investment required to perform the activity well.[1][2]

Illustrative example

Two experts can deliver prototypes, but the organisation lacks repeatable operations for scale.

3

Access routes and consequences

Compare make, buy, partner and build options across total cost, time, control, learning, dependency and reversibility.[1][2]

Illustrative example

A partner accelerates launch, but the agreement must preserve data access and internal architecture knowledge.

When to use it

  • When a roadmap creates capabilities the organisation does not currently possess.
  • When outsourcing or internal investment decisions have strategic consequences.

A practical workflow

  1. 1

    Define the activity or capability at a decision-ready level.

  2. 2

    Assess strategic importance and current internal strength.

  3. 3

    Identify plausible make, buy, partner and build options.

  4. 4

    Record rationale and promote uncertain cases into detailed scoring.

Fictional worked example

Example: building a connected service

This example is illustrative rather than a reported case. A manufacturer compares sourcing routes for three enabling activities.

Domain models

Observation:Distinctive and supported by strong internal knowledge.

Implication:Make and protect, while improving repeatability.

Cloud operations

Observation:Important for reliability but widely available from specialists.

Implication:Buy or partner with clear service and exit conditions.

Customer integration

Observation:Strategic and currently weak, with knowledge split across parties.

Implication:Co-develop through partnership and build internal ownership.

From analysis to decision

How to interpret the result

  • 1Use lifecycle cost and strategic consequence, not purchase price alone.
  • 2Assess how each option changes knowledge and dependency over time.
  • 3Move the chosen route and capability-building needs into the roadmap.

The interpretation guidance is an InnovationFlow synthesis of[1][2].

What a useful output looks like

A portfolio of preliminary sourcing positions.
Subjects for detailed option evaluation and roadmap action.

Common pitfalls

  • Do not decide from short-term cost alone.
  • Account for knowledge, dependency, flexibility and future strategic importance.

References and method basis

  1. [1]Probert, D. (1997). Developing a Make or Buy Strategy for Manufacturing Business. Institution of Electrical Engineers. Source ↗Original method source
  2. [2]Canez, L.E., Platts, K.W. and Probert, D.R. (2000). Developing a framework for make-or-buy decisions. International Journal of Operations & Production Management, 20(11), 1313-1330. Source ↗Peer-reviewed research

This guide synthesises the named sources into practical questions for strategy and innovation work. It does not claim that using a tool by itself produces a successful decision.

Practitioner support

Talk to an experienced practitioner

Ask about roadmapping, facilitation or applying a method in your organisation. Your question goes directly to the InnovationFlow team.

Sent securely to hello@innovationflow.app.