Get Started
Open source that pays

Mission 4 of 6

Launch your project properly, then reply for 48 hours.

A launch is a specific post, in a specific format, at a specific time, followed by two days of fast replies. You'll prepare each platform and a plan for when it doesn't land.

55 minIntermediateFree toolsStep 1 free

What you'll do

Run the pre-launch checks

Catch what would make the first commenter say 'doesn't work', before strangers do.

Post to Hacker News and Reddit

Write a Show HN and subreddit posts in the formats each community requires, without getting banned.

Reply, log and relaunch

Follow a 48 hour reply plan, log real numbers, and know what to do if it doesn't land.

  • Product Hunt, X and Discord used for what each is good at
  • A star-logging script, so you have numbers rather than a feeling
Before you start
  • A published package and a README that passes the ten second test, from the previous two missions
  • Accounts on Hacker News and Reddit that are older than a week and have a few comments on them. Brand new accounts posting links get filtered
  • A clear two days. Not a launch the morning before a holiday or a deadline
Your progress0/6
01/06The pre-launch checklist0 done
STEP 01 of 06~8 min

The pre-launch checklist

Catch the things that make the first commenter say 'doesn't work' before five hundred people read it.

A launch is not a tweet with a link. Most launches fail at the format, the venue or the follow-through, and you'll meet each of those in this lesson. First, the checks for the day before.

Launch traffic is a stranger, on their OS, running your install line once. If it fails, the first comment says so and every later visitor reads that first.

The checklist

Run through this the day before, not the morning of:

  • The install line from the README works on a clean machine. The Docker test from the last mission, today, against the version on PyPI. Not last week.
  • The GIF loads in under two seconds on your phone over mobile data. If not, shrink it.
  • The first three examples work from a fresh clone, including any example files they need.
  • Issues are open, templates work, Discussions is on. People will file things within minutes. If Issues is off, they'll complain in the thread instead.
  • The repo description, the PyPI description and the launch title say the same thing in the same words. Three different pitches read as three different projects.
  • There's a v0.1.x release and the last commit is today. 'Last commit 3 months ago' on launch day reads as abandoned.
  • Your profile has a way to contact you: a GitHub profile README or a bio with an email or a site. Launches bring job offers, collaborators and journalists, and they need somewhere to go.
  • Nothing private is in the repo history. gitleaks detect takes ten seconds; find leaked secrets in code if you've never run it.

The honesty pass

Then reread the README and delete any sentence you couldn't defend in a comment thread. 'Blazing fast' with no benchmark, 'production ready' at 0.1.0, 'the best way to'.

Hacker News in particular rewards 'here's a small tool, here's what it doesn't do' and punishes anything that sounds like a landing page.

Tip
Write a docs/launch.md with the posts from the next steps drafted in full, the links, and the times. On the day you want to be pasting, not composing.
Checkpoint
Every item on the list is ticked today, and docs/launch.md exists with your drafts in it.
If it breaksMy HN account is brand new
My HN account is brand new
Make it now and spend the week before launch commenting usefully on threads in your area. Three or four real comments. New accounts submitting links on day one are often filtered without anyone seeing them, and there's no notification that it happened.
Still stuck? Ask the community
Next mission · Open source that paysCommunity without burning out: triage rules, labels, saying no, and the three replies
→