Strategic Vertical Integration Rule
Own the components that create durable differentiation; source everything else.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
The rule begins by decomposing a product into the technologies and supplier relationships that make it work. Most components can remain modular and externally sourced, but a company should consider internal ownership when a component materially determines customer experience, security, performance, or long-term strategic freedom. Ownership may come through internal development or acquisition. Apple applied this logic selectively: it continued using many suppliers while acquiring semiconductor and fingerprint-sensor capabilities that could distinguish its devices. The mechanism is not integration for its own sake. It is selective control of the few layers where coordinated design produces an advantage competitors cannot easily reproduce. The rule also includes a timing constraint: startups should generally exploit existing infrastructure, while scaled firms can internalize critical layers once supplier dependence becomes strategically limiting.
Origin
Extracted from The Shawn Ryan Show
Core principles
- 01Use external suppliers for components that do not create strategic differentiation.
- 02Bring strategically important technologies under direct organizational control.
- 03Evaluate integrated components by their contribution to the whole customer experience.
- 04Internal ownership matters most when security, performance, or coordination depends on tight integration.
- 05Delay deep vertical integration until the company has sufficient scale and resources.
How to run it
- 1
Map the product stack
List the technologies, services, and suppliers required to deliver the complete customer experience. Note where the company currently lacks direct control.
Pro tip Map dependencies from the customer's experience backward rather than from the organization chart outward.
- 2
Locate true differentiators
Identify which layers materially affect performance, privacy, security, convenience, or another purchasing decision. Treat standard components as commodities unless evidence shows otherwise.
Watch out Do not label every important dependency as strategically differentiating.
- 3
Measure the control gap
Determine whether external ownership prevents the desired product quality, speed, integration, or strategic flexibility. Include the risk that a supplier may support competitors or be acquired by one.
Pro tip Model what happens if the component becomes unavailable to you tomorrow.
- 4
Choose build, buy, or source
Compare internal development, acquisition, and continued supplier use on time, cost, talent, maturity, and competitive access. Acquisition is strongest when it provides scarce expertise or proven technology faster than internal development.
Watch out Do not acquire a company merely because its technology is adjacent to your product.
- 5
Integrate around an outcome
Connect the capability to a specific customer-facing advantage rather than preserving it as an isolated technical asset. Coordinate the relevant hardware, software, and service teams.
Pro tip Define the promised experience before reorganizing the acquired team.
- 6
Extend and reassess
Reuse the capability across suitable products, then test whether it still creates meaningful differentiation as the market evolves. A sustaining advantage in one wave may not position the company for the next.
Watch out Past financial success does not prove that the capability will remain strategic.
In the wild
Apple acquired PA Semi's low-power chip expertise and AuthenTec's fingerprint technology. It then integrated Touch ID with an on-device secure enclave, allowing authentication data to remain isolated from servers, memory, and the main processing path while improving convenience for unlocking and payments.
→ Apple gained a tightly integrated security and product experience that fragmented competitors had difficulty matching.
A platform discovers that a third-party database prevents it from meeting latency and data-isolation requirements for its most valuable enterprise customers. After comparing continued sourcing, internal development, and acquisition, it acquires a specialist team and integrates the technology around a measurable reliability target.
→ The company turns an infrastructure constraint into a customer-facing performance advantage.
Common mistakes
Integrating every layer
Vertical integration consumes capital and management attention. Own only the layers where control creates a meaningful strategic or customer advantage.
Ignoring company stage
An early startup can exhaust itself rebuilding infrastructure that mature suppliers already provide. Deep integration becomes more practical after the company develops scale and resources.
Confusing past value with future relevance
A capability may sustain a mature product without positioning the company for the next technology wave. Reassess the strategic thesis as markets change.
Is it for you?
Best for
It is best for scaled technology companies whose flagship products depend on tightly coordinated hardware, software, security, or services.
Not ideal for
It is not ideal for early startups that lack the capital, talent, or scale to outperform established component suppliers.
From the transcript
“for the things that they think can can really differentiate them and really uh provide a strategic advantage for the long term they they bring…”
“as a startup, you want to embrace standing on the shoulders of giants, but at some point, if you really want to compete with the…”
“the ability of Apple to integrate these two products creates an advantage uh that other manufacturers don't have.”
From the episode
P.A. Semi + AuthenTec