Value proposition design

Value Proposition Design

Customers do not buy features; they hire an offering to make progress on a job, relieve a pain, or achieve a gain — and they pay for perceived value, not for your costs. This skill articulates that value precisely, prioritizes which needs to serve, and quantifies the value so it can anchor pricing and messaging. A vague value proposition is the root cause of weak pricing power and generic positioning.

Trigger

User asks for a value proposition, value prop canvas, customer needs/jobs analysis, benefit prioritization, Kano analysis, reasons-to-believe, or wants to convert features into customer value or justify a premium. Also trigger before pricing or message-drafting when the value story is not yet explicit.

Inputs

1. Offering — product/service and its notable features/capabilities
2. Target segment — who exactly (pull from STP if available); B2B roles differ from B2C individuals
3. The job the customer is trying to get done — functional, emotional, social
4. Alternatives the customer uses today (including "do nothing")
5. Evidence available — testimonials, data, benchmarks, case results (for proof and quantification)

Process

1. Understand the customer (the "circle")

Profile the target using Jobs-to-be-Done, then pains and gains:

• Customer jobs — what they are trying to accomplish. Split into functional (the task), emotional (how they want to feel), and social (how they want to be seen). In B2B, separate the organization's job from the individual buyer's job — they differ and both must be won.
• Pains — obstacles, risks, costs, and bad outcomes before/during/after the job (undesired results, blockers, frustrations).
• Gains — desired outcomes and benefits, from required minimums to unexpected delights.

Rank jobs, pains, and gains by importance/severity to the customer. Insignificant ones are distractions.

2. Map the offering (the "square")

Connect the offering to the profile:

• Products & services the value proposition is built on
• Pain relievers — how the offering eliminates or reduces the ranked pains
• Gain creators — how it produces the ranked gains

Achieve fit: a value proposition fits when your pain relievers and gain creators address the ranked-important jobs, pains, and gains — not every one, but the ones that matter most. Explicitly flag mismatches (relievers/creators that serve trivial needs, and important pains/gains left unaddressed).

3. Classify requirements with the Kano model

Not all attributes create satisfaction the same way. Classify each to decide where to invest and what to communicate:

Category	Effect	Rule
Must-be (basic)	Absence causes strong dissatisfaction; presence merely avoids it	Table stakes — deliver, don't brag
Performance (one-dimensional)	Satisfaction scales linearly with how much you deliver; customers seek and compare it	Compete and communicate here
Attractive (delighters)	Presence delights; absence is not missed (often unexpected)	Differentiators — spotlight them
Indifferent	No effect either way	Stop spending on these
Reverse	More of it lowers satisfaction for this segment	Watch for segment differences

Delighters decay into performance and then into must-be over time (yesterday's wow becomes today's baseline), so refresh them. Use Kano to avoid the two classic errors: over-investing in must-be attributes, and burying delighters that could differentiate.

4. Quantify the value

Perceived value is what sets the price ceiling, so quantify it wherever possible. Build the value in the customer's own economic terms:

• Reference value — the cost of the customer's best alternative (competitor price, in-house cost, or status quo cost).
• Differentiation value — the monetary worth of your advantages: revenue gained, cost avoided, time saved, risk reduced, quality improved. Translate each benefit into a number the customer would recognize (e.g., "cuts reporting time 40% = ~X hours = ~€Y/year").
• Total economic value = reference value + differentiation value. Price sits between cost (floor) and total economic value (ceiling); the gap between price and value is the customer's incentive to buy.

For B2B especially, express the value proposition as a business case, not adjectives. Where numbers aren't available, provide the value logic and the proof that would fill it in.

5. Assemble the value proposition & proof

Write the value proposition in a form the customer recognizes, then back every claim:

• Headline value proposition — one sentence: for [target], we help [do the job] by [what], resulting in [quantified outcome], unlike [alternative].
• Supporting benefits — 3-4, each tied to a ranked pain/gain and to a Kano category.
• Reasons to believe (proof) — data, case studies, testimonials, demos, guarantees, third-party validation for each benefit. An unproven claim is a liability, especially where superlatives invite challenge.
• Differentiation — the points of difference vs. alternatives, and the points of parity you must still match.

Output

Customer Profile

Ranked jobs (functional/emotional/social), pains, gains — for the organization and the buyer if B2B.

Value Map

Pain relievers and gain creators mapped to the ranked needs, with explicit fit/mismatch notes.

Kano Classification

Table of key attributes by category, with the invest/communicate/stop implications.

Quantified Value

Reference value, differentiation value, total economic value — with the calculation logic and the proof (or the proof still needed).

Value Proposition Statement

Headline + supporting benefits + reasons to believe + differentiation.

Handoff

What this implies for pricing (the value ceiling) and messaging (the story and proof).

Follow-up

Ask: "Would you like me to:

• Set pricing using this quantified value (value-based pricing)?
• Turn the value proposition into channel-ready messaging and content?
• Stress-test it against competitors' value propositions?
• Build the B2B business case / ROI model in more detail?"