From flywheel-pm
Segmentation, differentiation, and strategic thinking frameworks. Use when building product strategy, analyzing competition, or making strategic bets.
npx claudepluginhub abhitsian/compound-pm-marketplace --plugin flywheel-pmThis skill uses the workspace's default tool permissions.
Strategy is a function of segmentation and differentiation. This skill provides the frameworks for both, plus the connective tissue that turns analysis into a strategy document that actually drives decisions.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Strategy is a function of segmentation and differentiation. This skill provides the frameworks for both, plus the connective tissue that turns analysis into a strategy document that actually drives decisions.
Based on Shreyas Doshi's strategy framework and Hamilton Helmer's 7 Powers.
Strategy is about making choices that are hard to reverse and create compounding advantages.
Good strategy has three properties:
Segment by what users NEED and DO, not who they ARE.
Good segmentation dimensions (in priority order):
Bad segmentation dimensions:
Every segment must pass ALL five:
| Test | Question |
|---|---|
| Consistent needs | Do members share similar needs distinct from other segments? |
| Product-specific | Is this relevant to YOUR product, not just the market? |
| Targetable | Can you predictably find and reach these people? |
| Prioritizable | Can you rank segments meaningfully? |
| Winnable | Can you realistically serve them better than alternatives? |
| Dimension | What It Measures |
|---|---|
| Reach | How large is the segment? |
| Underserved degree | How poorly served by current alternatives? |
| Differentiation potential | Can you build something meaningfully better for them? |
| Ease of targeting | Can you find and reach them efficiently? |
| Power | Definition | How to Build It |
|---|---|---|
| Scale Economies | Unit cost declines with volume | Invest in infrastructure that amortizes |
| Network Effects | Value increases with more users | Build features where more users = better product |
| Switching Costs | Users face cost to leave | Make your product hold important user data, integrations, workflows |
| Branding | Higher perceived value for your brand | Consistent quality, emotional connection, community |
| Cornered Resource | Exclusive access to valuable input | Proprietary data, key hires, exclusive partnerships |
| Counter-Positioning | New model incumbents can't adopt | Build something that would cannibalize competitors' core business |
| Process Power | Organization capabilities that can't be copied | Deep domain expertise, operational excellence, culture |
| Type | What It Means | Priority |
|---|---|---|
| Differentiator | Users choose us BECAUSE of this | Invest heavily |
| MMR | Users reject us WITHOUT this | Build to parity |
| Neutralizer | Removes a reason to NOT choose us | Build to "good enough" |
"[Product] wins by [differentiation] for [segments] against [alternatives]."
Must be: specific, choosy, actionable, falsifiable.
The most important part of strategy:
| Category | Description |
|---|---|
| Trade-offs | "We choose X over Y because..." |
| Lower priority | "We acknowledge Z matters but won't invest because..." |
| Table stakes | "We'll maintain parity on [features] but won't differentiate here" |
| Below table stakes | "Competitors do [X] and we deliberately don't because..." |
| Reassessment triggers | "We'd reprioritize if [specific market change]" |
Before finalizing any strategy, pass these 5 tests: