Library, anchors Module 9

Monetizing Innovation

by Madhavan Ramanujam and Georg Tacke, 2016

Ramanujam and Tacke are partners at Simon-Kucher (the same pricing consultancy as Hermann Simon), and their book takes Simon's pricing discipline upstream into product development. The central argument is that pricing should be a Day One product question, not a Day 365 launch question, and that the dominant cause of new-product failure is not poor product but poor pricing decisions made too late. The authors identify four classic failure modes: feature shock (too many features that customers do not value), minivation (a great product priced too low), hidden gems (valuable features bundled invisibly), and undeads (products kept alive that the market has already rejected). The book is built from their consulting practice across hundreds of product launches at Porsche, LinkedIn, SAP, Optimizely, and dozens of smaller companies. Simon-Kucher's own analysis (cited in the book) found that 72 percent of new products fail to meet their financial goals, and that 80 percent of those failures trace to pricing decisions rather than product quality. For a CMO involved in product roadmap decisions or new-product launches, this is the operator's manual for fixing pricing-product fit before launch instead of after.

Core frameworks

1. Willingness to pay (WTP) as the upstream test

Before building anything, test what customers will actually pay for it. Most companies build first and price last. Ramanujam and Tacke's recommendation: structured WTP testing in the design phase. The methods include van Westendorp's price-sensitivity meter, Gabor-Granger ladder, conjoint analysis, and direct customer interviews.

The van Westendorp price-sensitivity meter is the most widely-used method and worth understanding mechanically. The method asks each survey respondent four questions about the product. At what price would you consider this product so expensive that you would not consider buying it? At what price would you consider this product expensive but still consider buying it? At what price would you consider this product a bargain, a great buy for the money? At what price would you consider this product so inexpensive that you would question its quality?

The four price points produce four cumulative distribution curves when plotted across the respondent population. The intersections of the curves identify meaningful price thresholds. The intersection of "too expensive" and "too cheap" identifies the optimal price point (OPP). The intersection of "expensive" and "cheap" identifies the indifference price point (IPP). The intersection of "too expensive" and "expensive" identifies the upper price point. The intersection of "too cheap" and "cheap" identifies the lower price point. The acceptable price range sits between the upper and lower bounds.

Porsche's Cayenne SUV development is the book's worked example. Before approving the program, Porsche tested WTP for an SUV among existing 911 owners through structured customer research. The test revealed not just price tolerance but feature-by-feature value perception: which interior features the customer valued, which exterior elements justified premium pricing, which performance specs translated to willingness to pay. The research shaped the product specification, the pricing tiers, and the launch positioning. The Cayenne became one of the most successful product launches in automotive history, and the success traced substantially to the upstream WTP work.

How to operate: run structured WTP testing on every new product before the engineering investment is final. The test is cheap (a survey of 300 to 500 target customers costs less than one engineering month), the answer is decision-altering, and the typical company skips it.

If you only remember one thing: price upstream, not downstream. The test is cheap and the answer reshapes the product.

2. The four product failure modes

Feature shock: the product has many features but customers value few of them. The product team is proud of the feature count; customers are confused by it. Marketing struggles to articulate value because the value is diffused across too many claims.

Minivation: the product is great and underpriced. The team built something genuinely valuable but anchored the price on cost-plus or competitor-matching rather than on customer value. The product sells well; revenue is far below what the customer would have paid.

Hidden gem: the valuable feature is bundled invisibly inside a larger product instead of monetized separately. Customers do not perceive the feature as distinct value and do not assign price to it. The bundle pricing leaves the gem's value on the table.

Undead: the product was wrong for the market but the company keeps investing in it because of sunk cost. The product cannot be made to fit; the right move is the kill decision. The wrong move is more investment.

A B2B software case the authors describe in detail. A vendor built an enterprise platform loaded with 47 distinct features. WTP testing revealed customers valued seven of the features highly enough to pay for them; the other forty represented engineering investment that produced zero pricing power. The product was a feature-shock case. The right response was cutting forty features, repackaging the seven valuable features, and repricing based on the value the seven produced. The repackaged product launched at a higher price than the original 47-feature version and produced substantially higher revenue per customer. The forty cut features were the wrong investment; the seven kept features were where the value was.

How to operate: audit the existing portfolio for the four failure modes. Feature shock products need feature cuts. Minivations need price increases. Hidden gems need repackaging into separately monetized tiers or modules. Undeads need kill decisions. The audit is uncomfortable because it forces public acknowledgment of failed bets, which is exactly why most teams skip it.

If you only remember one thing: most product failures are pricing failures. Diagnose the failure mode before you redesign the product.

3. Pricing model selection

The right pricing model depends on customer behavior and product economics. Subscription, per-seat, usage-based, freemium, tiered, outcome-based, dynamic. Each model fits different patterns of customer value perception and cost-to-serve.

