Value Proposition Canvas: build what customers buy, not what you imagine

Most founders pitch their product like this: “We have real-time sync, custom dashboards, API access, role-based permissions, and Slack integration.” That’s a feature list. It tells the customer what you built. It tells them nothing about why they should care.

Customers don’t buy features. They buy solutions to problems they already have. The Value Proposition Canvas — created by Alexander Osterwalder as a companion to the Business Model Canvas — forces you to see your product through the customer’s eyes [1].

Two circles. The right circle is the customer. The left circle is your product. When they overlap, you have product-market fit. When they don’t, you have a feature nobody asked for.

The customer profile (right side)

Fill this side first. If you fill the product side first, you’ll unconsciously justify features instead of questioning them.

Customer jobs

What is the customer trying to accomplish? Not “what problem do they have” — what are they doing (or trying to do)?

Jobs come in three types:

Functional jobs — the task they need to complete.

• “Reconcile inventory across 3 sales channels every Monday”
• “Generate a monthly financial report for my board”
• “Onboard new team members without breaking the workflow”

Social jobs — how they want to be perceived.

• “Look competent in front of investors”
• “Show my team I’m organized”
• “Be seen as innovative in my industry”

Emotional jobs — how they want to feel.

• “Feel confident that nothing is slipping through the cracks”
• “Stop worrying about cash flow at 2am”
• “Feel in control of a growing business”

The emotional and social jobs are the ones your marketing should address. The functional jobs are the ones your product must solve.

Customer pains

What frustrates them about completing these jobs? What are the risks, obstacles, and negative outcomes they want to avoid?

Rank pains by severity. A pain that costs $50,000/year in lost revenue ranks higher than one that wastes 20 minutes weekly. You can’t address every pain in your MVP — address the ones that hurt the most.

Pain	Severity	Current workaround
Inventory mismatches cause overselling	$12K/quarter in refunds	Manual spreadsheet check every morning
Board report takes 2 full days to compile	16 hours/month of founder time	Copy-paste from 4 different tools
New hires break existing workflows	2-week onboarding, 3 incidents/month	Tribal knowledge + Loom videos

Customer gains

What outcomes would make them happy? What would exceed their expectations?

Gains also rank: required gains (must have), expected gains (should have), desired gains (nice to have), and unexpected gains (delighters).

Focus your MVP on required and expected gains. Desired and unexpected gains are for version 2.

The value map (left side)

Now map your product to the customer profile.

Products and services

List every product, feature, and service you offer. Be granular — not “analytics dashboard” but “real-time revenue dashboard with cohort breakdown.”

Pain relievers

For each customer pain, which product feature addresses it?

Customer pain	Pain reliever (feature)	How it helps
Inventory mismatches	Auto-sync across channels (real-time)	Eliminates manual reconciliation
Board report takes 2 days	One-click report generation	Pre-built templates pull live data
New hires break workflows	Role-based permissions + guided onboarding	New users can’t access dangerous features

If a pain has no corresponding pain reliever, either you need to build something or accept that your product doesn’t address that pain. Both are valid — but you need to know which pains you’re deliberately ignoring.

Gain creators

For each desired customer gain, which feature creates it?

Customer gain	Gain creator (feature)	Result
Feel confident nothing slips	Real-time alerts for anomalies	Proactive notification before problems escalate
Look competent to investors	Professional automated reports	Board-ready output in 5 minutes
Spend less time on ops	Dashboard with everything in one view	Single screen replaces 4 tools

The fit test

This is the moment most founders resist. They’ve imagined features for months. They’ve sketched wireframes. They’ve told their co-founder about the social sharing button. And now the canvas says: nobody asked for this. Cut it.

Cut it.

The canvas isn’t telling you the feature is bad. It’s telling you the feature doesn’t map to a validated customer need. You might be right that customers will love it eventually. But you can’t validate that yet, and building unvalidated features is the most expensive mistake in product development.

How VPC connects to your product-market fit work

The Value Proposition Canvas is the operational version of product-market fit validation. PMF tells you whether you have a match between product and market. The VPC tells you where the match is strong, where it’s weak, and what to build next.

Use it in this sequence:

1. Interviews — Talk to 15-20 potential customers. Map their jobs, pains, and gains from their words, not yours.
2. VPC mapping — Plot the canvas. Identify the 3-5 pain relievers and gain creators that appear in most conversations.
3. MVP scope — Build only the features that map to validated pains and gains. This connects directly to the Solution block in your Lean Canvas.
4. Iterate — After launch, track which features get used. Features with high adoption validate the mapping. Features nobody uses mean the pain wasn’t as severe as customers said — or your solution doesn’t address it well enough.

The trap: building for imagined pains

The most dangerous version of the VPC is one filled out at a whiteboard without talking to customers. If you filled in the customer pains from your own imagination, the entire canvas is fiction.

Validation sources (in order of reliability):

1. Direct customer interviews — “Tell me about the last time you dealt with [problem]”
2. Support tickets and reviews — what are they complaining about? What do competitor reviews say?
3. Usage data — if you have an existing product, which features get used? Which get ignored?
4. Your intuition — valid as a hypothesis, worthless as a conclusion

---

We run Value Proposition Canvas sessions with founders and turn the output into product specs. The canvas maps the “what” and “why.” We build the “how.” Let’s map your product.

References

[1] A. Osterwalder, Y. Pigneur, G. Bernarda, A. Smith, Value Proposition Design, 2014. Wiley.