Back to GrowthDex
Growth idea action plan

Show HN title and timing formula

Use data-backed keyword and scheduling rules to maximize visibility when launching on Hacker News.

rare tactic
Best-fit channelHacker News
Stage + context0-100 · 100-1K
BudgetFreebudget tier
Suggested operator signalQualified Show HN visitors who complete the intended first product action

Why this can grow a startup

Including 'Open Source' or 'YC' in a Show HN title boosts points by 38%. 'CLI' or 'API' adds 26%. Question-style titles ('Why X Sucks and How Y Fixes It?') get 2.2x more comments. Titles under 55 characters get 24% more upvotes. Posting on Tuesdays or Wednesdays between 8-11 AM UTC drives 28% more engagement. Critically, 'AI-Powered' in the title now causes a 15% score penalty due to audience fatigue.

Source-backed example

Analysis of ~1,200 Show HN launches (scraped and published on r/indiehackers) revealed specific title keywords and posting windows that dramatically affect traction.

Source details

Source: reddit.com · Browse reddit.com tactics

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Source discovered: March 20, 2026

Hacker News0-100100-1K
GrowthDex operator note

When to use it

Use this when Hacker News is relevant to 0-100, 100-1K and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Follow Hacker News community guidelines: do not solicit votes, comments, or submissions; share a useful working demo and an original explanation.
  3. Record a baseline for: Qualified Show HN visitors who complete the intended first product action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Build creator and community systems around real incentives, trust, and repeat participation.

Work with Ian

SOURCE HUB

More tactics from reddit.com

Explore related GrowthDex examples and evidence connected to reddit.com.

Open reddit.com source hub