product-strategy-frameworks

name	product-strategy-frameworks
description	Strategy definition, unit economics, monetization models, and roadmap sequencing frameworks. Use when defining product strategy, modeling business economics, or sequencing roadmap priorities.

Product Strategy Frameworks

Product strategy answers three questions: what to build, in what order, and how it creates value. This skill covers the core frameworks for defining strategy, modeling economics, and sequencing work.

When to Use This Skill

• Defining or refining the product strategy document
• Modeling unit economics to validate strategic choices
• Choosing a monetization model for a new product or segment
• Sequencing roadmap priorities across competing options
• Evaluating build vs. buy vs. partner decisions
• Communicating strategic rationale to stakeholders

Core Concepts

1. Strategy = Choice

A strategy that doesn't say no to things isn't a strategy — it's a wish list. Every strategy document should have an explicit "what we are NOT doing" section. If everything is a priority, nothing is.

2. Tie Features to Business Outcomes

Every feature, initiative, and investment should connect to a business metric. If you can't articulate what moves when you ship something, you don't understand why you're building it.

3. Sequence by Strategic Value, Not Just Effort

The temptation is to sequence by what's easiest. The right sequencing considers:

• What's the minimum viable capability to test the core hypothesis?
• What unlocks other things (prerequisite sequencing)?
• What's the cost of being wrong and having to undo?

Strategic Pillar Format

A product strategy is organized around 2–5 strategic pillars — the major themes that define where to invest.

# Product Strategy: [Product Name]

## Vision
[One sentence: what world does this product help create?]

## Strategic Pillars

### Pillar 1: [Name]
- **Bet:** [What we believe about the market/user/technology]
- **Initiatives:** [What we'll build to execute on this pillar]
- **Success metric:** [How we'll know this pillar is working]
- **Time horizon:** [When we expect to see results]

### Pillar 2: [Name]
[Same structure]

## What We Are NOT Doing
- [Explicit deprioritization 1]
- [Explicit deprioritization 2]

## Key Assumptions
- [Assumption 1 — and how we'll validate it]
- [Assumption 2 — and how we'll validate it]

## Risks
- [Risk 1 — and mitigation]
- [Risk 2 — and mitigation]

Unit Economics

Unit economics determine whether a business model works. For product strategy, the key metrics are:

SaaS / Subscription

Metric	Formula	Healthy Range
CAC — Customer Acquisition Cost	Total sales + marketing spend ÷ new customers acquired	Context-dependent
LTV — Lifetime Value	ARPU × Gross Margin % ÷ Churn Rate	LTV:CAC > 3:1
Payback Period	CAC ÷ (ARPU × Gross Margin %)	< 12 months (B2C), < 24 months (B2B)
Net Revenue Retention	(Starting MRR + Expansion − Contraction − Churn) ÷ Starting MRR	> 100% = growth from existing customers

Marketplace / Transaction

Metric	Formula	Notes
Take Rate	Revenue ÷ GMV	% of transaction value captured
GMV per Active User	GMV ÷ Active users	Supply-side and demand-side separate
Contribution Margin	Revenue − Variable COGS − Variable Fulfillment	Must be positive per transaction

Unit Economics Validation

Before committing to a strategy, answer:

1. At current pricing, what's the LTV:CAC ratio?
2. At what scale does the business become unit-economics positive?
3. What's the gross margin at scale, and does it support the cost structure?
4. What's the biggest lever: reduce CAC, increase ARPU, or reduce churn?

Monetization Models

Model	Works Best When	Risks
Subscription (seat-based)	Predictable usage, team adoption	Seat count limits expansion ceiling
Usage-based	Value scales with consumption	Revenue unpredictability, churn on low-usage months
Freemium	High volume, low CAC, viral distribution	Conversion rate pressure, support cost
Transaction fee	Marketplace, payments, bookings	Volume dependency, take rate pressure
Outcome-based	High-value outcomes with measurable results	Revenue recognition complexity
Hybrid	Enterprise accounts, complex value delivery	Pricing complexity, negotiation overhead

Monetization Design Questions

1. What unit of value does the customer actually buy? (seats, transactions, outcomes, access)
2. Where in the user journey does the value realization occur?
3. What's the natural expansion motion — more users, more usage, or more features?
4. What pricing structure aligns vendor incentives with customer success?

Roadmap Sequencing

Sequencing Criteria

For each roadmap item, score on:

Criterion	Description
Strategic impact	How directly does this advance a strategic pillar?
Revenue impact	Direct revenue, retention, or expansion contribution
Prerequisite value	Does this unlock other high-value items?
Reversibility	How costly is it to undo if wrong?
Evidence quality	How confident are we this will deliver the expected outcome?

Sequencing Heuristics

• Minimum viable strategy first: Build the smallest thing that tests the core strategic hypothesis before expanding
• Prerequisite sequencing: If A is required for B and C, A goes first regardless of relative value
• Reversible before irreversible: Do experiments before commitments when both options are available
• De-risk the assumption, then build the feature: Validate the riskiest assumption with the lightest-weight test before full build

Build vs. Buy vs. Partner

Option	Consider When	Red Flags
Build	Differentiating capability, unique data advantage, core competency	Becoming a vendor in a non-core area
Buy	Speed to capability, acqui-hire talent, market consolidation	Paying premium for capability you could build in 6 months
Partner / Integrate	Non-differentiating but necessary, ecosystem positioning	Partner dependency for core user experience

Best Practices

1. One strategy document, one version of truth — strategy documents that exist in multiple versions create confusion
2. Review quarterly — strategy should be durable (12–18 month horizon) but updated when key assumptions are invalidated
3. Explicit assumptions — the riskiest part of any strategy is what it assumes to be true; surface these explicitly
4. Economic validation before commitment — model the unit economics before committing significant engineering resources
5. Communicate the "why not" — stakeholders who understand what you deprioritized and why are less likely to relitigate decisions