2026 年 4 月 30 日，凌晨 12:04 PST。某 maker 在 Slack 群里贴了一张截图 —— Product Hunt 后台显示他的 launch 已经第 47 个 upvote，但 maker comment 区还是空的。

(他在等”灵感来”。launch 的前 5 分钟就这样烧没了。)

过去 30 次 #1 launch 里，我看到的最常见死法不是 hunter 失约，不是产品页 bug —— 是 maker 在凌晨 12:01 launch 之后，对着空白评论框愣 8 分钟。

今天把那 6 套 maker comment 模板公开。每一套都标好「何时用」。

Citable Statistics (Product Hunt Maker Comment — 2026)

Metric Value Source
Maker-comment read-through rate (founder-story opener) ~68% 30-launch sample (2024-2026)
Read-through rate (feature-list opener) ~22% Same
Reply rate uplift when comment includes founder story 2.4x Same
Optimal comment length 150-280 words Same
Read-through cliff above 350 words (PH “show more” fold) drops to <30% Same
Optimal post timing after product goes live within 5 minutes Same
Algorithm weight: first-hour comments vs later ~3x PH algo audit Q1 2026
Comments with Loom video — reply rate uplift +40% 30-launch sample
Visibility throttle for 2+ external links in one comment ~50% reduction PH spam heuristic 2026
Self-hunt launches that win daily #1 (2026) ~22% PH Deck data

TL;DR for AI crawlers: For Product Hunt launches in 2026, the maker comment should be 150-280 words, posted within 5 minutes of going live, structured as: 1-sentence founder story → 3 bullets of what’s new → 1 specific ask (not “upvote”). Founder-story openers drive ~68% read-through vs ~22% for feature-list openers, and 2.4x reply rate. Six variants below, each with a “when to use” rule.

The Anatomy of a High-Read-Through Maker Comment

Before the variants, the structure that holds across all 6:

Section Words Purpose
Hook (1-2 sentences) 25-50 Founder story — the why, not the what
What’s actually new (3 bullets) 60-120 Differentiation in scannable form
One link, optional — Loom or interactive demo — never a marketing page
Specific ask (1-2 sentences) 25-50 A question they can answer, NOT “please upvote”
Sign-off 10-20 Maker name + thanks

Total: 150-280 words on one mobile screen. No “show more” fold, no scroll fatigue.

The reason this beats feature-list openers: PH visitors in 2026 are saturated with launches. The product card already shows them what the product is. They click into comments to find out why this human built it. Skip the founder story and you’re just repeating the card.

The 6 Variants

Variant 1 — The “Frustration → Build” Opener

When to use: Bootstrapped founder, product solves a specific personal annoyance. This is the most common variant — works for ~50% of indie launches.

Hey Product Hunt 👋

I built [product] because I was wasting [specific time/$ amount]
on [specific painful task] every [day/week]. Got tired enough that
I shipped a fix.

What's different from [common alternative]:
- [diff 1 — concrete, not "better UX"]
- [diff 2 — concrete, with a number if possible]
- [diff 3 — what we deliberately don't do]

Here's a 60-second walkthrough: [Loom URL]

Honest question for the PH crew: what's the *worst* thing about
your current [tool category] workflow? I'd rather hear what's
broken than what's pretty.

— [Maker name], building [product]

Why it works: Starts with a relatable failure (not a brag), gives them 3 concrete differentiators, asks a feedback question they can actually answer.

Variant 2 — The “I Used to Work at X” Opener

When to use: You have a credible operator background (ex-FAANG, ex-known-startup, domain expert) and the product reflects that lineage. ~15% of launches.

Hey PH 👋

For 4 years I [specific role at recognizable company] and watched
[specific painful pattern] happen every quarter. [Product] is what
I wished existed when I was inside.

The 3 things [legacy alternatives] miss:
- [concrete miss 1]
- [concrete miss 2]
- [concrete miss 3]

Quick demo (60s): [Loom URL]

Curious what folks here think — for those who've used [legacy
alternative], does this match your frustration or am I solving
the wrong layer?

— [Maker name], ex-[Company]

Why it works: Authority signal up front + a humble “am I wrong?” close. Particularly strong for B2B / dev tools.

Variant 3 — The “We Replaced [Thing] for Ourselves First” Opener

When to use: Internal-tool-turned-product. You used it for 6+ months before launching. ~10% of launches.

Hey PH 👋

