Agent skill · Business & Finance

monetizing-innovation

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-prod

wondelaigithub.com/wondelaiGitHub ↗
claude-codeMIT
Install
npx skills add wondelai/skills --skill monetizing-innovation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 20 KB
Bundled scripts: none
Version: 1.2.0
Declared author: wondelai
Path: monetizing-innovation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,835
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 tie

What's inside
Steps it walks through
  1. Core Principle
  2. Scoring
  3. Framework
  4. 1. Price Before Product
  5. 2. The Four Monetization Failures
  6. 3. Segment by Willingness to Pay
  7. 4. Packaging and Bundling
  8. 5. Choosing the Monetization Model
  9. 6. Behavioral Pricing and Price Communication
  10. Common Mistakes
  11. Quick Diagnostic
  12. Worked Examples
  13. Further Reading
  14. About the Authors
Ships with 5 files
  • references/case-studies.md
  • references/four-failures.md
  • references/monetization-models.md
  • references/packaging-tiers.md
  • references/wtp-conversations.md
More from skills
All skills →
About this skill
What does the monetizing-innovation skill do?

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-prod

How do I install it?

Run `npx skills add wondelai/skills --skill monetizing-innovation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going