platform-strategy
Framework-based guidance for designing and executing platform business strategies across marketplaces, ecosystems, and developer platforms.
- Covers platform lifecycle stages (moat-building, opening, closing) and helps identify which network effects and participant sides drive value
- Emphasizes treating platforms as products with dedicated management, reducing cognitive load through clear interfaces, and building comprehensive systems rather than isolated features
- Includes governance and trust design patterns, plus guidance on incremental investment based on adoption signals rather than upfront bets
- Flags common pitfalls: building in isolation, over-investing before validation, skipping the moat phase, and feature-first thinking instead of systems thinking
Platform Strategy
Help the user design and execute platform business strategies using frameworks from 24 product leaders who have built and scaled platforms.
How to Help
When the user asks for help with platform strategy:
- Understand the platform type - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform
- Identify the network effects - Help them understand which sides of the platform create value for each other
- Assess the lifecycle stage - Determine if they're in the moat-building, opening, or closing phase
- Design for trust and governance - Help them think through the rules that will govern platform participants
Core Principles
Treat internal platforms as products
Camille Fournier: "Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?" Internal platforms need dedicated product management and focus on user (developer) productivity, not just technical elegance.
Understand the four-stage platform lifecycle
More from refoundai/lenny-skills
personal-productivity
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
4.6Kcompetitive-analysis
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
1.9Kbrand-storytelling
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
1.8Kwriting-prds
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
1.8Kcontent-marketing
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
1.7Kvibe-coding
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
1.7K