monetizing-innovation

# Monetizing Innovation

A framework for designing the product around the price, distilled from Simon-Kucher partners Madhavan Ramanujam and Georg Tacke's *Monetizing Innovation*. Use it to validate willingness to pay before building, dodge the four monetization failures, segment customers by value, package features into tiers people actually want, choose the right monetization model, and price with behavioral science instead of gut feel.

## Core Principle

**Design the product around the price — have the willingness-to-pay talk early.** 72% of new products miss their revenue targets, and the common root cause is treating price as an afterthought: build first, guess a number at launch. Price is a measure of how much customers value what you are building, which makes it the best early signal of whether to build it at all. Test willingness to pay at the concept stage and let it shape scope, segments, packaging, and the business case.

## Scoring

**Goal: 10/10.** Rate pricing and packaging decisions 0-10 against the principles below. Report the current score and the specific changes needed to reach 10/10.

- **9-10:** WTP validated at concept stage; segments built on value; leader-led tiers with killers unbundled; price metric tracks delivered value; launch monitored against pre-agreed triggers
- **7-8:** Real WTP research, but it arrived late or packaging still carries a killer feature; monetization model chosen deliberately
- **5-6:** Price set near launch from costs or competitors; one-size-fits-all offer; tiers or freemium copied from industry fashion
- **3-4:** Roadmap driven by feature enthusiasm; price a finance afterthought; discounting starts in week one
- **0-2:** No pricing conversation before launch; feature-shocked flagship, no segments, price cuts as the only lever

## Framework

### 1. Price Before Product

**Core concept:** Have the willingness-to-pay talk while the product is still a concept — before specs freeze, before the business case is locked, before code is written. You are not setting the final price; you are measuring whether customers value the idea, how much, and which parts of it. Those answers shape what gets built and for whom.

**Why it works:** WTP data turns pricing from a launch-week guess into a design input. If customers will not pay enough to sustain the product, you learn it while change is cheap; if they will pay far more than assumed, you build the premium version instead of leaving money on the table. The business case stops being hockey-stick fiction and becomes a testable claim you maintain as a living document.

**Key insights:**
- Customers cannot name the perfect price, but they reliably reveal a range — ask what feels acceptable, what feels expensive, and what is prohibitively expensive
- Ask purchase probability on a 1-5 scale and trust only the top box: 5s count (discounted), 4s are maybes, everything below is a no
- Trade-off questions beat direct ones: ranking features or choosing between priced bundles exposes real priorities
- Run it as a value conversation ("what would this be worth to you?"), never as a quote — you are researching, not negotiating
- If you cannot state the WTP range for a feature, you cannot justify building it
- Rebuild the business case whenever scope, segment, or price assumptions move — it should live weekly, not annually

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| New product concept | Run WTP interviews before specs freeze | 15 target-buyer interviews put the concept at $40-60/seat before the roadmap is set |
| Business case | Anchor revenue on tested WTP, not analogy | Model uses the interview WTP curve, not "1% of a $2B market" |
| Feature decision | Gate roadmap items on WTP evidence | SSO ships because 8 of 10 enterprise interviews flag it as must-pay |

**Ethical boundary:** WTP research exists to match price to delivered value — not to find each customer's maximum pain and extract it.

See: [references/wtp-conversations.md](references/wtp-conversations.md)

### 2. The Four Monetization Failures

**Core concept:** Monetization disasters come in four types. Feature shock: cramming too much into one product until complexity and cost destroy value. Minivation: the right product priced too timidly, leaving money on the table. Hidden gem: a game-changing product the organization never recognizes or monetizes. Undead: a product nobody wants, kept alive past the evidence. Every struggling product is drifting toward one of these.

**Why it works:** Naming the failure mode turns a vague "sales are soft" into a specific countermeasure: cut the feature pile, raise the price, give the gem an owner, or kill the zombie. The same WTP research that would have prevented each failure is also how you diagnose it — the diagnosis is testable, not a matter of opinion.

**Key insights:**
- Feature shock shows up in research as flat WTP while features pile on — each addition raises cost and confusion but not value
- Minivation hides behind internal anchors: the 10x product priced 10% above the product it replaces
- A win rate near 100% and zero price pushback is not great sales — it is minivation's signature
- Hidden gems die of ownership, not value: byproducts and side tools have no monetization owner unless one is appointed
- Undead products survive on sunk cost and rationalized research ("respondents didn't get it") — set kill criteria before you are emotionally invested
- Each failure has an opposite cure — cut, raise, spin out, kill — and applying the wrong one makes things worse

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Pre-launch review | Classify which failure the product is drifting toward | All-in-one analytics suite tests as feature shock; cut to the three features with proven WTP |
| Price review | Check price against the WTP ceiling, not last year's list | Plugin priced at $9 while interviews call $49 acceptable — m