Aligned Licensing Flywheel
Combine licensing, services, and royalties to share customers’ upside
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 98%
The Aligned Licensing Flywheel separates foundational technology from the products built with it. First, the supplier licenses a reusable core, creating immediate revenue without manufacturing every finished unit. Second, its engineers work with customers to adapt that core to specific products, generating service revenue and improving implementation quality. Third, the supplier receives a small royalty whenever a customer ships a unit. That final component aligns both parties around successful products and increasing volume. Each implementation expands technical knowledge, ecosystem support, and compatibility, which makes the core more attractive to subsequent customers. The model can therefore compound across competing manufacturers while the supplier remains a neutral platform. Its strength depends on protecting the core intellectual property, maintaining excellent engineering talent, and ensuring that customers retain enough design flexibility to create differentiated products.
Origin
ARM CEO Robin Saxby developed the model after the Apple Newton failed to generate enough demand. ARM broadened beyond Apple by licensing its processor technology, embedding engineers with partners, and collecting royalties on shipped devices.
Core principles
- 01Monetize reusable intellectual property without manufacturing the final product
- 02Align revenue with customer adoption and unit growth
- 03Use embedded collaboration to make the licensed technology fit each use case
- 04Preserve customer flexibility rather than forcing a standardized finished product
- 05Build ecosystem dependence through sustained technical excellence
How to run it
- 1
Isolate the reusable core
Define the smallest defensible technology layer that delivers value across many products. Separate it from customer-specific design and manufacturing work.
Pro tip Choose a layer that customers benefit from standardizing but still want freedom to customize around.
Watch out Licensing an undifferentiated component gives customers little reason to keep paying.
- 2
License access upfront
Charge customers for the right to use the core technology. Use the agreement to define permitted implementations, support, and intellectual-property boundaries.
Pro tip Make adoption economically attractive compared with developing and maintaining a replacement internally.
Watch out Overpricing initial access can prevent the ecosystem from forming.
- 3
Embed with customer teams
Provide paid engineering collaboration that adapts the core to each customer’s product and constraints. Treat implementation success as part of the offering rather than an afterthought.
Pro tip Capture reusable technical lessons without exposing one customer’s confidential designs to another.
Watch out Unbounded customization can turn a scalable licensing company into a low-margin consultancy.
- 4
Share shipment upside
Collect a small royalty on each unit that includes the technology. This creates recurring revenue while keeping both parties focused on successful product launches and volume.
Pro tip Keep the royalty small enough that customers still benefit strongly from scale.
Watch out Use auditable definitions and reporting rules or unit-based revenue will be difficult to enforce.
- 5
Compound the ecosystem
Reinvest licensing and royalty income into the core technology, developer tools, and partner support. More successful implementations increase compatibility, trust, and switching costs.
Pro tip Remain neutral among competing customers so the ecosystem can expand broadly.
Watch out Favoring one downstream competitor can undermine confidence across the entire platform.
In the wild
After Newton demand disappointed, ARM worked with Texas Instruments on a processor for Nokia’s 6110. ARM supplied the processor foundation while its partners produced and shipped the handset, allowing ARM to benefit as GSM phone adoption accelerated.
→ ARM gained a scalable route into mass-market mobile devices without becoming a handset or semiconductor manufacturer.
A computer-vision company licenses its inference engine to several equipment manufacturers, charges for integration support, and receives a small royalty for every deployed camera. Customers retain control over hardware design while the supplier improves its shared engine from lessons across implementations.
→ The supplier develops recurring revenue and ecosystem reach without manufacturing complete camera systems.
Common mistakes
Selling only engineering hours
Custom work without a reusable licensed core scales like consulting and fails to compound across customers.
Taking royalties without enabling success
A supplier that collects unit revenue but provides weak implementation support creates misaligned expectations rather than a true partnership.
Competing with platform customers
Moving aggressively into customers’ downstream markets can destroy the neutrality that makes a shared technology platform valuable.
Is it for you?
Best for
It is best for companies with defensible intellectual property that can become a common component across many customers and products.
Not ideal for
It is not ideal when implementations cannot be measured, the intellectual property is easy to replace, or customers require exclusive ownership.
From the transcript
“So ARM gets gets paid three times.”
“So, how about we take a small royalty on every device you ship that has our technology in it?”
“We want you to make the best products and ship the best devices, and we'll embed our technology and our teams with you.”
From the episode
ARM & SoftBank