Agent skill

Monetizing Innovation

by getagentseal in getagentseal/founder-playbook

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…

MITAuto-check passed

Install Monetizing Innovation

skills CLI
$ npx skills add getagentseal/founder-playbook --skill monetizing-innovation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getagentseal/founder-playbook monetizing-innovation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/monetizing-innovation .claude/skills/monetizing-innovation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
monetizing-innovation
GitHub stars
729
Token cost
~2.9k tokens
SKILL.md length
1,217 words
Files
5
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: "Build it and they will come" - hides… → "Innovation needs isolated artists" -… → "High failure rates are normal" -… → …
  • Designing new products
  • SKILL.md covers Core Insight, The 4 Failure Types (Diagnose…, The 5 Pricing Myths (Counter… and The 9 Rules (Summary), plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Monetizing Innovation is an agent skill from getagentseal/founder-playbook. 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…

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `cases.md`, `examples.md` and `frameworks.md`).

The repository describes itself as: 15 proven business books distilled into AI-native skills. Works with Claude Code, ChatGPT, Gemini, Cursor. The licence is MIT.

When your agent uses it

  • Designing new products
  • Validating pricing for SaaS/B2B/B2C launches
  • Choosing between subscription/usage/freemium models
  • Fixing post-launch sales below plan

Example prompts

  • “s price it later”
  • “Use the monetizing-innovation skill to design products around price using the 9 rules from Ramanujam and Tacke - WTP conversations, needs-based…”
  • “/monetizing-innovation”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. "Build it and they will come" - hides 95% of failures
  2. "Innovation needs isolated artists" - customer input informs, doesn't pollute
  3. "High failure rates are normal" - failure is preventable
  4. "Customers must experience product to price it" - false, they react to concepts
  5. "You can't price what you haven't built" - cost-plus thinking; price is set by VALUE

What it can do on your machine

Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Monetizing Innovation loads about 2.9k tokens when it runs. Until then it costs about 148 tokens; SKILL.md has 1,217 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~148
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 1,217 words, ~2,897 tokens.

Download SKILL.mdSave it as .claude/skills/monetizing-innovation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
monetizing-innovation
description
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

Real examples: Amazon Fire Phone (Feature Shock, $170M write-down), Audi Q7 (Minivation, missed €210M/yr), Kodak digital camera 1974 (Hidden Gem), Segway/Google Glass (Undead).

Full case file: see cases.md.


The 5 Pricing Myths (Counter These)

  1. "Build it and they will come" - hides 95% of failures
  2. "Innovation needs isolated artists" - customer input informs, doesn't pollute
  3. "High failure rates are normal" - failure is preventable
  4. "Customers must experience product to price it" - false, they react to concepts
  5. "You can't price what you haven't built" - cost-plus thinking; price is set by VALUE

The 9 Rules (Summary)

#RuleHeadline
1WTP Talk Early80% of companies skip this. Have it before design freezes.
2Needs-Based SegmentationDemographic segmentation is broken. Segment by needs/value/WTP.
3Configuration & BundlingUse Leaders/Fillers/Killers + Good/Better/Best with FENCES.
4How You Charge > What You ChargeChoose the right monetization model (5 options).
5Pricing StrategyMaximization / Penetration / Skimming. Apply the BECAUSE test.
6Living Business CaseLink Price-Value-Volume-Cost. Update at every milestone.
7Value CommunicationSell benefits, not features. Use MOCA matrix.
8Behavioral Pricing6 tactics: compromise, anchoring, signals, razor-blade, pennies-a-day, thresholds.
9Maintain Price IntegrityDon't cut after launch. Use 3 nonprice actions first.

Full framework details with sub-frameworks, methods, and checklists: see frameworks.md.


Critical Frameworks (At-a-Glance)

Leaders / Fillers / Killers
TypeDefinitionAction
LeaderDrives buying, high WTPAlways include
FillerNice-to-haveUse to fill gaps
KillerBlows the deal if forced to payEliminate or sell à la carte

Killer test: valued by <20% of customers AND not valued at all by >20%. Killers are segment-dependent (heated seats: leader in cold, killer in tropical).

Good/Better/Best Distribution
DistributionDiagnosis
≤25% Good, ~70% Better+Best, ≥10% BestHealthy
>50% GoodTrip-wire: cut features from Good
Best <10%Premium tier underpowered

Fences are mandatory. Every tier needs visible, defensible differences. Without fences G/B/B cannibalizes itself. Fence test: in 10 seconds can a customer see what's missing from Good?

The 5 Monetization Models
ModelWhen to UseExample
SubscriptionContinual usageNetflix, Adobe
Dynamic PricingVolatile demand or constrained supplyUber, airlines
AuctionsSeller's market, constrained inventoryGoogle AdWords ($35B/yr), eBay
Pay-As-You-Go / Alternative MetricUsage tracks valueMichelin (per-mile), GE engines
FreemiumNear-zero production AND fixed costLinkedIn, Dropbox

Freemium warning: fails for 90% of companies; software conversion typically <10%; games lose 75% of users in day 1.

Models are mix-and-matchable (Costco = subscription + per-product; OpenTable = subscription + transaction fee).

The 6 Behavioral Pricing Tactics
  1. Compromise effect - always have 3 tiers; people avoid extremes
  2. Anchoring - The Economist test: $59 vs $125 vs $125-print-only made bundle pick rate jump 32% → 84%
  3. Price signals quality - Ariely placebo: $2.50 pill 85% pain relief, $0.10 same pill 61%
  4. Razor / razor blades - low upfront preferred even if total cost identical
  5. Pennies-a-day - $9.99/mo converts very differently from $120/yr
  6. Psychological thresholds - $69.99 works, $71 doesn't (drops acceptance >20%)

Caveat: can't price purely on behavior. Combine with rational/value-based.


Decision Trees

"Is my product likely to fail?"
Can I clearly state the customer benefit (not features)?
├─ NO  → Likely Feature Shock
└─ YES → Has WTP been validated with real customers?
         ├─ NO  → Could be Undead or Minivation
         └─ YES → Did C-suite engage personally?
                  ├─ NO  → Likely Hidden Gem (won't get launched right)
                  └─ YES → On the right track
"Which monetization model?"
Is value tied to usage?
├─ YES → Alternative Metric (Michelin model)
└─ NO  → Demand volatile or supply constrained?
        ├─ YES → Dynamic Pricing
        └─ NO  → Production cost near zero?
                ├─ YES → Freemium (only if 90% of users still profitable)
                └─ NO  → Subscription or per-unit
Show full SKILL.md (486 more words)Show less
"Should I cut the price?"
Sales below plan?
└─ YES → Identified ROOT CAUSE?
         ├─ NO  → Diagnose first (likely not price)
         └─ YES → Pricing-specific?
                  ├─ NO  → Fix actual problem
                  └─ YES → Tried 3 nonprice actions?
                           ├─ NO  → Try those (advertise; add value; upgrade)
                           └─ YES → War-game competitor reaction
                                    └─ Worse off after counter? → don't cut

Critical Numbers

NumberRule
72%New products fail
80%Companies wait until just before launch to set price
5%Business cases include real WTP data
3-4Ideal starting number of segments
<10%Killer features valued by less than this %
9 / 4Max benefits / products before psychological overload
≤25% / 70% / ≥10%G/B/B target (Good / Better+Best / Best)
50%Trip-wire: more than this picking Good = bleeding
20-30%Healthy deal escalation rate
30-40%Of ALL DEALS should have price changes upon escalation
3Nonprice actions required before any price cut
40%More likely to realize potential with defined pricing strategy
33%More profit when C-suite leads pricing (vs delegates) - also from Simon-Kucher client data; same provenance caveat as the 72% figure applies
25%Of customer interview questions should be "Why?"

The "BECAUSE" Test

Every pricing decision must end with a "because" traceable to customer data.

Bad: "We priced at $99 to be competitive." Good: "We priced at $99 BECAUSE 60% of segment B told us $100 was the threshold above which they'd reconsider, and our value advantage justifies the high end."

If you can't say "because customers told us X," you don't have a pricing strategy.


Quick Reference Checklist

Before designing a new product:

  • WTP conversations with real customers held
  • Segmented by needs/value/WTP (not demographics)
  • Leaders, fillers, killers identified
  • G/B/B configuration designed with FENCES
  • Monetization model picked (aligns with value)
  • Pricing strategy documented (max/penetration/skimming)
  • Living business case links Price/Value/Volume/Cost
  • Benefit-not-feature messaging tested
  • Behavioral tactics considered
  • Team prepared to maintain price integrity post-launch

The test: Ask anyone "Why this price?" If the answer is "cost-plus" or "competitor benchmark," failure is coming.


Critical Quotes

  • "Design the product around the price."
  • "How you charge trumps what you charge."
  • "Pricing too low is worse than pricing too high."
  • "Customers don't buy products. They buy benefits." - Drucker
  • "The single most important decision in evaluating a business is pricing power." - Buffett
  • "If I have 2,000 customers and 400 prices, I'm short 1,600 prices." - Crandall (American Airlines)

Supporting Files

  • frameworks.md - Full detail on all 9 rules, sub-frameworks, methods, and lists (10 WTP insights, 10 bundling insights, 6 post-launch tips, etc.)
  • cases.md - Detailed case studies (Porsche, Dodge Dart, LinkedIn, Dräger, Uber, Swarovski, Optimizely, Innovative Pharma) plus failure exemplars
  • examples.md - Worked examples: Pizza & Breadsticks bundling math, MOCA matrix, value-selling spreadsheet, 100-point goal allocation, BECAUSE test templates
  • integration.md - Implementation roadmap (4 phases), 9 pitfalls, startup/SaaS adaptation, WTP research limitations, conflict resolution with Mom Test/$100M Offers/SPIN

When This Doesn't Apply

  • Pure cost-plus regulated environments (utilities, some defense)
  • Pure commodities (sugar, copper)
  • Very early stage with no product (use Mom Test first)
  • B2C impulse buys under $50 (simpler approaches work)
  • Geographic markets with no purchasing power

Caveat on WTP Research

Stated WTP and revealed WTP differ. Customers predict their own behavior poorly in interviews. Treat WTP findings as a strong prior, not certainty. Validate with paid pilots, pre-orders, live A/B price tests, or money-back guarantees. See integration.md.

© getagentseal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/monetizing-innovation of getagentseal/founder-playbook.

  • SKILL.md
  • cases.md
  • examples.md
  • frameworks.md
  • integration.md

Open the folder on GitHubat commit e811e63

Compare with similar skills

Monetizing Innovation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Monetizing Innovation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monetizing Innovation this skillgetagentseal/founder-playbook729—~2.9kAutomated safety check: PassMIT
Product Design Workflow BundleXiaomiMiMo/MiMo-Code14k—~721Automated safety check: PassMIT
Product Designsickn33/agentic-awesome-skills47k2 repos~2.7kAutomated safety check: PassMIT
Product Design Framinglobehub/lobehub83k—~2.6kAutomated safety check: PassCustom licence
Monetizing Innovationwondelai/skills2.4k—~5.2kAutomated safety check: PassMIT
Gtm Technical Product Pricinggithub/awesome-copilot40k1 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • Product Design Workflow Bundle

    XiaomiMiMo/MiMo-Code

    Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.

    14k GitHub stars~721 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Product Design

    sickn33/agentic-awesome-skills

    Design de produto nivel Apple — sistemas visuais, UX flows, acessibilidade, linguagem visual proprietaria, design tokens, prototipagem e handoff.

    47k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Product Design Framing

    lobehub/lobehub

    Frames new surfaces, redesigns and vague product requests by grounding the business model and the user's task before any layout, in discover, frame or materialize modes.

    83k GitHub stars~2.6k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Monetizing Innovation

    wondelai/skills

    Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".

    2.4k GitHub stars~5.2k tokensUpdated 28 days ago
    Product & Project ManagementAuto-check passed
  • Gtm Technical Product Pricing

    github/awesome-copilot

    Official

    Pricing strategy for technical products. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • Product Designer

    borghei/Claude-Skills

    Product design across UI/UX, design systems, prototyping, and user research.

    886 GitHub stars~3.1k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

More from getagentseal/founder-playbook

All 16 skills in this repo
  • 100m Leads

    getagentseal/founder-playbook

    Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.

    729 GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check passed
  • 100m Offers

    getagentseal/founder-playbook

    Designs irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns.

    729 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed
  • Blue Ocean Strategy

    getagentseal/founder-playbook

    Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.

    729 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Diagnose

    getagentseal/founder-playbook

    Startup diagnostic router. An agent skill from getagentseal/founder-playbook.

    729 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed
  • Influence

    getagentseal/founder-playbook

    Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion.

    729 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed
  • Lean Startup

    getagentseal/founder-playbook

    Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.

    729 GitHub stars~4.6k tokensUpdated 2 days ago
    Auto-check passed

Questions about Monetizing Innovation

What does Monetizing Innovation do?

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…. Monetizing Innovation is an agent skill from getagentseal/founder-playbook. 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.

When should I use Monetizing Innovation?

Monetizing Innovation fits situations like: designing new products; validating pricing for SaaS/B2B/B2C launches; choosing between subscription/usage/freemium models; fixing post-launch sales below plan.

How do I install Monetizing Innovation in Claude Code?

Run `npx skills add getagentseal/founder-playbook --skill monetizing-innovation -a claude-code`. Or copy the skill folder (skills/monetizing-innovation in getagentseal/founder-playbook) into .claude/skills/monetizing-innovation in your project. Claude Code loads it when a task matches its description.

How do I install Monetizing Innovation in Codex?

Run `npx skills add getagentseal/founder-playbook --skill monetizing-innovation -a codex`. Or copy the skill folder (skills/monetizing-innovation in getagentseal/founder-playbook) into .agents/skills/monetizing-innovation in your project. Codex loads it when a task matches its description.

Can I use Monetizing Innovation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getagentseal/founder-playbook --skill monetizing-innovation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monetizing-innovation, .gemini/skills/monetizing-innovation, .github/skills/monetizing-innovation and .opencode/skills/monetizing-innovation in your project.

What does Monetizing Innovation need to run?

SKILL.md names no scripts, command-line tools or credentials: Monetizing Innovation is instructions for the agent only.

Does Monetizing Innovation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Monetizing Innovation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Monetizing Innovation use?

Monetizing Innovation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Monetizing Innovation use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Monetizing Innovation?

Skills that share tags, products or a category with Monetizing Innovation: Product Design Workflow Bundle (XiaomiMiMo/MiMo-Code, 14k stars), Product Design (sickn33/agentic-awesome-skills, 47k stars), Product Design Framing (lobehub/lobehub, 83k stars) and Monetizing Innovation (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monetizing Innovation?

getagentseal (a GitHub organization) maintains it in getagentseal/founder-playbook, which has 729 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.

Source: getagentseal/founder-playbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.