mcpField
P
product-strategy-and-marketing

product-strategy-and-marketing

github.com/manojbajaj95Marketing & growth109123 installsUpdated 6w ago
Repository

About product-strategy-and-marketing

A product strategy and marketing skill for product teams planning from customer problems through positioning, growth, and marketing context. It brings market sizing, PR/FAQ, business models, and product-led growth guidance into one reference.

Key features

  1. 01Product vision and strategy frameworks
  2. 02TAM、SAM、SOM opportunity sizing
  3. 03PR/FAQ working-backwards method
  4. 04Competitive positioning and moat analysis
  5. 05Growth loops, PLG, and funnel guidance
  6. 06Product marketing context template

Use cases

  1. 01Assessing a market opportunity
  2. 02Drafting a product PR/FAQ before building
  3. 03Choosing positioning and growth approaches
  4. 04Preparing shared product marketing context

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill product-strategy-and-marketing

After installing, type/product-strategy-and-marketingin Claude Code to confirm it loaded.

Details

From the project README

Product Strategy & Marketing

Unified product strategy skill — from vision and market opportunity through competitive positioning, growth loops, PLG, and product marketing context.


Philosophy

Great product strategy asks the right questions and makes reversible decisions quickly while being thoughtful about irreversible ones.

  • Start with the customer problem — not your solution
  • Create optionality — platform thinking enables multiple futures
  • Make trade-offs explicit — strategy is choosing what NOT to do
  • Systems over tactics — growth loops compound; growth hacks don't

Product Strategy Stack

┌─────────────────────────────┐
│          VISION             │  Where are we going? (3-10 years)
├─────────────────────────────┤
│         STRATEGY            │  How will we win? (1-3 years)
├─────────────────────────────┤
│          ROADMAP            │  What are we building? (Quarters)
├─────────────────────────────┤
│         EXECUTION           │  How are we building? (Sprints)
└─────────────────────────────┘

Product-Market Fit Spectrum

Level 0: Problem Fit    → You've found a real problem worth solving
Level 1: Solution Fit   → Your solution addresses the problem
Level 2: PMF            → Customers pull the product from you
Level 3: Scale Fit      → Repeatable growth engine working
Level 4: Moat Fit       → Defensible competitive advantage established

Market Opportunity Framework

TAM → SAM → SOM

MetricWhat It MeansHow to Calculate
TAMEveryone who could theoretically buyTarget customers × avg contract value
SAMThose you can reach and serveTAM × geographic/product constraints
SOMRealistic near-term shareSAM × realistic penetration (1-5%)

Always validate top-down with bottom-up: (realistic customers × conversion rate × ACV). If gap is >3x, revisit assumptions.


Working Backwards (PR/FAQ)

Amazon's product methodology: start with the customer outcome, work backward to the solution.

Write an internal press release BEFORE building anything. If you can't write a compelling press release, you don't have a compelling product.

PR/FAQ Structure

Press Release (~1 page):

  1. Headline — product name, one-sentence customer benefit
  2. Dateline + subheadline
  3. Opening paragraph — who is the customer and what problem is solved
  4. Problem paragraph — the current pain in detail
  5. Solution paragraph — what the product does
  6. Customer quote (fictional) — how it changes their life
  7. Company/founder quote — why this matters
  8. Getting started — how to begin
  9. Closing — call to action

FAQ (External + Internal):

  • External FAQ: Questions real customers would ask
  • Internal FAQ: Questions your skeptical colleagues would ask (the hard ones)

Anti-patterns to avoid:

  • Writing the PR after building (defeats the purpose)
  • Solution-first thinking — retrofitting a problem to your idea
  • Vague customer definition ("everyone could use this")
  • Skipping the hard internal FAQ questions
  • Marketing hyperbole instead of specific, measurable claims

For patterns and examples: see references/ directory


Competitive Positioning & Moats

Moat TypeDescriptionExamples
Network EffectsProduct improves as more users joinSlack, LinkedIn
Switching CostsPainful to leaveSalesforce, Workday
Data AdvantagesProprietary data improves productGoogle, Waze
Scale EconomiesCost advantages at scaleAWS, Stripe
BrandTrust and recognitionApple, Notion

