Part of the product-strategy skill. See SKILL.md for the workflow spine and when to load this file.

---

XXIV. Use-Case Patterns

Pattern 1 — New Market Entry

Trigger

The client wants to enter a new geography, segment, or category.

Core Question

Where should we play, and how should we enter?

Storyline

The market is attractive, but opportunity varies by segment.

The most attractive entry point is [segment] because it combines scale, growth, and feasible access.

Customer needs are underserved around [pain point].

The client can win by leveraging [asset].

We recommend entering through [product / GTM model], validating demand with [pilot], and scaling through [roadmap].

Key Exhibits

• Market attractiveness heatmap
• Segment ranking
• Competitive landscape
• Entry mode comparison
• Business case
• Roadmap

---

Pattern 2 — Product Expansion

Trigger

The client has an existing product and wants to expand features, segments, or use cases.

Core Question

What should we build next?

Storyline

Existing traction shows customer demand, but growth is constrained by [gap].

The next best expansion opportunity is [feature / segment / use case].

This expansion improves [engagement / monetization / retention] by addressing [need].

We recommend sequencing expansion through [Now / Next / Later].

Key Exhibits

• Usage analysis
• Feature adoption
• Customer pain point map
• Product option scorecard
• Roadmap
• Unit economics

---

Pattern 3 — Monetization Refresh

Trigger

The product has adoption but weak monetization or margin.

Core Question

How should we improve revenue and profitability?

Storyline

The product has engagement, but monetization underperforms because [reason].

Revenue upside is concentrated in [segment / feature / pricing lever].

We recommend moving from [current model] to [new model], supported by [packaging / tiering / usage metric].

This improves economics while protecting adoption through [mitigation].

Key Exhibits

• Revenue bridge
• Pricing benchmark
• Willingness-to-pay evidence
• Packaging architecture
• Unit economics
• Sensitivity analysis

---

Pattern 4 — Competitive Response

Trigger

A competitor or new entrant is gaining share.

Core Question

How should we defend or regain advantage?

Storyline

Competitors are gaining traction by solving [customer need] better than current offerings.

The client remains advantaged in [asset], but must close gaps in [capability / feature / UX / pricing].

We recommend [product response] to defend [segment] and create differentiation through [advantage].

Speed matters, so execution should prioritize [fastest viable path].

Key Exhibits

• Competitor teardown
• Feature benchmark
• Customer switching analysis
• Defensive roadmap
• GTM acceleration plan
• Risk assessment

---

Pattern 5 — Platform or Ecosystem Play

Trigger

The client wants to create a broader platform, ecosystem, or multi-product strategy.

Core Question

How can we use existing assets to create compounding advantage?

Storyline

The client has underleveraged assets in [distribution / data / brand / infrastructure].

A platform strategy can increase value by connecting [participants / products / workflows].

The best starting point is [anchor product / use case] because it creates immediate customer value and data advantage.

Over time, the platform can expand into [adjacent products / partners / segments].

Key Exhibits

• Ecosystem map
• Platform value proposition
• Participant incentives
• Capability roadmap
• Network effects logic
• Monetization model

---