Build, Borrow, or Buy: How to Choose a Growth Path

Every company eventually hits a capability gap. The build, borrow, or buy decision is how you close it. Do you develop the new capability in-house, partner with someone who already has it, or acquire them outright? Getting this choice right shapes your competitive position for years. Getting it wrong burns budget, misses windows, and sometimes kills good businesses.

This guide walks through each path, the trade-offs, a real decision process, and the most common ways executives get it wrong.

What is the build, borrow, or buy framework?

The build, borrow, or buy framework is a structured way to evaluate three pathways for acquiring a new capability or resource your organization needs:

• Build means developing the capability internally through organic investment, typically research and development (R&D), hiring, and internal product teams.
• Borrow means accessing the capability externally without owning it, through licensing agreements, joint ventures, strategic alliances, or partnerships.
• Buy means acquiring the capability outright through mergers and acquisitions (M&A), purchasing a company that already has what you need.

The framework, formalized by strategy researchers Laurence Capron and Will Mitchell, reframes capability-building as a resource procurement decision rather than a pure strategic vision exercise. The right answer depends on what you already have, how urgently you need the new capability, and how well you can integrate or manage external relationships.

Key framing: Build, borrow, or buy is not about ambition. It's about fit between the resource you need and the path most likely to deliver it reliably.

---

Key Facts

• Between 70% and 90% of acquisitions fail to create the shareholder value they were designed to deliver (McKinsey & Company, 2023). Most failures trace back to poor strategic fit and integration missteps, not deal mechanics.
• Companies that rely exclusively on organic (build) growth consistently underperform peers who combine build, borrow, and buy strategies across a 10-year horizon (Harvard Business Review, 2012 Capron and Mitchell research).
• Joint ventures and alliances have a failure rate of roughly 50% within 5 years, largely due to misaligned incentives and unclear exit terms (MIT Sloan Management Review, 2021).

---

Build vs borrow vs buy: a real decision table

Each path has a different risk and reward profile. None is inherently better. Context decides.

Two questions cut through most of the noise. First: how closely does this capability connect to your core competencies? Second: how much time do you have?

If the capability is central to your differentiation and you have 18 months, build. If it's peripheral and a trusted partner can deliver it in 90 days, borrow. If the capability is scarce, the window is closing, and the target fits your corporate strategy, buy.

The resource pathways framework

Capron and Mitchell's research identified a decision logic that goes deeper than the simple cost-speed matrix above. They looked at four factors that predict which path delivers the best outcome:

1. Relevance of your existing internal resources If your organization already has capabilities close to what you need, building is often faster and more reliable than it appears. The gap is incremental. But if you'd be building from scratch in unfamiliar territory, external paths are safer.

2. Trustworthiness and accessibility of partners Borrowing works when you can find a partner with the right capability who is willing to share it on acceptable terms. In fragmented markets, good partners exist. In concentrated markets, the only companies with the capability you need might be direct competitors who'd never license it to you.

