monetization-strategy
Skill2 starsChanged 10 days agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 113
Experiment: Test ads with small user segment, measure engagement and revenue impact
- Distinctive: line 130
Create testing roadmap and success criteria
- Distinctive: line 141
Test early and often; don't wait for perfect product to validate pricing
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Other versions13 projects use a version of this.
Word for word · 8
- The-Utopia-Studio/skills★ 6100% same
- Adhamxon/claude-code-skills★ 2100% same
- skytiger6724/qwen-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
- vijaysuperpositionist/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 5
- appeeky/aso-skills★ 2.2ksame name
- Eronred/aso-skills★ 2.2ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- travisjneuman/.claude★ 106same name
- Kungfookenny123/aso-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use ab-test-store-listing, app-analytics and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
appeekySkillab-test-store-listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Also in 3 projects that use this
- appeekySkill
app-analytics
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
Also in 3 projects that use this
- +10 more from appeeky
In this repository100 other files it gives its agents.
- ab-test-analysisSkill
- analyze-feature-requestsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- beachhead-segmentSkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstormingSkill
- brainstorm-okrsSkill
- browser-testing-with-devtoolsSkill
- business-modelSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- cohort-analysisSkill
- competitive-battlecardSkill
- context-engineeringSkill
- customer-journey-mapSkill
- debugging-and-error-recoverySkill
- define-hypothesisSkill
- define-jtbd-canvasSkill
- define-opportunity-treeSkill
- define-problem-statementSkill
- deliver-acceptance-criteriaSkill
- deliver-edge-casesSkill
- deliver-prdSkill
- deprecation-and-migrationSkill
- develop-solution-briefSkill
- discover-competitive-analysisSkill
- discover-interview-synthesisSkill
- discover-market-sizingSkill
- document-architectureSkill
- documentation-and-adrsSkill
- draft-ndaSkill
- dummy-datasetSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grammar-checkSkill
- growth-loopsSkill
- gtm-motionsSkill
- gtm-strategySkill
- ideal-customer-profileSkill
- identify-assumptions-existingSkill
- identify-assumptions-newSkill
- incremental-implementationSkill
- intended-vs-implementedSkill
- interview-meSkill
- interview-scriptSkill
- job-storiesSkill
- lean-canvasSkill
- marketing-ideasSkill
- market-segmentsSkill
- measure-experiment-designSkill
- metrics-dashboardSkill
- modern-web-guidanceSkill
- north-star-metricSkill
- observability-and-instrumentationSkill
- outcome-roadmapSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.