kostja94/marketing-skills

indie-hacker-strategy

When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/kostja94/marketing-skills --skill indie-hacker-strategy

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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.

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.

TraitIndie HackerVC-backed
FundingBootstrapping; product revenueExternal investment
GrowthSustainable; Ramen profitability firstScale at all costs
ControlFull autonomyInvestor reporting
TimelineLong game; niche focusFast expansion

Core Concepts

ConceptMeaning
BootstrappingSelf-funded; use product revenue to grow; no equity dilution
MVPMinimum viable product; ship fast, validate, iterate
Build in PublicShare progress, metrics, failures openly; attracts early adopters
Scratch your own itchSolve your own problem first; others likely have it too

Pieter Levels Playbook

TacticGuideline
Ship fast, fix laterLaunch ugly but functional MVPs; Nomad List started as Google Sheet + Stripe; Photo AI made $150K first week despite initial flaws
Monetize from day oneAdd payment button at launch; validate willingness to pay, not just usage
Automate everythingScripts, APIs, no-code; run without employees
Build in publicShare metrics openly; 600K+ followers; "Day 1: building X. Day 3: first customer" attracts early adopters

Reference: Pieter Levels: The One-Man Startup Empire

First 100 Users (Indie Hacker Tactics)

PhaseTactic
First 5Direct DMs to people who'd genuinely benefit
Next ~15Conversations in communities where target users hang out (Reddit, Indie Hackers)
Scale to 50Build in public with visible metrics
Reach 100Double 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, Indie10k – 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 MixShare
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, Indie Hackers Marketing 2025

Growth Channels (Indie Hacker Fit)

ChannelFitConversionSkill
Indie HackersSustained 4–6 months; authentic journey~23% vs PH 3%community-forum
Product HuntLaunch-day buzz~3%product-hunt-launch, cold-start-strategy
RedditNiche subreddits; 5+ months; lead with storyVaries by nichereddit-posts, community-forum
Twitter/XBreadth, fastest follower growth—twitter-x-posts
LinkedInHigher customer conversion than X—linkedin-posts
DiscordNiche communities; strong for first 100—community-forum
SEOLong-term organic; Micro-SaaS, tools—seo-strategy
LTD / AppSumoFast revenue, validation—discount-marketing-strategy
Founder-led outboundB2B, 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

TypeExampleGrowth Focus
Micro-SaaSNomad List, Tweet Hunter, SiteGPTSEO, Indie Hackers, Product Hunt
AI toolsPhoto AI, Interior AI, AutoShorts.aiProduct Hunt, Twitter, LTD
Digital productsTemplates, plugins, themesSEO, content
ContentBlog, course, toolsSEO, content-marketing

Monetization & Pricing

ModelUseSkill
SaaS (subscription)Monthly/annual; stable revenuepricing-strategy
One-time purchaseTools, templates; lower overheadpricing-strategy
LTDFast validation; cold startdiscount-marketing-strategy
Diversified revenueMultiple 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)

WeekFocus
1–2Audience building (LinkedIn 3×/week)
3–4Beta; community engagement
5Pre-launch countdown
6Product Hunt + Reddit/Indie Hackers
7Post-launch follow-up

Build in public before launch. For full launch checklist → cold-start-strategy.

When to Use Which Skill

ScenarioSkill
First users, launch timeline, Product Huntcold-start-strategy
Indie Hackers, HN, Reddit post structure, Discordcommunity-forum
PMF validation before scalepmf-strategy
SEO for organic growthseo-strategy
LTD structure, pricingdiscount-marketing-strategy
Product Hunt, Taaft, G2 submissionproduct-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

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
kostja94
Comunidade

google-search-console

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (

instalações
1
GitHub Stars
1,1 mil
Atualizado
6 de out.
kostja94
Comunidade

google-ads

When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube ads." For paid mix, use paid-ads-strategy.

instalações
3
GitHub Stars
1,1 mil
Atualizado
6 de out.
kostja94
Comunidade

growth-funnel

When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.

instalações
3
GitHub Stars
1,1 mil
Atualizado
6 de out.
kostja94
Comunidade

schema-markup

When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSit

instalações
3
GitHub Stars
1,1 mil
Atualizado
6 de out.