Mmcp.market

monetization-strategy skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product.

A100/100content scan

Is the monetization-strategy skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the monetization-strategy skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-strategy/skills/monetization-strategy ~/.claude/skills/monetization-strategy
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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
  1. For each strategy, design a low-effort validation experiment
  2. Prioritize by:
  • Strategic fit (revenue, growth, profitability goals)
  • Ease of implementation
  • Market validation potential
  • Competitive advantage
  1. Recommend 1-2 strategies to test first
  2. 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 and often; don't wait for perfect product to validate pricing
  • Most products use hybrid models (e.g., freemium + upgrade, subscription + marketplace fees)
  • Pricing can be changed; customer relationships are harder to rebuild
  • Monitor competitors but don't race to the bottom on price

Further Reading

  • Product Pricing Strategies 101

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze 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.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm 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.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform 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.

All agent skills → · MCP servers