monetizing-innovation

Featured

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.

AI & Automation 2,147 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 comp...

Details

Author
wondelai
Repository
wondelai/skills
Created
7 months ago
Last Updated
today
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

pricing

Designs pricing and packaging using value-metric selection, Van Westendorp willingness-to-pay analysis, and good-better-best tiering. Picks the metric you charge on, chooses the model (per-seat, usage, tiered), sets three tiers with anchoring, and stress-tests for money left on the table. Use when you say "how should we price this," "what should our tiers be," "are we underpriced," "per-seat vs usage," or "package our plans."

5 Updated 1 weeks ago
Sidsaladi9
AI & Automation Listed

pricing-strategy

Help users design and optimize pricing strategies. Use when someone is setting prices for the first time, considering freemium vs paid models, optimizing monetization, dealing with willingness to pay questions, or transitioning between pricing models.

1 Updated today
Layneformalized225
AI & Automation Listed

pricing

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

3 Updated today
patrickserrano