Skip to main content
Back to insights

Build, Buy or Integrate? Four Tests for a Better Decision

Choose build, buy or integration by testing differentiation, workflow fit, ownership and change, not by comparing licence price with development cost.

  • Architecture
  • Modernisation
  • Integration

Arinao Tshamano12 September 20261 min read

Build versus buy is rarely a binary decision. Most dependable systems combine products, custom workflows and integration around a specific operating model.

A licence can look cheaper while forcing teams into manual workarounds. A custom build can look flexible while creating long-term ownership the organisation is not prepared to carry. The decision needs a wider frame.

What good engineering looks like

Test four dimensions: strategic differentiation, workflow fit, integration complexity and enduring ownership. Buy standard capability where process alignment is acceptable. Build where the operating model creates material advantage. Integrate where existing systems remain useful but information and decisions must move reliably.

  • Differentiation: does this capability change how the organisation competes or serves?

  • Fit: how many critical exceptions sit outside the standard product?

  • Integration: what data, controls and timing must cross boundaries?

  • Ownership: who will maintain, secure and evolve the result?

A practical starting point

  1. Map the target workflow before vendor demonstrations.

  2. Cost the manual workarounds and data reconciliation.

  3. Assess exit, migration and support paths.

  4. Choose the smallest reversible commitment that tests the assumptions.

The decision to make

A sound decision makes the trade-offs explicit and leaves the organisation able to operate and change the system after implementation.

Apply the thinking

Working through a related technology decision?

Share the operational context, current systems, constraints, and decision you need to make.

Discuss a requirement