Innovation & product
Value Proposition Canvas
A two-part canvas that maps a customer profile (jobs, pains, gains) against a value map (products and services, pain relievers, gain creators), so a team can state, test and improve the fit between what it offers and what one customer segment actually cares about.
Also known as VPC, Customer Profile and Value Map. First set out by Alexander Osterwalder, Yves Pigneur, Gregory Bernarda and Alan Smith in 2014; the primary source is cited in full below.
Where this is contested
Not seriously contested. Osterwalder, Pigneur, Bernarda and Smith codified the canvas in Value Proposition Design (2014), though earlier versions circulated through Strategyzer from around 2012 under slightly different labels before the book fixed the current form.
- Format
- Canvas
- Level
- Product
- Best for
- Understand customers · Position against competitors
- Decision stage
- Diagnose · Explore options · Plan
- Difficulty
- Introductory
- Time to apply
- An hour for a first draft with a well-briefed team; days to weeks to test it against real customers.
Plate · The model
The components
Customer jobs
The things the customer is trying to get done in work or life: functional tasks, social positioning and emotional states. Jobs are ranked by importance, and the important ones are often not the ones the product category assumes.
Signals of strength
Expressed as the customer's task, not your product's function · Functional, social and emotional dimensions all captured · Ranked by importance to the customer, with evidence · Would still be true if your company vanished tomorrow
Pains
The bad outcomes, obstacles and risks the customer experiences before, during and after getting the job done. Good pain statements are concrete enough to measure and severe enough to pay to remove.
Signals of strength
Specific and observable, not 'wastes time' but where and how much · Includes obstacles that stop the job starting and risks of it going wrong · Ranked by severity · Traceable to a real quote, ticket or observed behaviour
Gains
The outcomes and benefits the customer wants: some required for any solution to count, some expected, some desired, and some that would delight precisely because nobody expects them. Gains are more than pains inverted.
Signals of strength
Distinguishes required and expected gains from desired and unexpected ones · Ranked by relevance · Includes how the customer measures success in their own terms · Not simply each pain rewritten with 'no more' in front
Products and services
The concrete list of what the value proposition is built on: the products, services and supporting items the customer can see, buy or use. This is a list, not an argument; the argument lives in the relievers and creators.
Signals of strength
Everything listed actually exists or is genuinely planned · Distinguishes core offer from supporting services · Comprehensible to the customer without translation · Short; a proposition built on forty items has not decided what it is
Pain relievers
How, specifically, the products and services eliminate or reduce particular pains in the profile. Relievers earn their place by pointing at a ranked pain; the best propositions relieve the severest pains, and admit which ones they leave alone.
Signals of strength
Each reliever names the pain it addresses · Concentrated on the top-ranked pains · States how the pain shrinks, not just that it does · The team can say which pains are deliberately out of scope
Gain creators
How the products and services produce the outcomes and benefits the customer expects or desires. Creators are distinct from relievers: removing a frustration and producing a positive outcome are different promises, sold differently.
Signals of strength
Each creator names the gain it produces · Focused on required and desired gains rather than nice-to-haves · Not a duplicate of the pain relievers with the polarity flipped · At least one creator addresses an unexpected gain worth talking about
When it earns its keep
- You are shaping a new product or feature and need to articulate why anyone would buy it before committing to build, in terms specific enough to be wrong.
- Your messaging is not landing and you want to restate the offer in the customer's terms, anchored in ranked jobs, pains and gains rather than in your feature list.
- You are zooming in on one customer segment of a Business Model Canvas to work out whether the value proposition block actually holds up.
- You are preparing customer discovery interviews and want explicit, prioritised hypotheses to test rather than an open-ended chat.
And when it doesn't
- You are designing a whole business. The canvas covers two of the nine Business Model Canvas blocks; channels, costs, revenues and partners all sit outside it.
- Product-market fit is already proven and the question is scaling operations or unit economics. The canvas has nothing to say about either.
- You have no route to customers to test with. Filled in from the boardroom alone, it becomes a wall of confident guesses with the epistemic status of a wish list.
- You are choosing which market to enter. Segmentation and targeting come first; the canvas assumes a segment has already been chosen.
How to run it
Before starting, gather the inputs the analysis depends on:
- One named customer segment per canvas. Blending segments averages away exactly the specificity the tool exists to create.
- Evidence about that segment: interview notes, support tickets, sales-call recordings, churn reasons, not just team opinion.
- An honest list of the alternatives customers use today, including spreadsheets, workarounds and doing nothing.
- A realistic view of the products and services you can actually deliver, so the value map describes an offer rather than an aspiration.
- Willingness to rank: jobs by importance, pains by severity, gains by relevance. An unranked canvas defers every hard decision.
- 1
Choose one segment
Pick a single customer segment, ideally a specific role in a specific situation. In the canonical form the canvas is drawn as two facing shapes: the customer profile as a circle on the right, the value map as a square on the left, with fit read across the gap between them.
- 2
Profile the customer
Work the circle first and keep your product out of it. List the jobs the customer is trying to get done (functional, social and emotional), the pains that obstruct or annoy them, and the gains they require, expect or desire. Then rank each list. The profile should read as true even if your company never existed.
- 3
Map the value side
List your products and services, then state how they relieve specific pains and create specific gains. Every pain reliever and gain creator must point at a named item in the profile. Anything that points at nothing is a feature in search of a justification.
- 4
Check fit on paper
Compare the two sides. Do your relievers and creators address the top-ranked pains and gains, or only the convenient ones? Strike whatever addresses nothing important. No proposition addresses every pain and gain; a good one nails the few that matter most.
- 5
Test with customers
The canvas states hypotheses; interviews and experiments test them. Take the ranked profile to real customers and find out which jobs, pains and gains survive contact. Expect the ranking to change, and let it.
- 6
Iterate and connect
Revise the canvas as evidence arrives, and feed the surviving proposition back into the wider business model. Fit on paper, then fit in the market, then fit in a model that makes money: the canvas covers the first and helps structure the second.
Reading the result
A ranked, evidence-based profile of one customer segment, a value map explicitly linked to it, and a short list of fit hypotheses ready to test: which top pains the offer relieves, which top gains it creates, and which it deliberately ignores.
- Read fit across the middle: draw a line from each top-ranked pain and gain to the reliever or creator that answers it. Unanswered top items are the risk register; answered bottom items are probably wasted effort.
- The customer profile is the test of the value map, never the other way round. If the map looks strong and the profile looks thin, the profile is where the work is.
- Treat the whole canvas as claims awaiting evidence. Fit asserted on paper is the start of validation, and the ranking will move once customers get a vote.
A worked example
A payroll software startup maps fit for small construction employers
A UK startup building cloud payroll software decides to focus on small construction firms with five to thirty workers, currently running payroll on spreadsheets or through a local bureau. Before the next quarter of development, the founders build a canvas for the owner-manager who actually runs payroll, drawing on fifteen discovery interviews.
- Customer jobs
- Functional: pay a mixed crew of employees and subcontractors correctly every week, file Real Time Information returns with HMRC, operate CIS deductions, keep pension auto-enrolment compliant. Emotional: stop dreading Friday evening. Social: be known as the firm that never misses payday, which matters for holding good tradespeople. The interviews rank the weekly cycle and the CIS and PAYE mix as the defining jobs.
- Pains
- Weekly pay runs multiply every admin task by four against monthly-payroll norms; CIS subcontractors and PAYE employees sit in one workforce but in different regimes; late RTI filings risk HMRC penalties; the bureau charges per payslip and wants data by Wednesday for a Friday run; and timesheets arrive as texts and photos of scraps of paper. Ranked top: chasing and deciphering timesheets, then the CIS and PAYE split.
- Gains
- Required: HMRC-recognised filings that never miss a deadline. Expected: payroll finished in under an hour a week. Desired: seeing true labour cost per site while a job is still running, since pricing the next job is guesswork without it. Unexpected: the crew getting payslips on their phones without ringing the office.
- Products and services
- A cloud payroll application with weekly pay runs, a single engine handling CIS and PAYE together, HMRC-recognised RTI submission, timesheet capture that accepts forwarded photos and texts, and an employee payslip app. Flat monthly subscription rather than per-payslip pricing.
- Pain relievers
- Automatic RTI validation and filing removes the penalty risk; one workflow for employees and subcontractors dissolves the two-regime pain; photo and text timesheet import attacks the top-ranked pain directly; flat pricing removes the per-payslip meter that makes weekly cycles expensive at the bureau.
- Gain creators
- A labour-cost-per-job dashboard creates the desired estimating gain; a compliance audit trail creates the required assurance gain; the payslip app creates the unexpected gain and quietly ends the 'where's my payslip' calls. Nothing on the map currently creates the expected under-an-hour gain end to end, because timesheet chasing happens before the software's current starting point.
The read. Fit is strong where incumbents are weakest: weekly cycles and the CIS and PAYE mix, both priced and designed for monthly office payrolls elsewhere. But the honest reading is uncomfortable in two places. The top-ranked pain is timesheet chasing, which the roadmap treats as a nice-to-have importer, so the proposition should lead on timesheet-to-payslip in one evening or stop claiming the top pain. And the bureau delivers a gain the startup cannot yet recreate: a human who takes the blame when HMRC writes. The next round of interviews tests whether firms will trade that reassurance for speed and price, before more code gets written.
Pitfalls
- Filling in the value map first and reverse-engineering a customer profile to flatter it. The circle comes first, and it should read as true independent of your product.
- Listing features as gain creators without naming the gain each one creates. A creator that points at nothing in the profile is decoration.
- Writing vague pains. 'Saves time' has no severity and no test; 'three hours every Thursday deciphering photographed timesheets' does.
- Serving multiple segments with one canvas. An owner-manager and a payroll bureau have different jobs; averaging them produces a proposition for nobody.
- Treating a completed canvas as validation. It is a hypothesis sheet, and the authors are explicit that it works paired with testing.
- Mirroring: writing gains as pains inverted and gain creators as pain relievers repeated, which fills the boxes while adding no information.
What the critics say
The canvas has no place for competition or price. Fit is judged between one firm and one segment in isolation, yet a proposition can fit perfectly and still lose to an alternative that fits nearly as well at half the price. Users must bolt on competitive and pricing analysis from outside the tool.
Evidence that canvas-family tools drive outcomes is thin. In a study of 271 teams at an accelerator, Ladd found that greater use of the related Business Model Canvas showed no straightforward association with venture success, cautioning against treating diligent canvas completion as progress.
Ladd, T. (2018) 'Does the business model canvas drive venture success?', Journal of Research in Marketing and Entrepreneurship, 20(1), pp. 57-69.
The category boundaries blur in practice. Pains and gains, and therefore relievers and creators, frequently collapse into mirror images of each other, which suggests the six-box structure is less analytically distinct than it appears and can reward box-filling over thinking.
Work it through
Work the customer profile first: jobs, pains and gains for one segment, ranked and evidenced. Then build the value map against it and strike anything that touches nothing important. Your entries persist for this browser session and can be copied out as Markdown or printed.
0 of 6 blocks filled
Run it as a workshop
Work the Customer Profile circle first, jobs, pains and gains for one named segment only, and resist the pull to sketch the Value Map alongside it. The circle should describe the customer honestly whether or not your product exists at all.
Running order
| Name the one segment this canvas is for | 5 min |
| Customer jobs, ranked | 15 min |
| Pains and gains, ranked by severity | 20 min |
| Build the Value Map against the finished profile | 25 min |
| Strike anything that touches nothing important in the profile | 15 min |
| Total | 80 min |
You will need
- Two circle-and-square canvas printouts (Customer Profile and Value Map)
- Sticky notes for jobs, pains and gains
- Real customer quotes or research if available
- A second colour of marker reserved for striking through weak fit
Traps to avoid
- Sketching the Value Map first and reverse-engineering a customer profile that flatters it. The profile has to be built as though the product did not exist.
- Accepting vague pains. 'Saves time' has no severity and cannot be tested; push for the specific, measurable version.
- Listing product features as gain creators without naming which specific gain each one creates. An unlinked feature is decoration, not fit.
- Running this for more than one segment at once. One canvas, one segment; build a second canvas rather than blending two customers into an average nobody actually is.
Sources and further reading
- Osterwalder, A., Pigneur, Y., Bernarda, G. and Smith, A. (2014) Value Proposition Design: How to Create Products and Services Customers Want. Hoboken, NJ: John Wiley & Sons. ↗
- Strategyzer, 'The Value Proposition Canvas' (official tool page and downloadable canvas). ↗
- Osterwalder, A. and Pigneur, Y. (2010) Business Model Generation. Hoboken, NJ: John Wiley & Sons.
- Ladd, T. (2018) 'Does the business model canvas drive venture success?', Journal of Research in Marketing and Entrepreneurship, 20(1), pp. 57-69.