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
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.