Build-or-Buy Capability Test
Test whether acquisition is the only credible path to a strategic capability
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 88%
The Build-or-Buy Capability Test evaluates whether a company can realistically create a strategic capability internally or needs an acquisition to overcome talent, time, and organizational barriers. It begins by defining the desired capability rather than treating the target's current code as the final product. Leaders then compare access to specialized people, development time, supporting acquisitions, and the likelihood that either path will receive sustained executive commitment. Siri illustrates why the acquired company and the eventual capability may differ: Apple reportedly replaced the original technology, lost the founders, hired new experts, and bought additional companies, yet the initial deal helped establish an enduring AI and voice organization. The output is a capability roadmap, not merely a purchase-price comparison.
Origin
Extracted from The Shawn Ryan Show
Core principles
- 01Compare realistic capabilities, not theoretical implementation costs
- 02Treat scarce talent and organizational momentum as strategic assets
- 03Account for the acquisitions and hiring still required after the initial deal
- 04Distinguish the acquired assets from the capability ultimately created
How to run it
- 1
Define the Required Capability
Describe the strategic outcome the company must achieve without anchoring on the target's existing product or brand. Specify the platform, talent, and operational abilities required.
Pro tip Frame the requirement in terms of what the company must be able to do repeatedly.
Watch out Do not assume the target's current implementation is the capability itself.
- 2
Test the Internal Talent Path
Determine whether the company can attract and organize the specialists needed to build the capability. Include gaps in technical credibility and domain leadership.
Pro tip Ask whether the best candidates would join before the company demonstrates serious commitment.
Watch out A theoretical ability to hire is not evidence that the necessary team can actually be assembled.
- 3
Decompose the Acquisition
Separate what the deal provides into people, technology, product, brand, and organizational momentum. Identify which elements are durable and which may disappear after closing.
Pro tip Model founder departures and discarded code as plausible outcomes.
Watch out Do not label the whole deal a technology acquisition simply because the target markets technology.
- 4
Map the Post-Deal Build
Estimate the additional hiring, integration, research, and follow-on acquisitions needed to reach the strategic outcome. Treat the initial acquisition as a possible starting point rather than a complete solution.
Pro tip Include the cost and time required to replace licensed or obsolete components.
Watch out Ignoring the post-acquisition roadmap understates the true cost of buying.
- 5
Compare Time and Commitment
Compare build and buy paths on speed, talent access, strategic focus, and probability of sustained execution. Choose the path with the stronger realistic route to capability.
Pro tip Consider whether spending acquisition-level capital will force the organization to take the initiative seriously.
Watch out Do not decide from headline price alone.
In the wild
Apple could compare building a voice-assistant capability from scratch with acquiring Siri as an initial product and organizational catalyst. The deal did not eliminate the need for new hires, internal speech technology, or later acquisitions such as Topsy, but it gave Apple a product commitment around which to build the broader capability.
→ Apple entered voice assistance earlier and created an AI and search organization despite replacing much of what it originally acquired.
A manufacturer needs machine-learning maintenance capabilities but cannot recruit an experienced industrial AI team. It assesses a specialist acquisition by separating its engineers, models, customer workflows, and brand, then budgets for integration and additional sensor expertise before comparing that route with internal hiring.
→ The company chooses the path with the highest probability of establishing the complete capability on schedule.
Common mistakes
Comparing Price With Coding Cost
A narrow financial comparison ignores scarce talent, execution time, organizational credibility, and the supporting work required after either decision.
Assuming the Acquired Assets Will Persist
Founders can leave and code can become obsolete, so leaders must identify which benefits remain valuable under those conditions.
Treating the First Deal as the Finish Line
A strategic acquisition may only establish the initial product and commitment; the complete capability can require years of further investment.
Is it for you?
Best for
It is best for leaders evaluating acquisitions in technically specialized fields where talent, urgency, and organizational commitment matter.
Not ideal for
It is not ideal for commodity capabilities that can be bought from vendors or assembled internally with readily available talent.
From the transcript
“in kind of thinking about any acquisition, you can use the framework of builder buy.”
“would they have been able to hire the really top people that they would have needed to in machine learning, AI, speech recognition to make…”
“There's no Siri people. There's no Siri technology. There's merely a Siri brand and basically what that original product did there”
From the episode
Siri