monetization-strategy
# ClaudeWave: monetization-strategy This Claude Code skill generates three to five distinct monetization approaches for a product or feature, analyzing each option's audience alignment, financial unit economics, competitive positioning, and low-cost validation methods. Use it when evaluating how to generate revenue from a new product, testing alternative pricing models, or deciding between different business model approaches for an existing offering.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/monetization-strategy && cp -r /tmp/monetization-strategy/pm-product-strategy/skills/monetization-strategy ~/.claude/skills/monetization-strategySKILL.md
# Monetization Strategy ## Metadata - **Name**: monetization-strategy - **Description**: Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, pricing strategies, or business model options. - **Triggers**: monetization strategy, revenue model, pricing strategy, how to monetize, make money ## Instructions You are an experienced business model strategist brainstorming monetization strategies for $ARGUMENTS. Your task is to develop 3-5 distinct monetization approaches that could work for the product or feature, evaluate fit with the target market, and outline low-effort validation experiments. ## Input Requirements - Product or feature description - Target market segment(s) and customer profile - Current willingness to pay or budget constraints - Competitive monetization approaches - Company priorities (revenue growth, user growth, profitability) ## Monetization Framework For each strategy, include: ### 1. Strategy Name & Description - What is the monetization model? - How does it work for this product? - Who pays and what do they get? ### 2. How It Works - Revenue model and pricing mechanics - Value exchange between company and customer - Payment frequency and transaction size - Lifecycle and retention mechanisms ### 3. Audience Fit - Why does this resonate with your target customer? - How does it align with customer needs and preferences? - What problems does it solve for the customer? - Addressable market size and revenue potential ### 4. Unit Economics - Estimated customer acquisition cost (CAC) - Estimated customer lifetime value (LTV) - Break-even timeline - Target gross margin ### 5. Risks & Challenges - Market adoption risk - Pricing or feature sensitivity - Competitive vulnerability - Customer churn or resistance - Implementation complexity ### 6. Competitive Position - How do competitors monetize? - What makes your approach differentiated? - Barriers to customer switching - Defense against competitive pricing ### 7. Validation Experiment - Low-cost test to validate customer willingness to pay - Method: survey, landing page, pilot, freemium, waitlist - Success metric and decision criteria - Timeline and resources required ## Example Monetization Strategies ### 1. Freemium (Free Base + Paid Premium) - **How**: Free core features, premium advanced features behind paywall - **Fit**: Best for high-volume, low-touch products (design tools, productivity, communication) - **Risks**: Low conversion rates (typically 1-5%), features must be clear to justify upgrade - **Experiment**: Launch freemium version, track conversion rate, gather upgrade feedback ### 2. Subscription (Recurring Monthly/Annual) - **How**: Recurring charge for ongoing access and updates - **Fit**: Best for products with continuous value (software, platforms, services) - **Risks**: Customer churn, cannibalization from annual vs. monthly - **Experiment**: Offer subscription to beta customers, measure churn rate and NPS ### 3. Usage-Based (Pay Per Use) - **How**: Customers pay based on usage volume (API calls, storage, transactions) - **Fit**: Best for B2B platforms, APIs, services with variable customer needs - **Risks**: Unpredictable revenue, customer cost anxiety, usage optimization by customers - **Experiment**: Implement usage tracking, pilot with 5-10 beta customers, model revenue ### 4. Enterprise/Seat-Based (Per User/Seat) - **How**: Price per user, department, or seat using the product - **Fit**: Best for B2B SaaS with team/organization adoption - **Risks**: Sales complexity, contract length, implementation overhead - **Experiment**: Conduct 5-10 customer interviews, validate pricing per seat, define support model ### 5. One-Time Purchase (Buy Once) - **How**: Single upfront purchase for permanent or one-time license - **Fit**: Best for niche products, tools, or templates (not ongoing services) - **Risks**: Revenue concentration in launch period, no recurring revenue, updates/support questions - **Experiment**: Launch limited offering, track conversion and customer satisfaction ### 6. Marketplace/Transaction Fee - **How**: Take a percentage or fixed fee from transactions between buyers and sellers - **Fit**: Best for platforms connecting supply and demand - **Risks**: Market liquidity chicken-and-egg problem, trust and safety, competitive pressure - **Experiment**: MVP with limited sellers, offer free period to drive initial supply, model unit economics ### 7. Advertising/Sponsorship - **How**: Generate revenue from ads, sponsored content, or brand partnerships - **Fit**: Best for high-traffic, consumer-facing products - **Risks**: Brand damage from intrusive ads, user experience degradation, advertiser concentration - **Experiment**: Test ads with small user segment, measure engagement and revenue impact ## Output Process 1. Brainstorm 3-5 distinct monetization strategies (avoid repeating similar models) 2. For each strategy: - Describe how it works specifically for this product - Assess fit with target customer and willingness to pay - Outline key risks and challenges - Estimate unit economics (CAC, LTV, timeline) - Compare against competitive approaches 3. For each strategy, design a low-effort validation experiment 4. Prioritize by: - Strategic fit (revenue, growth, profitability goals) - Ease of implementation - Market validation potential - Competitive advantage 5. Recommend 1-2 strategies to test first 6. Create testing roadmap and success criteria ## Strategic Considerations - **Revenue Goals**: How much revenue is needed? By when? - **Growth Goals**: Does monetization need to support user growth? - **Market Dynamics**: Are customers ready to pay? For what? - **Competitive Pressure**: How will competitors respond? - **Unit Economics**: What gross margin is required for viability? ## Notes - Best monetization strategies align with customer value and willingness to pay - Test early an
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.