3. Integration requirements Some capabilities only work when deeply integrated with your operations, culture, and systems. Vertical integration decisions often fall here. If integration depth is high, borrowing (which keeps the capability at arm's length) will underperform. Build or buy.

4. Scalability and exclusivity needs If you need the capability to scale with your business and you can't allow a competitor to access the same resource, licensing rarely works long-term. Acquisition or internal build preserves exclusivity.

A simplified decision tree:

• Can we build it with existing talent in the required timeframe? If yes, lean build.
• Is it core to differentiation and does it need to be exclusive? If yes, eliminate borrow.
• Is there a reliable partner who won't become a competitor? If no, eliminate borrow.
• Can we afford the acquisition premium and integrate well? If yes, buy. If no, build even if it's slower.

Benefits and trade-offs of each path

Build

The build path keeps strategic control in your hands. You define the capability from the ground up, tailored to your needs. But it's slower than most teams project and more expensive when you factor in true cost of talent, management overhead, and failed experiments.

Build makes the most sense when you're deepening a competitive advantage that's already working. If your advantage is in customer experience, building a proprietary analytics layer reinforces what you already do better than anyone else.

The risk is opportunity cost. A competitor who buys or licenses a comparable capability in six months while you spend two years building might take the market before you arrive.

Borrow

Borrowing (through alliances, licenses, joint ventures, or partnerships) is the fastest path that doesn't require capital-intensive ownership. Strategic alliances in particular let you access capabilities from companies that have spent years building them.

The downside is dependence. You're exposed to partner risk, pricing changes, and in some cases the partner deciding to enter your market directly. Intellectual property (IP) leakage is a real concern when sharing operational details with outside parties.

Borrow works well when you need to test whether a capability creates value before committing fully. If the experiment works, you can decide to build or buy later with much better data.

Buy

Acquisitions deliver speed and ownership together. But the execution challenges are severe. Most M&A failures aren't strategic misfires at the decision stage. They're integration failures: cultural clashes, talent attrition, technology incompatibility, and the difficulty of combining two organizations with different ways of working.

Horizontal integration acquisitions (buying a competitor) tend to be cleaner to integrate than diversification acquisitions (buying into a new market). The further the acquired company sits from your existing operations, the harder integration becomes.

Common mistakes

Defaulting to build because it "feels safer" Build feels like control. But slow internal development in a fast-moving market isn't safe. It's a choice to cede ground to competitors who are moving faster.

Acquiring because the deal was available, not because the strategy required it Deals happen when targets become available and capital is cheap. Good discipline means walking away from acquisitions that don't fit the capability gap you're actually trying to close.

Underestimating integration cost and time Most executives model integration at 90 days. Real integrations for mid-size acquisitions typically run 12 to 24 months before the capability is truly embedded. Any strategic evaluation should include integration cost as a first-class input.

Borrowing when exclusivity matters If a licensed capability is also licensed to three competitors, you haven't gained a durable advantage. You've added cost.

Skipping the resource audit Teams often evaluate build vs buy without first honestly assessing what internal resources they have. The VRIO framework exists precisely to force this audit. Skip it and you'll either overestimate internal capabilities (leading to slow, failed builds) or underestimate them (leading to unnecessary acquisitions).

How to choose: a step-by-step decision guide

Step 1: Define the capability gap precisely

Don't start with a path. Start with a capability statement. What specifically do you need to be able to do that you can't do now? "We need to enter the SMB segment" is not a capability. "We need a low-touch digital sales motion with a 14-day sales cycle" is a capability. Specificity determines which paths are even viable.

Step 2: Audit internal resources

Using the VRIO framework, assess whether your current assets, people, and processes are close to what's needed. If you have 70% of the capability and need 100%, build may be realistic. If you're starting from zero, the timeline required to build may eliminate that option.

Step 3: Map external options honestly

For borrow, identify actual potential partners: who has this capability, would they license or partner, and what are the realistic terms? For buy, identify realistic targets: who is acquirable at a price that creates value, and can you integrate them?

Don't build hypothetical external options. Map real ones. Many leadership teams decide to build by default because they haven't done the external search rigorously enough.

Step 4: Score each path against your constraints

Use the decision table from earlier in this article. Rate each path on speed, cost, control, risk, and fit with your corporate strategy. Weight the factors by what actually matters most. If time is the binding constraint, weight speed heavily. If capital is constrained, weight cost.

The Ansoff Matrix is useful here: existing markets and existing products favor build; new markets and new products raise the risk profile of build substantially and push toward borrow or buy.

Step 5: Stress-test the downside, not just the upside

Ask what happens if this path fails. A failed build is typically a write-off on headcount and R&D, painful but recoverable. A failed acquisition at significant premium is a balance sheet impairment and often a leadership credibility crisis. A failed alliance can leave you further behind than when you started, with competitive IP at risk. Weight the downside explicitly before committing.

Build, borrow, or buy examples

These examples show the framework in practice. Apple had no time to rebuild; buy was correct. Amazon had time, the capability was core to its differentiation, and no acquisition target could provide scale; build was correct. Starbucks needed speed and optionality; borrow gave them both.

Best practices

Do:

• Run a formal capability audit before opening any discussion about path choice.
• Define the decision criteria (speed, cost, control, risk, exclusivity) explicitly and weight them before evaluating options.
• Involve integration teams early in acquisition evaluations, not after deal close.
• Use borrow as a deliberate testing phase before committing to build or buy.
• Revisit the decision as market conditions change. The right path in 2020 may be wrong in 2026.

Don't:

• Let deal availability drive acquisition decisions. Strategy should drive deal search, not the reverse.
• Assume build is the default because it "keeps things in-house." In fast markets, slow internal development is a real risk.
• Negotiate alliance terms without clear exit clauses. Partnerships that are hard to exit become liabilities.
• Underestimate cultural fit in acquisitions. Technical integration is manageable; cultural integration is the hard part.
• Think about growth horizons. Build tends to fit Horizon 1 deepening; borrow fits Horizon 2 adjacent moves; buy often accelerates Horizon 2 and 3 entries.

Frequently asked questions

What is the difference between build borrow or buy and make-or-buy? Make-or-buy is an older operations management concept focused on whether to manufacture a component internally or source it from a supplier. Build, borrow, or buy is a broader strategic framework that covers capability acquisition at the firm level, including alliances and acquisitions, not just supply chain decisions.

When does borrow beat buy even if you have the capital? When you need to test market fit before committing fully, when the capability is peripheral rather than core, or when an alliance partner has capabilities so embedded in their culture that they'd lose value after acquisition, borrow is the right call. Acquisition premiums often destroy value when the thing you're buying is hard to detach from the original context.

How does build borrow or buy connect to the Ansoff Matrix? The Ansoff Matrix maps growth direction (existing vs new markets, existing vs new products). Build, borrow, or buy answers how to get there. Market penetration (existing market, existing product) typically favors build. Market development and diversification favor borrow or buy, because the risk of entering unfamiliar territory is too high to rely on internal development alone.

What role does the VRIO framework play in this decision? The VRIO framework (Valuable, Rare, Inimitable, Organized) helps you assess whether a capability, if built internally, would create durable competitive advantage. If the capability meets all four criteria, it's worth building even if it's slow. If it's only Valuable but not Rare or Inimitable (a commodity capability), borrow or buy is usually more efficient.

Can you use more than one path at the same time? Yes, and leading companies often do. A firm might build its core technology capability, borrow distribution through a channel partner, and buy a small team for a specific market entry, all simultaneously. The framework applies per capability gap, not per company.

Related reading

• Strategic Alliances covers how to structure borrow relationships for durable advantage.
• McKinsey Growth Pyramid frames the three levels of growth initiatives and where each path tends to apply.
• Hoshin Kanri shows how strategic intent cascades into operational plans, which determines build feasibility.
• Porter's Diamond Model examines how national and industry factors shape which capability-building paths are even available to firms in a given context.

---

The build, borrow, or buy decision is one of the most consequential choices leadership teams make. It determines not just whether you close a capability gap but whether you do so in a way that strengthens your competitive position or creates new vulnerabilities. The companies that get this right aren't always the ones with the most capital or the best technology. They're the ones who ask the right questions about fit, timing, and integration before committing to a path.