The Value Proposition Canvas¶
Most product pages describe what the product does. Customers care about what it does for them. The gap between those two things is why many well-built products never sell. The Value Proposition Canvas closes that gap: it separates "what the customer actually needs" from "what we actually offer", maps each in detail, and then checks item by item whether they match.
Created by Alexander Osterwalder and colleagues, the canvas is a magnifying glass on two blocks of the Business Model Canvas: Customer Segments and Value Propositions. Where the Business Model Canvas asks "how does this business work?", the Value Proposition Canvas asks the earlier and more dangerous question: does anybody actually want this?
The canvas has two halves. On the right, the Customer Profile describes the customer's reality: you can only observe and discover it, never invent it. On the left, the Value Map describes how your offering responds. When the two sides line up, you have fit.
Key takeaways
- Right side (Customer Profile): customer jobs, pains, gains — observed facts, not wishes.
- Left side (Value Map): products and services, pain relievers, gain creators.
- Order matters: fill in the right side first. Doing it the other way round, you will unconsciously shape customer needs to fit your product.
- You don't need to address everything: cover the few most important pains and gains; covering all of them blurs the product.
- Three levels of fit: on paper → in the market → in the business model. The last two require real evidence.
Right Half: The Customer Profile¶
Record only what you observed or heard, not what you hope. The raw material comes from interviews, ethnographic observation, support records and behavioral data.
1. Customer Jobs¶
What customers are trying to get done in their work and life, in three kinds:
- Functional jobs: concrete tasks, e.g. "invoice 30 clients every month".
- Social jobs: how they want to be seen, e.g. "look professional in front of clients".
- Emotional jobs: how they want to feel, e.g. "stop dreading the monthly reconciliation".
Key point: describe the customer's job, not your product's use. "Use our invoicing app" is not a job; "invoice accurately and on time every month" is.
2. Pains¶
The obstacles, risks and bad outcomes around getting the job done:
- Undesired outcomes: three hours spent and the accounts still don't reconcile.
- Obstacles: data scattered across three systems.
- Risks: an incorrect invoice could create a tax problem.
Rate severity: is this "extreme" or "moderate"? That determines whether anyone will pay to remove it.
3. Gains¶
The outcomes customers expect, desire or would be delighted by:
- Required gains: without them the solution doesn't work at all (invoices must be tax-compliant).
- Expected gains: assumed by default (it shouldn't be complicated).
- Desired gains: they'd be pleased to have (automatic reminders for overdue payments).
- Unexpected gains: beyond what they imagine (automatic cash-flow forecasting).
These four levels map closely onto the Kano Model and the two tools work well together.
Left Half: The Value Map¶
4. Products and Services¶
Simply the list of what you offer: physical, digital, services, experiences. It's only a list; the value shows up in the next two blocks.
5. Pain Relievers¶
Exactly how your offering removes or reduces specific pains listed on the right. Match them one to one: "pulls data automatically from bank feeds" answers "data scattered across three systems".
6. Gain Creators¶
Exactly how your offering produces the gains listed on the right, again matched one to one.
How to Fill It In¶
- Pick one customer segment. Different customers have different jobs, pains and gains; mixing them guarantees a blurry result.
- Build the right side from real research. Run 10–20 interviews and ask about specific past experiences ("how long did last month's invoicing take? what went wrong?"), not hypotheticals.
- Rank the right side. Order pains and gains by importance. Only the top few are worth building for.
- Then build the left side, addressing the highest-ranked pains and gains.
- Draw the connections. Which item on the left answers which item on the right? Anything on the left with no match is a candidate for removal; anything high on the right with no match is a product gap.
- Go and validate. Fit on paper proves nothing; test whether customers actually pay (see Lean Startup).
Template¶
Customer segment: ____
| Customer Profile (right) | Content | Importance (high / medium / low) |
|---|---|---|
| Customer jobs | ||
| Pains | ||
| Gains |
| Value Map (left) | Content | Which item on the right it addresses |
|---|---|---|
| Products and services | ||
| Pain relievers | ||
| Gain creators |
Fit checklist
- The right side comes from real interviews, not team assumptions
- Pains and gains are ranked by importance
- The three most important pains each have a pain reliever
- Nothing on the left is unmatched to a customer need
- An experiment is planned to test whether customers will pay
The Three Levels of Fit¶
| Level | Meaning | How to verify |
|---|---|---|
| Problem–Solution Fit | The two sides line up on paper | Team analysis plus interviews confirming the pains are real |
| Product–Market Fit | The market proves it wants this through behavior | Usage, retention, repeat purchase, payment |
| Business Model Fit | The business can make money sustainably | Positive unit economics, scalable acquisition |
Many teams stop at level one and start spending heavily, which is the most common failure path. Fit on paper is a hypothesis; fit in the market is a fact.
Examples¶
Example 1: An invoicing tool for small accounting practices
- Jobs: invoice dozens of clients accurately and on time each month, and chase payment.
- Pains (ranked): ① data scattered across clients' systems, costing hours; ② chasing overdue payments manually; ③ mistakes when tax rules change.
- Gains: less reconciliation time; fewer overdue invoices; audit evidence available quickly.
- Pain relievers: ① direct integrations with common bookkeeping software; ② automatic detection of overdue invoices with draft chase emails; ③ tax rules updated automatically.
- Gain creators: one-click export of an audit-ready evidence pack.
- What the canvas changed: the team had planned a "multi-dimensional business reporting" feature, but it matched none of the top-ranked pains or gains, so it was postponed. This is the canvas at its most useful: helping you decide what not to build.
Example 2: A fitness app for beginners
- Jobs: functional — "exercise regularly"; social — "not look clueless at the gym"; emotional — "not feel defeated by failing".
- Pains: don't know where to start; afraid of injury from bad form; give up after a few days.
- Gains: see visible progress; workouts that don't take long.
- Value map: beginner-only 15-minute plans (answers "no time" and "don't know where to start"); demonstration videos with common-mistake callouts (answers "afraid of bad form" and "look clueless"); streaks and milestone reminders (answers "give up" and "see progress").
- Note: the social and emotional jobs often determine retention more than the functional one, and are the ones product teams most often miss.
Example 3: Using the canvas to find a mismatch
A team built a "full-featured analytics platform" for small businesses, marketed on "50+ chart types and complete customization". After drawing the customer profile they found the primary job was "report key numbers to the boss at Monday's meeting" and the primary pain was "not knowing which metrics to look at". Fifty chart types didn't relieve that pain; it made it worse. The team repositioned the product around industry metric templates and a one-click weekly report. The capabilities didn't change; the value proposition did.
Common Mistakes¶
- Filling in the left side first. Starting from your product's strengths leads you to find exactly the pains your product happens to solve.
- Imagining the customer profile. A canvas without interviews is just the team's assumptions, drawn more neatly.
- Writing features as customer jobs. "Log meals in our app" is a feature; "manage my weight" is the job.
- Trying to address every pain. A product that tackles all of them usually solves none of them well.
- Several segments on one canvas. Use one canvas per segment, or the pains and gains will contradict each other.
- Treating paper fit as success. Lining up the two sides creates a hypothesis that still needs market evidence.
Value Proposition Canvas vs. Related Tools¶
| Value Proposition Canvas | Business Model Canvas | Lean Canvas | Empathy Map | |
|---|---|---|---|---|
| Focus | Does the offering match customer needs? | How does the whole business work? | What are the riskiest startup assumptions? | What is the user's inner world? |
| Scope | Magnifier on two blocks | Nine blocks, full picture | Nine blocks, risk-oriented | One user type |
| Best stage | Defining and sharpening the value | Designing and describing the model | Early, high-uncertainty ventures | Synthesizing research |
A common sequence: empathy map to synthesize research → value proposition canvas to sharpen the value → lean canvas or business model canvas to design the business.
Frequently Asked Questions¶
How does the Value Proposition Canvas relate to the Business Model Canvas?
It expands two of its blocks, Value Propositions and Customer Segments. Working through them in detail first makes the whole Business Model Canvas far stronger.
How much research does the customer profile need?
Usually 10–20 in-depth interviews with target customers surface the main jobs, pains and gains. What matters more than the number is asking about specific past experiences rather than hypotheticals.
Aren't pains and gains two sides of the same thing?
They overlap but aren't identical. Removing a pain doesn't automatically create a gain: "invoices are never wrong" and "I can forecast cash flow" are different things. Listing them separately reveals more opportunities.
How do I use it for B2B products?
In B2B the user, the decision-maker and the payer are often different people with different jobs and pains. Draw a canvas for each key role, then check how one value proposition can answer all of them.
What do I do after filling in the canvas?
Design experiments to test the critical assumptions: does the target customer really have this pain, and will they pay for your solution? See Lean Startup and MVP.
Extensions and Connections¶
- Business Model Canvas: design the full business model once the value proposition is clear.
- Lean Canvas: the one-page tool for capturing and iterating early-stage hypotheses.
- Lean Startup: the method for validating what the canvas assumes.
- Kano Model: classifies gains into must-be, performance and attractive, guiding feature priority.
- Empathy Map and User Persona: research synthesis tools that feed the customer profile.
- Design Thinking: the canvas is often used in the Define stage.
Reference: Alexander Osterwalder, Yves Pigneur and colleagues set out the Value Proposition Canvas in Value Proposition Design (2014), the companion volume to Business Model Generation.