Value Proposition Canvas

Describe one customer segment's world before you describe your offer, score your offer against it, then turn the fit into a statement customers can repeat, believe and test.

Practice, not research: the canvas is a practitioner design tool with no published empirical validation (Osterwalder, Pigneur, Bernarda & Smith, 2014). Its jobs language comes from jobs-to-be-done, practitioner theory with case-based support (Christensen, Hall, Dillon & Duncan, 2016). The scoring scales, the statement format and the message test on this page are rules of thumb and practitioner craft.

Use it when:

• You are designing or reshaping an offer and want to check it against what customers actually need.
• The team argues about features, or the message sounds generic, and you want the argument to move to customer pains and proof.
• A product sells less than expected and you suspect it solves a pain customers rank low, or that nobody can repeat what you promise.

Skip it when:

• You do not yet know which segment to focus on: start with 6.1 Who Are Our Customers.
• The proposition is done and you need to place it against competitors: go to 6.8 Positioning Map.

The canvas rests on one claim: value is the fit between two sides that you describe separately. One side is the customer's world (jobs, pains, gains). The other is your answer (products, pain relievers, gain creators). A value proposition exists only where the two connect (Osterwalder, Pigneur, Bernarda & Smith, 2014). The jobs language comes from jobs-to-be-done: customers take on a product to make progress in a given situation, and the social and emotional sides of that progress count as much as the practical one (Christensen, Hall, Dillon & Duncan, 2016).

Both are practitioner frameworks. No test of the canvas has been published, and jobs theory rests on cases. What makes the exercise pay is order and confrontation: customer before offer, ranking before answers, a score that names gaps, and a statement that must survive proof and a customer saying it back.

One canvas, one segment. Write what the customer is trying to get done, what hurts and what they want, in their words. Rank each from 1 to 5 by how much it matters to the customer, not by what you can fix. If you have a social or emotional job, make it the job. The optional prompt bank helps you list.

Strong answer: Job: "Get the weekly delivery schedule out by Thursday without calling every driver," plus the wish to go home on Friday not worrying about Monday. Pain: "a driver calls in sick and the schedule is redone by hand," rank 5, named by four of five interviewees (illustrative). Not: "Manage logistics efficiently."

Segment this canvas is for:

Real alternative (a rival, a workaround, or doing nothing):

Illustrative example: the business and all numbers are made up.

A regional accounting firm in Tampere offers a monthly bookkeeping package to small construction firms. The partner works through the template after six client meetings.

Step 1: top job: "Know each month whether a project is making money, without reading a ledger." Top pain: receipts arrive in a shoebox at quarter end (rank 5). Top gain: a one-page project result (rank 4). Alternative: the client's own spreadsheet.

Step 2: the receipt app scores 3 for the pain, because site foremen do not use it, so 15. The report is by company, not by project: 4 × 2 = 8. Biggest gap: no per-project report.

Step 3: "For small construction firms that need to know project profit monthly, our bookkeeping package delivers a one-page result per project, unlike a spreadsheet, so the owner stops guessing."

Step 4: benefit: no surprises at quarter end. Proof: three clients' monthly reports, strength 3.

Step 5: four of five said it back; one doubted the "per project" claim.

The partner builds the per-project report before marketing the package further.