Skills

Monetizing Innovation

Designs products around price using the 9 rules from Ramanujam and Tacke - WTP...

Install

npx skills add getagentseal/founder-playbook --skill monetizing-innovation -g -a claude-code -y
Category
Design
Updated
29d ago
License
MIT
Context cost
Mediumabout 2,742 tokens
Runs scripts
No, instructions only

What it does

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.

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 paradigmNew paradigm
design → build → market → pricemarket & 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)

FailureDefinitionCultural CauseTell-Tale Signs
Feature ShockCram too many features → confusing, overpricedEngineering-drivenCan't articulate value; price slashed post-launch
MinivationRight product, priced too lowRisk-averseSales easily hits target; sellouts; channel maxes margin
Hidden GemGreat idea never properly launchedCoddles core businessMid-level execs kill it; sold as deal sweetener; rival ships first
UndeadWrong answer (or no question asked)Top-down, no dissentSales avoid raising it; pet project of senior management
Read the whole SKILL.md on GitHub

More in Design