[Maschinell · Review ausstehend] Product Hunt Pre-Launch Playbook for Micro-SaaS

[Maschinell · Review ausstehend] Product Hunt spikes are not a growth strategy[Maschinell · Review ausstehend] — but a well-timed launch is still the fastest way to put a niche tool in front of the exact Baueers and operators who review it. The mistake most makers make is treating PH as the beginning of Marketing. It is thepayoff[Maschinell · Review ausstehend] of Marketing that started weeks earlier. This Playbook is the pre-launch half: what we do in the two weeks before a launch so that on launch day we are not scrambling.

1. Pick the day and the slot early

Launch on aTuesday[Maschinell · Review ausstehend] (engagement peaks Tue–Thu; avoid weekends). Go live at00:01 PT[Maschinell · Review ausstehend] so you get a full US day of votes, then keep a second product in the same cluster off by about an hour so the two do not cannibalize each other's upvotes. Announce the date two weeks out — a public date is a forcing function.

2. The waitlist is the launch pool

[Maschinell · Review ausstehend] If you have been collecting emails from day one, your waitlist is not a vanity metric — it is the group you email at 00:00 PT on launch day. Two weeks out we expect: a landing page that converts (clear CTA, one job), a pricing page live, and the core flow working end-to-end including checkout. A launch with 800 warm emails converts measurably better than a launch with zero.

[Maschinell · Review ausstehend] 3. Teaser cadence: one beat per channel, per week

• Week −2:[Maschinell · Review ausstehend] announce the date + what problem the tool kills (X/LinkedIn). Publish the first long-form post with a real screenshot.
• Week −1:[Maschinell · Review ausstehend] drop the "how it works" post (3 steps, real UI). Email the waitlist: launch day + request to upvote. Post a genuine question to one relevant subreddit (no link — value first).
• Day −3:[Maschinell · Review ausstehend] freeze the Product Hunt kit — tagline, description, 5 images, 60s demo video, first comment draft.
• Day 0:[Maschinell · Review ausstehend] 00:01 PT post goes live; share everywhere in hour one; reply toeverycomment in the first 4 hours.
• Day +2:[Maschinell · Review ausstehend] review the numbers against your funnel and write the retrospective.

4. Screenshots that sell, not decorate

[Maschinell · Review ausstehend] 5. First comment: founder voice, zero invented numbers

[Maschinell · Review ausstehend] The first comment is the story. Write it in your own voice: why you built it, the one problem you kept hitting, and an open question to the community. Donot[Maschinell · Review ausstehend] invent customers, revenue, or testimonials — the comment section will fact-check you. If you only have lighthouse users "in onboarding," say exactly that.

6. The 48-hour rule

[Maschinell · Review ausstehend] Product Hunt rewards momentum, not just quality. In the first 48 hours: reply to every comment by name, update the description if a top comment reveals a clearer angle, email anyone who upvoted a thank-you, and capture which traffic source actually converted. Then the real work starts — Verwandleing the spike into a channel through SEO/GEO content, not chasing another spike.

[Maschinell · Review ausstehend] Part of the LX Micro-SaaS Factory series. We ship niche AI tools at lxsaihub.com — try one live.