Positioning template:

For [target customer]
Who [customer need/problem]
[Product] is a [product category]
That [key benefit/differentiation]
Unlike [competitors]
Our product [unique value]

Competitive decision types:

  • Type 1 (irreversible): Business model, platform choice — take your time
  • Type 2 (reversible): Feature prioritization, pricing tiers — decide quickly

Growth Loops & PLG

Growth Loop Types
LoopMechanismKey Metric
ViralUsers invite usersK-factor
ContentUsers create discoverable contentIndexed pages
PaidRevenue funds acquisitionCAC payback
SEOContent ranks, drives trafficOrganic traffic
SalesPipeline → revenue → more repsACV/CAC
PLG Motion Types
MotionBest ForKey Lever
FreemiumSimple products, network effectsFree → paid conversion
Free TrialComplex productsTrial conversion rate
Reverse TrialHigh-value productsPremium feature discovery
Usage-BasedAPI/variable consumptionUsage expansion
North Star Metric Framework

A good North Star:

  • Measures value delivered to customers
  • Is a leading indicator of revenue
  • Reflects product strategy
  • Is actionable by the product team

Examples: Slack → DAU sending messages; Airbnb → Nights booked; Figma → Weekly Active Editors

AARRR Funnel

Acquisition → Activation → Retention → Revenue → Referral

Rule: Fix activation before optimizing acquisition. Filling a leaky bucket wastes spend.


Product Marketing Context

Before any marketing work, create .agents/product-marketing-context.md capturing:

  1. Product Overview — one-liner, what it does, product category, business model
  2. Target Audience — company type, decision-makers, primary use case, jobs to be done
  3. B2B Personas — user, champion, economic buyer, technical influencer (with pain + value promise)
  4. Problems & Pain Points — core challenge, why alternatives fail, cost of the problem
  5. Competitive Landscape — direct, secondary, and indirect competitors + how each falls short
  6. Differentiation — key differentiators, why customers choose you
  7. Objections & Anti-Personas — top 3 objections + who is NOT a good fit
  8. Customer Language — verbatim phrases for how customers describe the problem and your solution
  9. Brand Voice — tone, style, personality (3-5 adjectives)
  10. Proof Points — metrics, notable customers, testimonial snippets

Auto-draft approach (recommended): Study the repo (README, landing pages, marketing copy, package.json), draft a V1, then ask: "What needs correcting? What's missing?"

All other marketing skills reference this file automatically — create it once, update as needed.


Business Model Design

Revenue Model Options
ModelProsCons
SaaSPredictable, high LTVLong sales cycle
FreemiumLow CAC, viralFree → paid conversion hard
Usage-BasedScales with customerRevenue unpredictability
MarketplaceNetwork effectsHigh volume needed
Unit Economics
LTV = (Monthly Revenue per Customer × Gross Margin %) ÷ Monthly Churn Rate
Target: LTV > 3x CAC, CAC payback < 18 months

Key Strategic Questions

  1. Horizontal vs Vertical? — Serve many industries or dominate one deeply?
  2. High-Touch vs Self-Service? — Drives CAC, LTV, and scaling ability
  3. Niche vs Broad? — Start narrow, expand over time
  4. Premium vs Budget? — Rarely can do both
  5. First Mover vs Fast Follower? — Category size determines which matters

Anti-Patterns

  • Vision without strategy — inspiring destination, no map
  • Strategy without trade-offs — if everything is a priority, nothing is
  • TAM theater — unrealistic market sizes to impress investors
  • Feature parity obsession — chasing competitors instead of customers
  • Premature scaling — scaling before PMF
  • Optimizing acquisition before activation — filling a leaky bucket
  • Vanity metrics — MAU without engagement is meaningless

Related Skills

  • go-to-market-strategy — Launch planning and execution
  • pricing-strategy — Pricing decisions and packaging
  • sales-and-revenue-operations — Sales team, RevOps

Comments

Markdown supported