For Agents · MCP

Your task.
The right skill.

The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.

No local installationNo M11 loginRead-only

Broad task

Load 5–10 and go

SEO, Sales, Agents or another broad area → one bundle call → work.

MCP endpoint: https://skills.m11.ch/mcp

Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.

Task Packs

Marketing Foundation

Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.

Marketing Launch

Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.

Agent Audit Essentials

Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.

Conversion and Activation Review

Review the journey from landing page and lead capture through registration, first value and transparent upgrades.

Campaign Content and Brand Review

Plan a campaign, draft its channel content and review the work against actual brand guidance.

Content and Launch Planning

Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.

Customer, Market and Community Research

Understand customer needs, compare competitors and plan a community around real member value.

Lead Magnet to Lifecycle Nurture

Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.

API Contract and Observability

Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.

Data Analysis Foundation

Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.

B2B Outreach Foundation

Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.

Choose an area

01 · Category

What the MCP returns at this step

53 · Business · Pricing Strategy

Monetizing Innovation

Frames pricing and packaging around validated willingness to pay before product scope is committed.

pricingwillingness-to-paypackagingfreemiumprice-metricpreisstrategiezahlungsbereitschaftpaketierung

Monetizing Innovation · Original SKILL.md

---
name: monetizing-innovation
description: 'Design products and pricing around validated willingness to pay, from Ramanujam & Tacke''s "Monetizing Innovation". Use when the user mentions "pricing", "how much should we charge", "willingness to pay", "pricing page", "packaging", "freemium vs free trial", "are we leaving money on the table", "nobody buys at this price", "price increase", or "good-better-best". Also trigger when designing or auditing pricing and packaging, validating willingness to pay before building, segmenting customers by value, or choosing between subscription, usage-based, and freemium models. Covers price-before-product, willingness-to-pay talks, the four failures (feature shock, minivation, hidden gem, undead), leader/filler/killer packaging, and behavioral pricing. For offers and guarantees, see hundred-million-offers. For what customers value, see jobs-to-be-done.'
license: MIT
metadata:
  author: wondelai
  version: "1.2.0"
---

# 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) before you run interviews: the exact question scripts (direct, purchase-probability, acceptable/expensive/prohibitive), the simplified-conjoint procedure, sample sizes for B2B vs B2C, how to read the answers, and how to turn a WTP range into specs.

### 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 — minivation; reprice |
| Portfolio audit | Hunt for unmonetized byproducts and zombies | Internal fraud-scoring tool becomes a paid API; two zombie products sunset |

**Ethical boundary:** "Kill the undead" applies to products, never to evidence — massaging research to keep a favorite alive creates the next undead.

See [references/four-failures.md](references/four-failures.md) when a product is underperforming and you need to classify it: symptom checklists, root causes, the matching countermeasure, and a worked example for each of feature shock, minivation, hidden gems, and undead, plus a classification decision tree.

### 3. Segment by Willingness to Pay

**Core concept:** Customers differ in what they need and what they will pay, so a single offer at a single price overcharges some and undercharges the rest. Segment by needs, value, and WTP — not by demographics or firmographics — and design a distinct offer for each segment worth serving.

**Why it works:** Averages lie: a market with average WTP of $50 may contain nobody who would pay $50 — half value the product at $20, half at $100. One $50 product loses both halves. Segment-specific offers recover the high end's money and the low end's volume, and the segmentation tells sales who they are talking to before the demo starts.

**Key insights:**
- Segment on WTP and needs first, then find observable markers (size, industry, use case) that identify each segment — never the reverse
- Three or four segments is the practical ceiling: beyond that, sales cannot tell them apart and operations cannot serve them differently
- Segments are dynamic — early adopters' WTP rarely predicts the mainstream's; re-run the analysis as the market matures
- Serving everyone is a choice to serve no one well: pick segments where WTP, cost to serve, and reachability line up, and explicitly skip the rest
- Each segment needs its own value proposition and leader features, not just its own price point
- If two segments buy for the same reason at the same WTP, they are one segment — merge them

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Tier design | One offer per WTP cluster | Interviews cluster at $15, $40, and $120/seat → Starter, Team, Enterprise |
| Sales qualification | Identify the segment from two or three observable markers | Compliance requirement plus 200+ seats flags the high-WTP segment |
| Roadmap split | Build each segment's leader, not everyone's filler | Advanced permissions built for Enterprise only; Starter gets simplicity |

**Ethical boundary:** Differentiate prices by value delivered and offer differences — never by exploiting captivity or protected characteristics.

