launches
Prepare launch-day comments and upvotes
How to seed a healthy thread, ask for votes without spam, and avoid an empty project page.
5 min read
An empty comment box on launch day looks like nobody cared. You do not need a fake crowd. You need a plan that survives ~09:00 UTC go-live (UTC playbook) and honest ranking rules (PotD ranking).
MakerHunt rewards a living thread more than a silent upvote count. Operators notice. Makers who lurk notice. Your future customers notice. This post is the prep kit.
What “healthy” means
| Signal | Healthy | Unhealthy |
|---|---|---|
| Maker comment | Early, specific, one CTA | Missing or pure link dump |
| Replies | Maker answers within an hour when awake | Ghosted bug reports |
| Upvote asks | Direct, to people who know the product | Cold “upvote pls” spam |
| Accounts | Real users, optional self-upvote | Sockpuppets |
| After close | Thanks + changelog | Vanish until next launch |
Self-upvote is allowed under our ranking writeups. Buying engagement is not. Sockpuppets are not. Paste-the-same-ask across twenty Discords with no context is not.
Decision tree: who to ask
- Do you have 5–10 people who already use the product? Message them the MakerHunt URL + UTC open time first. Warm circle only.
- No users yet? Focus the maker comment on problem + demo. Do not rent a Telegram upvote farm. Prefer Premium/Featured only if you need chrome, not fake social proof (pricing explained).
- Launching while you sleep? Queue the maker comment draft and a pinned ask for a teammate. See UTC playbook.
- Want PotD? You cannot buy it. Comments + votes on the rules; PotD is not a SKU.
Before the day opens
- Write a maker comment you will post in the first minutes: problem, who it is for, one link to docs or demo, one feedback question.
- Tell 5–10 people who already use the product the MakerHunt URL and the UTC open time.
- Decide what you want feedback on (pricing, onboarding, naming). Ask that in the thread so comments have a job.
- Confirm Free crawl or paid status on submit / dashboard so you are not debugging payment mid-thread (FAQ).
- Skim legal/badges if you plan to screenshot the page for social.
Maker comment template (steal and edit)
We built [name] because [specific pain].
It is for [narrow audience], not [out of scope].
Try [docs/demo section].
Today I want blunt takes on [pricing / onboarding / naming].
If it helped you, upvote on MakerHunt and tell me what broke.
Keep it under ~120 words. Markdown links are fine; image spam is not.
Asking for upvotes without being that person
- Be direct and single-action: open the listing, upvote if it helped you.
- Include the UTC window so people do not arrive after close.
- Do not DM strangers with only “upvote pls.”
- Self-upvote is allowed (ranking rules, votes and PotD).
- Point people at trending?filter=today only as a spectator sport, not as “raid #1.”
Message template (warm circle)
We go live on MakerHunt ~09:00 UTC on [date]. Link: [project URL].
If the product saved you time, an upvote + one sentence of feedback helps more than a like on my tweet.
During the day
- Reply to every serious comment. Short beats perfect.
- If someone reports a bug, say what you will fix and whether it ships today.
- Use markdown in comments the way the composer allows (links, short code). No image walls.
- Pin or highlight the maker comment if the product supports maker highlight; keep the thread scannable.
- Mid-day: second share post with a narrower ask (“Is the pricing page clear?”).
- Watch trending?filter=today for pace, not ego.
Comment reply cheat sheet
| They said | You do |
|---|---|
| Bug | Repro steps? Fix ETA? Workaround? |
| Pricing doubt | Honest constraint + link to your pricing |
| Feature ask | Ship / later / no, with reason |
| “Cool” | Ask one follow-up question so the thread stays alive |
| Spam / hate | Report; do not feed |
What not to do
- Sockpuppet accounts
- Paste the same ask across twenty Discords with no context
- Buy engagement
- Promise PotD or fake DR next to the thread (honest proof)
- Confuse sponsor rails with launch social proof (sponsor vs Featured)
- Dump only your marketing homepage URL when the hunt project URL is the upvote target
After close
Thank people who showed up. Link the PotD badge if you earned one (winners, owner badge surfaces). Keep the best feedback in your public changelog within 48 hours. If you missed the window, do not beg for late votes on a closed day; schedule the next honest launch instead.
Pre-flight checklist
- Maker comment drafted and saved somewhere offline
- 5–10 warm contacts notified with UTC time
- Feedback theme chosen
- Project URL tested while logged out
- Free badge still live or paid SKU settled (pricing)
- Social posts queued for open / mid / late
- You accept empty > fake
Honesty section
A quiet launch with three real comments is better than twenty ghost accounts. MakerHunt is a small indie hunt. Density without trust burns you on the next product. We do not sell vote packs. Featured (€19) and SEO (€39) buy chrome and (for SEO) a queued article, not a comment section. Free still needs a real badge crawl. PotD remains earned.
Next step
Launch checklist, then submit. Clock: UTC playbook. Ranking: PotD guide. Money: pricing. Edges: FAQ.