← Writing

The PMF Expansion Map: Adapted vs Complementary vs New Use Cases

September 16, 2024 · PMF Expansion

The PMF Expansion Map: Adapted vs Complementary vs New Use Cases

Most products don’t die because the team “stopped building.” They die because the market ceiling shows up silently—growth slows, upsells get harder, and the roadmap turns into a fight over marginal improvements.

Thesis: PMF expansion is not one move; it’s three distinct moves. Knowing which one you’re making—and why—prevents months of wasted build and confused GTM.

The three moves (and what changes in each)

1) Adapted use case expansion

You keep the same core problem and value prop, but adapt it to a new context—new segment, new geography, new workflow, or new compliance environment.

2) Complementary use case expansion

You keep the same customer and core job-to-be-done, but add an adjacent job that increases frequency, stickiness, or ROI (think: reporting → activation, analytics → workflow).

3) New use case expansion

You leverage capabilities, distribution, or brand to enter a different job-to-be-done. This is closer to building a second product than “adding a feature.”

How to choose the right path

Use these questions:

  • Same buyer? If yes, complementary is often strongest.
  • Same data + workflow? If yes, adapted is usually cheapest.
  • Same distribution advantage? If yes, new use case can work—if you can keep CAC sane.

A simple heuristic:

  • If the current product is healthy but growth is flattening → Complementary.
  • If sales says “we keep losing to the same objection in a new segment” → Adapted.
  • If the market is shifting (tech/regulation) and your core is getting commoditized → New.

What each path breaks

  • Adapted breaks onboarding, pricing/packaging, and implementation assumptions.
  • Complementary breaks positioning (“what are we now?”), UX complexity, and support.
  • New breaks everything: roadmap focus, org design, and your GTM motion.

A practical template you can run this week

Create a one-page “expansion memo” with:

  1. Target user + context
  2. Pain statement (observable)
  3. Why now (market/tech trigger)
  4. Why us (unfair advantage)
  5. Minimal wedge (first shippable)
  6. Kill criteria (what will prove it’s not working)
  7. 90-day success metrics

Key takeaways

  • Name the expansion move explicitly before you build.
  • Adapted is cheapest, complementary is stickiest, new use case is riskiest.
  • Every expansion breaks something—plan for the breakage, not just the feature.
  • Write an expansion memo with kill criteria to avoid zombie bets.