skills/indie-monetization-strategist/SKILL.md
Monetization strategies for indie developers, solopreneurs, and small teams. Covers freemium models, SaaS pricing, sponsorships, donations, email list building, and passive income for developer tools, content sites, and educational apps. Activate on 'monetization', 'make money', 'pricing', 'freemium', 'SaaS', 'sponsorship', 'donations', 'passive income', 'indie hacker'. NOT for enterprise sales, B2B outbound, VC fundraising, or large-scale advertising (use enterprise/marketing skills).
npx skillsauth add curiositech/windags-skills indie-monetization-strategistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Turn side projects into sustainable income with battle-tested revenue strategies.
1. What type of product do you have?
├── Developer Tool
│ ├── If open source → GitHub Sponsors + Premium features
│ ├── If CLI/utility → Freemium SaaS ($9-29/mo)
│ └── If complex platform → Multi-tier SaaS ($29-199/mo)
│
├── Content/Educational
│ ├── If course material → One-time purchase ($49-299)
│ ├── If ongoing tutorials → Membership ($19-49/mo)
│ └── If reference site → Sponsorships + Premium tier
│
└── Community/Audience
├── If <10k followers → Focus on email list building
├── If 10k-100k → Add sponsorships ($500-2k/mo)
└── If >100k → Premium community ($29-99/mo)
2. Current performance check:
├── Revenue <$500/mo after 6 months
│ └── Pivot to: Better product-market fit or different audience
│
├── Churn >15%/month
│ ├── If usage low → Add onboarding/activation flows
│ └── If usage high → Pricing/positioning mismatch
│
├── Free users won't upgrade (conversion <2%)
│ ├── If high engagement → Pricing too high
│ └── If low engagement → Free tier too generous
│
└── Revenue plateau >3 months
└── Add: New pricing tier or complementary product
3. How to price your offering:
├── If solving urgent problem → Price 3x higher than comfort level
├── If nice-to-have feature → Start low, test increments
├── If developer audience → $29-99/mo (they expect quality)
├── If consumer audience → $9-29/mo (price sensitive)
└── If enterprise users → $99-999/mo (budget exists)
4. Annual vs monthly pricing:
├── If high churn risk → Push annual (2-3 months discount)
├── If trying to grow fast → Monthly only (lower barrier)
└── If established product → Both options (annual preferred)
Detection Rule: If you're adding payments before 100+ active free users
Detection Rule: If your pricing is >50% below comparable competitors
Detection Rule: If free users can't accomplish a complete workflow
Detection Rule: If you've tried 3+ monetization models in 6 months
Detection Rule: If you don't know your monthly churn rate
Initial State: Open source CLI tool, 500 GitHub stars, no revenue
Month 1-3 Decision Process:
Implementation:
Results & Pivots:
Key Lessons:
Initial State: Technical blog, 50k monthly visitors, AdSense revenue $200/mo
Decision Process:
Revenue Evolution:
Trade-off Analysis:
This skill is NOT for:
enterprise-sales-strategiststartup-pitch-expertdigital-marketing-strategistaffiliate-marketing-specialistecommerce-strategistDelegate when:
Sweet spot: Solo developers, small teams, digital products, recurring revenue $0-100k annually
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.