Indie Hacker Strategy
Choose indie-hacker growth moves—Build in Public, channels, and mindset—without VC playbooks when you are solo or a tiny team.
Overview
indie-hacker-strategy is an agent skill most often used in Grow (also Validate and Launch) that guides bootstrapped solo founders on channels, Build in Public, and indie-hacker growth strategy.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill indie-hacker-strategyWhat is this skill?
- Frames indie hacker mindset: autonomous, 1–3 people, profitability over VC scale
- Covers first users, Build in Public, and channel selection for bootstrapped founders
- Maps when to branch to cold-start-strategy for launch execution
- Points to community-forum for Indie Hackers, HN, and Reddit post structure
- Version 1.1.1 with optional brief intro on first invoke per SKILL.md
- Metadata version 1.1.1
Adoption & trust: 850 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping alone but defaulting to VC-style marketing advice that does not fit bootstrapped constraints or your first 100 users.
Who is it for?
Solo or 1–3 person founders running Micro-SaaS or tools who want sustainable traction and public-building norms.
Skip if: Venture-scale blitz scaling, enterprise sales motions, or cold-start launch runbooks without strategic context—use cold-start-strategy instead.
When should I use this skill?
User mentions indie hacker, indie developer, bootstrapping, solo founder, Build in Public, Micro-SaaS, first 100 users, or solo company; for cold start execution use cold-start-strategy.
What do I get? / Deliverables
You get a structured indie-hacker growth frame, clear skill handoffs to cold-start-strategy or community-forum when execution detail is needed.
- Channel and mindset recommendations
- Pointers to cold-start-strategy or community-forum for next steps
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Sustained bootstrapped growth is the canonical Grow shelf; strategy compounds after you have something to sell. Content and narrative-led distribution (BiP, forums) are the primary levers this skill organizes under grow/content.
Where it fits
Decide whether your itch-scratching idea fits indie economics before you over-build features.
Pick Build in Public and forum channels before handing off to cold-start-strategy for launch week.
Plan ongoing public updates and content loops that compound trust without paid ads.
Align retention and support expectations for a one-person company serving early adopters.
How it compares
Strategic indie playbook and skill routing—not a step-by-step Product Hunt launch checklist.
Common Questions / FAQ
Who is indie-hacker-strategy for?
Bootstrapping developers and solo founders building profitable small products who need marketing strategy aligned with indie constraints, not headcount-heavy growth teams.
When should I use indie-hacker-strategy?
During Validate to shape positioning; at Launch when choosing distribution angles; in Grow for Build in Public, channels, and first-user loops; whenever the user names indie hacker or solo founder tactics.
Is indie-hacker-strategy safe to install?
It is advisory marketing guidance without required shell or network hooks; review the Security Audits panel on this page before installing any skill from the repo.
Workflow Chain
Then invoke: cold start strategy, community forum
SKILL.md
READMESKILL.md - Indie Hacker Strategy
# 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%*