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.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/build-vs-buy/
01What 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.[1][2][3]
Custom fit and roadmap control; development, operation, maintenance, and staffing responsibility
Faster capability and vendor expertise; integration, dependency, pricing, migration, and exit risk
Strategic importance · lifecycle cost · evidence · reversibility
Reuse, open source, managed service, partnership, custom development, and hybrid configurations belong in the option set.
02Why 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.
03When 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.
04How it works
- Clarify the user outcome, strategic importance, constraints, and minimum acceptable capability before comparing solutions.
- Survey reuse, open-source, commercial, managed-service, custom-build, and hybrid options rather than forcing a binary choice.
- Compare time to value and full lifecycle cost, including integration, migration, operation, support, compliance, and exit.
- Assess product fit, extensibility, data control, security, reliability, accessibility, vendor health, and roadmap influence.
- Test uncertain claims through prototypes, reference checks, commercial discovery, and realistic workload or workflow trials.
- Record the decision, assumptions, review triggers, ownership, and an exit or replacement strategy proportionate to risk.
05A 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.
06Where 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.
07Sources
- Define Your Purchasing StrategyGOV.UK · Government technology guidanceDefine Your Purchasing Strategy
- Choosing Technology: An IntroductionGOV.UK Service Manual · Government service standard guidanceChoosing Technology: An Introduction
- Choose the Right Tools and TechnologyGOV.UK Service Manual · Government service standardChoose the Right Tools and Technology