# Build vs. Buy

A structured decision about whether to create a capability, acquire it, reuse an existing option, or combine approaches based on value, cost, risk, and control.

- Type: method
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/build-vs-buy/>)

## What it means

Build vs. buy evaluates how a product should obtain a capability. “Build” means owning custom development and operation; “buy” includes commercial software, managed services, and vendor platforms. Real decisions often include reuse, open source, partnership, or hybrid configurations. The aim is not ideological purity but a fit between strategic importance and lifecycle consequences.

## Why it matters

Technology choices commit money, people, time, data, and future flexibility. Building can create differentiation and control, but also creates maintenance and operational obligations. Buying can accelerate delivery and provide mature capabilities, but introduces integration, pricing, roadmap, continuity, and lock-in risks. A shared framework makes these trade-offs visible instead of letting familiarity decide.

## When to use it

Use this method before major platform, infrastructure, workflow, or product-capability investments, and revisit the decision when scale or vendor conditions change. Build is more plausible for strategically differentiating capabilities with unusual requirements. Buy or reuse is often stronger for commodity needs when an option meets essential requirements and its lifecycle risk is acceptable.

## How it works

1. Clarify the user outcome, strategic importance, constraints, and minimum acceptable capability before comparing solutions.
2. Survey reuse, open-source, commercial, managed-service, custom-build, and hybrid options rather than forcing a binary choice.
3. Compare time to value and full lifecycle cost, including integration, migration, operation, support, compliance, and exit.
4. Assess product fit, extensibility, data control, security, reliability, accessibility, vendor health, and roadmap influence.
5. Test uncertain claims through prototypes, reference checks, commercial discovery, and realistic workload or workflow trials.
6. Record the decision, assumptions, review triggers, ownership, and an exit or replacement strategy proportionate to risk.

## A practical example

A marketplace considers building identity verification. Because verification is regulated but not its differentiator, it pilots two vendors and a hybrid adapter. The team compares coverage, false decisions, accessibility, integration effort, incident support, unit economics, data retention, and migration rights—not just license price—and records volume and quality triggers for review.

## Where it breaks

Forecasts are uncertain, vendor demonstrations favor happy paths, and internal build estimates often omit long-term staffing. Weighted scorecards can disguise subjective assumptions behind precise numbers. Buying does not outsource accountability for user harm or compliance, while building does not guarantee control if the solution still depends on scarce expertise or external infrastructure.

## Common mistakes

- Comparing purchase price with initial development cost instead of total lifecycle cost and opportunity cost.
- Labeling a capability differentiating merely because the organization has always built it itself.
- Ignoring migration, data portability, contract change, vendor failure, and service exit scenarios.
- Selecting a product from a feature checklist without testing real workflows, edge cases, and integration constraints.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/build-vs-buy/#visualization-build-vs-buy>)

## Sources

1. [Define Your Purchasing Strategy](<https://www.gov.uk/guidance/define-your-purchasing-strategy>) — GOV.UK · Government technology guidance
2. [Choosing Technology: An Introduction](<https://www.gov.uk/service-manual/technology/choosing-technology-an-introduction>) — GOV.UK Service Manual · Government service standard guidance
3. [Choose the Right Tools and Technology](<https://www.gov.uk/service-manual/service-standard/point-11-choose-the-right-tools-and-technology>) — GOV.UK Service Manual · Government service standard

## Related topics

- [Architecture Decision Record](<https://wiki.soroush.uk/topic/architecture-decision-record/>)
- [Non-Functional Requirements](<https://wiki.soroush.uk/topic/non-functional-requirements/>)
- [Product Strategy](<https://wiki.soroush.uk/topic/product-strategy/>)
