/pricing-strategy

name: pricing-strategy
description: "Design products around price using Madhavan Ramanujam's \"Monetizing Innovation\" methodology—determine willingness to pay before you build, not after. Use when: **Set pricing for a new product** before or during development; **Validate willingness to pay** before investing in features; **Structure pricing tiers** (Good-Better-Best) for different segments; **Choose the right monetization model** (subscription, usage-based, freemium, etc.); **Diagnose why a product isn't monetizing** as expected"
license: MIT
metadata:
  author: ClawFu
  version: 1.0.0
  mcp-server: "@clawfu/mcp-skills"

Pricing Strategy

> Design products around price using Madhavan Ramanujam's "Monetizing Innovation" methodology—determine willingness to pay before you build, not after.

When to Use This Skill

Use this skill when you need to:

• **Set pricing for a new product** before or during development
• **Validate willingness to pay** before investing in features
• **Structure pricing tiers** (Good-Better-Best) for different segments
• **Choose the right monetization model** (subscription, usage-based, freemium, etc.)
• **Diagnose why a product isn't monetizing** as expected
• **Avoid common pricing failures** like leaving money on the table
• **Communicate value** in ways that justify your price
• **Maintain price integrity** after launch

This skill is particularly valuable for:

• Product managers designing new offerings
• Founders pricing SaaS or subscription products
• Teams launching into new markets or segments
• Companies suspecting they're underpricing
• Anyone who built first and is now struggling to monetize

---

Methodology Foundation

**Source:** Madhavan Ramanujam & Georg Tacke - *Monetizing Innovation: How Smart Companies Design the Product Around the Price* (2016)

**Core Principle:** Price determines product, not the other way around. Companies that design products around willingness to pay—rather than pricing as an afterthought—capture dramatically more value.

> "Price isn't a number. It's the perceived value that your product holds for the customer."

---

What Claude Does vs What You Decide

| Claude Does | You Decide | |-------------|------------| | Structures production workflow | Final creative direction | | Suggests technical approaches | Equipment and tool choices | | Creates templates and checklists | Quality standards | | Identifies best practices | Brand/voice decisions | | Generates script outlines | Final script approval |

What This Skill Does

When invoked, I will guide you through the Monetizing Innovation methodology:

1. **Diagnose monetization risk** by identifying which failure type threatens your product 2. **Conduct willingness-to-pay research** with the right questions 3. **Segment customers** by value perception, not demographics 4. **Configure products** using Leaders/Fillers/Killers and Good-Better-Best 5. **Select the right monetization model** for your business 6. **Apply behavioral pricing tactics** to optimize conversion 7. **Build price integrity** and avoid post-launch erosion

---

How to Use

Provide information about your pricing situation:

**Example prompts:**

• "Help me set pricing for my new B2B SaaS product"
• "I think we're underpricing our service—how do I validate and fix this?"
• "Design a Good-Better-Best pricing structure for our software"
• "What monetization model should I use for a developer tool?"
• "Our new product launched but sales are disappointing—diagnose the pricing"

**Information that helps:**

• Your product/service description
• Target customer segments
• Current pricing (if any)
• Competitor pricing landscape
• Key features and their perceived value
• Business model and goals
• Any existing willingness-to-pay data

---

Instructions

Phase 1: Diagnose Monetization Risk

Before setting prices, identify which failure type threatens your product:

The Four Types of Monetization Failure

| Failure Type | Symptoms | Root Cause | |--------------|----------|------------| | **Feature Shock** | Too many features, high price, confused value prop | Built everything instead of what customers pay for | | **Minivation** | Strong adoption, weak revenue | Priced too low, leaving money on table | | **Hidden Gem** | Great innovation stuck inside company | Dismissed as "not our core business" | | **Undead** | No willingness to pay at any price | Built on assumptions, not customer evidence |

**Diagnostic Questions:**

1. Have you validated willingness to pay with real customers? 2. Are you including features because customers will pay for them, or because you can build them? 3. Could any feature be a standalone paid product? 4. Is there evidence customers would pay more than your current price?

---

Phase 2: Conduct Willingness-to-Pay Research

**Critical:** This happens BEFORE product design is finalized, not after.

The Four Key Questions

Ask potential customers:

1. **"What would be an acceptable price for [product]?"**

• Establishes the comfort zone

2. **"What would be an expensive price?"**

• Identifies the premium threshold

3. **"What would be a prohibitively expensive price?"**

• Finds the ceiling

4. **"Would you buy this at $X?"**

• Tests specific price points

**Follow every answer with: "Why?"**

Research Methods

| Method | Best For | Sample Size | |--------|----------|-------------| | **1:1 Interviews** | Deep understanding, B2B | 10-20 customers | | **Focus Groups** | Testing reactions, consumer | 3-5 groups of 6-8 | | **Surveys** | Quantitative validation | 100+ responses | | **Purchase Simulations** | Realistic behavior data | 50+ scenarios |

Pro Tips for WTP Conversations

• Position as a conversation about "value," not "pricing"
• Make 25% of questions "why" questions
• Look at distributions, not just averages (you may have distinct segments)
• Be precise: "Would you buy at $20?" not "Would you buy?"
• Test features individual