Subscription pricing works when value accrues over time and the customer relationship is ongoing. Software, content libraries, ongoing services.

Per-seat pricing works when value scales with the number of users and seat usage is roughly homogeneous. Productivity software, collaboration tools, training platforms.

Usage-based pricing works when value scales with consumption and consumption is measurable. Cloud computing, APIs, transactional services. The model captures value from heavy users without pricing out light users.

Freemium pricing works when network effects matter, when the free product produces conversion at scale, or when the free tier creates the data set or community that funds the paid tier. Slack, Dropbox, Notion.

Tiered pricing works when customer segments have meaningfully different WTP and feature needs. The good/better/best structure captures multiple WTP segments simultaneously.

Outcome-based pricing works when the customer can measure the outcome the product produced and willingness to pay tracks the outcome. Performance marketing platforms, some consulting engagements, some software vendors with clear ROI metrics.

Adobe's 2013 shift from perpetual licenses to Creative Cloud subscription is the book's headline example. Before the shift, Adobe sold Photoshop, Illustrator, and the Creative Suite as perpetual licenses at four-figure price points. Customers either bought the license (often a multi-year decision) or pirated the software. The perpetual model captured customers who could afford the upfront cost and locked out everyone else. The subscription model at $50 per month per user (and $10 per month for single-app subscriptions) captured customers who could not justify the upfront license but happily paid monthly. Adobe's revenue per customer doubled within five years, and piracy rates dropped because the legal access price was now within reach. The product had not changed; the model had.

How to operate: examine your current pricing model and ask whether it matches the value-perception pattern of your customers. The default model your company runs is often wrong for the customer behavior pattern, particularly for products that grew up under one model and now serve a customer base with different value perception.

If you only remember one thing: the model is a strategic choice, not a default. Choose deliberately based on how value accrues.

4. Tier design and the good/better/best structure

Three-tier structures consistently outperform one-tier and two-tier structures in most B2B and consumer contexts. The good tier captures price-sensitive buyers. The better tier captures the largest segment with the best price-to-feature ratio. The best tier captures premium buyers and anchors the perception of value across the line.