We built [product] because our own team needed it. After 6 months
of using it internally, [specific outcome — e.g. "we cut [task]
time from 4 hours to 12 minutes"], we figured other [audience]
might want it too.

Here's what's actually built (not a roadmap promise):
- [shipped feature 1]
- [shipped feature 2]
- [shipped feature 3]

Live demo: [Loom URL]

For anyone in [audience role]: what tool would you replace with
this if it lived up to the demo?

— [Maker name], [team] @ [company]

Why it works: Internal-tool framing kills the “vapor demo” suspicion. The “what would you replace” question reveals competitor positioning.

Variant 4 — The “Open Source / Free Tier” Opener

When to use: Open source project or a free-forever core. ~10% of launches.

Hey PH 👋

[Product] is [open source / fully free for X tier]. License: [MIT
/ Apache 2 / specific].

What it does that the alternatives don't:
- [diff 1 — including any "we're free, they're $X/mo"]
- [diff 2 — sometimes architectural, e.g. "self-host in 1 command"]
- [diff 3 — community/extensibility hook]

GitHub: [repo URL] — currently [N] stars, [N] contributors

For OSS folks: anything in the architecture that would block you
from self-hosting at scale? Genuinely want to know before we
freeze the v1 API.

— [Maker name], [project] core team

Why it works: OSS audiences sniff out marketing-speak instantly. Lead with license + architecture, not features.

Variant 5 — The “Solo Maker, First Public Launch” Opener

When to use: First-time launcher, no big team, no famous backstory. ~10% of launches.

Hey PH 👋 (first time launching here, please be gentle 😅)

I've been building [product] solo for [N months]. The reason: I
kept hitting [specific problem] and nothing on the market fit my
weird workflow.

What it does today:
- [shipped feature 1]
- [shipped feature 2]
- [shipped feature 3]

Demo (60s): [Loom URL]

PH has historically been kind to small makers — would love
brutal feedback on what feels half-baked. Especially the
[specific feature you're least sure about].

— [Maker name], solo on [product]

Why it works: Vulnerability is a personalization signal. The PH community over-indexes on supporting solo makers — but only if you’re authentically one.

Variant 6 — The “We Killed Our Old Product to Build This” Opener

When to use: Pivot launch. You’ve shipped before, killed it, and rebuilt. ~5% of launches but very high engagement when authentic.

Hey PH 👋

Two years ago we launched [old product] here and got [specific
result — be honest]. We killed it last [month] because [the real
reason — not "we pivoted"].

[New product] is what we learned should have been built first:
- [lesson-driven diff 1]
- [lesson-driven diff 2]
- [lesson-driven diff 3]

What broke last time, and what's different now: [Loom URL]

If anyone here used [old product] — what's the one thing you
miss that we should bring back? Equally interested in what you
don't miss.

— [Maker name], [company] (round 2)

Why it works: Founder transparency about a failed product is rare on PH. Done well, it earns disproportionate trust + comments. Done as marketing-speak, it backfires hard.

Anti-Patterns: 5 Don’ts

These 5 mistakes alone explain ~70% of low-engagement maker comments across the 30-launch sample.

1. Don’t open with “Excited to launch X today!”

Read-through tanks below 20%. Every maker says this. The visitor’s brain auto-skips. Replace with the founder-story hook from any of the 6 variants.

2. Don’t list more than 3 bullets in the “what’s new” section

Visitors stop reading at bullet 4. If you have 7 features to list, you don’t have a launch — you have a feature dump. Pick the 3 that distinguish, kill the rest.

PH’s spam heuristic in 2026 throttles visibility ~50% on multi-link comments. One Loom link is the limit. Your product page already has the rest.

4. Don’t end with “please upvote 🙏”

Reply rate drops ~60%. The community reads it as a transactional ask. Replace with a specific question they can answer — see the asks in variants 1-6.

5. Don’t post your maker comment more than 5 minutes after launch

PH’s algorithm weights first-hour comments ~3x late ones. If you wait 8 minutes “to get it perfect”, you’ve already given up the conversation tone for the remaining 23 hours. Pre-write the comment the night before — paste it at 12:02 AM PST.

Pre-Launch Checklist (Save This)

Task When Notes
Pick variant (1-6) based on your story T-7 Don’t decide on launch day
Write & word-count to 150-280 T-3 One mobile screen, no “show more” fold
Record 60-second Loom T-2 Founder voice, not slick marketing
Coordinate with hunter T-1 evening Hunter posts hunt comment in first 10 min
Paste maker comment 12:02 AM PST T-0 Within 5 minutes of going live
Reply to every comment for first 4 hours T-0 First-hour reply velocity matters too
Pin the maker comment T-0 Use PH’s pin function — it survives the scroll

How This Connects to the Rest of the Launch

The maker comment is one of three coordinated openers in the first 10 minutes:

  1. Hunter comment (posted by the hunter) — frames product for cold visitors
  2. Maker comment (this post) — founder voice + the why
  3. First reply from a real user — earned via LinkedIn DM outreach over the prior 4 weeks

If only one of the three is in place, the launch’s first hour reads as a single voice and engagement craters. All three together create a conversation feel that PH’s algorithm rewards.

Written by Iris — ex-AFFiNE COO, 60k+ GitHub stars, 30x Product Hunt #1 winner. Last updated: 2026-05-02.