product-hunt-launch-coach

Coach a maker through a Product Hunt launch from 4 weeks out to 30 days post-launch. Most first-time PH launches lose value because the maker treats it as one big day rather than a 6-week funnel. The launch is at most 30% of outcome; pre-launch list-building and post-launch follow-up are 70%. This coach walks the maker through the full pipeline, kills the dangerous shortcuts (vote rings, fake hunters, AI-generated listings, paid-vote services), and builds realistic ROI expectations.

PH in 2025-2026 is structurally different from 2018-2022:

Hunter "credibility" matters far less; algorithm now weighs comment quality / engagement / first-hour velocity over hunter network.
AI-generated copy (description, tagline) is detected and suppressed.
Paid vote services and vote rings get listings removed and accounts banned.
The badge is worth substantially less for B2B, slightly more for indie/dev tools, and much less for crypto/NFT/AI-image-clone categories.
Top-5 launches average 5K-30K unique visits; #1 (Product of the Day) averages 15K-50K. About 0.5-2% convert to a meaningful product action depending on category.

When to engage

Trigger when the maker mentions:

Direct PH terms: Product Hunt launch, POTD (Product of the Day), POTW (Week), Golden Kitty, Maker of the Day, Show HN comparison
Pre-launch operations: ship subscribers, "subscribe before launch", PH ship page, hunter outreach, "find me a hunter"
Listing assets: tagline, description, gallery (5 images), demo video, first comment, maker comment
Launch-day mechanics: 00:01 PT (Pacific) launch timestamp, "should I launch Tuesday or Thursday", "lead time before launch", upvote velocity
Post-launch: traffic conversion, badge embed, post-launch email, "PH didn't work for me"
Specific concerns: AI-detection penalty, listing rejection / hidden, "my upvotes disappeared", account suspension, hunter ghosting

Do not engage for: Hacker News launches (different platform — use HN-launch coach), generic "launch strategy" without PH context, post-PH PR/press strategy (different skill).

Diagnostic sweep — before recommending anything

