Value Proposition Canvas
Align your product with what customers actually need. Map customer jobs, pains, and gains against your pain relievers and gain creators to find and validate product-market fit.
Why the Value Proposition Canvas matters
Most products fail not because they are poorly built but because they solve a problem customers do not have, or solve the right problem in a way that does not relieve the actual pain. The Value Proposition Canvas prevents this by forcing you to start with the customer, not the product.
The canvas creates a visual connection between what customers need and what you offer. Gaps become immediately visible: pains without relievers, relievers without pains, gains that no feature creates. This clarity makes it possible to have honest conversations about product-market fit before you invest months of engineering time.
Use this template to build both sides of the canvas. Start with the customer profile (right side), then map your value proposition (left side), and look for alignment between the two.
The Value Proposition Canvas
Six components across the customer profile and value map.
Customer Jobs
List the functional, social, and emotional jobs your customer is trying to get done. Functional jobs are tasks (write a PRD, analyze metrics). Social jobs relate to how they want to be perceived (look competent, be the informed person in the room). Emotional jobs relate to how they want to feel (confident, in control, not overwhelmed).
Example: "Functional: Write a data-grounded product spec in under 2 hours. Social: Present recommendations that engineering respects. Emotional: Feel confident that nothing important was missed in the spec."
Tips
- Include functional, social, and emotional jobs
- Rank jobs by importance to the customer
- Use customer interviews, not assumptions
- Focus on jobs related to your product domain
Customer Pains
Identify the obstacles, risks, and negative outcomes customers experience when trying to get their jobs done. Pains can be functional (it takes too long), social (they look unprepared), or emotional (they feel anxious). Rank pains by severity. The most severe pains are your biggest opportunities.
Example: "Functional pain: Gathering context from 5 tools takes 3+ hours before writing can begin. Social pain: Presenting a PRD with gaps that engineering points out in review. Emotional pain: Anxiety that the spec missed a critical requirement."
Tips
- Rank pains from severe to moderate
- Include functional, social, and emotional pains
- Ask customers: what is the worst part of this process?
- Map pains to specific jobs where they occur
Customer Gains
Describe the outcomes and benefits customers want. Gains can be required (must have for the job), expected (normal standard), desired (would love but do not expect), and unexpected (delighters). Required and expected gains are table stakes. Desired and unexpected gains are where differentiation happens.
Example: "Required: A spec that engineering can implement without ambiguity. Expected: Spec completed in one sitting. Desired: AI fills in sections using real data. Unexpected: The spec automatically updates when context changes."
Tips
- Categorize as required, expected, desired, or unexpected
- Desired and unexpected gains create differentiation
- Ask: what would make this job 10x easier?
- Connect gains to measurable outcomes when possible
Pain Relievers
Describe how your product alleviates specific customer pains. Each pain reliever should map directly to a pain from the customer profile. Be specific about how your product reduces or eliminates the pain. If a pain has no reliever, you have a gap. If a reliever has no corresponding pain, you may be building something unnecessary.
Example: "Pain: 3+ hours gathering context. Reliever: Vantage connects to Slack, Amplitude, Figma, and Linear and pulls relevant context automatically. Time to first draft: under 5 minutes."
Tips
- Map each pain reliever to a specific customer pain
- Unmapped pains reveal product gaps
- Unmapped relievers reveal wasted effort
- Quantify relief when possible (time saved, errors prevented)
Gain Creators
Describe how your product creates specific customer gains. Like pain relievers, each gain creator should map to a gain from the customer profile. The most powerful value propositions create unexpected gains that customers did not know they wanted.
Example: "Gain: Spec automatically updates when context changes. Creator: Vantage maintains live connections to data sources and flags when underlying data contradicts PRD assumptions."
Tips
- Map each gain creator to a specific customer gain
- Focus on gains that competitors do not create
- Unexpected gain creators drive word-of-mouth
- Test gain creators with customer demos before building
Products and Services
List the specific products, features, and services that deliver your pain relievers and gain creators. This is where you connect your value proposition to your actual product. Each product or feature should clearly map to at least one pain reliever or gain creator.
Example: "1. Connected data ingestion (URLs, docs, screenshots, integrations). 2. AI-generated PRD with traced sources. 3. Requirement extraction and ticket generation. 4. Bi-directional sync with Linear/Jira."
Tips
- Each feature should map to a pain reliever or gain creator
- Features without a mapping should be questioned
- Prioritize features that address the most severe pains
- This is your feature roadmap grounded in customer value
Related templates
Frequently asked questions
Validate your value proposition with data
Vantage connects customer feedback, analytics, and product data to help you build what customers actually need. Free to start.
Free to start. No credit card required.