Monetizing Innovation skill

Designs products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based segmentation, Good/Better/Best configuration, monetization models, behavioral pricing, and price integrity.

by getagentseal·MIT license·★ 729 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
> **Note:** This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core idea…

# Monetizing Innovation

> "Design the product around the price." - Ramanujam & Tacke

## Core Insight

**72% of new products fail** (Simon-Kucher 2014, n=1,615). Root cause: pricing is decided LAST instead of designing the product around it.…

| Old paradigm | New paradigm |
|--------------|--------------|
| design → build → market → price | market & price → design → build |

Only ~5% of business cases include real WTP (willingness-to-pay) data. Most companies wait until weeks before launch to set price.

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Monetizing Innovation

getagentseal/main1 file shown
SKILL.md
Show the full text242 lines

Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.

Monetizing Innovation

"Design the product around the price." - Ramanujam & Tacke

Core Insight

72% of new products fail (Simon-Kucher 2014, n=1,615). Root cause: pricing is decided LAST instead of designing the product around it. This figure comes from Simon-Kucher's own client survey data and has not been independently verified. The authors are principals at Simon-Kucher, a pricing consultancy - the stat motivates hiring firms like theirs. Treat it as directionally correct but not independently validated.

Old paradigm New paradigm
design → build → market → price market & price → design → build

Only ~5% of business cases include real WTP (willingness-to-pay) data. Most companies wait until weeks before launch to set price.


The 4 Failure Types (Diagnose Before Fixing)

Failure Definition Cultural Cause Tell-Tale Signs
Feature Shock Cram too many features → confusing, overpriced Engineering-driven Can't articulate value; price slashed post-launch
Minivation Right product, priced too low Risk-averse Sales easily hits target; sellouts; channel maxes margin
Hidden Gem Great idea never properly launched Coddles core business Mid-level execs kill it; sold as deal sweetener; rival ships first
Undead Wrong answer (or no question asked) Top-down, no dissent Sales avoid raising it; pet project of senior management

Real examples: Amazon Fire Phone (Feature Shock, $170M write-down), Audi Q7 (Minivation, missed €210M/yr), Kodak digital camera 1974 (Hidden Gem), Segway/Google Glass (Undead).

Full case file: see cases.md.


The 5 Pricing Myths (Counter These)

  1. "Build it and they will come" - hides 95% of failures
  2. "Innovation needs isolated artists" - customer input informs, doesn't pollute
  3. "High failure rates are normal" - failure is preventable
  4. "Customers must experience product to price it" - false, they react to concepts
  5. "You can't price what you haven't built" - cost-plus thinking; price is set by VALUE

The 9 Rules (Summary)

# Rule Headline
1 WTP Talk Early 80% of companies skip this. Have it before design freezes.
2 Needs-Based Segmentation Demographic segmentation is broken. Segment by needs/value/WTP.
3 Configuration & Bundling Use Leaders/Fillers/Killers + Good/Better/Best with FENCES.
4 How You Charge > What You Charge Choose the right monetization model (5 options).
5 Pricing Strategy Maximization / Penetration / Skimming. Apply the BECAUSE test.
6 Living Business Case Link Price-Value-Volume-Cost. Update at every milestone.
7 Value Communication Sell benefits, not features. Use MOCA matrix.
8 Behavioral Pricing 6 tactics: compromise, anchoring, signals, razor-blade, pennies-a-day, thresholds.
9 Maintain Price Integrity Don't cut after launch. Use 3 nonprice actions first.

Full framework details with sub-frameworks, methods, and checklists: see frameworks.md.


Critical Frameworks (At-a-Glance)

Leaders / Fillers / Killers
Type Definition Action
Leader Drives buying, high WTP Always include
Filler Nice-to-have Use to fill gaps
Killer Blows the deal if forced to pay Eliminate or sell à la carte

Killer test: valued by <20% of customers AND not valued at all by >20%. Killers are segment-dependent (heated seats: leader in cold, killer in tropical).

Good/Better/Best Distribution
Distribution Diagnosis
≤25% Good, ~70% Better+Best, ≥10% Best Healthy
>50% Good Trip-wire: cut features from Good
Best <10% Premium tier underpowered

Fences are mandatory. Every tier needs visible, defensible differences. Without fences G/B/B cannibalizes itself. Fence test: in 10 seconds can a customer see what's missing from Good?

