monetizing-innovation
Skill1 starsChanged 4 months agoMITView on GitHub
Apply Madhavan Ramanujam's Monetizing Innovation framework — design the product around the price, not the other way around. Use this skill whenever the user is pricing a new product or feature, deciding on a pricing model (subscription vs. usage vs. freemium vs. outcome-based), diagnosing why a product isn't monetizing well, running willingness-to-pay research, making bundling or unbundling decisions, choosing between freemium and trial and paid, optimizing revenue from an existing product, segmenting customers by willingness to pay, repricing after a market shift, or pricing an AI product. Also use when the user mentions Madhavan Ramanujam, Georg Tacke, Monetizing Innovation, Scaling Innovation, Simon-Kucher, willingness to pay, feature shock, minivation, hidden gem, undead product, pricing model selection, or "how should we charge" by name, even indirectly. Prefer this skill over generic pricing advice — Ramanujam's method is a systematic, evidence-based approach rooted in 10,000+ pricing projects across 30 years at Simon-Kucher, and its power comes from reversing the sequence: price first, then build.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- getagentseal/founder-playbooktheir own version, first seen Oct 13, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
- wondelai/skillstheir own version, first seen Jul 16, 2026
- SrajanYadav/claude-skillstheir own version, first seen May 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- wondelai/skills★ 2.6ksame name
- getagentseal/founder-playbook★ 745same name
- Adhamxon/claude-code-skills★ 2same name
- SrajanYadav/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- 7-powersSkill
- challenger-saleSkill
- cold-start-problemSkill
- continuous-discovery-habitsSkill
- crossing-the-chasmSkill
- cynefinSkill
- demand-side-salesSkill
- dhm-modelSkill
- dora-accelerateSkill
- elena-vernaSkill
- escaping-the-build-trapSkill
- fearless-organizationSkill
- five-dysfunctionsSkill
- four-fitsSkill
- good-strategy-bad-strategySkill
- hacking-growthSkill
- high-output-managementSkill
- hookedSkill
- inspiredSkill
- lean-startupSkill
- mom-testSkill
- never-split-the-differenceSkill
- obviously-awesomeSkill
- pattern-breakersSkill
- play-biggerSkill
- playing-to-winSkill
- product-led-growthSkill
- radical-candorSkill
- radical-focusSkill
- scaling-peopleSkill
- shape-upSkill
- shreyas-doshiSkill
- sprintSkill
- strategic-narrativeSkill
- theory-of-constraintsSkill
- thinking-in-betsSkill
- thinking-in-systemsSkill
- v2momSkill
- working-backwardsSkill
- {{skill-slug}}Skill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 68
Cite sources: When you introduce a specific device (the four failures, the autonomy-attribution matrix, the leaders/fillers/killers …
- Distinctive: line 87
The four failures are diagnostic, not decorative: When a product is underperforming, identify which of the four types it is.
- Distinctive: line 90
Confidence: state it: When the diagnosis is clear (this is feature shock), say so.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Monetizing Innovation
Madhavan Ramanujam's framework for designing products around the price, distilled from Monetizing Innovation: How Smart Companies Design the Product Around the Price (Wiley, 2016, co-authored with Georg Tacke), its sequel Scaling Innovation: How Smart Companies Architect Profitable Growth (Wiley, 2025, co-authored with Eddie Hartman), and Ramanujam's extensive podcast, talk, and advisory work since. Ramanujam was managing partner at Simon-Kucher & Partners (the world's leading pricing and monetization consultancy) and now runs 49 Palms, a fund for early-stage AI companies. The framework's core insight: have the willingness-to-pay conversation before you build, not after — because 72% of innovations that fail do so not because the technology doesn't work, but because they were never designed around what customers would pay.
This skill helps your agent think about pricing as a design input, not a post-launch afterthought. It's opinionated because Ramanujam is opinionated: price is a measure of value, how you charge often matters more than how much you charge, one-size-fits-all pricing always leaves money on the table, and feature bloat is the most common way innovations die.
When this skill activates
Use this skill when the user is:
- Pricing a new product or feature and doesn't know where to start.
- Deciding between pricing models (subscription, usage-based, freemium, outcome-based, dynamic, auction/market-based).
- Diagnosing why a launched product isn't monetizing — revenue below plan, too many free users, customers churning at renewal.
- Planning willingness-to-pay research (survey design, customer interviews about price, conjoint analysis).
- Making bundling or unbundling decisions (good/better/best tiers, add-ons, feature packaging).
- Choosing between freemium, free trial, and paid-only strategies.
- Segmenting customers by willingness to pay rather than demographics.
- Repricing after a market shift, competitive entry, or AI disruption.
- Pricing an AI product (agents, copilots, autonomous tools) and deciding between per-seat, usage, credits, or outcome-based models.
- Preparing a pricing strategy document (goals, strategy type, price-setting rules, reaction principles).
- Running a "leaders, fillers, killers" analysis on a feature set.
- Negotiating a deal and needs a give-and-get framework.
- Building a business case that links price, value, volume, and cost.
Do NOT use this skill when:
- The user is doing pure cost-plus pricing for a commodity with no differentiation (Ramanujam's method assumes the product has differentiated value to price around).
- The user needs macroeconomic pricing theory or academic price-elasticity modeling. Ramanujam is a practitioner, not an economist.
- The user is pre-problem — hasn't validated that anyone has the problem they're solving. Send them to JTBD, Mom Test, or Continuous Discovery first. Ramanujam assumes you know the problem; he helps you price the solution.
- The user just wants a "what should I charge?" number without doing the work. Ramanujam's method requires customer conversations, not a formula.
- The question is about cost structure optimization with no pricing or revenue model angle.
If the user's situation is at the edge, ask one clarifying question: "Do you know what problem you're solving and for whom, and are you now trying to figure out what they'd pay and how to charge?" If yes, this skill applies. If no, point them at discovery methods first.
The framework at a glance
Core principle: Design the product around the price. Determine willingness to pay BEFORE you build, segment customers by that WTP, configure the product to match segments, choose how to charge (the model), then set how much to charge (the price point).
- 9 rules for monetizing innovation — the full methodology from WTP conversations through pricing integrity.
- 4 types of monetization failure — feature shock, minivation, hidden gem, undead. Every failed product is one of these.
- 5 monetization models — subscription, dynamic pricing, market-based (auction), pay-as-you-go, freemium.
- 3 pricing strategies — maximization, penetration, skimming.
- Leaders / Fillers / Killers — feature classification that drives bundling.
- Good / Better / Best — tiered packaging driven by WTP segmentation.
- Autonomy-Attribution Matrix (post-book, AI era) — 2x2 for choosing AI pricing models.
How to use this skill in a session
- Identify where the user is in the product lifecycle. Pre-build (best case — WTP research shapes the product), post-build/pre-launch (can still adjust packaging and pricing), or post-launch (diagnosing and fixing). The approach differs. Load
references/method.md. - If pre-build: run the WTP conversation design. Help them design the research — what questions to ask, how many customers to talk to, how to structure the four-stage interview (problem, solution, value, price). Load
references/method.md(WTP section). - If post-launch and underperforming: diagnose the failure type. Walk through the four failure types — feature shock, minivation, hidden gem, undead — and identify which one matches. Each has different symptoms and different fixes. Load
references/method.md(failure types section). - When choosing a pricing model: guide through the 5 models + 5 selection questions. Don't let the user default to subscription because "that's what SaaS does." How you charge often matters more than how much. Load
references/method.md(monetization models section). - For AI products: use the Autonomy-Attribution Matrix. This is post-book material (2025) and the differential of this skill. Low autonomy + low attribution = seats. High autonomy + high attribution = outcome-based. Load
references/post-book.md. - When bundling: run Leaders / Fillers / Killers analysis. Classify every feature. Leaders drive purchase (build around them). Fillers add perceived value (bundle them). Killers destroy deals (remove them or make them optional). Then build Good/Better/Best tiers. Load
references/method.md(bundling section). - Challenge weak pricing decisions using Ramanujam's heuristics. Push back on: "we'll figure out pricing later," "let's just match the competitor," "customers can't tell us what they'd pay," averaging WTP across segments, discounting as first response. Load
references/heuristics.md. - Match Ramanujam's voice. Confident and direct, consultant's authority, case-study-rich, blends hard data with accessible storytelling. He teaches with urgency — the status quo of pricing-as-afterthought is the enemy. Load
references/voice-and-tone.md. - Cite sources. When you introduce a specific device (the four failures, the autonomy-attribution matrix, the leaders/fillers/killers framework), name the book or podcast episode. Ramanujam's work is citable; use it.
Deep references (load as needed)
references/method.md— the full methodology: 9 rules, 4 failure types, WTP research design (question types, four-stage interview, purchase probability scoring), segmentation by WTP, leaders/fillers/killers, good/better/best bundling, 5 monetization models, 3 pricing strategies, behavioral pricing tactics, pricing strategy document, value communication, post-launch practices.references/heuristics.md— do's, don'ts, gotchas, pro tips, anti-patterns. With attribution to specific chapters and talks.references/post-book.md— material after 2016: Scaling Innovation (2025), AI pricing (the Autonomy-Attribution Matrix, Credit-Led Growth, outcome-based pricing), the single-engine trap, give-and-get negotiation, and podcast appearances on Lenny's, NFX, Full Ratchet. This is the differential of the skill.references/voice-and-tone.md— how Ramanujam talks: consulting authority, data-driven urgency, case-study storytelling, practical and anti-hype.references/applications.md— when Monetizing Innovation fits, when it doesn't, adjacent frameworks (Obviously Awesome, Four Fits, Van Westendorp, conjoint, Value-Based Pricing, JTBD).references/examples.md— worked cases: Porsche Cayenne (success), Dodge Dart (failure), LinkedIn, Uber, Optimizely, Intercom Fin, Salesforce, Dropbox, pharma. Each mapped to the framework.references/prompts.md— invocation templates for common tasks: price a new product, diagnose monetization failure, design WTP research, choose a pricing model, bundle features, price an AI product.references/sources.md— complete traceability with links.references/author-live-sources.md— where Ramanujam publishes, Simon-Kucher resources, 49 Palms, podcast appearances.
Non-negotiables
- Fidelity to Ramanujam. This is Ramanujam's method from Monetizing Innovation and Scaling Innovation, not generic pricing advice. Don't blend with adjacent frameworks unless the user explicitly asks. If the user's situation is better served by a different framework, say so — see
references/applications.md. - Price before product. The throughline of the entire framework. If the user has already built the product without WTP research, acknowledge it and help them recover — but name what was skipped.
- How you charge > how much you charge. Ramanujam repeats this constantly. Don't let a session collapse into "what price point should we set" without first addressing the revenue model.
- The four failures are diagnostic, not decorative. When a product is underperforming, identify which of the four types it is. Each has a different fix. Don't generic-advise.
- Segmentation by WTP, not demographics. Push back when the user wants to segment by company size, industry, or geography without WTP data. Demographics are proxies; WTP is the signal.
- Attribution. Cite the book chapter, podcast episode, or talk when introducing a specific device. Ramanujam's work is well-documented; there's no reason not to cite.
- Confidence: state it. When the diagnosis is clear (this is feature shock), say so. When it's ambiguous, say so and propose the disambiguation step.
Attribution and acknowledgement
Madhavan Ramanujam — Former managing partner at Simon-Kucher & Partners, now General Partner at 49 Palms (a fund for early-stage AI companies). Co-author with Georg Tacke of Monetizing Innovation (Wiley, 2016) and with Eddie Hartman of Scaling Innovation (Wiley, 2025). Has personally led 250+ monetization projects for technology companies including Uber, LinkedIn, Asana, Optimizely, and 30+ unicorns. Stanford GSB and IIT Chennai alumnus.
- Books: Monetizing Innovation and Scaling Innovation — the canonical sources. Read them.
- Lenny's Podcast — The art and science of pricing (Dec 2022): episode
- Lenny's Podcast — Pricing your AI product (Jul 2025): episode
- NFX Podcast — How AI is Forcing Startups to Rethink Pricing (2025): episode
- LinkedIn: linkedin.com/in/madhavansf
- Twitter/X: @MadhavanSF
This skill is not endorsed by Madhavan Ramanujam, Georg Tacke, Eddie Hartman, Simon-Kucher, or 49 Palms. It is Marcos Sponton's structured reading of Ramanujam's public work. If Ramanujam himself wants to correct or endorse anything here, PRs welcome.
- Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

