Product Strategist Pro

An autonomous agent that develops product strategy — creating vision documents, analyzing product-market fit, designing go-to-market plans, and building strategic roadmaps that balance user needs with business objectives.

When to Use This Agent

Choose Product Strategist Pro when:

• You need to define or refine product vision and long-term strategy
• You are evaluating product-market fit for a new product or feature area
• You need a go-to-market strategy for a product launch
• You want to create a strategic roadmap that connects to business outcomes

Consider alternatives when:

• You need tactical feature prioritization (use a product champion agent)
• You need competitive intelligence gathering (use a market researcher agent)
• You need marketing campaign execution (use a content marketer agent)

Quick Start

Copy
# .claude/agents/product-strategist.yml
name: product-strategist-pro
description: Develop product strategy and go-to-market plans
agent_prompt: |
  You are a Product Strategist. Help teams define strategy:

  1. Articulate product vision and strategic positioning
  2. Analyze product-market fit signals
  3. Design go-to-market strategies
  4. Build outcome-driven roadmaps
  5. Identify strategic moats and differentiation
  6. Align product strategy with business model

  Strategy principles:
  - Strategy is choosing what NOT to do
  - Positioning is about perception, not features
  - PMF is measured by retention, not acquisition
  - Roadmaps are hypotheses, not promises

Core Concepts

Product Strategy Canvas

Element	Question	Output
Vision	Where are we going?	Vision statement
Position	How are we different?	Positioning statement
Audience	Who are we building for?	Target personas
Value	What value do we deliver?	Value propositions
Moat	Why can't competitors copy us?	Competitive advantages
Model	How do we make money?	Business model

Product-Market Fit Indicators

PMF Signal Strength:
  Strong PMF:
    - NPS > 50
    - Monthly retention > 90%
    - Organic growth > 40% of new users
    - Users would be "very disappointed" without product > 40%

  Weak PMF:
    - NPS < 20
    - Monthly retention < 70%
    - Growth requires paid acquisition
    - "Somewhat disappointed" is the common response

  Measurement:
    Sean Ellis Test: "How would you feel if you could no longer use [product]?"
    Target: > 40% respond "Very disappointed"

Go-To-Market Framework

GTM Strategy Components:
  1. Target Market: Who specifically are we selling to?
  2. Value Proposition: Why should they care?
  3. Pricing: How much and what model?
  4. Distribution: How do they find us?
  5. Launch Plan: How do we create awareness?
  6. Success Metrics: How do we measure GTM success?

GTM Motions:
  Product-Led Growth (PLG): Free tier → self-serve → upgrade
    Best for: Developer tools, productivity apps, SMB
  Sales-Led Growth (SLG): Marketing → SDR → AE → close
    Best for: Enterprise, high ACV, complex products
  Community-Led Growth (CLG): Community → adoption → monetize
    Best for: Open source, developer platforms

Configuration

Option	Type	Default	Description
strategyHorizon	string	"3-year"	Planning horizon: 1-year, 3-year, 5-year
gtmMotion	string	"plg"	Growth motion: plg, slg, clg, hybrid
marketType	string	"existing"	Market: new, existing, adjacent
includeFinancials	boolean	true	Include revenue projections
competitorAnalysis	boolean	true	Include competitive positioning
pmfAssessment	boolean	true	Evaluate product-market fit

Best Practices

1. Strategy is about focus, not comprehensiveness — A strategy that tries to serve everyone serves no one. Define who you are NOT building for as clearly as who you are building for. "We serve mid-market engineering teams" automatically excludes enterprise and SMB, which is a feature, not a limitation.

2. Measure product-market fit with retention, not signups — A product with 10K signups and 5% monthly retention does not have PMF. A product with 500 signups and 95% monthly retention does. Retention proves that the product delivers ongoing value. Acquisition proves only that your marketing works.

3. Position against the alternatives, not just competitors — Your biggest competitor may not be another product — it may be "doing nothing," "using spreadsheets," or "building in-house." Position your product against the real alternative your target audience is using today, not just the most visible competitor.

4. Build roadmaps around outcomes, not features — "Launch commenting feature in Q2" is a feature roadmap. "Increase team collaboration metrics by 40% in Q2" is an outcome roadmap. Outcome roadmaps give the team freedom to find the best solution rather than prescribing one.

5. Validate strategy assumptions before committing resources — Every strategy is built on assumptions: "mid-market teams will pay $50/user/month," "PLG can generate 1,000 signups/month." List your assumptions, rank them by risk, and validate the highest-risk assumptions first through experiments, surveys, or interviews.

Common Issues

Strategy document sits in a drawer, disconnected from execution — A beautifully crafted strategy means nothing if the team does not use it for daily decisions. Distill the strategy into 3-5 strategic priorities that fit on a single page, review them weekly, and use them as the filter for every feature and investment decision.

Product-market fit is declared prematurely — The founder declares PMF based on a few enthusiastic customers, and the team shifts to scaling. Scale amplifies what you have: if you have PMF, scaling grows the business; if you do not, scaling accelerates the burn rate. Use quantitative PMF indicators (retention, NPS, Sean Ellis test) rather than anecdotal evidence.

Go-to-market strategy does not match the product — A complex enterprise product with a self-serve GTM motion fails because buyers need education and configuration. Match the GTM motion to the product complexity, deal size, and buyer journey. Products with >$50K ACV almost always need sales assistance; products with <$500 ACV almost always need product-led growth.