Value Proposition Canvas: Template and How to Pressure-Test It

The Value Proposition Canvas is one of the few startup frameworks that earns its reputation. Developed by Alexander Osterwalder and colleagues at Strategyzer, it forces you to describe your customer before you describe your product, and then check whether the two actually fit.

The trouble is that most canvases get filled in once, in a workshop, from the founder's imagination, and never touched again. A canvas written that way is a list of hopes. This guide gives you a usable template, a worked example, and a set of tests that turn those hopes into claims you can check with real customers.

How the canvas is structured

The canvas has two halves.

The customer profile (usually drawn as a circle) describes one customer segment:

• Customer jobs: what they are trying to get done. Functional jobs (send invoices), social jobs (look professional to clients) and emotional jobs (stop worrying about cash flow).
• Pains: what annoys them, blocks them or carries risk before, during or after the job.
• Gains: the outcomes and benefits they want, including ones they would not think to ask for.

The value map (usually drawn as a square) describes your offer:

• Products and services: what you actually provide.
• Pain relievers: how the offer reduces specific pains.
• Gain creators: how the offer produces specific gains.

"Fit" is when your pain relievers and gain creators line up with the pains and gains that matter most to the segment. Not all of them. The ones that matter most.

The template

Copy this into a doc. Fill in the customer profile first, and do not touch the right-hand side until you have.

Segment: one specific group, described by what they do, not demographics. "Mobile dog groomers with one van" rather than "pet businesses".

Customer jobs (rank by importance): 1. 2. 3.

Pains (rank by severity; note how often each occurs): 1. 2. 3.

Gains (rank by how much they would value it): 1. 2. 3.

Products and services:

Pain relievers (each one must name the pain it relieves):

Gain creators (each one must name the gain it creates):

Evidence column: beside every entry, write where it came from: an interview, observed behaviour, a support ticket, or "assumption".

That last column is the one most templates leave out, and it is the one that matters. It shows you, at a glance, how much of your canvas is real.

A worked example (hypothetical)

Here is an invented canvas for a quoting app aimed at small residential electricians.

Segment: sole-trader and two-person electrical businesses doing residential work.

Top jobs: produce a quote on site or the same evening; win the job; get paid a deposit before buying materials.

Top pains: quoting at night after a full day on the tools; losing jobs to whoever quotes first; materials prices changing between quote and job; chasing deposits.

Top gains: quote sent before leaving the driveway; client accepts and pays deposit from the same link; fewer evenings on paperwork.

Pain relievers: saved templates for common jobs (switchboard upgrade, downlight install); materials list that pulls current supplier prices; deposit request built into the quote.

Gain creators: send from a phone in under five minutes; acceptance notification; quote converts to invoice without retyping.

Notice what is missing: a dashboard, reporting, team scheduling. They might matter later, but they do not relieve the top pains of this segment, so they do not belong on this canvas.

Five pressure tests

Once the canvas is filled in, run it through these. Each one is designed to expose a weak spot.

1. The evidence count. Count how many entries on the customer profile are marked "assumption". If it is more than half, stop designing and go and talk to customers. Ask about the last time they did the job, not what they would like in general.

2. The ranking test. Ask five people from the segment to rank your top three pains. If their order does not match yours, your value map is optimising for the wrong problem.

3. The "instead" test. For every top pain, write what the customer does about it today. If the answer is "nothing much", the pain may be real but not urgent enough to pay for. The electrician who already uses a spreadsheet template and is "mostly fine" is a harder sale than one who is losing jobs.

4. The one-sentence test. Try to write the promise in one sentence using only the top job, top pain and your main pain reliever: "Electricians send a priced quote from the driveway, so they stop losing jobs to faster competitors." If you need three sentences, your canvas has not prioritised.

5. The behaviour test. Put the one-sentence promise in front of real prospects in a form where they have to act: sign up for a trial, book a call, apply for a beta seat. Interest in conversation is cheap. Action is evidence.

When to redraw it

A canvas is worth redrawing whenever one of three things happens: you notice your best customers look different from the segment you wrote down, a pain you ranked highly turns out to be something people tolerate happily, or a competitor starts relieving your top pain as well as you do. Keep the old version. Comparing the two shows you how your understanding has changed, which is useful when you explain a pivot to a co-founder or an investor.

Common mistakes

• Mixing segments. A canvas that serves "small businesses" serves no one. If jobs or pains differ, draw a second canvas.
• Describing features as gains. "Has a mobile app" is a product. "Can quote without going back to the office" is a gain.
• Filling the value map first. You will unconsciously write the customer profile to match what you have already built.
• Treating it as finished. The canvas is a hypothesis sheet. Update it after every round of feedback.

Testing your canvas with real businesses

The fastest way to fill the evidence column is to watch real businesses use an early version of the product and tell you where it helped and where it did not.

On LetsBeta, you can list a build and let businesses in your category apply to try it. You accept the ones that match your segment. Each Early Adopter sends a mid-trial and end-of-trial report on what worked, what broke, whether they would pay and at what price. Read those reports against your canvas: every "this saved me time" confirms a gain creator, and every "I still had to…" is a pain you have not relieved yet.

You can also browse demand posts, where businesses describe the software they need in their own words. That language is often a better source for the jobs and pains column than anything you would write yourself.

For turning the canvas into a positioning statement, see Startup Positioning: A 60-Minute Framework and How to Explain Your Startup in One Sentence.

In brief

Describe the customer first, rank everything, mark what is evidence and what is guesswork, and make prospects act on your one-sentence promise. A canvas you have tested is worth ten you have only drawn.

List your build and start collecting evidence.