| name | sales-indiehackers |
| description | Indie Hackers platform help — the largest founder community for bootstrapped and indie businesses (~1-2M monthly visits, 165K+ entrepreneurs). Covers community engagement strategy (post types, formatting, timing), product pages (revenue milestones, transparent metrics), groups, interviews, podcast, Partner Up co-founder matching, advertising, and IH+ premium. DR75 nofollow backlinks. Use when your Indie Hackers posts aren't getting traction, product page isn't attracting interest, want more visibility among bootstrapped founders, or unsure if IH is worth the time for your launch. Do NOT use for multi-directory launch coordination (use /sales-launch-directory). Do NOT use for other launch platforms (use the platform-specific skill). |
| argument-hint | [describe what you need help with on Indie Hackers] |
| license | MIT |
| version | 1.0.1 |
| tags | ["sales","product-launch","startup","community","platform"] |
Indie Hackers Platform Help
Helps with everything related to using Indie Hackers — the largest community of bootstrapped founders, with 165K+ entrepreneurs, ~1-2M monthly visits, and DR75 backlinks (nofollow). Founded by Courtland and Channing Allen, acquired by Stripe in 2017, returned to indie ownership in 2023.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
-
What are you trying to do on Indie Hackers?
- A) Share my product / get feedback
- B) Build an audience / engage the community
- C) Learn from other founders (interviews, posts)
- D) Find a co-founder or collaborator
- E) Advertise to the IH audience
- F) Decide if IH is worth my time vs other platforms
- G) Something else — describe it
-
What's your product?
- A) SaaS / web app
- B) Mobile app
- C) Developer tool / API
- D) Digital product (course, ebook, template)
- E) Service business / agency
- F) Not launched yet — idea stage
-
What stage are you at?
- A) Pre-launch — building, no users yet
- B) Just launched — looking for first users
- C) Growing — have some traction, want more
- D) Established — looking for community and networking
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
Step 2 — Route or answer directly
If the request maps to another skill, route:
- Multi-directory launch planning →
/sales-launch-directory
- Product Hunt launch →
/sales-producthunt
- Email marketing to subscribers →
/sales-email-marketing
- Newsletter strategy →
/sales-newsletter
- Audience growth →
/sales-audience-growth
- Landing page optimization →
/sales-checkout
Otherwise, answer directly from the Indie Hackers knowledge below.
Step 3 — Indie Hackers platform reference
Read references/platform-guide.md for the full platform reference — core modules (Show/Ask IH, product pages, groups, Build Board, Ideas DB, newsletter advertising via BuySellAds/Passionfroot), backlink/SEO value (DR75 nofollow), the engagement DO/DON'T playbook, the IH vs Product Hunt vs Hacker News comparison, and pricing tiers.
Answer using only the relevant section — don't dump the full reference.
Step 4 — Actionable guidance
Based on the user's situation:
For launching a product on IH:
- Create your product page first — fill in description, tech stack, and revenue (even if $0)
- Build engagement for 2-4 weeks before your launch post — comment on others' posts, answer questions, join groups
- Write a "Show IH" post that tells the story: what problem you're solving, why you built it, what metrics you have so far, and a specific ask (feedback on pricing? beta testers? growth advice?)
- Post Tuesday-Thursday for best engagement (mirrors Product Hunt timing)
- Respond to every comment — IH rewards engagement heavily
- Follow up with milestone posts as you grow — the community loves ongoing stories
For building an audience on IH:
- Start with "Ask IH" and discussion posts — help others before promoting yourself
- Share genuine learnings from your building process — "I tried X and it failed because Y" performs better than "I did X and it was great"
- Post 1-2x per week consistently — don't spam, but stay visible
- Join 2-3 relevant groups and contribute there — smaller but more engaged audience
- Cross-promote with your newsletter or Twitter/X — IH rewards authentic multi-platform presence
For deciding if IH is worth it:
- Yes if: You're bootstrapped, willing to share transparently, and want long-term community relationships. IH has the highest trial conversion rate of any founder community (~24%).
- No if: You want a one-time traffic spike (use Product Hunt), need dofollow backlinks (IH is nofollow), or are building for enterprise (IH audience skews SMB/indie).
- Best strategy: Use IH as an ongoing engagement channel alongside Product Hunt (one-time launch) and your own newsletter (owned audience).
Gotchas
Best-effort from research — review these, especially items about plan-gated features and community norms that may shift.
-
All links are nofollow. Despite DR75, IH passes no SEO link equity. Don't use IH as a backlink strategy — it's a referral traffic and community play.
-
Community quality has degraded somewhat. SEO-spam listicles ("Best X tools 2026") now flood the feed. Genuine founder posts still get engagement, but you're competing with noise. Stand out by being specific and authentic.
-
IH+ features are opaque. The premium tier costs ~$24.75/mo but specific benefits aren't clearly documented publicly. Verify before subscribing.
-
No public API. You can't programmatically post or pull data from IH. Third-party scrapers exist (Apify, Browse AI) but violate ToS.
-
Advertising is now self-serve with public pricing. As of 2026, newsletter sponsorships are listed on BuySellAds and Passionfroot: Intro Section $749, Full Section $999, Bundle $1,199 (newsletter sent 3x/week, 200K+ subscribers). The audience is highly targeted but niche. Custom/direct deals can still be arranged with IH directly.
-
IH is indie again. After being owned by Stripe (2017-2023), Courtland and Channing Allen bought it back. The platform may evolve faster now but with fewer resources.
-
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
Related skills
/sales-launch-directory — Coordinate launches across 20+ directories including Indie Hackers. Install:
npx skills add sales-skills/sales --skill sales-launch-directory/sales-producthunt — Product Hunt platform help (largest launch platform, DR91 dofollow)/sales-peerlist — Peerlist platform help (weekly Launchpad, 203K+ users)/sales-audience-growth — Grow your email list and subscriber base/sales-newsletter — Newsletter monetization strategy/sales-email-marketing — Email marketing to your subscriber list/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
npx skills add sales-skills/sales --skill sales-do
Examples
Example 1: Plan a product share on Indie Hackers
User says: "I just launched my API monitoring tool and want to share it on Indie Hackers. What's the best approach?"
Skill does:
- Recommends creating a product page first with description, tech stack, and current metrics
- Advises spending 2 weeks engaging with the community before the launch post
- Drafts a "Show IH" post structure: problem, solution, metrics, specific ask
- Suggests posting Tuesday-Thursday for best visibility
- Emphasizes responding to every comment and following up with milestone updates
Result: Complete IH launch plan with post structure and engagement timeline
Example 2: Decide between IH and Product Hunt
User says: "Should I post on Indie Hackers or Product Hunt first for my bootstrapped SaaS?"
Skill does:
- Compares the two: IH is ongoing engagement (24% conversion), PH is a 24-hour sprint (3% conversion)
- Notes IH backlinks are nofollow while PH is DR91 dofollow
- Recommends IH first — lower stakes, build community, refine messaging
- Then PH as a polished, coordinated launch event
- Suggests using
/sales-launch-directory to plan the full multi-platform sequence
Result: Clear sequencing recommendation with reasoning
Example 3: Build an audience on IH from scratch
User says: "I have zero followers on Indie Hackers. How do I build an audience there?"
Skill does:
- Starts with "Ask IH" and discussion posts — help before promoting
- Recommends sharing authentic learnings: failures, experiments, real numbers
- Suggests posting 1-2x/week consistently
- Advises joining 2-3 relevant groups for targeted engagement
- Warns against link-dropping and generic promotions
Result: Community engagement playbook with specific tactics and anti-patterns
Troubleshooting
Posts getting zero engagement
Symptom: Shared a product or update but got no upvotes or comments
Cause: Most likely one of: dropped a link with no context, posted without prior community engagement, or posted at a low-traffic time. IH rewards members who contribute to others' posts before promoting their own.
Solution: Spend 2 weeks engaging genuinely (commenting on others' posts, answering questions). Then post a "Show IH" with a story arc: problem → solution → metrics → specific ask. Include screenshots or demos. Post Tuesday-Thursday. The 80/20 rule: 80% helping others, 20% self-promotion.
Competing with spam/listicle posts
Symptom: Your genuine founder post is buried under SEO-spam listicles
Cause: IH has seen increased spam content ("Best X tools 2026" type posts). The algorithm and moderation haven't fully addressed this.
Solution: Stand out by being specific and personal. Generic content gets lost — detailed case studies with real numbers, specific challenges, and authentic voice cut through the noise. Use the "Show IH" tag and engage in comments to boost visibility. Post in relevant groups (lower traffic but less spam) in addition to the main feed.
Unsure whether to share revenue numbers
Symptom: Hesitant to share transparent metrics on IH
Cause: Revenue transparency is IH culture but feels risky for some founders (competitive concerns, privacy)
Solution: You don't have to share exact revenue. Share growth percentages, user counts, or directional metrics ("we went from X to Y"). Even sharing what didn't work is valuable. The community values honesty over impressive numbers — "$200 MRR after 6 months of grinding" gets more engagement than vague "we're growing fast" claims.
