本文へ移動
cccskills
無料GitHub で公開

indie-monetization-strategist

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).

インストール方法を見る

含まれるファイル(5)

  • SKILL.md8.4 KB
  • CHANGELOG.md1.2 KB
  • references/email-sequences.md8.7 KB
  • references/pricing-templates.md7.4 KB
  • references/stripe-integration.md11.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Indie Monetization Strategist

Turn side projects into sustainable income with battle-tested revenue strategies.

DECISION POINTS

Choosing Primary Monetization Model

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)

When to Pivot Strategy (Revenue/Churn Thresholds)

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

Pricing Decision Framework

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)

FAILURE MODES

Anti-Pattern: "Premature Monetization"

Detection Rule: If you're adding payments before 100+ active free users

  • Symptom: Low conversion rates, users bounce at paywall
  • Diagnosis: No product-market fit established yet
  • Fix: Build value first, then monetize proven engagement

Anti-Pattern: "Race to Bottom Pricing"

Detection Rule: If your pricing is >50% below comparable competitors

  • Symptom: Attracting price shoppers, high churn, unsustainable margins
  • Diagnosis: Competing on price instead of value
  • Fix: Raise prices 2x, focus on unique value proposition

Anti-Pattern: "Crippled Free Tier"

Detection Rule: If free users can't accomplish a complete workflow

  • Symptom: No free-to-paid conversions, negative feedback on free tier
  • Diagnosis: Free tier doesn't demonstrate product value
  • Fix: Allow complete basic workflow free, gate advanced features

Anti-Pattern: "Revenue Stream Hopping"

Detection Rule: If you've tried 3+ monetization models in 6 months

  • Symptom: No model reaches $1k/mo, constantly switching strategies
  • Diagnosis: Not giving strategies time to work, avoiding hard optimization
  • Fix: Pick one model, optimize for 6+ months before considering change

Anti-Pattern: "Ignoring Retention Metrics"

Detection Rule: If you don't know your monthly churn rate

  • Symptom: Growing signups but flat revenue, high customer acquisition costs
  • Diagnosis: Leaky bucket - acquiring faster than you're retaining
  • Fix: Track churn weekly, optimize retention before acquisition

WORKED EXAMPLES

Example 1: DevTool SaaS Evolution ($0→$8k MRR)

Initial State: Open source CLI tool, 500 GitHub stars, no revenue

Month 1-3 Decision Process:

  • Analyzed GitHub issues → 60% requests for team features
  • Decision: Freemium SaaS model, not donations
  • Pricing strategy: Free (individual use) → Pro ($29/mo for teams)

Implementation:

  • Built web dashboard with team management
  • Kept CLI free, gated dashboard features
  • Email sequence: CLI users → dashboard trial → paid conversion

Results & Pivots:

  • Month 3: $400 MRR (1.2% free→paid conversion)
  • Issue: Conversion too low
  • Analysis: Free tier solved 90% of use cases
  • Pivot: Added usage limits to free tier (5 projects max)
  • Month 6: $2.1k MRR (4.8% conversion)
  • Month 12: $8.2k MRR (added $99 team tier)

Key Lessons:

  • Free tier must create upgrade pressure through limits, not features
  • B2B tools can support higher pricing ($29+ vs $9)
  • Team features unlock higher willingness to pay

Example 2: Educational Content Monetization ($0→$4k MRR)

Initial State: Technical blog, 50k monthly visitors, AdSense revenue $200/mo

Decision Process:

  • Audience analysis: 70% senior developers, 30% beginners
  • High email signup rate (8%) but low engagement
  • Decision: Premium newsletter + cohort course model

Revenue Evolution:

  • Phase 1: Premium newsletter ($19/mo) - 2% conversion from free subscribers
  • Month 4: $800 MRR from newsletter (42 paid subscribers)
  • Phase 2: Added monthly cohort course ($199) for newsletter subscribers
  • Month 8: $2.8k MRR (newsletter + courses)
  • Phase 3: Annual course option ($1,299 vs monthly $199)
  • Month 12: $4.2k MRR (40% take annual option)

Trade-off Analysis:

  • Newsletter provided steady baseline revenue
  • Courses had higher per-customer value but required more time investment
  • Annual pricing improved cash flow but required stronger value proof

QUALITY GATES

Revenue Model Validation Checklist

  • Free users can complete at least one valuable workflow end-to-end
  • Pricing is based on customer value metrics, not internal costs
  • At least 2% of free users convert to paid within 30 days
  • Monthly churn rate is below 10% for paid subscribers
  • Customer acquisition cost (CAC) is less than 3x monthly revenue per customer
  • Payment processing is implemented with proper error handling
  • Pricing page clearly differentiates tier value propositions
  • Email sequence captures leads and nurtures them toward conversion
  • Analytics track conversion funnel from visitor→signup→paid
  • Refund/cancellation process is documented and tested

Product-Market Fit Signals

  • Organic word-of-mouth referrals (>10% of signups)
  • Users actively request features (not just complain)
  • Paid users renew subscriptions (churn <5% monthly)
  • Free users engage regularly (weekly active users >40%)
  • Customer support queries are feature requests, not confusion

NOT-FOR BOUNDARIES

This skill is NOT for:

  • Enterprise B2B sales processes → Use enterprise-sales-strategist
  • VC fundraising or pitch decks → Use startup-pitch-expert
  • Large-scale advertising campaigns → Use digital-marketing-strategist
  • Affiliate marketing at scale → Use affiliate-marketing-specialist
  • Physical product monetization → Use ecommerce-strategist

Delegate when:

  • Annual revenue targets >$500k → Need enterprise sales approach
  • Seeking investment capital → Need fundraising expertise
  • Managing ad spend >$10k/month → Need marketing specialist
  • Complex B2B sales cycles → Need dedicated sales processes

Sweet spot: Solo developers, small teams, digital products, recurring revenue $0-100k annually

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

Apply normative BDI reasoning to agents that must detect norms, choose which commitments to internalize, and resolve conflicts by comparing consequences. Use when obligations, prohibitions, or policies collide in autonomous systems. NOT for simple fixed-priority rules, pure constraint satisfaction, or domains where no real normative conflict exists.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/windags-skills132026年10月12日 更新

curiositech のスキルをすべて見る

このスキルの問題を報告する