value-proposition

name

value-proposition

description

Designs a precise value proposition using a 6-part JTBD template (Who / Why / What Before / How / What After / Alternatives). Use this skill — proactively and without waiting to be asked — whenever the product's positioning is unclear, a new customer segment is being targeted, or messaging is inconsistent across teams. Also triggers for: "value proposition", "value prop", "why would customers choose us", "positioning for new segment", "win/loss analysis shows customer confusion", "customers can't explain why they use us", "what's our differentiation", "elevator pitch", "why us over competitors", "competitive differentiation", "JTBD template", "what problem do we solve", "who is this product for". Produces one value prop per segment — not a tagline, a positioning decision — with a synthesized 1-2 sentence statement ready for a PRD problem statement, landing page headline, or sales deck.

Value Proposition

Core Philosophy

A value proposition is not a tagline. It's the answer to: who is this for, what job are they trying to do, and why is this better than everything else they could use?

The most common failure: defining the value proposition from the product outward ("we are a platform that...") instead of from the customer inward ("when a [person] needs to [do a job]..."). Start with the customer's situation, not your solution.

One value prop per customer segment. If you're trying to write one that works for everyone, it will work for no one.

When to Use

• When building or re-evaluating product positioning
• Before writing a PRD — to verify the problem and customer are clearly defined
• When marketing and sales are using inconsistent messaging
• When customers can't explain in their own words why they use your product
• When entering a new segment that has different JTBD from your core users

Workflow

1. Define the Customer Segment

Pick one segment. Be specific: not "companies" but "early-stage SaaS founders who are the only PM on their team." Specificity makes the rest of the template easier and more honest.

2. Fill the 6-Part Template

Who The customer segment you're addressing. Include relevant characteristics and constraints (budget, time, technical ability, org size).

Why (Problem) The core problem or job-to-be-done. Use the JTBD frame: "When [situation], they want to [goal] so they can [desired outcome]."

Distinguish between:

• Functional job: the practical task they're trying to complete
• Emotional job: how they want to feel (confident, in control, respected)
• Social job: how they want to be perceived by others

What Before (Current State) What are they using today to solve this problem? What does their current workflow look like? What frustrations, workarounds, or costs exist in the current approach?

How (Solution) How does your product solve the problem? Be specific — not "we make it easy" but what specifically makes it easier or better.

What After (Future State) What changes in their life or work after using your product? Focus on outcomes, not features. What becomes possible that wasn't before?

Alternatives What else could they use instead of you? This forces honesty about your real competitive context and sharpens your "why us" claim.

3. Write the Value Proposition Statement

Synthesize the 6 parts into 1-2 sentences:

"[Product] helps [Who] [achieve What After] by [How] — unlike [Alternatives], which [limitation]."

4. Test It

A strong value proposition:

• A real customer would recognize their problem in it
• It says something specific enough to be wrong (if it can't be wrong, it's too vague)
• It says something that a competitor can't truthfully claim
• Someone outside the company reads it and immediately understands who it's for and why they'd care

Output Format

## Value Proposition — [Product / Segment]

### 6-Part Template

**Who**: [Customer segment with key characteristics]

**Why**: When [situation], they want to [goal] so they can [outcome].
- Functional: [task]
- Emotional: [feeling they want]
- Social: [how they want to be seen]

**What Before**: [Current workflow and its frustrations/costs]

**How**: [Specific ways the product solves the problem]

**What After**: [Changed outcomes — what's now possible]

**Alternatives**: [What they'd use without you] and why you're better

### Value Proposition Statement
[Product] helps [Who] [What After] by [How] — unlike [Alternatives], which [limitation].

### Positioning Note
Use this in: [PRD problem statement / landing page headline / sales deck intro]

Antipatterns

• Feature-led props: "We have 50+ integrations" is a feature, not a value proposition. Translate features into outcomes.
• Too broad a segment: A value prop for "all businesses" is a value prop for no business in particular.
• Ignoring alternatives: If you skip the Alternatives section, you skip the competitive reality. Customers always have alternatives — including doing nothing.
• Internal language: Using your product team's vocabulary ("seamless workflow," "AI-powered insights") instead of language your customer would actually use.
• Set and forget: Value propositions go stale as markets evolve. Revisit when customer language in interviews shifts or when win/loss patterns change.