Spread the launch over five dates instead of one crowded day
A launch crammed into one day reaches one room and leaves you answering five at once. Put waitlist sites a month ahead, the main launch, Show HN two days later, secondary sites a week on, then a recap with real numbers: five dates, five fresh audiences, each with you free to answer every comment.
By The Marketinque TeamReviewed November 2026
BackedAt least one source behind this play is a platform’s own documentation, a law, a study or a dataset that we read in full, or a checked claim supports it.
In the wiki: Backlinks and directories
Step 3.5.1 Write the launch calendar: a waitlist site four weeks out, launch day, Show HN two days later, the secondaries a week later, a recap after in the SaaS launch checklist · phase 3, Authority baseline
The play
Put each launch surface on its own day: waitlist sites about four weeks ahead (their queues are long), the main launch day, Show HN two days later written for builders, the secondary launch sites and your communities a week later, and a recap with real numbers after that. Each date is a fresh audience and a day you can answer every comment.
How to run it
- Write the calendar backwards from launch day before you submit anywhere.
- Four weeks out: submit to the waitlist sites, which queue for weeks.
- Launch day: the main platform, with the whole day kept clear to answer.
- Two days later: Show HN, only if people can try it without signing up, written as what you built and how.
- A week later: secondary launch sites and the communities you already belong to. Two days after that: the recap post with the real numbers.
Watch out for
- Show HN is for something people can try, never a landing page or sign-up page.
- Never ask anyone to upvote or comment, on any of the sites.
- Be there to answer on each date; a launch you cannot attend is wasted.
Best for
Plays like this one
- A Product Hunt launch treated like a campaignTreat Product Hunt as a campaign, not a lottery ticket: teaser page up early, a demo video and origin-story maker comment ready, genuine first-hour supporters lined up, and full-day comment presence. The rank matters less than the residue — the badge, the backlink, early adopters, and a launch-day audience you keep.
- Open PRs to the awesome-lists your users starSubmit your tool to the curated GitHub awesome-lists for your category via pull request, following each repository’s contribution guidelines to the letter. Developers genuinely shop from these lists, stars compound their reach, and a merged entry is a durable link from a domain engineers trust more than any ad.
- Put a side panel inside the tool your buyers already work inShip a small browser extension whose side panel sits beside the tools your buyers already use and shows your product’s answer for the page they are on. It meets them at the moment of the problem, inside their own workflow, and the extension store becomes one more place they find you.
- List where the AI-curious search: AI directories and registriesList AI-adjacent products in the directories AI-curious buyers browse — There’s An AI For That and its peers — and in machine-readable registries like MCP server lists where AI agents themselves discover tools. These indexes rank for "[task] AI" searches and increasingly feed the recommendations assistants make.
Sources
- Hacker News: Show HN guidelines (read in full)
Compiled by The Marketinque Team to our editorial standards.