Make–Buy–Partner Review¶
Decision framework — instantiates Comparative Advantage Specialization
Decides whether a function should stay in-house, be bought on the market, or be run through partnership by weighing opportunity cost, transaction cost, and dependency.
A Make–Buy–Partner Review is a structured decision framework that applies comparative advantage across the boundary of the organization itself: for a given function, should we make it internally, buy it from a market of specialists, or run it through a partnership? Its defining question is not "who on our team is cheapest?" but "does this function belong inside our walls at all?" To answer, it weighs three things a naive cost comparison misses — the opportunity cost of the internal capability the function ties up, the transaction cost of coordinating and enforcing an external arrangement, and the strategic dependency an outside relationship would create. The review produces a verdict — make, buy, or partner — and nothing else. It moves no goods, signs no service levels, and negotiates no ongoing relationship; those are downstream of the choice it settles.
Example¶
A growing online furniture retailer runs its own warehouse and ships every order itself. Fulfillment is competent, but it is eating the founders' attention and capital that could go into product design and supplier relationships — the things only they can do. A Make–Buy–Partner Review is convened for the fulfillment function.
The opportunity cost side is stark: every dollar and hour sunk into forklift leases and hiring pickers is a dollar and hour not spent on the design and sourcing edge that actually differentiates the brand. The transaction cost side asks what it would take to run this through a third-party logistics provider — writing the spec, integrating systems, verifying accuracy, handling exceptions — and whether that overhead would swallow the savings. The dependency side is the sharpest: hand fulfillment to one 3PL and the retailer's peak-season fate rests on a vendor who then holds real leverage. The review's output is a reasoned verdict — partner with a regional 3PL for standard SKUs but keep white-glove delivery in-house — with the dependency flagged for whatever contract follows. It decides the boundary; it does not draft the deal.
How it works¶
- Frame the function as a boundary question. The unit of analysis is a whole function or capability, and the choices are make / buy / partner — not which internal person owns a task.
- Price the internal opportunity cost. Estimate what scarce internal capability the function consumes and what higher-value work that capability is displaced from — the reason keeping a competent function in-house can still be the wrong call.
- Run the transaction-cost check. Tally the search, negotiation, integration, verification, and enforcement costs of an external arrangement and test whether they erase the comparative-advantage gain.
- Review the dependency created. Assess single-source risk, switching costs, bargaining power, and backup capacity, so the verdict weighs strategic exposure and not just this year's price.
Tuning parameters¶
- Strategic-core boundary — how broadly "things only we should do" is drawn. Draw it wide and almost nothing is outsourced; draw it narrow and the org risks hollowing out a capability it later needs.
- Transaction-cost horizon — whether you count only setup costs or the full lifetime of coordinating and policing the arrangement. Short horizons flatter outsourcing.
- Dependency tolerance — how much single-source exposure is acceptable for the efficiency gained. Lower tolerance favors partnership or dual-sourcing over a clean buy.
- Partner-vs-buy weighting — how much to prefer a collaborative partnership (shared risk, deeper integration) over an arm's-length purchase (simpler, more replaceable).
- Review trigger — one-time for a new function, or re-run when internal capacity, market maturity, or the dependency picture shifts.
When it helps, and when it misleads¶
Its strength is that it stops an organization from doing everything itself out of habit or pride, and — unlike a pure price quote — it refuses to outsource a function without first pricing the coordination overhead and the strategic exposure that a cheap quote hides. It is the mechanism that applies comparative advantage where the gains are often largest: the org boundary.
Its failure mode is underweighting dependency for a visible near-term saving. Outsource a function that requires relationship-specific investment and the buyer can find itself exposed to the hold-up problem — once you depend on a specialized supplier, that supplier gains leverage to renegotiate on worse terms.[n1] The classic misuse is choosing the cheapest provider on a spreadsheet while ignoring exchange reliability and lock-in, which the archetype flags as an unsafe use of comparative advantage. The guarding discipline is to make the dependency review a veto, not a footnote: a "buy" that creates unmanaged single-source risk should be sent back as a "partner with safeguards" or a "make," not waved through on price.
How it implements the components¶
opportunity_cost_comparison— prices the internal capability a function consumes against the higher-value work it displaces, which is what makes keeping a competent function in-house sometimes the wrong choice.transaction_cost_check— tallies search, negotiation, integration, verification, and enforcement costs to test whether an external arrangement's overhead erases the specialization gain.dependency_review— assesses single-source risk, switching costs, and bargaining power created by a buy or partner verdict, so strategic exposure shapes the decision.
It writes no role_specialization_rule and runs no fairness_and_power_review (those belong to internal role design), and it builds no exchange_channel or coordination_protocol. Its nearest twin is Supplier or Partner Specialization Contract: this review decides whether to externalize at all, while the contract governs the exchange once the verdict is "buy" or "partner" — the review moves nothing, the contract runs the relationship.
Related¶
- Instantiates: Comparative Advantage Specialization — applies relative-opportunity-cost logic across the organizational boundary.
- Sibling mechanisms: Comparative Task Assignment Matrix · Role Design Workshop · Internal Service Agreement · Supplier or Partner Specialization Contract · Cross-Functional Work Split · Trade or Swap Arrangement
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Make–Buy–Partner Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it decides whether a function should stay in-house, be bought on the market, or be run through partnership by weighing opportunity cost, transaction cost, and dependency.
Independent corroboration: The frozen evidence defines Make–Buy–Partner Review as 'Decides whether a function should stay in-house, be bought on the market, or be run through partnership by weighing opportunity cost, transaction cost, and dependency', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Comparative advantage and transaction-cost economics provide the core make-or-buy lineage.
Related originating lineages:
- Logistics & Supply Chain Management — Sourcing practice materially shapes supplier-market availability and continuity analysis.
- Organizational & Management Science — Make-buy-partner choices are canonical strategic-management decisions about organizational boundaries and capabilities.
Review resolution: Light authoritative research supports economics_finance as the primary provenance: Comparative advantage and transaction-cost economics provide the core make-or-buy lineage. GAO documents make-or-buy reviews that compare internal capability with external providers, costs, and market conditions. The competing reviewed lineage (organizational_management) and other formative traditions remain explicit alternates rather than being erased or confused with downstream applicability. origin_mode=cross_disciplinary_synthesis records the relationship among those origin traditions, while domain_reach=multi_domain separately records how broadly the generalized mechanism can be applied.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://www.gao.gov/assets/gao-13-417.pdf — GAO documents make-or-buy reviews that compare internal capability with external providers, costs, and market conditions.
Notes¶
The review deliberately ends at a verdict. Bolting the contract terms onto the same meeting tends to let a preferred vendor's proposal drive the make/buy/partner logic backwards — deciding to buy because a good deal is on the table, rather than deciding to buy and then shopping. Keeping the boundary decision and the governing contract separate protects the logic of both.
[n1] In transaction-cost economics, the hold-up problem arises when one party makes investments specialized to a relationship; the counterparty can then threaten to withdraw or renegotiate to capture the value, because the invested party has no cheap alternative. It is the core reason a make-or-buy decision must weigh dependency, not just price. ↩