pricing-strategy
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
What this skill does
# 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 individually to understand relative value --- ### Phase 3: Segment by Willingness to Pay **Critical shift:** Segment by needs and willingness to pay, NOT demographics. **Wrong segmentation:** - Small/Medium/Enterprise (by company size) - Marketing/Sales/Product (by role) - US/Europe/Asia (by geography) **Right segmentation:** - High-value seekers vs. budget-conscious buyers - Power users vs. occasional users - Self-service vs. high-touch support needs #### Segmentation Process 1. **Cluster by WTP data** - Group customers with similar price sensitivity 2. **Validate with behavior** - Do they actually behave differently? 3. **Ensure you can reach them** - Can marketing/sales target this segment? 4. **Keep it simple** - Fewer segments is better (3-4 max) 5. **Describe for action** - Define segments so teams can sell to them --- ### Phase 4: Configure Products with Leaders, Fillers, Killers #### Identify Feature Types | Feature Type | Definition | Identification | Action | |--------------|------------|----------------|--------| | **Leaders** | Drive purchase decision, high WTP | >50% highly value, willing to pay | Emphasize, charge premium | | **Fillers** | Nice-to-have, rounds out offering | 30-50% value, moderate WTP | Include in bundles | | **Killers** | Low value, blocks deals if included | <20% value OR >20% actively dislike | Remove or make optional | #### Build Good-Better-Best Tiers ``` GOOD (Entry) BETTER (Standard) BEST (Premium) ━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━ Core Leaders only Leaders + Key Fillers All Leaders + Fillers Self-service Email support Priority support Basic limits Generous limits Unlimited/Custom $X/month $2-3X/month $5-10X/month ``` **Configuration Principles:** - Each tier appeals to a specific segment - Don't give away too much in entry tier - Clear differentiation between tiers - Maximum 4 tiers, 9 benefits per tier - **Requires courage to remove features** --- ### Phase 5: Select the Right Monetization Model **Key insight:** How you charge is often more important than how much. #### Five Monetization Models | Model | Description | Best For | Example | |-------|-------------|----------|---------| | **Subscription** | Fixed recurring payment | Predictable value delivery | Netflix, SaaS | | **Usage-Based** | Pay per unit consumed | Variable consumption | AWS, Twilio | | **Freemium** | Free tier + paid upgrades | High-volume acquisition | Slack, Dropbox | | **Dynamic** | Prices vary by demand | Perishable inventory | Airlines, Uber | | **One-Time** | S
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.