Make vs. Buy vs. Partner: The Most Important Capability Decision You Will Make
Not every capability should be built internally. The make-buy-partner decision is the most consequential capability sourcing choice — and most organizations make it without a structured framework.
The make-buy-partner decision is one of the most consequential strategic choices an organization makes — and it is one that business architecture is uniquely positioned to inform. For every capability in the capability model, the organization must decide: should we build this capability internally (make), acquire it through a purchase or license (buy), or access it through a strategic partnership (partner)? The decision is not purely financial — it involves strategic considerations (is this capability a source of competitive advantage?), operational considerations (do we have the talent and resources to build it?), and risk considerations (what happens if we depend on an external provider?). A business architecture framework for make-buy-partner decisions provides a structured way to make these choices consistently and transparently across the capability portfolio. This framework becomes especially critical during digital transformation initiatives, where organizations must rapidly acquire new capabilities while maintaining focus on their core differentiators. Without a structured approach, companies either over-invest in non-strategic capabilities or inadvertently outsource their competitive advantages.
Make (Build Internally)
Developing capabilities internally using your own talent, resources, and infrastructure over an extended timeframe.
Best for
- Core differentiating capabilities that define competitive advantage
- Capabilities requiring deep integration with proprietary systems
- Long-term strategic capabilities with high utilization rates
Buy/Partner (Source Externally)
Accessing capabilities through external providers via licensing, partnerships, or acquisitions rather than internal development.
Best for
- Commodity capabilities that don't differentiate your business
- Specialized capabilities requiring expertise you lack internally
- Capabilities needed immediately with no time for internal development
Make (Build Internally) vs. Buy/Partner (Source Externally): Side-by-Side
| Dimension | Make (Build Internally) | Buy/Partner (Source Externally) | Insight |
|---|---|---|---|
| Strategic Control | Full control over capability design, roadmap, and evolution. You decide priorities, features, and integration points based solely on your business needs. | Limited control — dependent on vendor roadmap and partner priorities. Your requirements compete with other customers' needs for development attention. | Build for strategic capabilities; buy/partner for supporting capabilities |
| Time to Market | Extended development cycles typically requiring 12-36 months for mature capabilities. Includes hiring, training, development, and testing phases. | Rapid deployment — weeks to months rather than years. Existing solutions can be implemented and configured quickly. | Buy/partner when speed is critical; build when you can afford the timeline |
| Total Cost of Ownership | High upfront investment in talent, infrastructure, and development. Lower ongoing costs if capability is heavily utilized over multiple years. | Lower initial costs but ongoing licensing fees, partnership revenue shares, or acquisition premiums that may exceed internal build costs over time. | Build for high-volume, long-term use; buy/partner for lower-volume needs |
| Talent Requirements | Requires recruiting specialized talent, developing internal expertise, and retaining key personnel. Creates ongoing HR and management overhead. | Accesses external expertise without recruitment challenges. Provider manages talent acquisition, development, and retention. | Buy/partner when talent is scarce or expensive; build when talent is available |
| Innovation Velocity | High customization potential and continuous innovation aligned with your specific business needs. Can pivot quickly based on market feedback. | Innovation constrained by vendor priorities and partner capabilities. May lag market needs or include unnecessary features. | Build for rapidly evolving competitive requirements; buy/partner for stable needs |
| Risk Profile | Execution risk — can the team deliver on time and budget? Will the capability perform as expected in production? | Dependency risk — vendor failure, contract changes, or service discontinuation. Also integration and data security risks. | Choose based on risk tolerance and mitigation capabilities |
| Scalability | Scalability depends on your infrastructure investments and technical architecture decisions. May require significant additional investment. | Typically designed for multi-tenant scalability. Provider handles infrastructure scaling, but you pay for increased usage. | Buy/partner for unpredictable scaling needs; build when scale requirements are well-understood |
| Data and IP Protection | Complete control over proprietary data and intellectual property. No risk of competitive information leakage. | Potential exposure of sensitive data and business processes to external parties. Requires careful contract and security management. | Build for highly sensitive or proprietary capabilities; buy/partner with strong security controls |
| Exit Flexibility | Low flexibility — internal capabilities represent sunk costs and may be difficult to repurpose if strategy changes. | Higher flexibility for partnerships and licenses. Acquisitions are harder to exit but partnerships can be terminated more easily. | Buy/partner when strategic direction is uncertain; build for stable, long-term needs |
When to Use Each
- Core Revenue-Generating Capability
- Build internally. Capabilities that directly generate revenue and differentiate your offering should be built internally to maintain competitive advantage and maximize control over the customer experience.
- Compliance and Regulatory Requirements
- Buy or partner. Regulatory compliance is typically commodity functionality that doesn't differentiate your business. External providers often have deeper expertise and can spread compliance costs across multiple clients.
- Emerging Technology with Uncertain ROI
- Partner first, then evaluate building. Partner to experiment and learn about new technologies before making significant internal investments. Build only after proving business value and understanding requirements.
- Critical Infrastructure Under Time Pressure
- Buy immediately, build selectively later. When facing urgent needs, buy or partner for immediate capability access, then evaluate building strategic components internally once immediate needs are met.
- Highly Specialized Niche Capability
- Partner with specialist providers. When capabilities require deep specialized knowledge that's not core to your business, partnering with expert providers is more cost-effective than building internal expertise.
- High-Volume Transactional Processing
- Build if truly differentiating, otherwise buy. High-volume capabilities benefit from economies of scale. Build only if the processing itself creates competitive advantage; otherwise, leverage external providers' scale economics.
How They Work Together
Yes — and most organizations use all three sourcing strategies simultaneously across their capability portfolio. The key is to be intentional about which strategy applies to which capability — and to review the decisions regularly as the strategic importance of capabilities evolves. A capability that was once a source of competitive differentiation (and therefore built internally) may become a commodity as the market matures (and therefore become a candidate for outsourcing). Conversely, a capability that was initially accessed through a partnership may become strategically critical (and therefore worth building internally). The capability sourcing strategy should be reviewed as part of the annual strategic planning cycle.
The Common Mistake
The most common mistake is applying a single sourcing strategy to all capabilities — either building everything internally (the 'not invented here' syndrome) or outsourcing everything (the 'asset-light' strategy taken too far). Organizations that build everything internally end up with high costs and slow time-to-market for commodity capabilities. Organizations that outsource everything end up with no proprietary capabilities and no sustainable competitive advantage. The make-buy-partner framework provides the structure to make nuanced, capability-specific sourcing decisions rather than applying a blanket policy.
The Strategic Framework for Capability Sourcing
Making effective make-buy-partner decisions requires a systematic evaluation framework that goes beyond simple cost analysis.
The most effective organizations use a structured decision matrix that evaluates each capability across multiple dimensions simultaneously. This framework starts with strategic importance — is this capability a source of competitive differentiation or a commodity requirement? From there, it considers operational factors like required speed-to-market, available internal talent, and integration complexity. Financial analysis includes not just upfront costs but total cost of ownership over multiple years, including hidden costs like management overhead for partnerships or scaling costs for internal builds. Risk assessment evaluates both execution risk (can we successfully build this?) and dependency risk (what happens if our external provider fails?). The framework culminates in a capability sourcing portfolio that balances strategic control with operational efficiency.
Implementation Patterns and Hybrid Approaches
Real-world capability sourcing rarely follows pure make-or-buy patterns. Most successful implementations use hybrid approaches that evolve over time.
Many organizations start with external providers to quickly access new capabilities, then selectively build internal alternatives for the most strategic components. This 'partner-to-learn' approach reduces initial risk while preserving the option to internalize critical capabilities later. Another common pattern is the 'build-the-core, buy-the-edge' strategy, where organizations maintain internal control over core functionality while partnering for peripheral features. Some companies use strategic partnerships as extended development teams, maintaining design control while accessing external development capacity. The key is designing partnership agreements that preserve future optionality — including rights to internalize capabilities, access to underlying data and algorithms, and clear intellectual property ownership.
Review Capability Sourcing Annually: Strategic importance of capabilities changes over time. What's differentiating today may become commodity tomorrow, and vice versa. Schedule annual reviews of your capability sourcing decisions as part of strategic planning.
Measuring Success and Course Correction
Capability sourcing decisions should be measured and adjusted based on actual performance rather than initial projections.
Successful organizations establish clear success metrics before making sourcing decisions, then track performance rigorously. For internal builds, key metrics include development timeline adherence, budget performance, capability adoption rates, and business impact measurement. For external sourcing, focus on service level achievement, cost per transaction, innovation velocity, and strategic alignment with provider roadmap. Most importantly, measure optionality preservation — are you maintaining the ability to change sourcing strategies as business needs evolve? Regular capability portfolio reviews should evaluate whether sourcing decisions are delivering expected value and whether changing business conditions warrant different approaches. Don't hesitate to change course when evidence suggests a different sourcing strategy would better serve business objectives.
Bottom Line
Build the capabilities that differentiate you. Buy or partner for the capabilities that don't. Review the decision regularly as the strategic landscape evolves. And never outsource a capability that is genuinely differentiating — no matter how attractive the short-term cost savings appear.