The Value Proposition Canvas is a two-sided template for checking whether what you are building matches what a customer needs. One side profiles the customer as jobs, pains and gains. The other maps your offering as products and services, pain relievers and gain creators. Fit is achieved when specific items on your side address specific items on theirs, which is a stricter test than most filled-in canvases pass.
When you have research about a customer and want to check your offering against it item by item. It is a fit-checking tool, so it needs a filled customer profile from evidence; run on assumption it produces a tidy diagram confirming what you already believed.
What the Value Proposition Canvas is
The Value Proposition Canvas is a two-sided template for checking whether what you are building matches what a customer actually needs. It was published in 2014 by Alexander Osterwalder, Yves Pigneur, Greg Bernarda and Alan Smith in Value Proposition Design, and it is a zoom-in on two blocks of their earlier Business Model Canvas.
The customer profile describes the person: the jobs they are trying to get done, the pains they experience, and the gains they want. The value map describes your offering: your products and services, your pain relievers and your gain creators.
Fit is what happens when specific items on your side address specific items on theirs. Not a general sense that the two halves are about the same subject, which is what most completed canvases actually demonstrate.
- Two sides, filled in one order Customer first, always
Fill your own side first and everything you write about the customer bends to match what you already have.
- Three items per side And they correspond
Jobs, pains, gains against products, pain relievers, gain creators.
- Fit is line-by-line Not a vibe
Each reliever points at a named pain. Relievers with nothing opposite them are features you built for yourself.
- Fit is not willingness to pay The canvas cannot see it
Addressing a confirmed pain says nothing about whether relief is worth money.
Why it matters
Most product decisions are made in the value-map language and never translated. A team discusses features, integrations and roadmap, all of which are statements about the left side, and the right side is carried around in people’s heads as an impression.
Putting both on one page forces the translation, and the translation is where the gaps appear. The usual result of an honest first pass is several features nothing on the customer side asked for, and one or two severe pains nothing addresses.
Both discoveries are unwelcome and both are the point. If your first pass comes out tidy, you have filled in the customer side from the product side. That is the most common way to complete this exercise and learn nothing from it.
The two sides
What are they trying to get done? Functional, social and emotional.
Decide what to build next, and be able to defend the decision to the team.
What goes wrong, gets in the way, or carries risk. Ranked, not listed.
Severe: cannot defend the prioritisation. Moderate: feedback arrives in five places.
Outcomes they want, including ones they would not think to ask for.
Visible proof that customer input changed the roadmap.
What you actually offer. The only block that is a plain list.
Feedback inbox, automatic summarisation, draft spec generator.
How each specific pain is reduced. Points at a named pain or it does not belong.
Draft spec generator answers "turning feedback into something engineering can act on".
How each specific gain is produced. Beyond neutral, not back to it.
Auto-generated changelog showing which customer request drove which release.
Fit is drawn as lines between specific items. Here 'draft the spec automatically' answers 'turning feedback into something engineering can act on'. Nothing yet answers 'defending the prioritisation to the team', which is the most severe pain on the profile, and that gap is the most useful thing on the canvas.
The order matters more than the content
Fill the customer profile completely, from research, and finish it before you look at your own side.
This sounds procedural and it is the single most consequential rule in the tool.
Profile filled from interviews, finished, then the value map written against it.
Result: several features with nothing opposite them, and one severe pain nothing addresses. Both are findings.
Offering listed, then the customer profile written while the features are in mind.
Result: excellent fit, every line connected, nothing learned. Looks identical on the wall.
Cite a source next to every item on the customer side. It is the only thing that survives on the page to distinguish the two.
A team that maps its offering first will write a customer profile shaped to match, because the features are already in mind and every pain that comes to hand is one the product happens to address.
When to run it
- You have interview research and want to check your roadmap against it.
- The team discusses features constantly and customer pains rarely.
- You suspect you are building things nobody asked for.
- A competitor keeps winning deals and nobody can say on what.
- You are writing positioning and need the customer language for it.
- You have no customer research yet. Use The Mom Test →
- You need the pains ranked by how much they hurt. Use Emotional Friction States →
- You want to know what they are hiring a product to do. Use Jobs to be Done →
- You need to know whether relief is worth paying for. Use Van Westendorp →
Against the alternatives
Does what we offer correspond, item by item, to what they need?
Gives you: Drawn connections, and the visible misses on both sides
What progress are they hiring something to make?
Gives you: A job statement. Sharper about why anyone switches
How does the whole business fit together?
Gives you: Nine blocks. This canvas is a zoom-in on two of them
Which of these pains actually hurt enough to act on?
Gives you: A ranking. The canvas lists pains and does not rank them
When it won’t help you
- A canvas filled from assumption looks exactly like one filled from research
Nothing on the finished diagram records where any item came from. A team can complete all six blocks in an afternoon with no customer contact and produce something that reads as evidence.
Instead: Cite a source next to every item on the customer side. Anything without one is a hypothesis, and marking it so is what keeps the canvas honest.
- It has no concept of magnitude
Every pain occupies the same amount of space on the diagram. A catastrophic risk and a minor irritation sit side by side looking equally important, and teams reliably address whichever is easiest.
Instead: Rank the pains before you map relievers, and let the ranking rather than the ease decide.
- Fit is not willingness to pay
You can demonstrate that your offering addresses confirmed pains and still find nobody will pay for the relief. The canvas contains no price, no budget and no buyer, and it cannot notice any of the three missing.
Instead: Test the price separately. Fit is a precondition for a sale, not evidence of one.
- It describes a moment, not a decision
The canvas shows a static correspondence. It says nothing about what triggers someone to look for a solution, what holds them with their current one, or what they compare you against.
Instead: Pair it with the four forces from Jobs to be Done, which is where switching actually gets explained.
Further reading
- Osterwalder, Pigneur, Bernarda & Smith, Value Proposition Design (2014). The source.
- Osterwalder & Pigneur, Business Model Generation (2010). The wider canvas this zooms into.
- Jobs to be Done. Sharper on why anyone switches at all.
- The Mom Test. How to fill the customer side from evidence.
- Emotional Friction States. Ranking the pains the canvas lists flat.
- Van Westendorp. Whether the relief is worth money.
How to apply Value Proposition Canvas
- 1
Fill the customer profile first, and finish it before you look at your own side
Jobs, pains and gains, from interviews rather than from imagination. Doing your own side first is the single most common sequencing error, because everything you then write about the customer will be shaped to fit what you already have.
- 2
Write jobs as things the customer is trying to get done
Functional, social and emotional. Not tasks inside your product. 'Publish a roadmap' is a job; 'log into the dashboard' is a step in your interface, and a profile full of those describes your product rather than their work.
- 3
Rank the pains and gains rather than listing them
An unranked list of fifteen pains is unusable, because it implies they matter equally and they do not. Mark which are severe and which are nice-to-have, and be prepared for the ranking to disagree with your roadmap.
- 4
Map your offering as responses, not as features
Pain relievers answer specific pains. Gain creators answer specific gains. If you cannot say which item on the customer side a feature responds to, that is a finding rather than an oversight.
- 5
Test fit line by line and leave the misses visible
Draw the connections. A pain reliever with no pain opposite it is something you built for yourself. A severe pain with nothing pointing at it is either your next roadmap item or the reason a competitor keeps winning.
- 6
Check the fit is one a customer would pay for
Fit on paper means your offering addresses their stated pains. It does not mean the relief is worth money, and the canvas has no mechanism for telling the difference. That question is answered by a price test, not by the diagram.
Common mistakes
- **Filling your own side first.** Everything you then write about the customer gets shaped to match what you already have, and the canvas confirms a decision instead of testing it.
- **Writing jobs as tasks inside your product.** 'Log into the dashboard' is a step in your interface. 'Show the team what we decided and why' is a job. A profile full of the first kind describes your product rather than their work.
- **Listing pains without ranking them.** Fifteen unranked pains implies they matter equally. They do not, and the ranking frequently disagrees with the roadmap, which is exactly the value.
- **Claiming fit from general resemblance.** Fit is line-by-line correspondence between specific items, not a sense that the two halves are broadly about the same thing.
- **Hiding the misses.** A severe pain with nothing pointing at it is the most useful thing on the canvas. Erasing it to make the diagram look complete throws away the finding.
- **Treating fit as validation.** The canvas can show your offering addresses their pains and say nothing about whether relieving them is worth paying for.
How ShipFit operationalizes this
ShipFit runs the Value Proposition Canvas in Stage 4 (How to Win?). The customer-profile side is built from earlier stages rather than from a workshop: Stage 2 (Who Pays?) supplies the buyer and their context, and Stage 3 (What Hurts?) supplies pains ranked by frequency and intensity rather than listed flat. Stage 4 then generates solution approaches against that ranked profile, which is the value map constructed to answer specific items.
ShipFit runs 55 frameworks across 9 decision stages
Value Proposition Canvas is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What is the Value Proposition Canvas?
What is the difference between pains and gains?
What does 'fit' mean on the canvas?
Which side of the canvas should I fill in first?
Does fit on the canvas mean people will buy?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
Adele Revella's Five Rings of Buying Insight, the questions that produce each one, and why a persona built without buyer interviews informs no decision.
Rahul Vohra's method for measuring product-market fit and improving it: the 40% benchmark, the survey mechanics that make it comparable, and the roadmap it produces.
Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.
Most early-stage competitive analysis is a 2x2 with your product in the top-right quadrant. The real version is harder, more boring, and tells you whether you can actually win.
How many months until the bank account hits zero?
The state where a product satisfies a strong market demand from a specific buyer segment such that customer pull on the product exceeds the founder's effort to push it. Coined by Marc Andreessen in 2007 ('the only thing that matters'). Operational measure: 40%+ of active users would be 'very disappointed' if they could no longer use it (Sean Ellis test, popularized by Rahul Vohra at Superhuman in 2018). Below 40%, you don't have PMF yet, regardless of revenue or press.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
Replit turns ideas into deployed apps in minutes. Describe it, publish it. ShipFit makes 9 decisions before you open Replit so the deploy is the right thing. ShipFit even exports a Replit-optimised prompt that encodes every decision. Use both. ShipFit first.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.