Launch on Product Hunt the right way
A 12-step playbook. Open in Dock and you'll get four surfaces seeded:
- **Steps** (table) — the 12 gates as rows, each owner + due + status
- **Assets** (table) — gallery images, GIFs, the demo video, the maker comment
- **Brief** (doc) — the product positioning + why-now you maintain alongside the work
- **Hunt log** (table) — hourly rank + comment count + signups during the 24-hour window
Read `Steps` top-to-bottom. Day-of work begins at 9pm Pacific the night before, not the morning of.
Outcome
A Product Hunt launch that lands in the top 5 of the day, drives 500-2000 signups, and seeds a launch-day press cycle you can repurpose for the next 6 months.
Estimated time: 2-3 weeks of prep, 24 hours live, 1 week post-mortem
Difficulty: intermediate
For: Founders running their first or second public launch.
What you'll need
Pre-register or install before you start.
- Product Hunt (Free) — The launchpad itself. The official launch checklist + scheduler live here.
- Loom (Free tier (25 videos)) — Record the 60-90 second demo video that goes in the gallery.
- Figma (Free tier) — Design the gallery cards (1270x760), the GIFs, the social card.
- Buffer ($15/mo for the Essentials plan) — Schedule the launch-day social posts on X, LinkedIn, Bluesky.
- Resend (Free tier (3k/mo, 100/day)) — Send the morning-of email blast to your list.
- Plausible ($9/mo starter) — Real-time traffic dashboard for the 24-hour window.
The template · 12 steps
Step 1: Pick the launch date and the day-of slot
Estimated time: 30 min decision
Product Hunt resets at 12:01am Pacific every day, and the rank you hit by hour 4 mostly decides where you end up at hour 24. Tuesday, Wednesday, and Thursday have the highest engaged audience; Friday and weekends are quieter, which is great if you want a softer launch but punishing if you need top-of-day. Avoid the same week as a Y Combinator demo day or a major Apple event.
Tasks
- Pick the target date: Tuesday, Wednesday, or Thursday
- Cross-check the date against YC demo days, Apple keynotes, OpenAI DevDay, and AWS re:Invent
- Pick the slot: schedule the launch in Product Hunt for 12:01am PT on that date
- Block out the next 24 hours on every team member's calendar
Pointers
- [Official] Product Hunt launch checklist
- [Official] Product Hunt launch FAQ
[!CAUTION] Gotchas
- Product Hunt launches start at 12:01am Pacific, not midnight in your local time. Set your alarm.
- Mondays look tempting (lots of attention) but the launch fatigue is real. The community shows up Tuesday.
- If you submit before scheduling, your draft becomes a duplicate detector and any retry will get auto-merged into the original. Schedule first.
Step 2: Pick a hunter (or self-hunt)
Estimated time: 1-2 hours of outreach if hunting; 0 if self-hunting
Hunters are Product Hunt users with established followings. A well-known hunter pings their network with a launch alert, which is worth a hundred upvotes in the first hour. Self-hunting is fine in 2026: the algorithm no longer rewards hunter notoriety the way it did in 2018, but a hunter can still help if they have an audience overlap with your buyer.
Tasks
- Decide: hunter or self-hunt
- If hunting: list 5-10 hunters whose previous launches overlap your audience
- DM each hunter on X or email them with a 2-paragraph pitch + your launch date
- If they accept: send them the Product Hunt draft URL so they can submit on launch day
- If self-hunting: confirm your own Product Hunt profile has a real avatar, bio, and 5+ upvotes (new accounts get throttled)
Pointers
- [Community] Top hunters leaderboard
- [Official] Product Hunt makers vs hunters
[!CAUTION] Gotchas
- Brand-new Product Hunt accounts (less than 30 days, fewer than 5 prior upvotes) get rate-limited automatically. Warm yours up two weeks before.
- A hunter who has launched a competitor recently won't help you. Check their last 10 launches before reaching out.
Step 3: Write the tagline, description, and topic tags
Estimated time: 2-3 hours
The tagline is 60 characters. It is the single highest-leverage word count of the entire launch. Lead with the verb the user wants to do, not your category. The description is 260 characters and shows in the feed under the tagline. The topic tags decide which sub-leaderboards you appear on and which followers get notified.
Tasks
- Draft 10 candidate taglines (60 char max), pick the one that survives a 'does my mom understand it' read
- Draft the description (260 char max) leading with the user benefit, not the tech
- Pick 3-5 topic tags that match where your buyer hangs out (Productivity, Developer Tools, Marketing, etc.)
- Run the tagline past 3 people outside your team for the gut-check
Pointers
- [Community] Recent top-of-day launches (study) — Read the taglines on yesterday's top 5. Pattern-match.
[!CAUTION] Gotchas
- Taglines with 'launch' or 'announcing' get penalised in the feed. The community knows you're launching, you're on Product Hunt.
- Avoid emoji in the tagline. Some clients render them as squares; the visual noise hurts the click-through.
- Topic tags are sticky. The launch ranks against the launches in those topics for 30+ days.
Agent prompt for this step
Draft 10 candidate taglines for our Product Hunt launch.
Read the Brief surface in this workspace for product positioning. Constraints:
1. 60 characters max each
2. Lead with the verb the user does ("Track", "Ship", "Run"), not the category
3. No "AI-powered", no "revolutionary", no "the future of"
4. One should be sober, one should be punchy, one should be unexpected, the rest balanced
5. Pair each with a 260-character description draft
Output as a 10-row table with columns: tagline, description, why-this-one. Then recommend the top 3 with reasoning.
Step 4: Build the gallery: video, GIFs, and screenshots
Estimated time: 1 day
The gallery is what converts a feed scroller into a profile clicker. The first slot should be a 60-90 second demo video (auto-plays muted in the feed); the next 3-5 slots should be high-contrast screenshots or GIFs that each show a single distinct value prop. Boring gallery, dead launch.
Tasks
- Record a 60-90 second demo video showing the core flow end-to-end
- Export at 1270x760 (the gallery aspect ratio) with captions baked in (audio is muted by default)
- Design 3-5 gallery cards at 1270x760, one core value prop each
- Optionally: 1-2 GIFs of the most magical moment (under 5MB)
- Test the gallery on mobile Product Hunt — most viewers see it small
Pointers
- [Official] Product Hunt media specs
- [Tool] Loom for product demo recording
[!CAUTION] Gotchas
- Videos auto-play muted. If the value prop only lands with sound, bake captions into the video frame, not as a separate track.
- GIFs over 5MB get compressed badly. Keep them under 5MB and short loops (3-5 sec).
- First gallery slot is the post-thumbnail in feeds. Make it self-explanatory at thumbnail size.
Step 5: Draft the maker comment (the first comment on your own launch)
Estimated time: 2-3 hours
The maker comment is the second-most-read piece of copy after the tagline. It pins to the top of the comment thread and gives you 1500 characters to set the founder voice, share why-now, and seed the comment-thread momentum. Write it three days before launch, edit it the night before.
Tasks
- Open with one human sentence: who you are, why you built this
- Add a paragraph on why-now: what changed in your life or the world that made this product feel inevitable
- Add a paragraph on what is in the launch and what is NOT (set expectations, prevents 'buggy' comments)
- Close with a question that invites replies: 'What would make this 10x more useful for you?'
- Save the draft in the Brief surface; you'll paste it as the first comment at 12:02am PT
[!CAUTION] Gotchas
- Don't paste 'press release' tone. The Product Hunt community downvotes corporate voice.
- Mentioning revenue, fundraise, or 'first $X in ARR' is fine and even welcomed. It's an indie-builder community.
- Avoid asking for upvotes in the maker comment. Product Hunt's terms forbid it and the community reports it.
Agent prompt for this step
Draft the maker comment for our Product Hunt launch.
Read the Brief surface for the why-now and the founder backstory.
Structure:
1. Opening: one sentence on who you are + why you built this
2. Why-now: a paragraph on what changed that made the product feel inevitable
3. What's in / what's not: a paragraph setting expectations
4. Invitation: a question that invites replies
Constraints: 1500 characters max. No "we" if it's a solo founder. No "excited to announce". Talk like you would to a friend at a dinner party who asked "so what are you working on?".
Output the draft + 3 alternative openings + 3 alternative closing questions.
Step 6: Build the soft-supporter list without violating the no-upvote-asking rule
Estimated time: 1-2 days
Product Hunt forbids asking for upvotes, but it explicitly allows telling your network that you launched. The line is: notify, don't beg. A 50-200 person notify list of friends, customers, and prior-launch hunters who genuinely care will give you organic engagement; a mass DM blast will get reported.
Tasks
- Build a list of 50-200 people in a sheet: name, channel (X DM, email, Slack), relationship
- Pre-write a personal-tone notification message (not a copy-paste; one paragraph, mention them by name)
- Schedule sending for 6am Pacific on launch day (so they wake up to it, not get rage-pinged at 12:01am)
- Email your existing user list with a launch-day ping (BCC or proper ESP, not gmail.com)
- Post in 1-3 Slack/Discord communities you are an active member of (not a drive-by)
Pointers
- [Official] Product Hunt community guidelines — Read the section on what counts as upvote-asking.
- [Tool] Resend for transactional email
[!CAUTION] Gotchas
- Product Hunt detects coordinated voting from new accounts. If 50 people who have never used PH suddenly upvote, your launch ranks get reduced silently.
- Asking 'please support our launch' in a message is the upvote-ask. 'We launched on Product Hunt today, here's the link' is fine.
- Slack workspaces with #launches channels are gold. Drive-by posting in unrelated channels gets you removed.
Step 7: Set up launch-day analytics and the war room
Estimated time: 2-3 hours setup
Launch day data is fast-moving and the Product Hunt analytics tab is delayed. Set up a real-time dashboard of: PH rank (manual hourly check), traffic source breakdown, signup conversion, top-of-funnel hits per channel. Run a private Slack channel or Discord room for the team so the launch comment-replying gets distributed.
Tasks
- Create a launch-day Slack channel (or Discord room) and pin the PH URL + rolling rank tracker
- Wire Plausible (or your analytics) to a public dashboard you can refresh on a phone
- Set up UTM-tagged links for every distribution channel (twitter, email, slack, hn) so you can attribute
- Print a comment-response rotation: who handles comments which hour
- Designate one person as Comment Captain for the day. They reply within 15 min to every top-level comment
Pointers
- [Tool] Plausible dashboards
- [Tool] UTM builder
[!CAUTION] Gotchas
- Product Hunt's own analytics tab updates every 4-6 hours. Don't rely on it for hour-by-hour rank.
- Phones drain fast on launch day. Keep a charger at the war-room desk.
- Comment Captain MUST be a real human voice. Auto-generated replies stand out and get downvoted.
Step 8: Pre-write the X / LinkedIn / Bluesky launch threads
Estimated time: 3-4 hours
Cross-channel distribution drives 30-60% of launch-day traffic. Write the threads in advance so you can hit publish at 6am Pacific instead of staring at a blank tweet at 12:30am. Each platform has a different tone: X is punchy and screenshot-forward, LinkedIn is story-forward, Bluesky is the indie-builder side audience.
Tasks
- Draft a 5-7 tweet launch thread on X with one screenshot or GIF per tweet
- Draft a LinkedIn post (1200-2000 chars) leading with the founder story
- Draft a Bluesky thread (mirror of X but with the Bluesky-specific tone)
- Schedule them all for 6am Pacific in Buffer or Hypefury
- Pre-write 3-5 reply tweets to common questions you'll get
Pointers
[!CAUTION] Gotchas
- X's algorithm penalises threads where the first tweet has the link. Put the PH link in the second tweet or in the reply.
- LinkedIn posts with 3+ links get reach-throttled. One link.
- Bluesky posts with media render at 1:1. Crop accordingly so screenshots aren't squashed.
Agent prompt for this step
Draft the X / LinkedIn / Bluesky launch posts for our Product Hunt launch.
Read the Brief surface for positioning, the Assets surface for screenshot URLs.
Output 3 separate drafts:
1. X thread: 5-7 tweets, hook tweet with screenshot, each subsequent tweet one feature/value prop with one image
2. LinkedIn post: 1200-2000 chars, founder-story tone, ends with the PH link
3. Bluesky thread: same shape as X but slightly more indie-builder voice
Constraints: no exclamation marks. No "I'm thrilled to announce". Lead with the user benefit. Each platform's own native tone.
Step 9: Launch hour: 12:01am to 4am Pacific
Estimated time: 4 hours, live
The first four hours decide where you sit at hour 24. Be awake, be fast, and reply to every top-level comment within 15 minutes. The team in the war room rotates: one person watches the comment thread, one watches the analytics, one fields DMs and emails. The third hour is when the first wave of momentum comes from East Coast morning users.
Tasks
- 12:01am PT: confirm the launch is live, paste the maker comment as the first comment on the thread
- 12:02am PT: hunter (or self) posts the upvote
- 12:05am PT: the war room ping-list of 5-10 closest friends gets notified
- Reply to every top-level comment within 15 min — no exceptions
- Track rank at the top of every hour in the Hunt log surface
- Around 3am PT, East Coast US starts to wake; expect a second wave of comments
Pointers
- [Official] Product Hunt live leaderboard
[!CAUTION] Gotchas
- Refreshing the launch page from your maker account does NOT increase its rank. Don't sit there F5-ing at 12:30am.
- The 12:01am-1am hour is sparsely populated. Don't panic if you're not in top 10 yet; momentum builds.
- If you're shadow-banned (rank stuck at 20+ with low engagement), email support@producthunt.com immediately. They've done it for stress.
Step 10: Launch day daytime: 6am to 6pm Pacific
Estimated time: 12 hours, live
This is the long middle. Schedule fires (X, email, LinkedIn, Bluesky) at 6am PT. Comments slow but get longer and more thoughtful. The buyer-shaped traffic shows up in this window: the people who actually convert, not the cheerleading.
Tasks
- 6am PT: scheduled X / LinkedIn / Bluesky posts fire automatically
- 6:30am PT: send the email blast to your existing list
- Throughout the day: reply to every comment within 30 min, track signups by source
- Lunchtime PT (~12pm): post the rank update on X ('up to #4!'), drives a second wave
- 3pm PT: cross-post the launch in 1-2 indie-builder communities (carefully, not as spam)
- 6pm PT: assess: top 5? top 3? plan the next 6 hours accordingly
[!CAUTION] Gotchas
- Don't post 'help us reach #1' updates. They violate the no-upvote-ask rule.
- If the Comment Captain is slipping past 30 min response time, rotate. Stale comments hurt momentum.
- Save EVERY interesting comment thread to repurpose into testimonials, blog posts, or future launch copy.
Step 11: Launch night: 6pm to 11:59pm Pacific
Estimated time: 6 hours, live
The closing hours. Most of the rank is locked in by now, but the comment thread is still active and the East Coast evening drives a final bump. Save the day's data, draft the thank-you post, and start planning the post-launch press cycle.
Tasks
- Reply to every remaining comment by 9pm PT
- 11pm PT: post the thank-you tweet/comment ('thanks everyone, here are the highlights')
- Export every comment thread to the Brief surface for testimonials + objections analysis
- Snapshot the final rank, total upvotes, total comments, total signups in the Hunt log
- Sleep. Tomorrow is the press follow-up.
[!CAUTION] Gotchas
- Product Hunt freezes leaderboards at midnight PT. The rank you have at 11:59 is the rank that goes in the daily leaderboard email.
- Don't stay up past midnight pushing for one more upvote. The marginal effort is worse than 8 hours of sleep before the press cycle.
Step 12: Post-launch: ride the press cycle and ship the post-mortem
Estimated time: 1 week
A top-5 daily launch typically buys 3-7 days of press attention if you keep momentum. Pitch reporters, repurpose the launch comments into testimonials, and write the post-mortem so the next launch is sharper. Your Product of the Day badge (if you got one) stays on the listing forever and is worth dropping into the footer of your site.
Tasks
- Day +1: pitch the launch to 10-20 newsletters and reporters with the rank as social proof
- Day +2: ship a 'lessons from launch day' post on your blog or LinkedIn (drives a second traffic wave)
- Day +3: turn the top 5 launch comments into testimonials on the landing page
- Day +7: write the post-mortem — what worked, what didn't, what to repeat next time
- Day +7: schedule the 1-month follow-up post ('a month after launch, here's what changed')
[!CAUTION] Gotchas
- Reporters get 200 PR pitches a day. Lead with one number (the rank, the signups, the revenue), not the product.
- The Product Hunt badge image (if you won Product of the Day) is downloadable from the launch page. Put it in the site footer.
- If the launch flopped (rank 20+), still ship the post-mortem. The honest post-mortem often outperforms the launch itself in evergreen traffic.
Agent prompt for this step
Draft the post-launch press pitch for our Product Hunt launch.
Read the Hunt log surface for the final numbers + the Brief surface for the product positioning.
Output:
1. A 5-bullet press pitch with: rank achieved, total upvotes, what makes this launch newsworthy
2. A list of 20 publications + writers to pitch (TechCrunch, The Information, Hacker Noon, indie newsletters)
3. A personalised first-line for each pitch
4. A 'lessons from launch day' blog post outline (5-7 sections)
5. The post-mortem template: what worked, what didn't, repeat / drop / try-next-time
No "thrilled to announce". Lead with the data.
Hand the template to your agent
Paste the prompt below into your agent's permanent system prompt so the agent reads, writes, and maintains this workspace as you work through the steps.
You are an agent on the "Launch on Product Hunt" playbook workspace at your-org/launch-on-product-hunt.
Your role: keep the four surfaces (Steps, Assets, Brief, Hunt log) in sync as the team works through the 12-step playbook.
Cadence:
- During launch day, append a row to Hunt log every hour with rank, comment count, signups since last check.
- When a step ships (Done), add a one-line summary to the Brief noting what shipped at that gate.
- Mirror any new asset (gallery card, GIF, video link) into the Assets table.
- After launch day, draft a post-mortem section in the Brief: top 3 converting comments, top 3 traffic sources, what to repeat or drop next time.
First MCP tool calls:
1. list_surfaces(workspace_slug="launch-on-product-hunt")
2. list_rows(workspace_slug="launch-on-product-hunt", surface_slug="steps")
3. get_doc(workspace_slug="launch-on-product-hunt", surface_slug="brief")
Do NOT post anything to Product Hunt directly. Drafting goes in the Brief; humans copy-paste to PH so the maker account stays human-attributed.
FAQ
What rank do I need on Product Hunt to call it a successful launch?
Top 5 of the day is the rank that converts to lasting attention: badges, leaderboard email, press pickup. Top 10 is solid. Outside top 10 means you'll get the traffic from your own distribution but Product Hunt itself won't compound it. Don't measure success by rank alone, though: 800 signups at rank 8 is a better launch than 200 signups at rank 1.
Do I need a hunter, or can I self-hunt?
Self-hunting is fine in 2026. The algorithm doesn't materially favour hunter notoriety the way it did pre-2020. A hunter helps if their audience overlaps your buyer; a hunter with no overlap is decoration. The single best version is: self-hunt if you have your own warm Product Hunt account, get a relevant hunter only if they actually use your category of product.
Can I ask my friends and customers to upvote?
You can notify them of the launch; you cannot ask for upvotes. The line: 'we launched on Product Hunt today, here's the link' is allowed. 'Please support our launch by upvoting' is forbidden by the community guidelines and gets reports. The notification version drives just as many real upvotes from people who would have voted anyway, plus zero risk of penalty.
What time should I launch?
12:01am Pacific. Product Hunt resets at midnight Pacific, and the rank you achieve in the first 4 hours sets your trajectory for the day. Tuesday, Wednesday, and Thursday slots are the highest-engaged. Weekend launches get less competition but also less traffic.
Can my AI agents help with the Product Hunt launch?
Yes. Agents are particularly useful for: drafting taglines + descriptions from your product brief, drafting the maker comment, drafting the multi-platform launch threads, building the press pitch list for the post-launch cycle, and tracking the launch log in real time. Posting on Product Hunt itself should stay human-attributed: drafts go in the Brief, the maker pastes them.
What does it cost to launch on Product Hunt?
Product Hunt itself is free. The associated tools (scheduler, analytics, email) typically run $30-50/mo if you don't have them already. The biggest cost is the team-time: 2-3 weeks of prep + the 24-hour launch day + 1 week of follow-up.