School Me MarketingSMM
FoundationsAdvanced10 min deep read · 30-sec skim available

Value Quantification: Outcomes & Willingness to Pay

The canvas told you which pains matter. This is how you put numbers on them: scoring which outcomes are underserved at market scale, and measuring what their relief is worth in rupees. Value you haven't quantified is value you're guessing at twice — once when you build, once when you price.

⚡ Understand it in 30 seconds

  • Interviews rank pains; quantification prices them. Two instruments do the work: opportunity scoring tells you where value is underserved across a market, and willingness-to-pay measurement tells you how much the relief is worth. Build to the first, price to the second.
  • Ulwick's move: translate the job into outcome statements ('minimise the time it takes to…'), then survey each on importance and satisfaction. Opportunity = importance + (importance − satisfaction). Above 10, customers are waiting. Where satisfaction exceeds importance, they're overpaying for polish they never asked for — the classic opening for a cheaper disruptor.
  • Never ask 'would you pay ₹X?' — stated intent is a compliment, not a contract. Climb the same ladder as proposition testing: price-sensitivity surveys < trade-off (conjoint) choices < real pre-orders. Each rung costs more and lies less.
  • Fogg reads as the method in one bottle: the deodorant category's underserved outcome was 'sprays I actually get per can' — half of every rival was propellant. One quantified promise ('800 sprays, no gas') attacked the number head-on, and the number, not the fragrance, took market leadership.

Go deeper

The core idea

Start with the intuition, not the formula. A customer hires a product for a job, and every job decomposes into measurable outcomes — things the customer is trying to increase, decrease, or stabilise. 'Freshen up' is a job. 'Maximise the number of uses per bottle', 'minimise the time the fragrance takes to fade', 'minimise the chance of staining a shirt' — those are its outcomes. Outcomes are written with a direction, a metric, and a context, which is exactly what makes them surveyable at scale. The canvas (the Intermediate layer) found these in interviews, ranked by feel. Quantification asks a few hundred category buyers to rate every outcome twice: how important is this, and how satisfied are you today?

Those two ratings produce the opportunity landscape. Importance high and satisfaction high: table stakes — defend, don't invest. Importance high, satisfaction low: underserved — this is where innovation and premium pricing live, and the gap has a number (Ulwick's score: importance + max(importance − satisfaction, 0), with anything above ten a flashing light). Importance low, satisfaction high: overserved — the category is busy polishing what nobody weighs, which is exactly where a stripped-down entrant undercuts everyone (overservice is subsidised by every customer who never wanted it). The map turns 'we believe customers want…' arguments into a ranked queue of gaps, each one with a size.

Then price the gap — and here the discipline is refusing to ask directly. 'Would you pay ₹249?' collects politeness, not demand. The instruments climb in honesty: Van Westendorp's four questions (at what price is this a bargain, expensive, suspiciously cheap, out of the question) sketch the acceptable range cheaply; conjoint analysis forces respondents to trade features against price across repeated choices, recovering what each outcome is worth because nobody can stay polite to every option; and behavioural tests — deposits, pre-orders, a live price test — are the only rungs where money actually talks. The evidence ladder from proposition testing applies verbatim: say < click < use < pay.