See [references/wtp-conversations.md](references/wtp-conversations.md) (the "Build the WTP curve, not the average" section) when your interview data is in hand: reading cliffs and plateaus to find segments, why the mean of a bimodal market describes a customer who does not exist, and the worked WTP-curve example.

### 4. Packaging and Bundling

**Core concept:** Classify every feature as a leader (drives the purchase decision), a filler (adds modest value), or a killer (actively reduces WTP if customers are forced to pay for it). Build good-better-best tiers around leaders, use fillers to round out and differentiate, and pull killers out into add-ons — or out of the product.

**Why it works:** Leaders give each tier a reason to exist; a premium tier anchors the middle as reasonable; a single killer left in a bundle gives buyers a reason to reject the whole thing, not just that feature. The same features, packaged differently, can double or halve revenue.

**Key insights:**
- A killer is not a bad feature — it is value one segment refuses to fund; on-prem deployment is a killer for SMBs and a leader for banks
- Never give the leader away in the lowest tier — leave a taste of it, not the meal
- Design the middle tier first: the compromise effect means most buyers take it, so make it the offer you want to sell
- Plan around roughly 70/20/10 across middle/premium/entry tiers — most buyers at the bottom means weak fences; most at the top means you are minivating
- Bundle when components are complementary and raise total WTP; unbundle the moment segments diverge or a killer sneaks in
- Three tiers is the default, four the ceiling — beyond that, choice paralysis cuts conversion

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Pricing page | Anchor high, sell the middle | Best at $199 anchors; Better at $79 carries ~70% of buyers |
| New feature | Classify before you slot it | Audit log tests as an enterprise leader → Best tier only |
| Bundle review | Pull killers out as add-ons | White-label reporting becomes a $49 add-on; Pro price drops, conversion rises |

**Ethical boundary:** Fence tiers on value added, never on essentials held hostage — security, privacy, and data export belong in every tier.

See [references/packaging-tiers.md](references/packaging-tiers.md) when you are slotting features into tiers: the leader/filler/killer scoring procedure, good-better-best design rules, a feature-allocation matrix, tier naming, upgrade paths, the bundling checklist, and pricing-page implications.

### 5. Choosing the Monetization Model

**Core concept:** How you charge matters as much as how much: subscription, usage-based, freemium-fed, dynamic, or outcome-based — and within the model, the price metric (per seat, per gigabyte, per transaction, per outcome). Pick the metric that tracks delivered value, then the model that matches how customers consume and pay.

**Why it works:** The same product at the same average price succeeds or fails on model alone, because the model allocates risk and aligns cash flow with value. A metric that tracks delivered value grows revenue automatically as customers succeed; a mismatched metric — per-seat pricing for a product whose value is per-transaction — caps upside and breeds resentment at renewal.

**Key insights:**
- Choose the price metric first, the price level second — the metric decides whether revenue scales with the value you create
- Freemium is an acquisition tool, not a pricing model: the free tier is marketing spend and must be engineered for conversion, not generosity
- Usage-based pricing lowers the adoption barrier but imports volatility and bill shock — add caps, alerts, or committed tiers
- Per-seat is easy to budget but taxes collaboration; per-outcome aligns perfectly but requires attribution both sides trust
- Hybrid (platform fee plus usage) is often the adult answer: a predictable floor with value-tracking upside
- A model migration reprices every existing customer at once — grandfather generously and lead with the value story

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Model selection | Match the model to value delivery and cash flow | Infra API prices per 1,000 calls; design tool stays per-editor |
| Freemium design | Free tier demonstrates the leader, capped at the habit point | Free covers 3 boards; the 4th — where teams form habits — starts Pro |
| Migration | Run old and new models in parallel | Flat-rate customers keep 12 months' grandfathering while new signups join tiers |

**Ethical boundary:** Pick metrics customers can predict and audit — a surprise bill monetizes confusion, not value.

See [references/monetization-models.md](references/monetization-models.md) when you are choosing how to charge: when each model wins (subscription, usage, hybrid, freemium, dynamic, outcome-based), the failure mode of each, how to choose the price metric, and how to migrate between models without churning your base.

### 6. Behavioral Pricing and Price Communication

**Core concept:** Customers do not compute value; they perceive it in context. Anchors, the compromise effect, decoy options, and price endings shape that perception — and after launch, disciplined communication and patience protect the price you set. Decide in advance how you will respond to underperformance so week-one fear never sets strategy.

