| name | platform-strategist |
| type | domain |
| family | executive |
| rigor | standard |
| description | Use when analyzing platform business models, network effects, or aggregation dynamics. |
| keywords | platform, business-model, network-effects, aggregation, strategy, architecture |
| compatibility | Claude Code and compatible agent products |
| requires | [] |
| enhances | ["strategy-clarity","market-context","operational-excellence"] |
| sources_pdf | ["Zero to One (Thiel)","High Growth Handbook (Gil)","Working Backwards (Bryar)","Working in Public (Eghbal)"] |
| sources_web | ["Stratechery: The Bill Gates Line","Stratechery: Shopify & Platforms","Stratechery: The Amazon Tax"] |
Overview
Platform strategy is the art of building foundational systems that facilitate value creation by third parties. This skill distinguishes between "Aggregators" (who own the user relationship) and "Platforms" (who empower an ecosystem), focusing on network effects, economies of scale, and the externalization of internal "primitives" as a growth engine.
Guiding Principles
Principle 1: The Bill Gates Line (Source: Stratechery, "The Bill Gates Line")
A true platform's value is defined by the economic value created by third parties exceeding the value of the platform itself. If you capture all the value, you aren't a platform; you're a vertical silo.
Principle 2: Empower, Don't Intermediate (Source: Stratechery, "Shopify & Platforms")
A platform wins by enabling its suppliers to differentiate themselves and acquire their own customers. Aggregators commoditize supply; Platforms empower supply. (Example: Shopify vs. Amazon Marketplace).
Principle 3: Externalize the Primitives (Source: Stratechery, "The Amazon Tax")
Identify the fundamental "building blocks" of your business (storage, compute, logistics, payments). Design them as modular APIs (primitives) so they can be used internally and then externalized to the market. (Source: Bryar, Working Backwards).
Principle 4: Network Effects & The Niche (Source: Thiel, Zero to One)
Platform value scales with network density. To avoid the "chicken and egg" problem, start by monopolizing a small, high-intensity niche (e.g., Harvard for Facebook) before expanding to the broader market.
Principle 5: The Marketplace Subsidy (Source: Gil, High Growth Handbook)
In a two-sided platform, one side is usually harder to acquire. Identify which side (supply or demand) is the "limiting step" and subsidize them to create the initial liquidity required for network effects to take hold.
When to Use This Skill
- When evaluating whether a business model is structurally a "Platform" or an "Aggregator."
- When designing APIs or developer ecosystems.
- When planning the expansion from a product-centric business to a platform-centric one.
- When identifying potential "Network Effects" in a new category.
When NOT to Use This Skill
- For pure B2B service businesses that don't scale through third-party value creation.
- For niche products where network effects are non-existent or irrelevant to the value prop.
Core Process
Step 1: Identify the Ecosystem Role
Determine if the strategic goal is to be a Platform or an Aggregator. (Source: Stratechery, "The Bill Gates Line")
- The Aggregator Path: Own the user experience, commoditize supply, capture high rent.