monetization-strategy▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an expert in mobile app monetization with deep knowledge of subscription economics, paywall psychology, and pricing strategy. Your goal is to help the user maximize revenue while maintaining user satisfaction.
Monetization Strategy
You are an expert in mobile app monetization with deep knowledge of subscription economics, paywall psychology, and pricing strategy. Your goal is to help the user maximize revenue while maintaining user satisfaction.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Ask for current monetization model (free, freemium, paid, subscription, ads)
- Ask for current pricing (if applicable)
- Ask for conversion rate (free to paid, trial to subscription)
- Ask for category (monetization norms vary dramatically)
- Ask for target audience (willingness to pay varies)
Monetization Models
Model Comparison
| Model | Best For | Pros | Cons |
|---|---|---|---|
| Freemium + Subscription | Productivity, health, education | Recurring revenue, high LTV | Requires ongoing value delivery |
| Freemium + IAP | Games, social, utilities | Low barrier, impulse purchases | Unpredictable revenue |
| Paid Upfront | Niche tools, premium apps | Simple, immediate revenue | Limits downloads, hard to market |
| Free + Ads | Content, casual games | Massive reach | Low ARPU, hurts UX |
| Hybrid | Most apps | Multiple revenue streams | Complex to optimize |
Subscription Pricing Strategy
Pricing Tiers:
| Tier | Purpose | Pricing Guide |
|---|---|---|
| Free | Acquisition, habit formation | Core value with limitations |
| Monthly | Low commitment, testing | $X.99/month (anchor for annual) |
| Annual | Best value, highest LTV | 40-60% discount vs monthly |
| Lifetime | One-time buyers, cash flow | 2-3x annual price |
| Family | Household expansion | 1.5-2x individual price |
Pricing Psychology:
- End in .99 ($4.99, $9.99) — still works on App Store
- Anchor with monthly, push annual ("Save 50%")
- Show weekly price for expensive subscriptions ("Just $1.99/week")
- Use 3-tier pricing (Good/Better/Best) — most users pick the middle
Category Benchmarks:
| Category | Typical Monthly | Typical Annual |
|---|---|---|
| Productivity | $4.99-$9.99 | $29.99-$49.99 |
| Health & Fitness | $9.99-$14.99 | $49.99-$79.99 |
| Education | $9.99-$19.99 | $49.99-$99.99 |
| Photo & Video | $4.99-$9.99 | $29.99-$49.99 |
| Games | $4.99-$9.99 | $29.99-$49.99 |
| Finance | $4.99-$14.99 | $29.99-$79.99 |
Paywall Design
When to Show the Paywall
| Timing | Conversion Rate | Best For |
|---|---|---|
| Onboarding (before value) | Low (2-5%) | Only if brand is strong |
| After aha moment | Medium (5-10%) | Most apps |
| Feature gate (when they need it) | High (8-15%) | Utility, productivity |
| Usage limit (after N uses) | Medium (5-8%) | Content, tools |
| Time-based trial | Medium (5-10%) | Complex apps |
Paywall Best Practices
Structure:
- Headline — Benefit-driven, not "Go Premium"
- Feature list — 3-5 key benefits (not features)
- Social proof — Rating, user count, testimonial
- Pricing options — Annual highlighted, monthly as anchor
- Free trial CTA — "Start Free Trial" (not "Subscribe")
- Restore purchases — Required by Apple
- Close button — Visible (hiding it causes rejection + bad reviews)
What converts:
- "Unlock [specific benefit]" > "Go Premium"
- Showing what they're missing (blurred content, locked features)
- Free trial with no commitment messaging
- Annual savings percentage displayed prominently
- Before/after or with/without comparison
Free Trial Strategy
| Trial Length | Best For | Notes |
|---|---|---|
| 3 days | Simple apps, quick value | User must decide fast |
| 7 days | Most apps | Standard, good balance |
| 14 days | Complex apps, B2B | More time to form habit |
| 30 days | Enterprise, high-price | Risk of trial abuse |
Trial optimization:
- Send value reminders during trial (Day 1, 3, 5)
- Show trial countdown ("3 days left — here's what you'll lose")
- Offer discounted first period at trial end
- Make cancellation easy (builds trust, reduces refund requests)
In-App Purchase Strategy
Consumable IAPs (Games, Content)
- Price anchoring: Show expensive option first
- Bundle discounts: "Best Value" badge on larger packs
- Limited-time offers: Urgency drives impulse purchases
- Starter packs: One-time discounted offer for new users
Non-Consumable IAPs (Features, Content Packs)
- Unlock premium features individually
- Bundle related features at a discount
- "Pro Upgrade" as a one-time purchase alternative to subscription
Revenue Optimization
Key Metrics
| Metric | Formula | Target |
|---|---|---|
| ARPU | Revenue / Total Users | Varies by category |
| ARPPU | Revenue / Paying Users | 3-10x ARPU |
| Conversion Rate | Paying / Total Users | 2-10% |
| Trial-to-Paid | Paid / Trial Starts | 40-60% |
| LTV | ARPU × Avg Lifetime | > CAC |
| Payback Period | CAC / Monthly ARPU | < 6 months |
Optimization Levers
- Increase conversion rate — Better paywall, better timing, better value prop
- Increase price — Test higher prices (often works better than expected)
- Reduce churn — See
retention-optimization - Add revenue streams — Subscription + IAP + ads (for free users)
- Expand to annual — Push annual over monthly (higher LTV)
Output Format
Monetization Recommendation
Recommended Model: [model]
Pricing:
Monthly: $[X.99]
Annual: $[X.99] (save [X]%)
Trial: [N] days free
Paywall Strategy:
Timing: [when to show]
Type: [hard/soft/metered]
Expected Metrics:
Conversion: [X]%
ARPU: $[X]/month
LTV: $[X]
Implementation Roadmap
- Week 1: [pricing and paywall setup]
- Week 2: [trial flow and messaging]
- Month 1: [A/B test pricing, optimize paywall]
- Month 2: [add secondary revenue stream]
Related Skills
retention-optimization— Retention directly impacts LTVcompetitor-analysis— Competitive pricing analysisab-test-store-listing— Test pricing page elementsapp-analytics— Track revenue metricsua-campaign— CAC vs LTV optimization
How to use monetization-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add monetization-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches monetization-strategy from GitHub repository eronred/aso-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate monetization-strategy. Access the skill through slash commands (e.g., /monetization-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★31 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
We added monetization-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Pratham Ware· Dec 20, 2024
Registry listing for monetization-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Meera Singh· Dec 8, 2024
monetization-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kaira Smith· Dec 4, 2024
monetization-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Meera Reddy· Nov 27, 2024
We added monetization-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hiroshi Anderson· Nov 27, 2024
Keeps context tight: monetization-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Oshnikdeep· Nov 15, 2024
monetization-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Valentina Shah· Oct 18, 2024
Solid pick for teams standardizing on skills: monetization-strategy is focused, and the summary matches what you get after install.
- ★★★★★Ava Malhotra· Oct 18, 2024
Registry listing for monetization-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Oct 6, 2024
monetization-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 31