**Why it works:** WTP is constructed at the moment of choice: the same $79 plan reads as expensive alone and as reasonable next to a $199 anchor. And because launches wobble before they converge, teams without pre-agreed triggers panic-discount in week one — permanently resetting price perception to fix what was usually an awareness or packaging problem.

**Key insights:**
- Anchors work even when arbitrary — lead with the premium option and everything after it looks affordable
- The compromise effect pulls buyers to the middle: adding a deliberately premium option moves the whole distribution up
- A decoy — an option slightly worse than the one you want sold — exists to be rejected; measure whether it shifts choices, not whether it sells
- Charm endings ($9.99) signal deal; round numbers ($200) signal quality — match the ending to your position instead of defaulting
- Announce price increases with the value story first, specifics second, and ample notice — never apologize-and-discount in the same breath
- Underperformance has many causes — awareness, channel, packaging — and price is the last lever to pull; set day-30/60/90 triggers before launch, then monitor instead of panicking

**Applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Pricing page | Order tiers high to low to set the anchor | Listing $499 Enterprise first lifts $149 Pro conversion |
| Price increase | Lead with delivered value, give notice | "What shipped this year" recap precedes the +15% renewal notice |
| Slow launch | Diagnose before discounting | Day-30 review: trial-to-paid is healthy, traffic is low → fix acquisition, hold price |

**Ethical boundary:** Behavioral tactics must frame real value, never manufacture it — anchors, decoys, and endings become deception the moment the claims behind them are false.

## Common Mistakes

| Mistake | Why It Fails | Fix |
|---------|-------------|-----|
| Building first, pricing at launch | Joins the 72% that miss revenue targets; flaws surface when change is expensive | Test WTP at concept stage and let it shape scope |
| Cost-plus or competitor-copy pricing | Anchors on your costs or their strategy — neither measures your customers' value | Price from validated WTP ranges |
| Asking "would you buy this?" | Yields polite yeses; stated intent always overstates | Use acceptable/expensive/prohibitive probes and forced trade-offs |
| Designing for average WTP | The mean describes a customer who does not exist | Segment the WTP curve; build per segment |
| One-size-fits-all offer | Overcharges some segments, undercharges others | Three or four offers matched to WTP clusters |
| Bundling killers into tiers | Buyers refuse to fund value they do not want | Unbundle killers into add-ons or cut them |
| Freemium as the business model | Free users feel like traction while revenue starves | Treat free as acquisition; cap it at the habit point and gate the leader |
| Panic-discounting a slow launch | Permanently resets price perception and masks the real problem | Pre-set triggers; diagnose awareness and packaging first |

## Quick Diagnostic

| Question | If No | Action |
|----------|-------|--------|
| Did customers answer WTP questions before specs froze? | You are building on hope | Run 15-20 WTP interviews on the concept now |
| Do you know which of the four failures you are drifting toward? | Countermeasures will be guesses | Run the four-failures classification |
| Are segments defined by needs and WTP, not demographics? | Offers will not match value | Re-cluster customers on WTP interview data |
| Is every feature classified leader, filler, or killer? | Packaging is guesswork | Score features by WTP before slotting them into tiers |
| Does the lowest tier withhold the leader feature? | Nobody has a reason to upgrade | Move the leader up; leave a taste, not the meal |
| Does the price metric grow as customer value grows? | Revenue decouples from success | Re-pick the metric: seat, usage, or outcome |
| Is there a living business case linking WTP, price, volume, and cost? | Targets are fiction | Build it before launch; update it on every change |
| Are post-launch reaction triggers agreed in advance? | Week-one fear will set pricing | Define day-30/60/90 metrics, thresholds, and responses now |

## Worked Examples

See [references/case-studies.md](references/case-studies.md) to watch the whole framework run end-to-end on three companies: flat-to-tiered repricing after WTP interviews surfaced three segments, catching feature shock pre-launch when the WTP curve stayed flat as scope grew, and fixing a 1.1% freemium conversion by moving the leader behind the paywall.

## Further Reading

