indie-hacker-strategy

Name: indie-hacker-strategy
Author: kostja94/marketing-skills

$npx mdskill add kostja94/marketing-skills/indie-hacker-strategy

Guides indie hackers on sustainable product development and growth

Identifies user needs and market opportunities for an autonomous startup.
Deploys tools like analytics platforms to track user engagement and performance metrics.
Decides on the best channels and tactics based on user feedback, competitor analysis, and personal experience.
Delivers actionable growth strategies through reports and recommendations tailored to the startup's unique situation.

SKILL.md

.github/skills/indie-hacker-strategyView on GitHub ↗

---
name: indie-hacker-strategy
description: 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.
metadata:
  version: 1.1.1
---

# 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

More from kostja94/marketing-skills

Skill	Description
404-page-generator	When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generator	When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketing	When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generator	When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-tracking	When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generator	When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generator	When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-ads	When the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-content	When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysis	When the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.