Open-Source Coordination Model
Lower integration costs by giving products shared open interfaces
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 96%
Mullenweg adapts Berkshire Hathaway's decentralized portfolio logic to software. The portfolio seeks strong products and leaders, but open source lowers the coordination cost between them. A product such as WooCommerce can build on WordPress through public code, APIs, and a plugin framework without arranging meetings with the WordPress team or depending on private permission. That makes autonomy more practical while preserving opportunities for shared distribution and integration. The model distinguishes products that run directly on the common platform from those that are philosophically adjacent, such as an encrypted journaling app. The decision test is not whether every acquisition can be tightly combined; it is whether openness removes avoidable dependency, protects users from a platform rug pull, and lets capable product teams operate with limited central coordination.
Origin
Mullenweg explains how Automattic uses WordPress and open source to pursue a digital version of Berkshire Hathaway with lower coordination costs.
Core principles
- 01Shared open interfaces replace repeated coordination meetings
- 02Autonomy improves when products can integrate without permission
- 03Open platforms prevent a single owner from pulling the rug
- 04Acquisitions can share philosophy or distribution without forced technical coupling
How to run it
- 1
Define the portfolio thesis
State the shared user benefit or philosophy that makes otherwise distinct products belong together.
Pro tip Mullenweg uses an open web, user freedom, and liberty as the durable umbrella.
Watch out A vague conglomerate label does not explain why the products belong in one portfolio.
- 2
Map common infrastructure
Identify the open code, APIs, standards, extension system, or distribution that products can share.
Pro tip Prefer interfaces teams can use without scheduling a meeting.
Watch out A proprietary internal dependency can recreate the coordination burden.
- 3
Preserve local autonomy
Give strong product leaders room to operate while the common platform handles routine interoperability.
Pro tip Centralize only what genuinely benefits from central control.
Watch out Forcing every product into the same operating process can erase the advantage.
- 4
Classify the relationship
Decide whether a product is built on the core platform, gains distribution from it, or is only philosophically adjacent.
Pro tip Do not invent a technical integration where philosophical alignment is sufficient.
Watch out Calling every acquisition synergistic hides real differences in fit.
- 5
Audit user freedom
Verify that users can inspect, extend, move, or continue using the product without depending entirely on the portfolio owner.
Pro tip Treat non-revocable user rights as part of the product architecture.
Watch out An API whose owner can revoke access at any time does not provide the same protection.
In the wild
WooCommerce can build on WordPress through open code, APIs, and the plugin framework. Its team does not need a meeting with the WordPress developers before using the platform, reducing the recurring coordination normally required between company divisions.
→ A portfolio product integrates with the common platform while retaining operating autonomy.
Day One does not share technology with WordPress or Tumblr, but its encrypted local journaling supports the broader philosophy of user-controlled publishing. Automattic can therefore treat it as adjacent without forcing a false platform integration.
→ The portfolio preserves a coherent philosophy without requiring every product to use identical technology.
Common mistakes
Forcing centralized integration
Mandating coordination between every division recreates the costs the open platform is meant to remove.
Building on revocable access
A proprietary platform can change its terms or remove access after a dependent product has committed to it.
Is it for you?
Best for
Software portfolios that can share an open platform, APIs, standards, distribution, or a durable user-rights philosophy.
Not ideal for
Businesses whose safety, regulation, or physical dependencies require tightly centralized control and coordinated operation.
From the transcript
“What we do with a digital version of that is we lower coordination costs between the different products by open source.”
“It doesn't need a meeting, doesn't need to talk, doesn't even to know the people developing WordPress.”
“There's open APIs, open source, there's a plugin framework, et cetera.”
From the episode
#713: Matt Mullenweg — The Art of Crafting a Sabbatical, Tips for Defending Against Hackers, Leveraging Open Source, Thriving in an AI World, and Tips for Life’s Darkest Hours
Matt Mullenweg