indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
Best use case
indie-hacker-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
Teams using indie-hacker-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/indie-hacker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How indie-hacker-strategy Compares
| Feature / Agent | indie-hacker-strategy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Strategies: Indie Hacker Guides marketing and growth strategy for **indie hackers** (bootstrapped founders, solo developers)—autonomous, small-team or solo, no external funding. Covers mindset, first users, Build in Public, growth channels, and when to use which skills. For cold start execution (launch timeline, Product Hunt, directory submission), see **cold-start-strategy**. For forum tactics (Indie Hackers, HN, Reddit post structure), see **community-forum**. Full guide (cases, resources) → [Alignify – Indie Hacker Complete Guide](https://alignify.co/zh/insights/indie-hackers). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Definition **Indie Hacker** = Bootstrapped founder who builds products autonomously, typically 1–3 people, no external funding. Focus: sustainability, profitability, fast iteration—not VC-scale growth. | Trait | Indie Hacker | VC-backed | |-------|--------------|-----------| | **Funding** | Bootstrapping; product revenue | External investment | | **Growth** | Sustainable; Ramen profitability first | Scale at all costs | | **Control** | Full autonomy | Investor reporting | | **Timeline** | Long game; niche focus | Fast expansion | ## Core Concepts | Concept | Meaning | |---------|---------| | **Bootstrapping** | Self-funded; use product revenue to grow; no equity dilution | | **MVP** | Minimum viable product; ship fast, validate, iterate | | **Build in Public** | Share progress, metrics, failures openly; attracts early adopters | | **Scratch your own itch** | Solve your own problem first; others likely have it too | ## Pieter Levels Playbook | Tactic | Guideline | |--------|-----------| | **Ship fast, fix later** | Launch ugly but functional MVPs; Nomad List started as Google Sheet + Stripe; Photo AI made $150K first week despite initial flaws | | **Monetize from day one** | Add payment button at launch; validate willingness to pay, not just usage | | **Automate everything** | Scripts, APIs, no-code; run without employees | | **Build in public** | Share metrics openly; 600K+ followers; "Day 1: building X. Day 3: first customer" attracts early adopters | **Reference**: [Pieter Levels: The One-Man Startup Empire](https://www.systemscowboy.com/pieter-levels-indie-hacker-strategy/) ## First 100 Users (Indie Hacker Tactics) | Phase | Tactic | |-------|--------| | **First 5** | Direct DMs to people who'd genuinely benefit | | **Next ~15** | Conversations in communities where target users hang out (Reddit, Indie Hackers) | | **Scale to 50** | Build in public with visible metrics | | **Reach 100** | Double down on what works; don't add new channels until one consistently converts | **Niche products**: Reddit (60/100 users in one case), Discord (25), Indie Hackers (15). Twitter/HN may yield 0 for niche—target existing conversations in niche communities. **Reference**: [How I got my first 100 users - Indie Hackers](https://www.indiehackers.com/post/how-i-got-my-first-100-users-2fc9d71c34), [Indie10k – First 100 Users](https://indie10k.com/blog/get-first-100-users) ### Traction Triangle 1. **Clear Offer** — "I built X to help Y do Z" 2. **Right Channel** — Go where your niche congregates 3. **Social Proof** — Screenshots, roadmaps, user feedback, rapid shipping ## Build in Public (Content Framework) | Content Mix | Share | |-------------|-------| | **40%** | Learnings | | **30%** | Progress updates | | **20%** | Challenges, failures | | **10%** | Helping others | **Principles**: Transparency over perfection; authenticity over polish; consistency over intensity; value over self-promotion (90/10 rule). Post weekly minimum; engage two-way. Founders who build in public see ~4.2× more day-one users; ~34% of launch users from audience. **Reference**: [Building in Public: Complete Strategy 2026](https://getathenic.com/blog/building-in-public-startup-strategy-2026), [Indie Hackers Marketing 2025](https://awesome-directories.com/blog/indie-hackers-launch-strategy-guide-2025/) ## Growth Channels (Indie Hacker Fit) | Channel | Fit | Conversion | Skill | |---------|-----|------------|-------| | **Indie Hackers** | Sustained 4–6 months; authentic journey | ~23% vs PH 3% | community-forum | | **Product Hunt** | Launch-day buzz | ~3% | product-hunt-launch, cold-start-strategy | | **Reddit** | Niche subreddits; 5+ months; lead with story | Varies by niche | reddit-posts, community-forum | | **Twitter/X** | Breadth, fastest follower growth | — | twitter-x-posts | | **LinkedIn** | Higher customer conversion than X | — | linkedin-posts | | **Discord** | Niche communities; strong for first 100 | — | community-forum | | **SEO** | Long-term organic; Micro-SaaS, tools | — | seo-strategy | | **LTD / AppSumo** | Fast revenue, validation | — | discount-marketing-strategy | | **Founder-led outbound** | B2B, high ACV; 10–15 DMs/day | — | cold-start-strategy | **Principle**: 2–3 channels executed well > many poorly. Twitter/X for breadth; LinkedIn for conversion. Indie Hackers + SEO or Product Hunt + Reddit common combos. ## Indie Hackers Platform Tactics - **Sustained engagement**: 4–6 months; not one-time launch - **Content**: Authentic journey posts, small wins, lessons learned, relatable struggles - **Promotion**: Product "sprinkled within" content; avoid heavy promotion - **Result**: ~12.5% conversion from authentic sharing; Plausible Analytics 24% trial vs PH 1.38% - **Build in Public**: Share progress, metrics, failures openly For HN launch, Reddit post structure, Discord tactics → **community-forum**. ## Product Types & Growth Fit | Type | Example | Growth Focus | |------|---------|--------------| | **Micro-SaaS** | Nomad List, Tweet Hunter, SiteGPT | SEO, Indie Hackers, Product Hunt | | **AI tools** | Photo AI, Interior AI, AutoShorts.ai | Product Hunt, Twitter, LTD | | **Digital products** | Templates, plugins, themes | SEO, content | | **Content** | Blog, course, tools | SEO, content-marketing | ## Monetization & Pricing | Model | Use | Skill | |-------|-----|-------| | **SaaS (subscription)** | Monthly/annual; stable revenue | pricing-strategy | | **One-time purchase** | Tools, templates; lower overhead | pricing-strategy | | **LTD** | Fast validation; cold start | discount-marketing-strategy | | **Diversified revenue** | Multiple products; lower risk | — | **Principle**: Monetize early; add payment on day 1 to validate demand. Ramen profitability = first milestone. Avoid platform dependency (e.g., Twitter API). ## Multi-Channel Launch (Indie Hacker) | Week | Focus | |------|-------| | 1–2 | Audience building (LinkedIn 3×/week) | | 3–4 | Beta; community engagement | | 5 | Pre-launch countdown | | 6 | Product Hunt + Reddit/Indie Hackers | | 7 | Post-launch follow-up | **Build in public** before launch. For full launch checklist → **cold-start-strategy**. ## When to Use Which Skill | Scenario | Skill | |----------|-------| | First users, launch timeline, Product Hunt | cold-start-strategy | | Indie Hackers, HN, Reddit post structure, Discord | community-forum | | PMF validation before scale | pmf-strategy | | SEO for organic growth | seo-strategy | | LTD structure, pricing | discount-marketing-strategy | | Product Hunt, Taaft, G2 submission | product-hunt-launch, directory-submission | | Full GTM (new product, 90-day) | gtm-strategy, product-launch | ## Output Format - **Channel** selection (2–3; fit for indie) - **First 100 users** plan (DMs, communities, Build in Public) - **Build in Public** content mix (40/30/20/10) - **Skill mapping** (cold-start, community-forum, seo-strategy, etc.) - **Timeline** (pre-launch, launch, sustained) ## Related Skills - **cold-start-strategy**: Launch timeline, Product Hunt, directory submission; first users execution - **open-source-strategy**: Open source commercialization; GitHub, DevHunt; Build in Public for OSS - **community-forum**: Indie Hackers, HN, Reddit, Discord tactics; forum post structure - **pmf-strategy**: Validate before scaling; avoid large paid before PMF - **seo-strategy**: Organic growth; Micro-SaaS, tools - **discount-marketing-strategy**: LTD structure; cold start revenue - **product-hunt-launch**: Product Hunt preparation and launch - **directory-submission**: Taaft, G2, curated lists - **gtm-strategy**: Full GTM framework; new product launch - **product-launch**: Launch execution; channels, checklist - **twitter-x-posts, linkedin-posts**: Build in Public post copy - **reddit-posts**: Reddit post copy for cold-start
Related Skills
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
pricing-strategy
When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
open-source-strategy
When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.