Creates compelling unique value propositions that differentiate your offering and resonate with target audience. Synthesizes insights from context, audience, and pain points to generate multiple UVP variations across different styles. Provides feature-benefit mapping, component breakdowns, and resonance assessment.

Requirements
How To Start
- Scan prompt for sensitive categories including competitive claims that must be substantiated, superlative claims (best, only, number one), health or medical benefit promises, financial outcome guarantees, and regulatory compliance issues. If sensitive content detected, flag unsubstantiated claims and recommend evidence gathering. For superlatives, recommend qualifying language or proof points.
- Load and verify required inputs from previous recipes. Parse context block from Recipe 1 for business name, stage, goals, industry, and constraints. Parse audience profile from Recipe 2 for persona details and primary persona focus. Parse pain point summary from Recipe 3 for critical pain points and solution alignment. If any input is missing, request it before proceeding. Note competitive context if provided.
- Present four UVP style frameworks and recommend best fit. Benefit-focused structure emphasizes clear outcomes for target audience. Transformation-focused structure emphasizes before and after state changes. Problem-solution structure leads with pain point and resolution. Hybrid structure combines elements for complex propositions. Select framework based on uvp_style parameter or recommend based on context.
- If include_feature_benefits is enabled, map features through three levels. Level 1 identifies core features and capabilities. Level 2 translates to functional benefits (what users can do). Level 3 connects to emotional outcomes (how users feel). Create prioritized benefit list based on pain point severity, differentiation strength, believability, and emotional resonance.
- Generate specified number of value proposition variations. Quick mode produces 2 variations in primary style. Standard mode produces 3 variations across 2 styles with component breakdowns. Comprehensive mode produces 4-5 variations across all styles with extended formats (long, short, tweet-length, tagline). Include comparative analysis rating clarity, differentiation, emotional resonance, and believability.
- For primary recommended UVP, deconstruct each component. Parse UVP into segments and explain purpose of each. Connect segments to specific pain points or benefits addressed. Explain why language choices work (emotional hooks, concrete imagery, transformation signals). Provide strategic rationale for overall structure.
- Generate copy-paste ready summary block for downstream recipes. Include target audience reference, core offering description, primary UVP with rationale, short version and tagline, alternative UVPs with use cases, key benefits in priority order, messaging applications for hero and support sections, proof points needed, and differentiation notes.
- Evaluate primary UVP against quality criteria. Rate clarity (immediately understandable), specificity (concrete vs vague), differentiation (unique vs generic), relevance (connects to pain points), credibility (believable claims), and emotional resonance (connects to feelings). Provide improvement recommendations and testing suggestions.
- Deliver summary of all outputs including value proposition summary block, UVP variations, component breakdown, and quality assessment. Confirm primary UVP recommendation. Provide strategic guidance for next recipe (Competitive Edge Definer) and ask if user wants to proceed or refine any aspect.
When to Use This Recipe
Recipe FAQ
enough contrast, while five can be overwhelming. Use
quick mode (2) for time constraints, comprehensive (5)
when exploring multiple positioning options. Q: Which UVP style should I choose? A: Benefit-focused works for clear, singular benefits.
Transformation-focused works for dramatic improvement
stories. Problem-solution works for pain-driven markets.
Hybrid works for complex offerings or multiple segments.
When uncertain, use hybrid (default). Q: What if my UVP sounds generic? A: Generic UVPs usually lack specificity or differentiation.
{PERSONA_NAME} will flag this in quality assessment.
Solutions include adding concrete outcomes, naming
specific pain points, or highlighting unique approach. Q: Should I include all features in the value proposition? A: No. Focus on 1-3 core benefits that address top pain
points. Feature lists dilute messaging. Save detailed
features for product pages, not value propositions. Example 1: Fine Dining Restaurant (Standard Mode) Parameters:
– context_block: Terra and Olive (Mediterranean
farm-to-table, pre-launch, fine dining)
– audience_profile: Sofia the Food Enthusiast,
Marcus the Business Host (from Recipe 2)
– pain_point_summary: Finding authentic
experiences, special occasion anxiety
(from Recipe 3)
– uvp_style: transformation-focused
– depth_mode: standard
– variation_count: 3
– include_feature_benefits: True
– competitive_context: Local fine dining lacks
authentic farm-to-table story Output: VARIATION 1 (Transformation – Recommended):
“Transform special occasions into unforgettable
Mediterranean journeys. Terra and Olive brings
farm-to-table authenticity to every celebration.” Component Breakdown:
– “Transform special occasions” – elevates dining
beyond transaction
– “unforgettable Mediterranean journeys” – concrete
sensory promise
– “farm-to-table authenticity” – differentiator
from generic fine dining Confidence: 85% VARIATION 2 (Benefit-Focused):
“Experience authentic Mediterranean cuisine with
ingredients sourced directly from local farms –
no compromises, no pretense.” Confidence: 80% VARIATION 3 (Problem-Solution):
“Tired of restaurants that promise authenticity
but deliver generic? Terra and Olive sources
every ingredient with a story worth sharing.” Confidence: 78% Short Version: “Farm-to-table Mediterranean dining
that delivers on authenticity.” Tagline: “Where Every Ingredient Has a Story” Feature-Benefit Mapping:
– Local sourcing -> Fresh ingredients -> Trust
in quality
– Chef transparency -> Know your food origin ->
Confidence in choices
– Private dining -> Exclusive experience ->
Special occasion assurance {PERSONA_NAME} Analysis: “Lead with transformation
for emotional resonance with Sofia. Authenticity
differentiator addresses core frustration. Recommend
testing tagline on social media before launch.” Example 2: Environmental Consulting (Standard Mode) Parameters:
– context_block: GreenPath Solutions
(environmental consulting, beta stage, B2B)
– audience_profile: Dana the Sustainability
Director (from Recipe 2)
– pain_point_summary: Board-ready reporting gap,
regulatory uncertainty (from Recipe 3)
– uvp_style: problem-solution
– depth_mode: standard
– variation_count: 3
– include_feature_benefits: True
– competitive_context: Existing consultants
focus on compliance, not business case Output: VARIATION 1 (Problem-Solution – Recommended):
“Sustainability directors struggle to translate
environmental impact into boardroom language.
GreenPath delivers executive-ready insights that
make you the strategic voice, not just the
compliance checkbox.” Confidence: 88% VARIATION 2 (Transformation-Focused):
“Transform sustainability reporting from
compliance burden to strategic advantage.
GreenPath helps you lead the conversation,
not chase it.” Confidence: 82% VARIATION 3 (Benefit-Focused):
“Deliver board-ready sustainability metrics with
business impact language executives understand –
without becoming a full-time report writer.” Confidence: 80% Short Version: “Sustainability insights in
boardroom language.” Tagline: “Make Sustainability Strategic” {PERSONA_NAME} Analysis: “Dana needs to look
competent to leadership. Problem-solution framework
resonates because it names her exact frustration.
Differentiation: business case focus vs compliance
focus sets GreenPath apart.” Example 3: Task Management SaaS (Quick Mode) Parameters:
– context_block: TaskFlow (AI task management,
growth stage, B2B SaaS)
– audience_profile: Emma the Overwhelmed Manager
– pain_point_summary: Tool sprawl, priority
confusion, context switching
– uvp_style: benefit-focused
– depth_mode: quick
– variation_count: 2
– include_feature_benefits: False
– competitive_context: Asana too complex,
Notion too flexible Output: VARIATION 1 (Benefit – Recommended):
“Manage all your tasks in one intelligent
workspace – without the overwhelm of enterprise
project management tools.” Focus: Simplicity + consolidation
Confidence: 80% VARIATION 2 (Benefit – Alternative):
“Stop losing track of priorities. TaskFlow
keeps your most important work front and center,
automatically.” Focus: Priority management + automation
Confidence: 75% {PERSONA_NAME} Quick Analysis: “Variation 1
addresses tool sprawl and complexity pain points
directly. Test both on landing page with 500+
visitors to validate. Ready for Recipe 5.”
