Price Before Product: The Willingness-to-Pay Conversation
Have the pricing conversation months before launch and use it to prioritize what you build.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 95%
Most teams build first and slap a price on at the end, which is why (per Simon-Kucher's benchmarking) roughly 72% of innovations fail commercially. Ramanujam's counter-move is to run the exact sales-and-marketing pitch with customers before the product exists, ask whether they would pay, and ask why. The answers become the input for the R&D roadmap: you prioritize features by willingness to pay (WTP), not by internal excitement or engineering convenience.
Origin
Developed by Madhavan Ramanujam at Simon-Kucher & Partners across 250+ tech companies and codified in his book Monetizing Innovation (2016). The catalyst was a VC asking him at Stanford GSB how he 'truly knew' his pricing assumptions were right — he didn't. First Round Capital later compressed the idea into the phrase 'price before product'. It extends product-market fit (Lean Startup lineage) into what Ramanujam calls product-market-pricing fit.
Core principles
- 01Price is a measure of value, not a dollar figure — WTP is a proxy for whether customers actually want the product.
- 02You do not control whether you have a pricing conversation with a customer, only when you have it.
- 03Product-market fit without price validation makes you hear what you want to hear.
- 0420% of what you build drives 80% of the willingness to pay — find that 20% before you build.
- 05There is no such thing as too early; the exercise is repeated and refined as the product matures.
- 06Never ask 'how much should I charge?' — that answer is your job, and asking gets you garbage back.
How to run it
- 1
Run the launch pitch six months early
Take the exact sales and marketing conversation you would have after launch — the value story, the benefits, the concepts, wireframes or prototypes — and have it with real customers and prospects now, before the product is built.
Pro tip Prime them with the value pitch first. Asking 'what would you pay' cold, without the benefits conversation, produces a random number.
- 2
Ask 'would you pay for this?' — then always ask why
The binary answer is the litmus test; the 'why' is the payload. A no tells you what to pivot; a yes makes the customer articulate the value back to you in their own words, which becomes your value messaging.
Pro tip Roughly half your questions in the conversation should be 'why'. Yes-answers are as informative as no-answers.
Watch out If someone says no six months before launch, no amount of perfume in the intervening six months changes the answer.
- 3
Frame value questions relatively, not absolutely
People are meaningless in absolutes and smart in relatives. Index against a product they already buy: 'If Salesforce is 100 on value, where are we?' then 'If Salesforce is 100 on price, where should we be?'
Pro tip A 120-on-value / 110-on-price answer tells you premium pricing is available — a usable signal from a single conversation.
- 4
Use most/least (MaxDiff-style) to rank the roadmap
From a list of ~10 candidate features, show subsets of ~6 and ask only for the most important (must-have, will pay) and least important (don't need, won't pay). Rotate the subsets. Repeat until the whole set is ranked in relative order.
Pro tip Ranking 10 items 1-to-10 is painful and produces mush; picking two extremes from six is easy and people can do it all day.
- 5
Escalate method to company stage
Idea/seed: just ask 'would you pay, why'. Seed/Series A: purchase-probability scales (only a 5 converts at 30-50%, a 4 at 10-20%, a 3 or below never buys). Late stage / launch: trade-off (conjoint) exercises with real shopping scenarios to model elasticity and packaging.
Pro tip B2B: interview the 20-30 accounts that make up 80-90% of your business. B2C: 1,000-2,000 quantitative responses is enough to be significant.
Watch out Discount raw purchase-probability scores. Even people who say 5 out of 5 only buy 30-50% of the time.
- 6
Prioritize the R&D roadmap on WTP, then re-run every 6-18 months
Cut or de-prioritize anything with no willingness to pay behind it, and build the 20% that drives 80% of the WTP first. Revisit pricing at least every six months and at every pivot point (new plan, new feature tier).
Watch out Do not ship the 20% as a free MVP just because it is easiest to build — then you spend the rest of your life building the 80% that drives 20% of the value.
In the wild
Before a blueprint was drawn, Porsche tested whether the market wanted, valued and would pay for a Porsche SUV. Every feature was then battle-tested with customers in car clinics with prototypes — no amount of internal engineering conviction counted. Large cup holders survived because customers would pay for them; the six-speed manual transmission was thrown out because SUV buyers didn't want it.
→ The Cayenne launched into validated demand and now accounts for more than half of Porsche's profit — one of the great successes in automotive history.
Product teams generated thousands of post-its, prioritized down to 40 buy-side ideas, and took them to the CEO, who asked how they knew any of it would monetize. They didn't. They tested wireframes and concepts with customers. The internal #1 feature — 'highlight connections from Facebook' who had bought from the same seller — got savaged: one group said it spoiled the fun of doing their own research, one said they liked it but would pay 'hell no', one didn't want their Facebook circle knowing what they were buying.
→ Not one customer segment would pay for the company's favourite feature. Without the exercise they would have built the entire product around it; instead they re-prioritized the whole roadmap around what customers would actually pay for.
Common mistakes
Spray and pray — build, slap on a price, hope
Companies invest years in an innovation and then call a pricing consultant asking for a price 'yesterday'. By then the product is fixed and the only lever left is a number, which is why most innovations fail commercially.
Asking the customer to set your price
'How much should I charge?' is your job, not theirs. Ask it and you get a meaningless lowball. Tease out WTP through relative, threshold, probability and trade-off framings instead.
Prioritizing the roadmap on internal conviction or technical ease
If you rank features by what the team feels or what engineering can resource, you are guessing. Ranking by what customers need, value and will pay for is the only defensible order.
Is it for you?
Best for
Founders and product leaders in the design or pre-launch phase of a new product, feature tier, or innovation — especially B2B SaaS teams building a roadmap they cannot afford to get wrong.
Not ideal for
Free/ad-funded consumer products where users are not the payers, or purely internal tooling with no monetization surface.
From the transcript
“you cannot prioritize a product roadmap without having a willingness to pay conversation”
“as an entrepreneur or a company you actually don't have a choice whether you'll have a pricing conversation with your customer the only thing in…”
“20 of what you build drives 80 of the willingness to pay”
“how do you truly know that people will actually pay for your Innovation when you built it”
“if Salesforce was indexed at 100 in value where do you think we are in terms of like the value that we bring”
“there's a lot of psychological theory that people are very Adept at identifying the extremes”
From the episode
The art and science of pricing
Madhavan Ramanujam (Monetizing Innovation, Simon-Kucher)