This episode says pricing isn't an afterthought—it's where product strategy starts. Madhavan Ramanujam argues 72% of innovations fail because they can't monetize, while successful firms 'price first, build later' with CEO involvement. Key examples: Porsche Cayenne (asked customers if they'd pay before designing; now makes 50% of Porsche's profit); Amazon Fire Phone (packed unwanted features, price crashed from $179 to $0.99); SuperHuman (founder used 'acceptable/expensive/ridiculous' price questions to set its email app price). Bottom line: don't build first—test willingness to pay early.
This report explores the core principles of pricing strategy. Author Madhavan Ramanujam emphasizes the disruptive approach of "price first, product later" to avoid product failure. The core view: pricing should be based on customers' willingness to pay for "benefits," not features; it is necessary t
Madhavan Ramanujam is a pricing strategy expert, author of Monetizing Innovations, and has provided pricing consulting to companies such as Porsche, Uber, LinkedIn, and SuperHuman. The core thesis of this episode: Pricing is not the epilogue of a product, but the starting point of product strategy. The author advocates "price first, product second" — before investing significant resources, systematically validate the fit between product, market, and pricing through customer conversations, rather than the traditional gamble of "build the product first, then slap a price on it."
The most impactful statement in the entire episode: Madhavan Ramanujam argues that "72% of innovation failures stem from failure to monetize successfully, and the successful 28% of companies share only two commonalities — 'price first, product second' and direct CEO-level involvement." This statistic elevates pricing from an "outsourceable tactical detail" to a "strategic core that determines the life or death of a company."
Madhavan Ramanujam argues that pricing is not a number, but a measure of how much customers desire the value of a product. He finds a subtle correspondence in Latin: "There is only one word that means both price and value—pretium. They are two sides of the same coin."
Traditional companies "build the product first, then slap a price on it," a practice the author calls "spraying perfume on it, throwing it into the market, and leaving it to fate." He advocates testing customers' willingness to pay for the "benefit" at the blueprint stage, rather than collecting positive feedback on the "feature." The difference is enormous: customers may like your product, but they may not be willing to pay for it. The author emphasizes: "If you have a prototype, pitch the value, and the customer says 'no,' then even if you build a more beautiful version, they still won't pay. That 'no' is the most valuable information—ask why, and you know what to design."
Porsche Cayenne case: In the early 1990s, Porsche, without a single design drawing, simply asked potential customers if they would buy an SUV based on the idea "we want to build an SUV." The answer was yes. Only then did they sketch, build prototypes, and test customers' willingness to pay for specific features at each iteration—for example, the large cup holder that engineers disliked was kept because customers demanded it, and the six-speed manual transmission was scrapped because no one was willing to pay for it. The resulting Cayenne accounted for more than 50% of Porsche's profits, becoming one of the most successful models in automotive history. The author concludes: "If you don't include pricing in your product-market fit validation, you often hear only what you want to hear. What you need is a 'product-market-pricing' three-way fit."
Madhavan Ramanujam proposes a practical framework for product configuration — "Leader, Filler, Killer" — to decide how to bundle product features.
"The Leader is what customers really want to buy; the Filler is the add-on that boosts incremental sales when bundled together; the Killer is the element that ruins the entire deal when included in a package." He uses McDonald's Happy Meal as an example: the burger is the Leader, while fries and Coke are Fillers. But if coffee is also added to the combo, the double caffeine would ruin the deal for most people — yet coffee has standalone value for those who want it, so it should be offered as a separate paid add-on rather than being bundled at a discount.
He warns against the mistake of "Feature Shock" — i.e., throwing the kitchen sink into a product, believing "more is better." He cites the failure of Amazon Fire Phone: "MarketWatch documented that it was crammed with features nobody wanted. The phone started at $179, dropped to $0.99 six months later, and the entire business was written off." The correct approach is to productize based on the needs, perceived value, and willingness to pay of different customer segments, rather than trying a one-size-fits-all approach.
Madhavan Ramanujam argues that directly asking "How much are you willing to pay?" is ineffective—clients will give garbage answers. However, relative questions can elicit real information.
He proposes three core techniques:
1. The "Acceptable-Expensive-Too Expensive" Three-Tier Method: After presenting the product's value, ask three questions in sequence: "What price do you find acceptable? What price would you consider expensive? What price would make you laugh?" The author finds that the "acceptable" price is typically the frictionless entry price, the "expensive" price is the client's true value price (they will pay it but won't like it), and the "too expensive" price is the psychological threshold. Mass testing these responses can identify psychological price thresholds in the market—for example, "demand is high at a monthly fee below $49, but drops sharply above $50." Rahul Vora of SuperHuman admitted on the A16Z podcast that he used this exact method to set SuperHuman's price.
2. The Relative Reference Method: Ask clients, "If Salesforce's value is 100, how much do you think our product is worth?"—Clients can answer such relative questions. This can be used both for pricing tests and for subsequent negotiations.
3. "Double the Price Until You're Kicked Out of the Room": One founder used this method to find the price ceiling—continuously doubling the quoted price until the client laughed.
The author emphasizes that the key is not the perfection of the method, but "just doing it." Embed these conversations into the early and ongoing stages of product development, rather than waiting until the product is built to consider them.
Madhavan Ramanujam argues that "how to charge" is far more important than "how much to charge." The decision framework he provides is based on customer usage patterns and value delivery models:
Scenarios where a subscription model is suitable:
Scenarios where a usage-based model is suitable:
A key warning: When using a usage-based pricing model, you must have a 'trackable metric that both you and the customer agree on' – if value delivery cannot be clearly attributed, a subscription model may be a safer choice.
Madhavan Ramanujam cites data from Simon-Kucher's biennial global pricing study, the largest of its kind: 72% of innovations fail; the successful 28% share only two common traits—"price before product" and direct involvement from the CEO/founder. The latter's KPI is 35% higher than the former's.
He explicitly states: "Pricing, monetization, growth—especially when you put growth on the table—this is 100% a CEO issue." This does not mean the CEO should personally crunch the pricing numbers, but rather "set the right culture, the right tone, and ask the right questions." He argues that the CEO should ask in every meeting: "How do we know the customer will pay for this innovation?"
The three things about entrepreneurs that surprise him most:
1. Pricing is a science, not an art based on intuition.
2. Commercial conversations must happen early in product development, not left until the end.
3. The need to "unlearn" the most familiar mindset—the inertia of "build first, then sell"—and shift to "understand customer needs and willingness to pay first, then productize."
Quantitative rule for "value-based pricing": The author recommends that companies capture at least 20–25% of the economic value they create for customers. If below 20%, you are "leaking value"; if above 50%, you leave room for competitors to disrupt with low prices.
| Ticker | Guest Attitude (Bullish / Risk Warning / Neutral) | Key Data |
|---|---|---|
| Porsche | Case positive, used as a successful example of pricing-forward strategy | Cayenne accounts for over 50% of Porsche's profit |
| Apple/iPhone | Case positive, used as a model of "productizing rather than pricing" | iPhone from $299 to $1,499, multiple versions cover different willingness-to-pay segments |
| SuperHuman | Case positive, citing founder Rahul Vora's use of "acceptable/expensive/ridiculously expensive" method | Pricing method from Ramanujam's book |
| Amazon Fire Phone | Failure case warning | Dropped from $179 to $0.99, written off within six months |
| Google Glass | Failure case warning | Priced at $1,500, discontinued after two months |
| Kodak | Failure case warning ("hidden gem" not productized) | Owned digital photography IP in the 1970s but never brought it to market |
| SmugMug | Case positive, demonstrating the impact of shifting communication "from features to benefits" | Achieved double-digit revenue growth by only changing the communication approach |
| Netflix vs Blockbuster | Case positive, showing the advantage of subscription model in simplifying conversations | Compared to Blockbuster's then-complex pricing |
| AWS | Case positive, illustrating the rationale of pay-per-use model | Underlying costs scale with usage |
| LifeLock | Case positive, showing the rationale of subscription model "intermittent use + ongoing value" | Identity theft protection, very low frequency of use but continuous value |
1. Pricing is a measure of value, not a number. In Latin, "pretium" means both price and value. Price is a quantitative expression of customer desire. If no one buys after pricing, it means the product's value has not been recognized.
2. "Price first, product second" — pricing must precede product development. 72% of innovation failures are due to an inability to monetize, and the common trait shared by the 28% of successful companies is "price first, product second." The case of the Porsche Cayenne proves this — without any design drawings, it first verified whether customers were willing to pay for a "Porsche SUV."
3. The "Acceptable-Expensive-Too Expensive" three-tier approach is the core tool for guiding customers to reveal their true willingness to pay. Acceptable price = zero-friction entry price, Expensive = true value price, Too Expensive = psychological threshold. The founder of SuperHuman succeeded using this method.
4. The "Leader, Filler, Killer" framework is a practical guide for product configuration. Leaders are what customers truly want to buy, Fillers are items that boost sales when bundled, and Killers are items that would ruin the deal if included in a package. Coffee in McDonald's combo meals is a Killer — for most people, double caffeine would ruin the combination.
5. The difference between "benefits" and "features": Features are "what you built," benefits are "what the customer gets from it." SmugMug achieved double-digit revenue growth simply by shifting communication from "listing 10-15 features" to emphasizing the benefit of "you can sell photos online," without changing the product itself at all.
6. The decision framework for subscription vs. usage-based pricing depends on the combination of "usage frequency, value delivery frequency, and cost structure." Subscriptions suit scenarios where "usage is intermittent but value is ongoing" (e.g., LifeLock), while usage-based pricing suits scenarios where "usage and value delivery are intermittently aligned and costs scale with usage" (e.g., AWS).
7. The CEO must personally engage in pricing — this is not a tactical issue that can be outsourced. Companies with CEO/founder involvement in pricing decisions have 35% higher KPIs than those without. Pricing is a 100% CEO-level issue for "growth."
8. At least 20-25% of the economic value you create for customers should be captured. Below 20% means you are "leaking value," and above 50% means you leave room for competitors to undercut with low prices.
9. Four failure modes of innovation: ① Feature overload (too many features that no one wants, e.g., Amazon Fire Phone); ② Mini-innovation (built the right product but lacked the courage to set a high price, e.g., a semiconductor company priced at $0.85, creating $50 in value, and was ridiculed by customers); ③ Hidden gems (afraid to productize due to fear of cannibalizing existing business, e.g., Kodak's digital photography); ④ Walking dead (should never have been launched — it was the answer to the wrong question, e.g., Google Glass's consumer strategy, which should have been a B2B niche market).
10. Steve Jobs should be viewed more as a pricing genius than a product genius. The iPhone's tiered pricing ($299 to $1,499), productization across different willingness-to-pay segments, and the strategy of high entry pricing followed by subsequent price cuts, prove that he did not "fail to test customers" but rather cleverly integrated pricing into product strategy.