- [*"Monetizing Innovation: How Smart Companies Design the Product Around the Price"*](https://www.amazon.com/Monetizing-Innovation-Companies-Design-Product/dp/1119240867?tag=wondelai00-20) by Madhavan Ramanujam & Georg Tacke
- [*"Confessions of the Pricing Man: How Price Affects Everything"*](https://www.amazon.com/Confessions-Pricing-Man-Affects-Everything/dp/3319203991?tag=wondelai00-20) by Hermann Simon

## About the Authors

**Madhavan Ramanujam** is a board member and partner at Simon-Kucher & Partners who has led hundreds of monetization projects and advised many of Silicon Valley's unicorns on pricing. **Georg Tacke** was co-CEO of Simon-Kucher, the world's largest pricing and monetization consultancy, with three decades advising executives worldwide. Together they distilled the firm's methodology into *Monetizing Innovation*.

When to use

Frames pricing and packaging around validated willingness to pay before product scope is committed.

What you get

The complete original framework with its attribution, declared license and M11 routing limits.

How it works

Establish the actual context and evidence, apply the framework, then separate recommendations from decisions that need an accountable owner.

Requirements

Product, segments, observed customer evidence, cost model, pricing constraints and decision owner.

Delivery and review notes

Original documentation is published by Wondel.ai sp. z o.o. under the repository MIT license at the pinned revision. Its cited books and named frameworks are not reproduced or relicensed by M11; the unchanged upstream document is the supplied source. The content is planning guidance only: validate claims, benchmarks, pricing, market facts and legal/commercial decisions against current evidence. Loading it does not authorize outreach, purchases, data collection, publishing, account changes or other external action.

Starting prompt

Use Monetizing Innovation for [TASK]. First establish Product, segments, observed customer evidence, cost model, pricing constraints and decision owner. Separate known facts from assumptions and return a bounded plan with open questions. Do not claim validation, authorization, execution or current benchmarks without evidence.

Not for

Setting prices, making revenue guarantees or treating framework scores as financial advice.

What M11 added

M11 added German discovery terms, flat public routing and scope limits. Original documentation is published by Wondel.ai sp. z o.o. under the repository MIT license at the pinned revision. Its cited books and named frameworks are not reproduced or relicensed by M11; the unchanged upstream document is the supplied source. The content is planning guidance only: validate claims, benchmarks, pricing, market facts and legal/commercial decisions against current evidence. Loading it does not authorize outreach, purchases, data collection, publishing, account changes or other external action.

Original authorship remains with wondelai/skills · Original source ↗

Original license & copyright

MIT License

Copyright (c) 2025 Wondel.ai sp. z o.o.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Source SHA-256: 690c57380a24a34f41069d3915366160be8d4db08fa7a643ff5c3751dad14375
Snapshot checked: 2026-09-28T17:34:39.899Z

Find a skill.Get to work.

All skills

Multi-Agent Orchestration

AI Context Window Audit

AI Agent Architecture Audit

AI Skill Discovery

Lead Magnet Strategy

Ideal Customer Profile

Go-to-Market Strategy

Marketing Campaign Ideas

Product Growth Loops

Competitor Analysis

North Star Metric

Product Positioning

Product Vision

Go-to-Market Motion Selection

Customer Feedback and JTBD Analysis

PESTLE Market Environment Analysis

Customer Journey Mapping

Ansoff Growth Options

Data Analysis Validation

Dataset Profiling

Statistical Analysis Guidance

Programmatic SEO Planning

Landing Page and Form Conversion Review

Paywall and Upgrade Planning

Signup and Registration Review

User Onboarding and Activation

Popup and Modal Planning

Email Sequence Copy and Flow

Marketing Campaign Planning

Marketing Content Drafting

Brand Voice and Content Review

Marketing Performance Reporting

Sales Company Research

Company and Contact Enrichment

Website Information Architecture

Content Strategy and Editorial Roadmap

Product Launch Planning

Customer Research and Voice of Customer

Community Growth and Member Experience

Competitor Research Profiles

Roadmap and Release Communication

Lifecycle Email Sequences

API Contracts and Interface Design

Observability and Instrumentation Planning

Agent Context and Session Handoff

Product Discovery Sprint

Deal Quality Scoring

Enrichment Waterfall Design

Customer Retention Playbook

Sales Coaching Practice

Revenue Cohort Analysis

Intent Signal Scoring

Customer Identity Matching

Segment Activation Planning

Sales Call Review

Retention Dashboard Design

Sales Coaching Competencies

Offer Delivery Design

Offer Value Communication

Service Productization

Conversion Hypothesis Prioritization

Braze Engagement Guidance

Brand Voice Guide Design

Content Pipeline Orchestration

Website Brand Profile

Buyer Objection Clarification

Klaviyo Integration Guidance

Offer Bonus Planning

Klaviyo Marketing Review

Cross-Platform Advertising Review

Expertise Business Model

LinkedIn Advertising Guidance

TikTok Advertising Guidance

Evidence Research Brief

Cinematic Video Prompts

Visual Prompt Model Adaptation

Visual Prompt Diagnostics

Short Film Development

Find a skill.
Get to work.