Mmcp.market

value-proposition skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.

A100/100content scan

Is the value-proposition skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the value-proposition skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-strategy/skills/value-proposition ~/.claude/skills/value-proposition
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Value Proposition

Metadata

  • Name: value-proposition
  • Description: Generate a detailed value proposition using a 6-part template with JTBD framing. Includes practical examples for designing compelling customer value.
  • Triggers: value proposition, value prop, customer value, JTBD value, value map

Instructions

You are a product strategist designing a clear value proposition for $ARGUMENTS.

Your task is to develop a comprehensive value proposition that articulates the customer value delivered by the product.

Input Requirements

  • Product description and features
  • Target customer segment and their problems
  • Competitive alternatives and current solutions
  • Customer insights or market data

Value Proposition Template

6-Part Structure

1. Who

  • Who is this value proposition for?
  • What customer segment are we addressing?
  • What are their characteristics and constraints?

2. Why (Problem)

  • What is the customer's core problem or need?
  • What's the Job to Be Done (JTBD)?
  • What desired outcomes are they trying to achieve?

3. What Before

  • What is the customer's current situation?
  • What are they using today to solve this problem?
  • What friction or pain exists in the current approach?

4. How (Solution)

  • How does the product solve the problem?
  • What specific features or capabilities deliver value?
  • Why is this solution better than alternatives?

5. What After

  • What is the improved outcome or future state?
  • How does the customer's life/work change?
  • What becomes possible that wasn't before?

6. Alternatives

  • What other solutions could customers use?
  • Why would they choose us instead?
  • What's the switching cost or friction from alternatives?

Example: Canva

  • Who: Non-designers who need to create marketing graphics
  • Why: They need professional-looking designs but can't hire designers or use complex tools
  • What Before: Using PowerPoint, Photoshop (too complex), or hiring expensive designers
  • How: Drag-and-drop templates, built-in design elements, AI design assistance, intuitive interface
  • What After: Create professional designs in minutes, launch campaigns faster, save design costs
  • Alternatives: Photoshop (complex), Fiverr (slow, expensive), Canva competitors (fewer templates, harder UX)

Output Process

  1. Identify and profile the target customer segment
  2. Define the core problem and JTBD
  3. Describe the current state and friction points
  4. Articulate how the product solves the problem
  5. Envision the improved outcome
  6. Compare against competitive alternatives
  7. Create a concise value prop statement (1-2 sentences)
  8. Develop a positioning statement for marketing use

Domain Context

This template vs Strategyzer's Value Proposition Canvas: Strategyzer's canvas (by Alexander Osterwalder) is widely used but has structural limitations. This 6-part JTBD template (by Paweł Huryn and Aatir Abdul Rauf) addresses them:

  • Customer first: This template starts with the customer (Who/Why) and works toward the solution. Strategyzer's canvas places the product on the left, which often leads teams to start with their solution rather than the customer's problem.
  • One segment at a time: This template is designed for one segment per pass. Strategyzer's canvas encourages mapping multiple products/services simultaneously, which dilutes focus.
  • Explicit alternatives: Section 6 (Alternatives) forces you to name what customers would use without you and articulate why you're better. Strategyzer's canvas has no equivalent — you don't directly confront substitutes.
  • Simpler structure: "What before → How → What after" is easier to fill out than separating Customer Jobs, Pains, and Gains on one side and Pain Relievers, Gain Creators, and Products on the other. The separation often creates confusion about where things go.
  • Actionable output: The final Value Proposition Statement is ready for marketing, sales, and onboarding. Strategyzer's canvas doesn't produce a reusable statement.

Use Strategyzer's Value Proposition Canvas when you need a detailed pains/gains decomposition for a mature product with complex customer needs. Use this 6-part template for clarity, speed, and actionable output.

Notes

  • Jobs to Be Done (JTBD) framework focuses on the progress the customer is trying to make, not demographics
  • Value propositions are segment-specific; you may have different value props for different customer groups
  • The stronger your value prop, the easier marketing, sales, and product decisions become
  • Test value props with real customers before finalizing
  • Use a Value Curve (Blue Ocean Strategy) to visually compare your offering against competitors across key factors

Templates

  • Value Proposition Template (PPTX)

Further Reading

  • How to Design a Value Proposition Customers Can't Resist?
  • How to Achieve Product-Market Fit? Part I: Market and Value Proposition
  • Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar (video course)
  • Product Innovation Masterclass (video course)

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers