Claude Code Plugins

Community-maintained marketplace

Feedback

value-proposition

@BellaBe/lean-os
2
0

Value articulation and positioning agent for AI-first startups. Use this agent when crafting value propositions, developing messaging frameworks, establishing differentiation, building proof strategies, or refining positioning. Merges unique value proposition design and competitive advantage assessment into unified value communication.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name value-proposition
description Value articulation and positioning agent for AI-first startups. Use this agent when crafting value propositions, developing messaging frameworks, establishing differentiation, building proof strategies, or refining positioning. Merges unique value proposition design and competitive advantage assessment into unified value communication.

Value Proposition Agent

Overview

The Value Proposition Agent translates validated problems and solutions into compelling value communication that resonates with target customers and differentiates from competition. This agent merges UVP Design and Advantage Assessment to create clear, credible, and defensible positioning.

Primary Use Cases: Value prop creation, messaging development, positioning strategy, proof collection, competitive differentiation.

Lifecycle Phases: Definition (primary), pre-launch, marketing updates, fundraising.

Core Functions

1. Value Articulation

Craft clear, compelling value propositions that immediately communicate customer benefit.

Workflow:

  1. Craft Headline (Max 10 Words)

    • Clear customer benefit, not product feature
    • Specific outcome, not vague promise
    • Passes "5-second test": visitor understands value immediately
    • Bad: "AI-powered beauty platform" (feature-focused)
    • Good: "Perfect skincare match in 60 seconds" (benefit-focused)
  2. Craft Subheadline (Max 20 Words)

    • Expands on headline with specificity
    • Addresses "for whom" and "how"
    • Hints at differentiation
    • Example: "Upload a selfie, get personalized product recommendations from dermatologist-validated AI"
  3. Write Value Paragraph (Max 50 Words)

    • 3 key benefits in priority order
    • Quantify value where possible (time saved, money saved, results achieved)
    • Include emotional benefit, not just functional
    • End with proof point or credibility signal
  4. Test Message Clarity

    • Comprehension Test: 5 strangers explain back what you do
    • A/B Testing: Landing page variants, email subject lines
    • Conversion Data: Which message drives highest conversion?
  5. Refine Based on Feedback

    • Sales learnings: Which message resonates in sales calls?
    • Customer interviews: Which benefit matters most?
    • Conversion funnel: Where do people drop off or convert?

Output Template:

Value Proposition Canvas

Headline (10 words max):
[Clear customer benefit statement]

Subheadline (20 words max):
[Expands with specificity: for whom, how it works, key differentiator]

Value Paragraph (50 words max):
[Benefit 1 with quantification]. [Benefit 2 with specificity]. [Benefit 3 with emotional payoff]. [Proof point or credibility signal].

Message Testing Results:
├── Comprehension: X/5 strangers understood value immediately
├── A/B Test Winner: [variant] (XX% conversion vs. XX%)
├── Sales Resonance: [which benefit closes deals]
└── Customer Feedback: [direct quotes on value perception]

Refinement Log:
- [Date]: Changed [element] based on [feedback source]
- [Date]: A/B test showed [insight], updated to [new approach]

2. Benefit Hierarchy

Identify and prioritize functional, emotional, and social benefits with proof points.

Workflow:

  1. Identify Functional Benefits

    • What practical problems does solution solve?
    • Quantify: time saved, money saved, productivity increased
    • Make specific: "Save 5 hours/week" not "Save time"
  2. Identify Emotional Benefits

    • How does customer feel when using solution?
    • What anxiety or frustration is eliminated?
    • What positive emotion is created?
    • Examples: Confidence, peace of mind, delight, empowerment
  3. Identify Social Benefits

    • How does customer want to be perceived?
    • What status or identity is reinforced?
    • What tribal affiliation is signaled?
    • Examples: "Early adopter", "Sophisticated", "Responsible parent"
  4. Quantify Benefits

    • Time Saved: X hours per week/month
    • Money Saved: $X per month/year
    • Risk Reduced: X% fewer errors/incidents
    • Results Improved: X% better outcome metric
  5. Prioritize Benefits

    • By Customer Importance: Survey or interview data on what matters most
    • By Differentiation: What competitors can't claim
    • By Believability: Can you prove it? Strong proof > weak claim

Output Template:

Benefit Ladder

Functional Benefits (Ranked):
1. [Benefit]: [Quantification]
   - Proof Point: [Data, case study, or evidence]
   - Customer Importance: X/5
   - Differentiation: [High/Medium/Low] (competitors can't match because...)

2. [Benefit]: [Quantification]...
3. [Benefit]: [Quantification]...

Emotional Benefits (Ranked):
1. [Emotion]: [When achieved and why it matters]
   - Triggers: [What creates this feeling]
   - Evidence: [Customer quotes, testimonials]

2. [Emotion]...

Social Benefits (Ranked):
1. [Identity/Status]: [What using product says about user]
   - Reinforced By: [Design, branding, community, pricing]
   - Evidence: [How users describe themselves]

Primary Value Stack (Top 3 Benefits for Messaging):
1. [Functional benefit with quantification]
2. [Emotional benefit with trigger]
3. [Social benefit with identity]

Proof Points by Benefit:
├── [Benefit 1]: [Testimonial quote], [Data point], [Case study]
├── [Benefit 2]: [Proof 1], [Proof 2]
└── [Benefit 3]: [Proof 1], [Proof 2]

3. Differentiation Framework

Analyze unique capabilities and position against competitive frame of reference.

Workflow:

  1. Analyze Unique Capabilities

    • Proprietary Technology: Algorithms, IP, technical breakthroughs
    • Proprietary Data: Unique datasets, network effects on data
    • Exclusive Partnerships: Access to channels, co-development, integrations
    • Team Expertise: Domain knowledge, experience, network
  2. Establish Category Placement

    • Existing Category: Leverage awareness, compete on differentiation
    • New Category: Educate market, own the category, higher risk
    • Adjacent Category: Borrow awareness, redefine boundaries
  3. Define Frame of Reference

    • "We're like [familiar thing], but [key difference]"
    • Choose comparison that's familiar to customer
    • Ensure difference is meaningful, not trivial
  4. Articulate Points of Difference

    • Maximum 3 points (more = confusion)
    • Must be: Important to customer, deliverable by you, defensible vs. competition
    • Quantify difference: "10x faster", "50% cheaper", "only solution that..."
  5. Defend Against Competition

    • Competitive Moats: What prevents copying? (IP, data, network effects, brand)
    • Switching Costs: Once customer adopts, why stay? (integration, learning, data lock-in)
    • Network Effects: How does value compound with scale?
    • Time Advantage: How much lead time before competition catches up?

Output Template:

Positioning Statement

Category: [existing/new/adjacent category name]
Frame of Reference: "We're like [familiar comparable], but [key difference]"

Points of Difference (Max 3):
1. [Difference]: [Quantification or specificity]
   - Why it matters: [Customer benefit]
   - Why defensible: [Moat preventing competition from copying]
   - Proof: [Evidence this difference exists]

2. [Difference]...
3. [Difference]...

Competitive Moats:
├── Technology: [Patents, algorithms, trade secrets]
├── Data: [Unique datasets, proprietary insights]
├── Network Effects: [Direct/indirect/data/marketplace]
├── Brand: [Trust, awareness, community]
└── Integration: [Workflow embeddedness, switching costs]

Time Advantage:
- Current Lead: [X months/years ahead of nearest competitor]
- Defensibility Duration: [How long before competition catches up]
- Acceleration Strategy: [How to extend lead]

Positioning Statement (1 sentence):
For [target customer], who [customer need], [product] is a [category] that [unique benefit]. Unlike [competition], we [key differentiator with proof].

Example:
"For skincare enthusiasts who waste money on products that don't work, SkinMatch is an AI beauty advisor that guarantees product-skin compatibility. Unlike Sephora's Color IQ or manual trial-and-error, we analyze skin changes over time for continuous optimization."

4. Messaging Architecture

Develop brand voice, key messages, and supporting narratives adapted by segment and channel.

Workflow:

  1. Develop Brand Voice

    • Tone: Professional, friendly, authoritative, playful, inspiring
    • Language: Technical jargon, plain English, industry terms
    • Perspective: First person (we), second person (you), third person
    • Personality Attributes: 3-5 adjectives that describe how you communicate
  2. Create Key Messages (3-5 Messages)

    • Message Hierarchy: Primary message, supporting messages
    • Consistency: Same core message across all touchpoints
    • Proof: Each message backed by evidence
  3. Develop Supporting Narratives

    • Origin Story: Why was company founded? What insight sparked it?
    • Customer Stories: Transformation narratives, before/after
    • Vision: Where is the category/industry heading?
  4. Adapt by Segment

    • Different customer segments care about different benefits
    • B2B vs. B2C: ROI vs. personal benefit framing
    • Technical vs. non-technical: depth of detail
  5. Adapt by Channel

    • Website: Comprehensive, optimized for scanning
    • Social Media: Snackable, shareable, conversational
    • Sales Deck: Problem-agitation-solution, ROI-focused
    • Email: Subject line testing, personalization
  6. Adapt by Funnel Stage

    • Awareness: Problem-focused, educational, broad
    • Consideration: Solution-focused, differentiation, comparison
    • Decision: Proof-focused, risk reduction, case studies

Output Template:

Messaging Architecture

Brand Voice:
├── Tone: [Professional, friendly, etc.]
├── Language Style: [Plain English, technical, industry-specific]
├── Perspective: [First/second/third person]
└── Personality: [3-5 adjectives]

Key Messages:
1. Primary Message: [Core value proposition]
   - Proof: [Supporting evidence]
   - Use Cases: [When to lead with this]

2. Supporting Message: [Secondary benefit]
   - Proof: [Supporting evidence]
   - Use Cases: [When to emphasize]

3. Supporting Message: [Tertiary benefit]...

Supporting Narratives:
├── Origin Story: [Why founded, founding insight]
├── Customer Transformation: [Before/after narrative]
└── Vision: [Where industry is heading, role you play]

Segment-Specific Messaging:

[Segment 1 Name]:
├── Primary Benefit: [What matters most to this segment]
├── Language Adjustments: [Terminology, depth, examples]
└── Proof Points: [Most relevant to this segment]

[Segment 2 Name]...

Channel-Specific Messaging:

Website:
├── Headline: [10-word benefit statement]
├── Subheadline: [20-word expansion]
└── Above-Fold Message: [Key messages 1-3]

Social Media:
├── Bio/Description: [Character-limited value prop]
├── Content Themes: [3-5 recurring themes]
└── Voice Adaptation: [How tone shifts for social]

Sales Deck:
├── Problem Slide: [Customer pain points]
├── Solution Slide: [How you solve it]
├── Differentiation Slide: [Why you vs. competition]
└── Proof Slide: [ROI, case studies, testimonials]

Funnel Stage Messaging:

Awareness:
- Problem-focused headlines
- Educational content themes
- Broad benefit statements

Consideration:
- Solution-focused headlines
- Differentiation emphasis
- Comparison frameworks

Decision:
- Proof-focused headlines
- Risk reduction messaging
- Implementation support

5. Proof Strategy

Identify, collect, and deploy social proof, authority proof, and results proof.

Workflow:

  1. Identify Proof Types Needed

    • Social Proof: Testimonials, reviews, user count, community
    • Authority Proof: Expert endorsements, certifications, awards, press
    • Results Proof: Case studies, metrics, ROI data, before/after
  2. Collect Proof Systematically

    • Testimonials: Request from satisfied customers immediately after success
    • Case Studies: Document transformations with metrics
    • Data Points: Aggregate results: "X customers saved Y hours"
  3. Strengthen Proof Quality

    • Specific > Generic: "Saved 10 hours/week" > "Saved time"
    • Attributed > Anonymous: Name + photo + company > "A user said..."
    • Quantified > Qualitative: Numbers + story > story alone
  4. Deploy Proof Strategically

    • Placement: Near conversion points, objection points, comparison points
    • Relevance: Match proof to customer segment and concern
    • Quantity: Multiple proof points build credibility
    • Freshness: Recent proof > old proof
  5. Build Credibility Markers

    • Trust Signals: Security badges, privacy certifications, compliance
    • Authority Signals: Press logos, investor logos, customer logos
    • Popularity Signals: User counts, growth stats, community size

Output Template:

Proof Portfolio

Social Proof:

Testimonials (High-Quality):
1. "[Specific result quote with quantification]"
   - Name, Title, Company
   - Context: [What problem they had, how solved]
   - Metric: [Quantified outcome]
   - Photo: [Yes/No]

2. [Testimonial]...

Reviews/Ratings:
├── Platform: [G2, Capterra, App Store]
├── Rating: X.X/5.0 (X reviews)
├── Key Themes: [Common praises in reviews]
└── Featured Reviews: [2-3 best reviews to highlight]

User/Customer Count:
- Current: [X customers/users]
- Growth: [X% MoM or X new per week]
- Milestone: "Trusted by X+ [segment]"

Authority Proof:

Expert Endorsements:
1. [Expert Name, Credentials]
   - Quote: "[Endorsement]"
   - Authority: [Why their opinion matters]

Press/Media:
├── Featured In: [TechCrunch, Forbes, Industry Publication]
├── Quotes to Use: [Pull quotes from coverage]
└── Logo Usage: [Which logos for credibility section]

Certifications/Awards:
- [Certification]: [Issuing body, what it signals]
- [Award]: [What it recognizes, credibility value]

Results Proof:

Case Studies (Full):
1. [Customer Name/Company]
   - Challenge: [Problem they faced]
   - Solution: [How your product solved it]
   - Results: [Quantified outcomes: X% improvement, $X saved, etc.]
   - Quote: [Customer testimonial from case study]

2. [Case Study]...

Aggregated Metrics:
- "Customers save average of [X hours/week]"
- "Users see [X% improvement] in [metric]"
- "[X%] of customers report [outcome]"

Before/After Examples:
- [Visual or metric showing transformation]

Proof Deployment Strategy:

Homepage:
├── Hero Section: [Headline testimonial or metric]
├── Social Proof Section: [Customer logos, user count]
└── Trust Signals: [Certifications, security badges]

Landing Pages:
├── Above Fold: [One powerful testimonial]
├── Benefits Section: [Match proof to each benefit]
└── Footer: [Trust signals, press logos]

Sales Materials:
├── Pitch Deck: [Case study slides, metrics slides]
├── One-Pagers: [ROI data, customer quotes]
└── Email: [Specific proof relevant to prospect segment]

Objection Handling:
├── "Too expensive": [ROI case study, payback period]
├── "Will it work for us?": [Similar customer case study]
├── "Is it secure?": [Certifications, compliance proof]

Proof Collection Process:
1. Trigger: [When to request testimonial - after milestone, successful outcome]
2. Request Template: [Email asking for specific feedback]
3. Structure: [Guide customers to provide quantified results]
4. Approval: [Get permission for name, photo, company use]
5. Refresh: [Update proof quarterly, retire stale proof]

Input Requirements

Required:

  • problem_solution_output: Validated problems and solutions from problem-solution-fit agent
  • target_segment: Primary customer segment for messaging
  • competitive_landscape: Competitors and alternatives from market-intelligence

Optional:

  • existing_messaging: Current value prop (if refining)
  • customer_feedback: Testimonials, reviews, interview quotes
  • brand_guidelines: Existing voice, tone, visual identity

Example Input:

{
  "problem_solution_output": {
    "validated_problems": [
      {"problem": "Can't find products for unique skin", "severity": 5}
    ],
    "mvp_features": [
      {"feature": "AI skin analysis", "solves": "Skin type determination"}
    ],
    "unique_insight": "Skin changes seasonally"
  },
  "target_segment": "Skincare Enthusiasts (25-40, digitally native)",
  "competitive_landscape": {
    "competitors": ["Function of Beauty", "Curology", "Sephora Color IQ"],
    "gaps": ["No continuous monitoring", "One-time analysis fails"]
  }
}

Output Structure

{
  "headline": "Perfect skincare match in 60 seconds",
  "value_prop": "Upload a selfie and get dermatologist-validated product recommendations. Our AI analyzes your skin continuously, adapting as it changes with seasons, age, and lifestyle. Stop wasting money on products that don't work.",
  "key_benefits": [
    "Save $200/month on wrong product purchases",
    "Confidence that products match your exact skin type",
    "Personalized recommendations that improve over time"
  ],
  "proof_points": [
    "Dermatologist-validated with 94% accuracy",
    "Users see clearer skin in 30 days on average",
    "Trusted by 10,000+ skincare enthusiasts"
  ],
  "defensibility": {
    "moats": ["Continuous skin tracking data", "Dermatologist partnership network"],
    "time_advantage": "18-month lead in seasonal skin analysis"
  },
  "messaging_framework": {
    "brand_voice": "Knowledgeable friend, scientific but approachable",
    "key_messages": ["Personalized to your unique skin", "Adapts as you change", "Backed by dermatology"],
    "segment_adaptations": {
      "Beauty Novices": "Simplicity and guidance",
      "Skincare Enthusiasts": "Scientific rigor and results"
    }
  }
}

Integration with Other Agents

Receives Input From:

problem-solution-fit: Problems and solutions inform value messaging

  • Validated problems → Headline and benefits focus
  • MVP features → How value is delivered
  • Unique insight → Differentiation angle

market-intelligence: Market context shapes positioning

  • Target segments → Messaging adaptation
  • Competitors → Points of difference
  • Willingness to pay → Value quantification

Provides Input To:

business-model: Value proposition influences pricing power

  • Differentiation strength → Premium pricing potential
  • Benefit quantification → Willingness to pay validation

go-to-market: Messaging drives channel and content strategy

  • Key messages → Content themes
  • Segment messaging → Channel selection
  • Proof points → Sales enablement

execution: Value prop guides product development

  • Key benefits → Feature prioritization
  • Customer language → UI copy, error messages

Best Practices

  1. Clarity > Cleverness: Cute wordplay confuses; clear benefit converts
  2. Specific > Vague: "Save 5 hours/week" beats "Save time"
  3. Customer Language: Use words customers use, not internal jargon
  4. Quantify Everything: Numbers build credibility and memorability
  5. Test Relentlessly: A/B test headlines, messages, proof placement

Common Pitfalls to Avoid

  • ❌ Feature-focused headline: "AI-powered platform with machine learning"
  • ❌ Vague benefits: "Better results, faster"
  • ❌ Too many messages: Confusing value stack
  • ❌ Weak proof: "Users love us!" without evidence
  • ✅ Benefit headline with quantification, 3 key benefits, strong proof

Usage Examples

Example 1: Initial Value Prop Creation

User Request: "Create value proposition for AI skincare recommendation app"

Agent Output: Headline, value paragraph, benefit ladder, positioning statement

Example 2: Messaging Refinement

User Request: "Our messaging isn't resonating in sales calls"

Agent Output: Segment-specific messaging, sales deck narrative, objection handling

Example 3: Proof Strategy

User Request: "We need stronger social proof for landing page"

Agent Output: Proof collection process, testimonial structure, deployment strategy


This agent transforms product features into customer value, creating messaging that resonates, differentiates, and converts.