monetization-strategy
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.
- Installs
- 3.2K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill monetization-strategy- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads monetization-strategy automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Brainstorm 3-5 distinct monetization strategies (avoid repeating similar models)
- 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
- For each strategy, design a low-effort validation experiment
- Prioritize by:
- Strategic fit (revenue, growth, profitability goals)
- Ease of implementation
- Market validation potential
- Competitive advantage
- Recommend 1-2 strategies to test first
- 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
FAQ
What does the monetization-strategy skill do?
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.
How do I install monetization-strategy?
Run npx skills add https://github.com/phuryn/pm-skills --skill monetization-strategy in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/monetization-strategy/ (personal) or .claude/skills/monetization-strategy/ (project).
Which AI agents can use monetization-strategy?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is monetization-strategy safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains monetization-strategy?
It is published by phuryn in phuryn/pm-skills. It has 3,175 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.