agentleFS
EronredEronred/aso-skills/skills/monetization-strategy/SKILL.md

monetization-strategy

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.

13 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for context

    line 14
  2. Distinctive:

    Ask for current monetization model (free, freemium, paid, subscription, ads)

    line 15
  3. Distinctive:

    Ask for current pricing (if applicable)

    line 16
  4. Distinctive:

    Ask for conversion rate (free to paid, trial to subscription)

    line 17
  5. Distinctive:

    Ask for category (monetization norms vary dramatically)

    line 18
  6. Distinctive:

    Ask for target audience (willingness to pay varies)

    line 19
  7. Very specific:

    Use 3-tier pricing (Good/Better/Best) — most users pick the middle

    line 49
  8. Distinctive:

    Before/after or with/without comparison

    line 90

“Common” is measured: kept by at least 6 in 10 of the 11 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Check for app-marketing-context.md — read it for context
  2. Ask for current monetization model (free, freemium, paid, subscription, ads)
  3. Ask for current pricing (if applicable)
  4. Ask for conversion rate (free to paid, trial to subscription)
  5. Ask for category (monetization norms vary dramatically)
  6. Ask for target audience (willingness to pay varies)

Monetization Models

Model Comparison

ModelBest ForProsCons
Freemium + SubscriptionProductivity, health, educationRecurring revenue, high LTVRequires ongoing value delivery
Freemium + IAPGames, social, utilitiesLow barrier, impulse purchasesUnpredictable revenue
Paid UpfrontNiche tools, premium appsSimple, immediate revenueLimits downloads, hard to market
Free + AdsContent, casual gamesMassive reachLow ARPU, hurts UX
HybridMost appsMultiple revenue streamsComplex to optimize

Subscription Pricing Strategy

Pricing Tiers:

TierPurposePricing Guide
FreeAcquisition, habit formationCore value with limitations
MonthlyLow commitment, testing$X.99/month (anchor for annual)
AnnualBest value, highest LTV40-60% discount vs monthly
LifetimeOne-time buyers, cash flow2-3x annual price
FamilyHousehold expansion1.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:

CategoryTypical MonthlyTypical 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

TimingConversion RateBest For
Onboarding (before value)Low (2-5%)Only if brand is strong
After aha momentMedium (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 trialMedium (5-10%)Complex apps

Paywall Best Practices

Structure:

  1. Headline — Benefit-driven, not "Go Premium"
  2. Feature list — 3-5 key benefits (not features)
  3. Social proof — Rating, user count, testimonial
  4. Pricing options — Annual highlighted, monthly as anchor
  5. Free trial CTA — "Start Free Trial" (not "Subscribe")
  6. Restore purchases — Required by Apple
  7. 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 LengthBest ForNotes
3 daysSimple apps, quick valueUser must decide fast
7 daysMost appsStandard, good balance
14 daysComplex apps, B2BMore time to form habit
30 daysEnterprise, high-priceRisk 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

MetricFormulaTarget
ARPURevenue / Total UsersVaries by category
ARPPURevenue / Paying Users3-10x ARPU
Conversion RatePaying / Total Users2-10%
Trial-to-PaidPaid / Trial Starts40-60%
LTVARPU × Avg Lifetime> CAC
Payback PeriodCAC / Monthly ARPU< 6 months

Optimization Levers

  1. Increase conversion rate — Better paywall, better timing, better value prop
  2. Increase price — Test higher prices (often works better than expected)
  3. Reduce churn — See retention-optimization
  4. Add revenue streams — Subscription + IAP + ads (for free users)
  5. 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

  1. Week 1: [pricing and paywall setup]
  2. Week 2: [trial flow and messaging]
  3. Month 1: [A/B test pricing, optimize paywall]
  4. Month 2: [add secondary revenue stream]

Related Skills

  • retention-optimization — Retention directly impacts LTV
  • competitor-analysis — Competitive pricing analysis
  • ab-test-store-listing — Test pricing page elements
  • app-analytics — Track revenue metrics
  • ua-campaign — CAC vs LTV optimization

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.