The two numbers have to meet. An underserved outcome with no willingness to pay is a complaint, not a market (customers want queues shorter everywhere, but they'll pay to skip very few). Willingness to pay with no underserved outcome means you're re-selling satisfaction the incumbent already delivers — a price-war application form. The fundable quadrant is both: a scored gap and a priced relief. Fogg lived exactly there — waste was the category's most important unsatisfied outcome, the relief was worth a premium, and '800 sprays' let the buyer audit the promise standing in the aisle.

The business case

Why marketers care

It ends the loudest-voice-wins roadmap. Opportunity scores turn 'the founder likes it' and 'a big client asked' into positions on one ranked list — and the discipline cuts both ways, killing pet features that score as overservice while surfacing dull, valuable gaps nobody championed.

It connects product decisions to pricing power before the build, not after. If conjoint says the outcome is worth ₹40 a month and building it costs ₹60 a head to serve, the feature dies in a spreadsheet instead of in the market — the cheapest possible funeral.

And it's the honest counterweight to feature-count competition: markets are lost by overserving measured-but-unimportant outcomes while the important-unsatisfied one sits open. The score sheet shows where rivals' polish is actually vulnerability.

See it

The visual model

The opportunity landscape

Every outcome lands in a quadrant, and each quadrant is an instruction — build, defend, strip, or ignore.

Read this diagram as text

A two-by-two matrix plotting customer outcomes by importance (vertical axis, low to high) and current satisfaction (horizontal axis, low to high). Top-left, high importance and low satisfaction: underserved — innovate and price here. Top-right, high importance and high satisfaction: table stakes — defend but don't over-invest. Bottom-right, low importance and high satisfaction: overserved — the polish customers never asked for, and a disruptor's entry point. Bottom-left, low importance and low satisfaction: irrelevant — ignore.

The receipts

Where it comes from

Anthony Ulwick's outcome-driven innovation — 'Turn Customer Input into Innovation' (HBR, 2002) and What Customers Want (2005) — operationalising the jobs-to-be-done lens; Van Westendorp's Price Sensitivity Meter (1976); conjoint analysis from Green & Srinivasan's marketing-research work (1970s).

Ulwick's contribution was making jobs measurable. Christensen's theory says people hire products for jobs. Ulwick added the syntax — desired outcomes phrased as direction + metric + object — so a job becomes 50–150 surveyable statements rather than a narrative. His canonical case: Cordis, a medical-device maker, surveyed outcomes around angioplasty, built to the underserved ones, and its market share in the segment famously multiplied.

The pricing half is older. Van Westendorp's four-question meter (1976) remains the fast, cheap range-finder. Conjoint analysis became the professional standard because it infers value from forced trade-offs rather than stated opinion — respondents can flatter a feature, but they can't keep flattering it once it starts costing them things they want more.

The synthesis is the modern practice: opportunity scores decide where value should be created, willingness-to-pay measurement decides how much of it can be captured, and economic value to the customer (the pricing page's EVC) supplies the ceiling for rational buyers. Three instruments, one arithmetic of value.

Brands you know

Seen in India

Educational readings of familiar brands — how the concept helps you see what they do, not claims about their current campaigns.

Fogg

The challenger that took over Indian deodorants against global brands.

Its launch reads as outcome quantification in public: the category's cans were roughly half propellant, so the most important unsatisfied outcome — usable sprays per rupee — sat wide open. Fogg's no-gas format and '800 sprays' claim turned that gap into an auditable number, and the buyer could price the value standing right at the shelf: more sprays, same money. Fragrance variety, the axis rivals fought on, reads as the overserved quadrant funding the attack.

What to steal: The sharpest propositions are quantified outcomes — find the number the category hides, and make it your headline.

Tata Ace

The mini-truck that created India's sub-one-tonne cargo segment.

The product decisions read as outcome arithmetic for the last-mile operator: three-wheelers were unsatisfying on safety, load security, and driver dignity (important, unserved), while full trucks overserved on capacity the routes never used. Pricing reads as willingness-to-pay work — pitched where a driver-owner's daily earnings could carry the EMI, which is conjoint logic done on a notepad.

What to steal: Quantify value in the buyer's own P&L — the winning price is the one their arithmetic approves, not yours.

Beyond India

The global lens

Cordis

Ulwick's original medical-device case in angioplasty.

The team surveyed clinicians' desired outcomes, scored the landscape, and built specifically to the high-opportunity gaps rather than to the loudest feature requests — the case study credited with taking the product line from an also-ran to segment leadership, and the demonstration that made outcome-driven innovation a named method.

What to steal: Ranked outcome gaps outperform collected feature requests — customers are accurate about their struggles and unreliable about your roadmap.

Dollar Shave Club

The subscription razor that attacked a five-blade arms race.

The razor category is the textbook overserved quadrant: satisfaction on cutting performance had long exceeded its importance, while price frustration sat important and unsatisfied. The launch reads as a bet that customers would trade laboratory-grade blades they didn't value for money they did — overservice, priced honestly, is a competitor's budget.

What to steal: Audit incumbents for overservice: every outcome they gold-plate beyond importance is margin a simpler rival can hand back to the customer.

From theory to Monday morning

How to use it

  1. Write the outcome inventory

    From job interviews (the Intermediate layer's fieldwork), phrase 30–80 outcome statements with direction + metric + context: 'minimise the time it takes to reconcile a day's payments'. No solutions, no adjectives — outcomes describe the customer's success, not your feature.

  2. Survey importance and satisfaction at scale

    Put the inventory to 150–300 category buyers, each outcome rated on both scales. Compute opportunity scores, then sort. The deliverable is one ranked list with a line drawn at 10 — above it, gaps worth building for; below it, the polite decline you'll send stakeholders.

  3. Price the top gaps before building

    Run Van Westendorp for the range, conjoint if the decision is expensive, and a behavioural test (deposit, pre-order, price-varied landing page) before committing serious build. Record the number the evidence supports, not the number the business case needs.

  4. Check the two numbers agree

    Fund only where the opportunity score is high and measured willingness to pay clears cost-to-serve with margin. One without the other is a complaint or a commodity — file both politely.

  5. Re-survey when the market moves

    Satisfaction scores drift as competitors ship, so last year's underserved outcome may be this year's table stakes. Re-run the survey on a cadence matched to category speed, and treat a rival's launch in your top gap as an automatic re-score.

Watch out

Common mistakes

✕ Asking customers what they'd pay, and believing the answer.

Fix: Stated willingness to pay is systematically inflated — respondents spend imaginary money generously. Use trade-off methods or behavioural tests. If money hasn't moved or been forced into a trade-off, you've measured courtesy.

✕ Writing features as outcomes.

Fix: 'An app with UPI autopay' is your solution. 'Minimise the effort of paying on time' is their outcome. Solutions smuggled into the survey rig the scores toward your roadmap — phrase every statement so a competitor could act on it too.

✕ Averaging the landscape across segments.

Fix: Opportunity scores averaged over everyone hide the segment where the gap is severe — a mediocre overall score is often one desperate segment diluted by four indifferent ones. Cut the scores by segment before deciding anything.

✕ Treating high willingness to pay as permission to ignore cost-to-serve.

Fix: Value captured is WTP minus what it costs you to deliver the relief, at your quality bar, repeatedly. Run the unit economics with the survey — a priced gap you can't profitably serve belongs to someone else's cost structure.

Don't just read it

Practice task — 10 minutes

Take a category you buy weekly and write ten outcome statements for its core job. Score each yourself on importance and satisfaction, compute the opportunities, and find the one gap above 10. Then design the cheapest possible willingness-to-pay test for it — what would you need to see before betting ₹10 lakhs on that gap?

If you remember five things

  • Jobs decompose into outcomes — direction + metric + context — and outcomes can be surveyed where interviews can only be felt.
  • Opportunity = importance + (importance − satisfaction): underserved gaps are build orders, overserved polish is a disruptor's doorway.
  • Willingness to pay is measured by trade-offs and behaviour — say < click < use < pay — never by asking nicely.
  • Fund only where both numbers agree: a scored gap and a priced relief. One alone is a complaint or a commodity.
  • Landscapes drift as rivals ship — re-score on a calendar, and read every competitor launch as new satisfaction data.