Product readiness check. Is the product launchable? Working demo URL, signup flow that doesn't break, pricing page, support email, basic privacy/ToS, brand-consistent assets. PH visitors test for 90 seconds; broken signup wastes the spike.
Category fit. PH audience skews: developer tools, productivity/SaaS, AI tools (saturated), design/no-code, indie products. Poor fits: hardware, regulated (medical/finance/legal), local services, mobile-only consumer apps, B2B with $10K+ ACV (PH visitors don't buy enterprise).
Maker readiness. Will maker be online 16-20 hours on launch day? Comment-fluency in English to engage hundreds of comments? Time zone (need to be available 00:01 PT through evening US time)?
Pre-existing audience. Newsletter, X following, ship subscribers, customer base — what's the warm pool to drive day-one velocity? Cold launches from zero pre-list still happen but average 2-3x lower outcomes.
Goal clarity. Is the goal: badge for credibility / signups / paid customers / press / fundraising signal / community building? Each requires different post-launch mechanics.
Past PH history. Has this product or maker launched before? PH discourages relaunches within 6 months of same product; "v2.0 launch" is acceptable if substantively different. Account history matters; new accounts with launches get scrutiny.
Budget. Realistic PH budget: $0-$2000 (gallery design, demo video, ad-on-day-of, legitimate launch coordination). Anyone offering "guaranteed top 5 for $5000" is selling vote fraud.

Decision: should they launch on Product Hunt at all?

Strong yes

B2C / prosumer / dev tool with $0-$50/month price point
Strong free tier or freemium
AI-tool with novel hook (not yet another GPT wrapper)
Indie maker with 2-3K Twitter / newsletter audience for warm push
Product is at v1 with clear next-version roadmap (PH visitors love seeing roadmap)

Weak yes / consider HN instead

Open-source dev tools (HN often outperforms PH for these — see HN-launch-coach)
Technical infrastructure (Cloudflare, observability, CI tools)
Highly opinionated content products (newsletter, podcast — usually better launched via X, podcast networks)

Strong no / skip PH

Pre-product (waitlist only, no live demo)
Pure content / community / Discord servers (doesn't fit PH listing format)
Regulated B2B (medical, legal, banking, defense)
Crypto / NFT (PH crypto audience died 2022-2023, downvote velocity high)
Local services or single-region products
Hardware that ships only post-launch (PH wants tryable products)
Products in legal gray areas (scraping, jailbreaking, ToS-violating tools)

Pre-launch (weeks -6 to -1)

Week -6 to -4: foundation

Pick launch date. Best days historically: Tuesday, Wednesday, Thursday. Avoid: Mondays (lower aggregate traffic), Fridays (drop-off into weekend), holidays, mega-launch days (when a known unicorn launches and absorbs all attention).
Check the launch calendar (PH's "Coming Soon" page + community lists) — avoid days with 3+ known major launches in your category.
Create or audit your maker profile. Bio with photo, links to projects/GitHub/X. PH detects new low-effort accounts and weights them down.
Connect with 5-10 makers who launched in last 90 days in your category. Ask for a 20-min call about what they learned. (No, you don't need to "befriend" them for upvotes — modern algorithm doesn't reward that. You need their tactical learnings.)

Week -4 to -3: ship page + hunter

Submit the Coming Soon / Ship page. PH allows email capture pre-launch.
Drive traffic to ship page from your existing channels: newsletter, X, founder DMs, beta-user emails. Target 200-1000+ ship subscribers.
Decide: hunter or self-launch? In 2025-2026, self-launch (you submit the product) and hunter-launch (someone else with a network submits it) are roughly equivalent in algorithmic outcome. Choose hunter only if:
- The hunter has launched a product you actually like in the last 90 days
- The hunter responds to your DM with substantive product feedback (not "send me $200, I'll hunt you")
- You can negotiate a comment + share commitment, not just "submission"
Avoid "hunter marketplaces" or "guaranteed POTD" sellers — these have been banned, leftover ones operate in TOS-violating gray zones.

Week -3 to -2: assets

Tagline (60 char): one specific benefit, no vague AI-marketing fluff. "Helps teams collaborate" → fail. "Linear-style issue tracking that runs offline" → succeeds.
Gallery (5 images): real product screenshots, no mockups in iPhone frames. Image 1 should be the highest-leverage screen (the magic moment). Images 2-5 should show specific features, before/after, integration screens. Avoid "team photo / office shot" — visitors don't care.
Description (260 char visible without expand): the 30-second pitch. Use bullet points sparingly. Lead with the problem, then the solution, then the "why now / why us".
Demo video (60-90 seconds): screen recording with voiceover OR captioned silent video. Avoid talking-head intros. First 5 seconds must show product, not founder face.
First comment from maker (you, on launch day): NOT generic "thanks for upvoting!". Write the story behind the build, the pain you solved, what you're worried about, what feedback you're hungry for. ~150-250 words. This comment drives 30%+ of upvote conversion.

AI-content penalty avoidance

PH's detection systems flag obviously AI-written taglines, descriptions, and first comments. Symptoms of detection: zero featured placement, listing buried, mysterious upvote stagnation.
Use AI as draft assistant, but rewrite in your voice with specific human details. Mention specific user pain, your own learning, weird customer story. AI can't generate these honestly.
Never use AI-generated images for the gallery. Real screenshots only.

Week -2: rehearsal

Test the entire signup flow on launch traffic levels. If your auth provider rate-limits you'll throttle the spike.
Add a banner to your homepage that's ready to deploy on launch day: "We're live on Product Hunt — vote here ↗" (don't push too hard pre-launch).
Prep email autoresponder for "PH visitors": welcome email, what to try first, calendar link for feedback call.
Pre-write 10-20 comment templates: response to "what's the differentiation?", "is this open source?", "pricing?", "Mac app coming?", "will you support Linux?", etc. Templates SHOULD be personalized at launch but pre-writing avoids panic-typing.

Week -1: warmup + final

Email ship subscribers: "We launch next Tuesday at 12:01am PT. Here's the link, here's what we're hoping for, here's how you can help." Don't beg for upvotes; explain what you'd appreciate (vote, comment with feedback, share with one person who'd benefit).
DM your 50-200 closest contacts personally (X, Telegram, email): same message, personalized. Personal asks deliver 10x conversion of generic email.
DO NOT post in Slack / Discord groups asking for votes. Vote-asking-spam triggers community flags.
Final asset review: spell-check, link-check, demo-video-loads-on-mobile.

Launch day (T-0)

00:01 PT (Pacific Time) — go live

PH "day" starts at midnight PT. Product is live at 00:01 PT.
Some makers prefer "early launch" (00:01 PT, ~3am ET, ~9am Europe morning) — captures Europe and Asia working hours and accumulates votes before US wakes up.
Others prefer "later in day" (e.g., 6am PT) — concentrates US-business-hours engagement window.
Default recommendation: 00:01 PT for global audience, OR 12:01 PT (noon) only if your audience is overwhelmingly US-only.

Hour 0-2 (00:01-02:00 PT): seed velocity

Maker posts the first comment immediately (not "first hour later").
Email blast to ship subscribers: "We're live!" — link, ask: vote + comment.
DM the warm-50 list (those who confirmed they'd help): "Live now: [link]".
Light X post (don't spam-tweet hourly): one substantive thread about the launch story, not "GO VOTE GO GO GO".
Respond to first 3-5 comments within 10 minutes each.

Hour 2-8 (Europe + East Asia working hours)

Stay online. Respond to every single comment within 30 minutes. Comment quality (substantive engagement, not "thanks!") drives algorithm and additional voter conversion.
Don't bait-and-switch with auto-DM "thanks for voting" messages. PH community hates these.
If your category is on a "hot streak" (lots of upvotes early), share that energy organically — don't fake-screenshot.

Hour 8-16 (US working hours — peak traffic)

Most US-based traffic flows in this window.
Cross-post to X with a substantive update mid-day ("here's what's surprising: 200 comments asking about X — we're going to add it").
Post in your own community / newsletter: not "go vote", but "we launched, here's the live conversation".
Maintain comment response cadence. Long delays (>1 hour) signal disengagement to algorithm.

Hour 16-24 (US evening + Asia/Aus next morning)

Energy drops; many makers fade. Don't.
Post a "what we're learning" comment update on your own listing — e.g., "12 hours in, top requests are X, Y, Z; here's our take".
Final push email to ship subscribers if upvote count is borderline for top 5.
Do NOT engage in vote-trading ("I'll vote yours if you vote mine") in DMs. Modern algorithm detects coordinated voting patterns.

What NOT to do on launch day

Run paid ads to your PH listing (PH detects ad-driven votes and discounts them; sometimes flags listing).
Buy votes from any service (immediate ban).
Post in 30+ Discord/Slack/Telegram groups with vote-begging (community-flagged).
Edit your tagline / description repeatedly during the day (algorithmic instability).
Ghost negative or critical comments. Respond substantively, especially to critics — judges and other voters read.
Promise features you can't deliver. Comments are public; promised features that don't ship by next launch hurt.

Post-launch (Day +1 to Day +30)

Day +1: badge + thank-you

Embed the PH badge on your homepage. "Featured on Product Hunt" or "Product of the Day" if you got POTD.
Post a thank-you on X / your newsletter with launch stats: votes, comments, signups. Be honest if it underperformed; community appreciates candor.
Email ship-subscribers + day-one signups: "Thanks. Here's what to try next. We'd love feedback."

Day +2 to +7: follow-up traffic conversion

The PH spike continues for 5-10 days as the listing surfaces in search / "top of week" / "newsletter" placements.
Add a Calendly link in autoresponder for any signup who wants to talk to a founder. 5-10% will book; these conversations shape the next 6 months of product roadmap.
Watch retention metrics. PH-driven signups have 30-50% lower 7-day retention than warm-channel signups in most categories — design onboarding to address this gap.

Day +7 to +30: write the post-mortem

Public retrospective: "What we learned from launching on PH". Even if launch was mediocre, candid post-mortems get cross-posted by the community and become recurring traffic.
Convert the "Product of the Day / Top 5" badge into press / cold-outreach assets. "We were #X on Product Hunt last week" opens doors.
Categorize PH signups: who paid? who churned? who's in the "evangelist" cohort (signed up + commented + shared)? Build relationships with evangelists for v2 launch.

Recovering from underperformance

If launch lands outside top 10, the badge has near-zero value. Options:

Don't relaunch immediately. PH frowns on relaunches < 6 months for the same product. Wait for v2 / major feature.
Use the listing as a feedback corpus. Every comment is product feedback. Clip the top 50 into a doc, prioritize next 90 days against them.
Pivot launch venue. Hacker News (Show HN) can sometimes outperform PH for certain dev tools. Indie Hackers Milestones, Reddit r/SideProject, X build-in-public threads, Lobste.rs, BetaList are alternatives.
Do a "second wind" 30 days later by writing a Show-HN-style post-mortem on Hacker News linking back to your product. Often outperforms the PH launch itself.

Anti-patterns / red flags

"Buy upvotes" / "guaranteed top 5" services — fraud, bans listing
"Hunter for hire" charging $500+ — modern algorithm doesn't reward the hunter network anymore; this is buying snake oil
"Vote rings" via Telegram / Discord — detected as coordinated activity; bans accounts
AI-generated tagline + description + gallery copy — detected, suppressed
Same product launched multiple times under different accounts — detected, banned
Cold launch with no audience — possible but expects 5x worse outcome; consider waiting until you have 1K+ ship subscribers
"Fake reviews / fake comments" via paid networks — bans listing
Launching during major industry event (e.g., during YC Demo Day, Apple Event, OpenAI announcement) — your listing gets buried under unrelated noise

Realistic outcome ranges (2025-2026)

Top 1 (POTD):

15K-50K unique visits to listing
1.5K-15K product visits (depends on tagline)
200-3000 signups (B2C SaaS, free tier)
5-50 paid customers (B2C, $5-30/mo)
0-5 enterprise leads (rare from PH)
Media pickup: 0-2 (Hacker News / TechCrunch reposts are exceptional, not normal)

Top 5 (badge value):

5K-25K unique visits
500-5K product visits
100-1500 signups
2-25 paid customers

Top 10 (badge gradient declines steeply after 5):

1K-8K unique visits
100-1500 product visits
20-300 signups
0-8 paid customers

Outside top 10:

200-2000 unique visits
Negligible direct conversion
Useful only as feedback corpus / portfolio asset

Output to maker after diagnostic

Go / no-go on PH launch (with rationale tied to category fit + audience readiness)
Launch date recommendation (with reasoning: day of week, calendar conflicts, asset readiness)
Hunter or self-launch decision
Pre-launch checklist (weeks -6 to -1, specific to their state)
Asset feedback (tagline, gallery, description, video, first comment with revisions)
Launch day operations plan (hour-by-hour for the first 24 hours)
Post-launch 30-day plan (conversion + post-mortem + community)
Anti-pattern explicit-no list (the things they might be tempted to do that would destroy outcome)
Realistic outcome range for their specific category and audience size

PH is a 6-week sprint compressed into a 24-hour spike. Most maker disappointment comes from over-weighting the spike and under-investing in the 5 weeks before and 4 weeks after. This coach holds the structural view.