The 5 Monetization Models
Model When to Use Example
Subscription Continual usage Netflix, Adobe
Dynamic Pricing Volatile demand or constrained supply Uber, airlines
Auctions Seller's market, constrained inventory Google AdWords ($35B/yr), eBay
Pay-As-You-Go / Alternative Metric Usage tracks value Michelin (per-mile), GE engines
Freemium Near-zero production AND fixed cost LinkedIn, Dropbox

Freemium warning: fails for 90% of companies; software conversion typically <10%; games lose 75% of users in day 1.

Models are mix-and-matchable (Costco = subscription + per-product; OpenTable = subscription + transaction fee).

The 6 Behavioral Pricing Tactics
  1. Compromise effect - always have 3 tiers; people avoid extremes
  2. Anchoring - The Economist test: $59 vs $125 vs $125-print-only made bundle pick rate jump 32% → 84%
  3. Price signals quality - Ariely placebo: $2.50 pill 85% pain relief, $0.10 same pill 61%
  4. Razor / razor blades - low upfront preferred even if total cost identical
  5. Pennies-a-day - $9.99/mo converts very differently from $120/yr
  6. Psychological thresholds - $69.99 works, $71 doesn't (drops acceptance >20%)

Caveat: can't price purely on behavior. Combine with rational/value-based.


Decision Trees

