Keep doubling your price each deal until a prospect laughs you out of the room
Outcome: 3-4x expansion of realised price until laughter surfaces the demand ceiling; stabilise just below it.
Context: Madhavan narrated a founder who used this directly to find his pricing strategy — kept doubling each deal until he hit the laughter threshold, and stabilised there.
“One of the easiest things that I remember a founder actually did to find out their pricing strategy is he kept doubling the price in every deal till someone laughed him out of the room… He found that there was a threshold, and he hit that. And then he knew that, that's where he needs to stabilize.”
salesfundraisingpre-seedseed
Apply the 20-25% value capture rule to set floor and ceiling
Outcome: Calculate the economic value your product delivers to the customer in dollars (e.g. cost savings, revenue lift). Capture at least 20-25% of that value in your price — under 20% you're under-monetizing; over ~50% you leave space for someone to undercut you.
“Madhavan Ramanujam — How To Price a Product”
- 1
Quantify economic value delivered to the customer
Measure in dollars: cost saved, revenue generated, time saved × hourly rate, etc.
- 2
Calculate 20-25% of that value as floor price
If you deliver $1,000/month in value, floor is $200-250/month.
- 3
Check ceiling at ~50% of value delivered
Pricing above 50% opens disruption risk; if you deliver $1,000/month, ceiling is ~$500/month.
- 4
Price within the 20-50% band
Default to 25-35% capture for defensibility and customer satisfaction.
Stop or pivot when
- →Under 20% capture → under-monetizing
- →Over ~50% capture → disruption risk
Before you start
- · Quantifiable economic value delivered to customers
- · Clarity on cost savings, revenue lift, or time saved
pricing0-11-10
Test monetization model preference with economic-indifference thought experiments
Outcome: Don't pick subscription vs usage-based because competitors do it — run a thought experiment with customers: 'If you're selling $100, would you prefer 10% commission or $5 flat + 5% or $10 flat?' Rational economics says indifferent; real customers never are, and their answer reveals the intuitively-right model.
“Madhavan Ramanujam — How To Price a Product”
- 1
Design economically-equivalent model scenarios
Create 2-3 pricing models (e.g. pure usage, hybrid, pure subscription) that have the same expected revenue under median usage.
- 2
Pitch each model to target customers as a preference question
'If you're selling $100 in value, would you prefer [model A] or [model B]?' Frame as indifferent mathematically.
- 3
Record which model customers intuitively prefer
Ask which feels fairer, more predictable, or simpler — capture their reasoning.
- 4
Pick the model with strongest preference signal
The model customers prefer is the one that makes intuitive sense for your value delivery.
Scripts
qualify
If you're selling $100, would you prefer 10% or $5 and 5% or $10?
Before you start
- · Clarity on value delivery and usage patterns
- · Access to target customer segment for preference interviews
pricingbusiness-model0-11-10
Use relative anchoring to elicit WTP against a known competitor
Outcome: Instead of asking 'what should I charge' (which gets garbage answers), ask customers to index your value and price relative to a known competitor like Salesforce — 'If Salesforce is $100 in value, what do we bring? If Salesforce is $100 in price, where should we be?' — to get actionable relative pricing signals.
“Madhavan Ramanujam — How To Price a Product”
- 1
Identify a reference competitor customers know
Pick a category leader (e.g. Salesforce) that prospects are familiar with.
- 2
Ask the value indexing question first
'If [competitor] is indexed at $100 in value, what value do we bring?' Let them answer.
- 3
Ask the price indexing question second
'If [competitor] is $100 in price, where should we be?' Capture their relative price sense.
- 4
Use the ratio in pricing and negotiation
If they say you deliver 120% of Salesforce value but should be priced at 80%, you have a wedge for negotiation and positioning.
Scripts
qualify
If Salesforce is indexed at $100 in value, what do we bring?
qualify
If Salesforce is $100 in price, where should we be?
Before you start
- · Known category competitor that prospects reference
- · Willingness-to-pay conversation with target customers
pricingpositioning0-11-10
Double price every deal until someone laughs you out of the room
Outcome: In early sales conversations, keep doubling your quoted price deal-by-deal until a prospect laughs or rejects outright — that tells you the willingness-to-pay ceiling; then stabilize pricing just under it.
“Madhavan Ramanujam — How To Price a Product”
- 1
Start with a conservative baseline price
Pick a number you believe is safe but likely low.
- 2
Quote double the last price in the next deal
Each successive prospect gets 2x the prior quote until someone rejects outright or laughs.
- 3
Record the rejection threshold
When a prospect rejects or laughs, you've found the ceiling.
- 4
Stabilize pricing just below the rejection point
Set your standard price at the highest accepted quote or one step below the rejection.
Stop or pivot when
- →Prospect laughs or rejects outright → you've hit the ceiling
Before you start
- · Pipeline of prospects willing to have pricing conversations
- · Early-stage product with pricing flexibility
pricingsales0-1
Run acceptable/expensive/prohibitively-expensive WTP tiering on prototypes
Outcome: Before building, pitch prototype benefits (not features) to target customers and ask three price points — acceptable, expensive, prohibitively expensive — to find the psychological ceiling and demand drop threshold where customers walk away.
“Madhavan Ramanujam — How To Price a Product”
- 1
Prepare a benefits-focused pitch
Describe what the product does for the customer, not how it works — prototype stage is sufficient.
- 2
Ask three tiering questions at scale
For each customer: what price is acceptable (lowball), what is expensive (neutral), what is prohibitively expensive (laugh-out-of-room).
- 3
Aggregate responses to find the ceiling
Look for the threshold where 'prohibitively expensive' clusters — e.g. $49/mo acceptable, $50/mo demand drops.
- 4
Price just under the prohibitive threshold
Set launch price at the expensive tier, not the acceptable tier, to capture value without crossing the psychological ceiling.
Stop or pivot when
- →If customers laugh you out of the room, you've crossed the prohibitively expensive threshold
Before you start
- · Prototype or detailed benefits pitch (not features)
- · Access to target customer segment at scale
pricingproduct0-11-10
Pitch benefits on a prototype and have prospects quantify willingness to pay before showing a product
Outcome: Produces non-intuitive product choices (big cupholder in; 6-speed manual out) because every inclusion was battle-tested on willingness to pay.
Context: Madhavan's canonical Porsche story: no blueprint initially, then sketches, then full-scale prototypes in car clinics, then real WTP conversations. The Cayenne outcome is the payoff.
“They came up with blueprints, sketches and kept having this conversation with customers trying to identify what do they need, what do they value in an SUV, and are they willing to pay for it. They even did what we call as car clinics, where they would build a prototype, full-scale prototype… Things like a big cupholder is in the car because people said they need it, they value it, and they're willing to pay for it. A 6-speed manual transmission, no one needed that in an SUV. That was out of the window.”
productmarketingseedseries-aseries-b
Index your price against a known reference (e.g., "if Salesforce is $100, where are we?")
Outcome: Relative pricing questions surface a defensible anchor; use it in value-justification and negotiation.
Context: Madhavan's heuristic: "people are absolutely meaningless but relatively super smart." Ask against Salesforce (or any reference the prospect knows at $100) both in value AND in price.
“If Salesforce was indexed at $100 in value, what do you think we bring to the table for your business? That's a question people can answer all day long… Similarly, if you say if Salesforce is indexed at $100 in price, where do you think we should be? That's also an answer that people can make more sense of.”
salesmarketingseedseries-aseries-b
Ask prospects for acceptable, expensive, and prohibitively-expensive prices (ladder all three)
Outcome: Acceptable = they love price AND product (lowball); expensive = neutral reaction, the value price; prohibitively = they laugh. At scale reveals demand ceilings (e.g., $49 vs $50 demand collapse). Rahul Vohra used this to price Superhuman.
Context: Requires a prototype or benefits-led pitch you can put in front of prospects before final build.
“Ask them, what do you think is an acceptable price for this innovation?… Then ask them, what do you think is an expensive price? And then follow that with like, what do you think is a prohibitively expensive price?… Rahul Vohra from Superhuman actually used this method after he read Monetizing Innovation… that's how he priced Superhuman.”
salesproductpre-seedseedseries-a