The mechanism: customers presented with a single price compare to outside alternatives and often conclude the price is too high. Customers presented with three tiers compare among themselves and the middle tier feels reasonable. The compromise effect (from Itamar Simonson's choice research) consistently shifts the choice toward the middle option when three options are presented.

Apple's iPhone tier structure is the consumer-product worked example. The iPhone Pro line, iPhone Pro Max line, and the regular iPhone (plus the lower-priced SE in some years) creates a price corridor from roughly $400 to $1,599. The structure extracts roughly twice the average revenue per device of a single-tier strategy because the price corridor lets the company serve multiple WTP segments simultaneously. The price-sensitive buyer takes the SE or the regular iPhone; the brand-loyal customer takes the Pro; the premium customer takes the Pro Max. Apple captures revenue from all three segments without alienating any of them.

The tier design follows specific rules. The good tier must be genuinely useful (a stripped-down version that no one would want defeats the purpose). The better tier must be the obvious right choice for the largest segment (the price-to-feature ratio must be the strongest). The best tier must be aspirational (high enough that few buy it, but visible enough that it anchors perceptions of the line). The price gaps between tiers matter; gaps too small make tiers feel undifferentiated, gaps too large push buyers to the bottom tier.

How to operate: build three-tier structures wherever the customer base shows segmentation. Single-tier pricing leaks value at both ends of the WTP distribution. Two-tier pricing leaks value in the middle.

If you only remember one thing: three tiers extract more value than one tier. Design the middle tier as the obvious choice.

5. Behavioral pricing and the anchoring effect

Customers do not evaluate price in isolation; they evaluate it relative to anchors. The tier structure, decoy options, comparison context, and price display all shape the anchor and the resulting choice.

The authors describe a software product that increased average revenue per customer by 23 percent simply by repricing the highest tier. The original three tiers were $50, $100, $200 monthly. The middle tier ($100) was the most popular; the top tier ($200) sold to a small segment. The repricing moved the top tier to $400 monthly. The middle tier stayed at $100. The result: more customers chose the middle tier (because $100 now felt reasonable next to $400, which had not been true when the comparison was $200), and the top tier still captured the price-insensitive segment. The product was identical. The anchor changed.

The anchoring works because consumers do not have an absolute reference for what a software product "should" cost. They construct the reference from the options they see. The highest tier becomes the anchor that frames the middle tier as reasonable; the lowest tier becomes the anchor that frames the middle tier as worth the upgrade. Removing either anchor weakens the middle tier's appeal.

A second behavioral lever: the order of presentation. Tiers presented in descending order (best, better, good) anchor on the highest price first, making subsequent prices feel like discounts. Tiers presented in ascending order (good, better, best) anchor on the lowest price first, making subsequent prices feel like premiums. The order shifts the mix toward different tiers without changing the prices.

How to operate: test anchor design before launch. The tier prices that frame the middle option as the obvious choice consistently outperform tier prices that do not. Run controlled tests with different anchor structures and measure the mix shift, not just the conversion rate.

If you only remember one thing: the anchor is doing more work than the product copy. Choose it deliberately.

Actionable takeaways

  1. Run structured WTP testing on every new product before the engineering investment is final. The test is cheap, the answer is decision-altering, and the typical company skips it.
  2. Audit the existing portfolio for the four failure modes. Feature shock products need feature cuts. Minivations need price increases. Hidden gems need repackaging. Undeads need kill decisions.
  3. Choose the pricing model deliberately. Subscription, usage, tiered, outcome-based. The default model your company runs is often wrong for the customer behavior pattern.
  4. Build three-tier structures wherever the customer base shows segmentation. Single-tier pricing leaks value at both ends of the WTP distribution.
  5. Test anchor design before launch. The tier prices that frame the middle option as the obvious choice consistently outperform tier prices that do not.

What this book is NOT about

This book is not a deep behavioral-economics text. The anchoring and decoy material is operational rather than theoretical. For the rigorous foundation, pair with Thaler's "Nudge" (2008) and Ariely's "Predictably Irrational" (2008). The book is also written from a B2B consulting practice and the consumer case studies are thinner.

Two specific misreads to avoid. First, "design the product around the price" is not "price determines everything." The book's argument is that pricing should be a Day One question that shapes product specification, not that pricing supersedes product quality. A bad product priced perfectly still fails; a great product priced poorly often also fails. The discipline is integrating pricing into product development, not subordinating product to pricing. Second, "tiered pricing always wins" overstates the framework. Tiering works when customer segments have meaningfully different WTP and feature needs. Some markets are best served by a single price (commodity goods, network products at scale). The discipline is matching the structure to the customer pattern.

Field updates since publication: the WTP testing methodology has aged well; Simon-Kucher's consulting practice has continued to develop the methods. The pricing-model-selection landscape has shifted substantially with the rise of AI products (where consumption-based pricing has dominated) and product-led growth (where freemium and reverse trials have become standard). The book's frameworks accommodate the shifts; the specific case studies are now older. The authors occasionally overstate the case that pricing is the single cause of product failure when other causes (poor distribution, market timing, competitive entry) also matter. Pair with Simon's "Confessions of the Pricing Man" (2015) for the broader pricing discipline and with Thaler's "Nudge" (2008) for the behavioral foundation of anchoring and tier design.

Want more?

Borrow the full book on archive.org: https://archive.org/details/monetizinginnova0000rama

The original is about 240 pages and is dense with case studies from the authors' consulting practice. The summary above captures the operator-relevant frameworks. Read the full book if you want the deeper WTP testing methods, the worked examples from Porsche and LinkedIn, or the chapter on building pricing capability inside an organization. Pair with Simon's "Confessions of the Pricing Man" (2015) for the broader pricing discipline and with Thaler's "Nudge" (2008) for the behavioral foundation of anchoring and tier design.

Watch, to capture the material

Recommended viewing

The art and science of pricing | Madhavan Ramanujam (Monetizing Innovation, Simon-Kucher). Lenny's Podcast 98 minutes. Ramanujam walks the book's nine pricing failures and the design-the-product-around-the-price method, with current B2B and AI pricing applications.

Essay anchored to this reading

Essay prompt

Ramanujam and Tacke argue that pricing should be a Day One product question, not a Day 365 launch question, and that most product failures are pricing failures in disguise. Pick a product launch you have followed closely: your employer's most recent product, a competitor's launch you tracked, a startup's first product, a feature release at a company you use. In 600 to 900 words, autopsy it using the four failure modes and the WTP frame.

Your essay must:

  1. Identify which of the four failure modes the product showed at launch (feature shock, minivation, hidden gem, undead) or whether it avoided them. Use specific evidence: customer reviews, pricing-page screenshots, sales-call leaks, public revenue or churn signals. If the product succeeded, identify which failure modes the team avoided and how.
  2. Apply WTP testing in reverse. Estimate the customer's willingness to pay based on the value the product delivers. Compare to the actual price. Identify whether the company captured the value, left value on the table (minivation), or overshot WTP (premature pricing).
  3. Redesign the tier structure if there is one (or propose one if there is not). Apply the good/better/best frame and the anchor logic. Be specific about the prices, the features in each tier, and why the structure would extract more value than the current approach.

If your essay just says "the price was too high" or "too low" without engaging WTP, the failure modes, or the tier design, you have not done the work. The book is operational. Produce an operational redesign.

Submitted. View it in Module 9 Discussion.