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.
What this skill does
# 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; Bu
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".