"Is my product likely to fail?"
Can I clearly state the customer benefit (not features)?
├─ NO  → Likely Feature Shock
└─ YES → Has WTP been validated with real customers?
         ├─ NO  → Could be Undead or Minivation
         └─ YES → Did C-suite engage personally?
                  ├─ NO  → Likely Hidden Gem (won't get launched right)
                  └─ YES → On the right track
"Which monetization model?"
Is value tied to usage?
├─ YES → Alternative Metric (Michelin model)
└─ NO  → Demand volatile or supply constrained?
        ├─ YES → Dynamic Pricing
        └─ NO  → Production cost near zero?
                ├─ YES → Freemium (only if 90% of users still profitable)
                └─ NO  → Subscription or per-unit
"Should I cut the price?"
Sales below plan?
└─ YES → Identified ROOT CAUSE?
         ├─ NO  → Diagnose first (likely not price)
         └─ YES → Pricing-specific?
                  ├─ NO  → Fix actual problem
                  └─ YES → Tried 3 nonprice actions?
                           ├─ NO  → Try those (advertise; add value; upgrade)
                           └─ YES → War-game competitor reaction
                                    └─ Worse off after counter? → don't cut

Critical Numbers

Number Rule
72% New products fail
80% Companies wait until just before launch to set price
5% Business cases include real WTP data
3-4 Ideal starting number of segments
<10% Killer features valued by less than this %
9 / 4 Max benefits / products before psychological overload
≤25% / 70% / ≥10% G/B/B target (Good / Better+Best / Best)
50% Trip-wire: more than this picking Good = bleeding
20-30% Healthy deal escalation rate
30-40% Of ALL DEALS should have price changes upon escalation
3 Nonprice actions required before any price cut
40% More likely to realize potential with defined pricing strategy
33% More profit when C-suite leads pricing (vs delegates) - also from Simon-Kucher client data; same provenance caveat as the 72% figure applies
25% Of customer interview questions should be "Why?"

The "BECAUSE" Test

Every pricing decision must end with a "because" traceable to customer data.

Bad: "We priced at $99 to be competitive." Good: "We priced at $99 BECAUSE 60% of segment B told us $100 was the threshold above which they'd reconsider, and our value advantage justifies the high end."

If you can't say "because customers told us X," you don't have a pricing strategy.


Quick Reference Checklist

Before designing a new product:

  • WTP conversations with real customers held
  • Segmented by needs/value/WTP (not demographics)
  • Leaders, fillers, killers identified
  • G/B/B configuration designed with FENCES
  • Monetization model picked (aligns with value)
  • Pricing strategy documented (max/penetration/skimming)
  • Living business case links Price/Value/Volume/Cost
  • Benefit-not-feature messaging tested
  • Behavioral tactics considered
  • Team prepared to maintain price integrity post-launch

The test: Ask anyone "Why this price?" If the answer is "cost-plus" or "competitor benchmark," failure is coming.


Critical Quotes

  • "Design the product around the price."
  • "How you charge trumps what you charge."
  • "Pricing too low is worse than pricing too high."
  • "Customers don't buy products. They buy benefits." - Drucker
  • "The single most important decision in evaluating a business is pricing power." - Buffett
  • "If I have 2,000 customers and 400 prices, I'm short 1,600 prices." - Crandall (American Airlines)

Supporting Files

  • frameworks.md - Full detail on all 9 rules, sub-frameworks, methods, and lists (10 WTP insights, 10 bundling insights, 6 post-launch tips, etc.)
  • cases.md - Detailed case studies (Porsche, Dodge Dart, LinkedIn, Dräger, Uber, Swarovski, Optimizely, Innovative Pharma) plus failure exemplars
  • examples.md - Worked examples: Pizza & Breadsticks bundling math, MOCA matrix, value-selling spreadsheet, 100-point goal allocation, BECAUSE test templates
  • integration.md - Implementation roadmap (4 phases), 9 pitfalls, startup/SaaS adaptation, WTP research limitations, conflict resolution with Mom Test/$100M Offers/SPIN

When This Doesn't Apply

  • Pure cost-plus regulated environments (utilities, some defense)
  • Pure commodities (sugar, copper)
  • Very early stage with no product (use Mom Test first)
  • B2C impulse buys under $50 (simpler approaches work)
  • Geographic markets with no purchasing power

Caveat on WTP Research

Stated WTP and revealed WTP differ. Customers predict their own behavior poorly in interviews. Treat WTP findings as a strong prior, not certainty. Validate with paid pilots, pre-orders, live A/B price tests, or money-back guarantees. See integration.md.

1---
2name: monetizing-innovation
3description: "Designs products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based segmentation, Good/Better/Best configuration, monetization models, behavioral pricing, and price integrity. Use when designing new products, validating pricing for SaaS/B2B/B2C launches, choosing between subscription/usage/freemium models, fixing post-launch sales below plan, diagnosing failed launches as Feature Shock/Minivation/Hidden Gem/Undead, or when product teams say 'let's price it later'. Not for pure commodities or cost-plus regulated environments."
4---
5 
6> **Note:** This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.
7 
8 
9# Monetizing Innovation
10 
11> "Design the product around the price." - Ramanujam & Tacke
12 
13## Core Insight
14 
15**72% of new products fail** (Simon-Kucher 2014, n=1,615). Root cause: pricing is decided LAST instead of designing the product around it. This figure comes from Simon-Kucher's own client survey data and has not been independently verified. The authors are principals at Simon-Kucher, a pricing consultancy - the stat motivates hiring firms like theirs. Treat it as directionally correct but not independently validated.
16 
17| Old paradigm | New paradigm |
18|--------------|--------------|
19| design → build → market → price | market & price → design → build |
20 
21Only ~5% of business cases include real WTP (willingness-to-pay) data. Most companies wait until weeks before launch to set price.
22 
23---
24 
25## The 4 Failure Types (Diagnose Before Fixing)
26 
27| Failure | Definition | Cultural Cause | Tell-Tale Signs |
28|---------|------------|----------------|-----------------|
29| **Feature Shock** | Cram too many features → confusing, overpriced | Engineering-driven | Can't articulate value; price slashed post-launch |
30| **Minivation** | Right product, priced too low | Risk-averse | Sales easily hits target; sellouts; channel maxes margin |
31| **Hidden Gem** | Great idea never properly launched | Coddles core business | Mid-level execs kill it; sold as deal sweetener; rival ships first |
32| **Undead** | Wrong answer (or no question asked) | Top-down, no dissent | Sales avoid raising it; pet project of senior management |
33 
34**Real examples:** Amazon Fire Phone (Feature Shock, $170M write-down), Audi Q7 (Minivation, missed €210M/yr), Kodak digital camera 1974 (Hidden Gem), Segway/Google Glass (Undead).
35 
36Full case file: see [cases.md](cases.md).
37 
38---
39 
40## The 5 Pricing Myths (Counter These)
41 
421. "Build it and they will come" - hides 95% of failures
432. "Innovation needs isolated artists" - customer input informs, doesn't pollute
443. "High failure rates are normal" - failure is preventable
454. "Customers must experience product to price it" - false, they react to concepts
465. "You can't price what you haven't built" - cost-plus thinking; price is set by VALUE
47 
48---
49 
50## The 9 Rules (Summary)
51 
52| # | Rule | Headline |
53|---|------|----------|
54| 1 | **WTP Talk Early** | 80% of companies skip this. Have it before design freezes. |
55| 2 | **Needs-Based Segmentation** | Demographic segmentation is broken. Segment by needs/value/WTP. |
56| 3 | **Configuration & Bundling** | Use Leaders/Fillers/Killers + Good/Better/Best with FENCES. |
57| 4 | **How You Charge > What You Charge** | Choose the right monetization model (5 options). |
58| 5 | **Pricing Strategy** | Maximization / Penetration / Skimming. Apply the BECAUSE test. |
59| 6 | **Living Business Case** | Link Price-Value-Volume-Cost. Update at every milestone. |
60| 7 | **Value Communication** | Sell benefits, not features. Use MOCA matrix. |
61| 8 | **Behavioral Pricing** | 6 tactics: compromise, anchoring, signals, razor-blade, pennies-a-day, thresholds. |
62| 9 | **Maintain Price Integrity** | Don't cut after launch. Use 3 nonprice actions first. |
63 
64Full framework details with sub-frameworks, methods, and checklists: see [frameworks.md](frameworks.md).
65 
66---
67 
68## Critical Frameworks (At-a-Glance)
69 
70### Leaders / Fillers / Killers
71 
72| Type | Definition | Action |
73|------|------------|--------|
74| **Leader** | Drives buying, high WTP | Always include |
75| **Filler** | Nice-to-have | Use to fill gaps |
76| **Killer** | Blows the deal if forced to pay | Eliminate or sell à la carte |
77 
78Killer test: valued by <20% of customers AND not valued at all by >20%. Killers are segment-dependent (heated seats: leader in cold, killer in tropical).
79 
80### Good/Better/Best Distribution
81 
82| Distribution | Diagnosis |
83|--------------|-----------|
84| ≤25% Good, ~70% Better+Best, ≥10% Best | Healthy |
85| >50% Good | Trip-wire: cut features from Good |
86| Best <10% | Premium tier underpowered |
87 
88**Fences are mandatory.** Every tier needs visible, defensible differences. Without fences G/B/B cannibalizes itself. Fence test: in 10 seconds can a customer see what's missing from Good?
89 
90### The 5 Monetization Models
91 
92| Model | When to Use | Example |
93|-------|-------------|---------|
94| **Subscription** | Continual usage | Netflix, Adobe |
95| **Dynamic Pricing** | Volatile demand or constrained supply | Uber, airlines |
96| **Auctions** | Seller's market, constrained inventory | Google AdWords ($35B/yr), eBay |
97| **Pay-As-You-Go / Alternative Metric** | Usage tracks value | Michelin (per-mile), GE engines |
98| **Freemium** | Near-zero production AND fixed cost | LinkedIn, Dropbox |
99 
100**Freemium warning:** fails for 90% of companies; software conversion typically <10%; games lose 75% of users in day 1.
101 
102Models are mix-and-matchable (Costco = subscription + per-product; OpenTable = subscription + transaction fee).
103 
104### The 6 Behavioral Pricing Tactics
105 
1061. **Compromise effect** - always have 3 tiers; people avoid extremes
1072. **Anchoring** - The Economist test: $59 vs $125 vs $125-print-only made bundle pick rate jump 32% → 84%
1083. **Price signals quality** - Ariely placebo: $2.50 pill 85% pain relief, $0.10 same pill 61%
1094. **Razor / razor blades** - low upfront preferred even if total cost identical
1105. **Pennies-a-day** - $9.99/mo converts very differently from $120/yr
1116. **Psychological thresholds** - $69.99 works, $71 doesn't (drops acceptance >20%)
112 
113**Caveat:** can't price purely on behavior. Combine with rational/value-based.
114 
115---
116 
117## Decision Trees
118 
119### "Is my product likely to fail?"
120 
121```
122Can I clearly state the customer benefit (not features)?
123├─ NO → Likely Feature Shock
124└─ YES → Has WTP been validated with real customers?
125 ├─ NO → Could be Undead or Minivation
126 └─ YES → Did C-suite engage personally?
127 ├─ NO → Likely Hidden Gem (won't get launched right)
128 └─ YES → On the right track
129```
130 
131### "Which monetization model?"
132 
133```
134Is value tied to usage?
135├─ YES → Alternative Metric (Michelin model)
136└─ NO → Demand volatile or supply constrained?
137 ├─ YES → Dynamic Pricing
138 └─ NO → Production cost near zero?
139 ├─ YES → Freemium (only if 90% of users still profitable)
140 └─ NO → Subscription or per-unit
141```
142 
143### "Should I cut the price?"
144 
145```
146Sales below plan?
147└─ YES → Identified ROOT CAUSE?
148 ├─ NO → Diagnose first (likely not price)
149 └─ YES → Pricing-specific?
150 ├─ NO → Fix actual problem
151 └─ YES → Tried 3 nonprice actions?
152 ├─ NO → Try those (advertise; add value; upgrade)
153 └─ YES → War-game competitor reaction
154 └─ Worse off after counter? → don't cut
155```
156 
157---
158 
159## Critical Numbers
160 
161| Number | Rule |
162|--------|------|
163| **72%** | New products fail |
164| **80%** | Companies wait until just before launch to set price |
165| **5%** | Business cases include real WTP data |
166| **3-4** | Ideal starting number of segments |
167| **<10%** | Killer features valued by less than this % |
168| **9 / 4** | Max benefits / products before psychological overload |
169| **≤25% / 70% / ≥10%** | G/B/B target (Good / Better+Best / Best) |
170| **50%** | Trip-wire: more than this picking Good = bleeding |
171| **20-30%** | Healthy deal escalation rate |
172| **30-40%** | Of ALL DEALS should have price changes upon escalation |
173| **3** | Nonprice actions required before any price cut |
174| **40%** | More likely to realize potential with defined pricing strategy |
175| **33%** | More profit when C-suite leads pricing (vs delegates) - also from Simon-Kucher client data; same provenance caveat as the 72% figure applies |
176| **25%** | Of customer interview questions should be "Why?" |
177 
178---
179 
180## The "BECAUSE" Test
181 
182Every pricing decision must end with a "because" traceable to customer data.
183 
184**Bad:** "We priced at $99 to be competitive."
185**Good:** "We priced at $99 BECAUSE 60% of segment B told us $100 was the threshold above which they'd reconsider, and our value advantage justifies the high end."
186 
187If you can't say "because customers told us X," you don't have a pricing strategy.
188 
189---
190 
191## Quick Reference Checklist
192 
193Before designing a new product:
194- [ ] WTP conversations with real customers held
195- [ ] Segmented by needs/value/WTP (not demographics)
196- [ ] Leaders, fillers, killers identified
197- [ ] G/B/B configuration designed with FENCES
198- [ ] Monetization model picked (aligns with value)
199- [ ] Pricing strategy documented (max/penetration/skimming)
200- [ ] Living business case links Price/Value/Volume/Cost
201- [ ] Benefit-not-feature messaging tested
202- [ ] Behavioral tactics considered
203- [ ] Team prepared to maintain price integrity post-launch
204 
205**The test:** Ask anyone "Why this price?" If the answer is "cost-plus" or "competitor benchmark," failure is coming.
206 
207---
208 
209## Critical Quotes
210 
211- "Design the product around the price."
212- "How you charge trumps what you charge."
213- "Pricing too low is worse than pricing too high."
214- "Customers don't buy products. They buy benefits." - Drucker
215- "The single most important decision in evaluating a business is pricing power." - Buffett
216- "If I have 2,000 customers and 400 prices, I'm short 1,600 prices." - Crandall (American Airlines)
217 
218---
219 
220## Supporting Files
221 
222- **[frameworks.md](frameworks.md)** - Full detail on all 9 rules, sub-frameworks, methods, and lists (10 WTP insights, 10 bundling insights, 6 post-launch tips, etc.)
223- **[cases.md](cases.md)** - Detailed case studies (Porsche, Dodge Dart, LinkedIn, Dräger, Uber, Swarovski, Optimizely, Innovative Pharma) plus failure exemplars
224- **[examples.md](examples.md)** - Worked examples: Pizza & Breadsticks bundling math, MOCA matrix, value-selling spreadsheet, 100-point goal allocation, BECAUSE test templates
225- **[integration.md](integration.md)** - Implementation roadmap (4 phases), 9 pitfalls, startup/SaaS adaptation, WTP research limitations, conflict resolution with Mom Test/$100M Offers/SPIN
226 
227---
228 
229## When This Doesn't Apply
230 
231- Pure cost-plus regulated environments (utilities, some defense)
232- Pure commodities (sugar, copper)
233- Very early stage with no product (use Mom Test first)
234- B2C impulse buys under $50 (simpler approaches work)
235- Geographic markets with no purchasing power
236 
237---
238 
239## Caveat on WTP Research
240 
241Stated WTP and revealed WTP differ. Customers predict their own behavior poorly in interviews. Treat WTP findings as a strong prior, not certainty. Validate with paid pilots, pre-orders, live A/B price tests, or money-back guarantees. See [integration.md](integration.md#wtp-research-limitations-critical-caveat).
242 

Discussion

Alternatives

Mobile App Monetization StrategyWhen the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.Sales & ecommerce · MITPaywall Optimization (Subscription Apps)When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.Sales & ecommerce · MITPricing and packagingSets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.Sales & ecommerce · MITPricing Strategy (Lenny's Podcast)Help users validate willingness-to-pay, select the right value metrics, and continuously optimize pricing and packaging to drive growth.Sales & ecommerce · MIT