Value Proposition Canvas
The Value Proposition Canvas lines up what customers are actually trying to get done, their pains and desired gains, against what you offer to relieve those pains and create those gains, so a mismatch shows up before you've built anything.
Two three-row columns sit side by side, your offer on the left lined up against the customer's jobs, pains and gains on the right.
Reach for this when…
- You're about to build a feature and can't say which customer pain it solves.
- Sales keeps hearing 'nice product, not for us' and nobody knows why.
- You're rewriting messaging and the current version reads like a features list.
How to run it
- Map the customer profile: the jobs they're trying to do, the pains they hit, the gains they want.
- Map your value map: your products and services, what relieves those pains, what creates those gains.
- Check the fit: does each pain reliever match a named pain, each gain creator a named gain.
- Cut anything on your side with no matching customer entry.
- Test the sharpest matches with real customers before building further.
A worked example
Situation. Rami Haddad built TawlaGo, a restaurant booking and payments app in Beirut, Lebanon, adding features every time a client asked for one.
Applied. Running the canvas with his three biggest restaurant clients, he found their real pain wasn't bookings at all, it was no-shows eating their margin, and his app had no gain creator that addressed it directly.
Result. He built a simple deposit-on-booking feature aimed squarely at that pain. It became the single reason clients gave for renewing, ahead of every other feature combined.
The catch
The canvas is only as good as the customer research behind it; teams often fill in both sides from their own assumptions and call it validated. It also stops at fit, it doesn't tell you if customers will pay for the gains you've matched.
A canvas filled in without talking to an actual customer is a guess with a nice template.
Origin: Alexander Osterwalder & Yves Pigneur