Skip to content
cccskills
FreePublished on GitHub

value-proposition

Explain why a specific customer group should choose a product using six parts: audience, problem, current situation, solution, improved outcome, and alternatives. Turn the analysis into a concise value proposition and a statement for marketing use.

OriginalShow the original description

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.

Works withCanva
See how to install

Good for

  • Writing a value proposition for a specific customer group
  • Clarifying changes before and after product use
  • Explaining why customers should choose over alternatives
  • Preparing product positioning for marketing

Files included (1)

  • SKILL.md5.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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


Further Reading

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ab-test-analysis

FreeSummary

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills27.2KUpdated Oct 16, 2026

ansoff-matrix

FreeSummary

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills27.2KUpdated Oct 16, 2026

See all skills by phuryn

Report a problem with this skill