Skip to main content
ClaudeWave
Skill1k estrellas del repoactualizado 4mo ago

platform-strategy

The platform-strategy skill guides users through designing and executing platform business models by applying frameworks from 24 product leaders. Use it when building marketplaces, ecosystems, API platforms, or developer platforms, or when analyzing network effects, platform lifecycle stages, governance structures, and trust mechanisms to establish defensible competitive advantages in multi-sided environments.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/platform-strategy && cp -r /tmp/platform-strategy/skills/platform-strategy ~/.claude/skills/platform-strategy
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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:

1. **Understand the platform type** - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform
2. **Identify the network effects** - Help them understand which sides of the platform create value for each other
3. **Assess the lifecycle stage** - Determine if they're in the moat-building, opening, or closing phase
4. **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
Brian Balfour: "The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization." Platforms follow a predictable lifecycle from market consensus to closing for monetization.

### Reduce cognitive load through clear interfaces
Jeremy Henrickson: "The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem." A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.

### Find compounding dynamics
Alex Komoroske: "Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate." Platform success comes from identifying "gardening" opportunities - projects with inherent compounding loops that grow on their own.

### Build systems, not features
Aparna Chennapragada: "The way I think about how we are positioned and what we do with GitHub is... So it's a system, not just a product or a set of features." Long-term platform defensibility comes from building a comprehensive system and repository of context rather than just a single feature or tool.

### Invest incrementally based on signals
Alex Komoroske: "Invest incrementally in ecosystem projects only as you receive signals of utility and adoption." Don't bet big on platform initiatives until you have evidence of demand and usage patterns.

## Questions to Help Users

- "Which side of your platform is harder to acquire? That's probably where you should focus first."
- "What value does your platform provide to a user with zero other participants?"
- "What stage of the platform lifecycle are you in - building the moat, opening, or closing?"
- "How will you prevent the supply side from being commoditized or going around you?"
- "What compounding dynamics exist in your platform that accelerate as it grows?"
- "What governance rules will you enforce, and how will you handle disputes?"

## Common Mistakes to Flag

- **Building platforms in a vacuum** - Not iterating based on actual product and developer needs
- **Treating all participants equally** - Not recognizing that power users and high-quality suppliers deserve different treatment
- **Skipping the moat phase** - Opening a platform before establishing defensibility
- **Feature thinking over systems thinking** - Building point solutions instead of comprehensive systems with context
- **Over-investing before signals** - Betting big on platform initiatives without evidence of utility and adoption

## Deep Dive

For all 28 insights from 24 guests, see `references/guest-insights.md`

## Related Skills

- platform-infrastructure
- retention-engagement
- pricing-strategy
ai-evalsSkill

Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.

ai-product-strategySkill

Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.

analyzing-user-feedbackSkill

Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.

behavioral-product-designSkill

Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.

brand-storytellingSkill

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.

building-a-promotion-caseSkill

Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.

building-sales-teamSkill

Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.

building-team-cultureSkill

Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.