Build a Network, Not a Moat
Defend a market by enabling an ecosystem to succeed with you
- Difficulty
- Expert
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 96%
Build a Network, Not a Moat reframes competitive defense as ecosystem enablement. A company enters or creates a market, provides a stable technology or service platform, and helps developers, partners, customers, and complementary suppliers succeed around it. Compatibility compounds participation because work performed for one generation remains useful across later products. As participants create applications and serve the final market, their investments attract additional users and contributors. The resulting network becomes difficult to reproduce, but defensibility is an outcome rather than the operating objective. This outward orientation prevents the company from concentrating solely on barriers around its existing business. The practical question is not how to keep competitors out, but how to make more participants prosper by building, distributing, or operating through the platform.
Origin
Jensen Huang contrasted moat-building with Nvidia's preferred model of enabling a network of developers, customers, and ecosystem partners to share in the success of an emerging market.
Core principles
- 01Create value for ecosystem participants, not only for the platform owner
- 02Treat compatibility as a long-term commitment
- 03Help developers and customers reach the final market
- 04Let accumulated relationships and applications strengthen the platform
- 05Focus outward on shared success rather than inward on defensive barriers
How to run it
- 1
Define the shared destination
Specify the end market or customer outcome that the ecosystem will collectively serve. Clarify how the platform participates without capturing every layer.
Pro tip Choose an opportunity large enough to support many successful participants.
Watch out A platform with no meaningful external value is merely an internal product.
- 2
Recruit essential participants
Identify developers, suppliers, distributors, service providers, and customers whose contributions make the market more useful. Understand what each needs to justify investing.
Pro tip Recruit participants capable of creating uses the platform company would never invent itself.
Watch out Do not assume access to your technology is sufficient incentive.
- 3
Provide a durable foundation
Offer stable interfaces, compatible architecture, tools, documentation, and support. Protect participants from unnecessary resets that strand their investment.
Pro tip Make backward compatibility an explicit strategic constraint.
Watch out Frequent incompatible changes destroy accumulated network value.
- 4
Enable participant success
Help ecosystem members build products, reach users, improve performance, and earn returns. Treat their outcomes as leading indicators of platform health.
Pro tip Invest early in developer relations and reference implementations.
Watch out Extracting value before participants prosper can collapse the network.
- 5
Compound the network
Use successful applications and customers to attract additional participants. Expand capabilities while preserving the common foundation.
Pro tip Publicize repeatable participant successes rather than only platform specifications.
Watch out Growth in registrations or integrations does not matter if participants remain inactive.
In the wild
Nvidia hired developer-relations talent early, pursued a unified architecture, and later ensured that its accelerators remained architecturally compatible with CUDA. Developers could build across a growing installed base instead of targeting disconnected products.
→ Applications, developers, customers, and compatible hardware accumulated into a platform network that reinforced Nvidia's position.
A construction platform publishes stable APIs, supports specialist estimating and compliance vendors, and helps those partners reach contractors. Customers gain a broader solution while partners gain distribution and recurring revenue.
→ The platform becomes more valuable and harder to replace as complementary products and shared customers accumulate.
Common mistakes
Building barriers before value
Defensive restrictions cannot substitute for an ecosystem in which participants receive meaningful benefits.
Breaking compatibility casually
Stranding developer and partner investments resets the network and teaches participants not to trust the platform.
Capturing every layer
A platform that competes away all participant economics prevents complementary businesses from forming.
Is it for you?
Best for
It is best for products whose value increases through developers, partners, compatible components, or shared customers.
Not ideal for
It is not ideal for isolated products with little opportunity for complementary innovation or recurring ecosystem participation.
From the transcript
“I tend to like thinking about things in the context of building a network and that network is about enabling other people to enjoy the…”
“as many good ideas as we have um you don't have all the world's good ideas and and the benefit of having developers is you…”
From the episode
NVIDIA CEO Jensen Huang
Jensen Huang