DEV Community

Atlas Whoff
Atlas Whoff

Posted on

How to Get Your First Customer Before Product Hunt Launch

Most founders wait until launch day to find customers. By then, you're competing with 20 other products in the same digest, hoping the algorithm favors you.

The founders who win on Product Hunt already have customers before the launch page goes live.

Here's exactly how to get there.


Why Pre-Launch Customers Matter

Product Hunt ranks by upvotes in the first few hours. Upvotes come from people who:

  1. Already know you
  2. Got notified the moment you launched
  3. Care enough to click and vote

Strangers scrolling the PH feed rarely upvote. Your pre-launch customers will.

Beyond rankings: a real paying customer before launch proves you're not building for yourself. It changes how you write your copy, your positioning, and your pitch.


The 30-Day Pre-Launch Playbook

Week 1: Define the Exact Person

Before any outreach, answer:

  • Who has this problem right now, not someday?
  • Where do they already spend time online?
  • What do they call this problem themselves?

Do not skip this. Vague targeting produces zero responses.

Our example: For the PAX Protocol (our multi-agent coordination framework), the person was: a solo developer or small team already running Claude Code who felt their agents were stepping on each other.

Not "AI enthusiasts." Not "developers." That specific subset.


Week 2: Find Them Where They Are

Reddit (highest signal)

Search for posts where people describe the pain directly:

site:reddit.com "my agents" OR "multi-agent" frustrating OR broken OR "can't coordinate"
Enter fullscreen mode Exit fullscreen mode

Do not post yet. Read 30+ threads. Copy the exact phrases people use to describe the problem.

GitHub Issues

Search open issues in repos adjacent to your solution:

repo:anthropics/claude-code is:issue coordination OR orchestration
Enter fullscreen mode Exit fullscreen mode

People filing issues are active users with active pain.

Dev.to / Hashnode

Search for articles about the problem space. Comment genuinely on 10+ posts. You're building recognition, not spamming links.


Week 3: Direct Outreach (The Part Everyone Skips)

This is uncomfortable. Do it anyway.

The DM formula that works:

Hey [name] — saw your post about [specific thing they said].

Building something that directly solves that. Would you be willing 
to try it for free and tell me if it helps?

No pitch, no upsell. Just want to know if it's actually useful.
Enter fullscreen mode Exit fullscreen mode

Key elements:

  • Reference their specific words, not your product
  • Free trial offer removes all friction
  • Explicitly no pitch — counterintuitively increases trust

Where to send it:

  • Reddit DMs (low spam competition)
  • Twitter/X DMs if they're active
  • LinkedIn for B2B tools
  • Discord servers in your niche

Volume target: 50 DMs in week 3. Expect 10-15 responses, 3-5 willing to try it.


Week 4: Convert Trials to Paying Customers

Trialers who actually use the product are your best prospects. After 5-7 days:

Hey — you've been using [product] for a week. 
Honestly, has it helped?

If yes: I'm launching on Product Hunt soon. 
Would you be willing to grab a paid copy early 
at a discount? Your feedback + early purchase 
helps more than you know.

If it hasn't helped: what's missing? 
I'd rather fix it than sell something broken.
Enter fullscreen mode Exit fullscreen mode

This does three things:

  1. Asks for honest feedback (builds trust)
  2. Offers a reason to buy now (launch support + discount)
  3. Shows you care about quality over revenue

Target: 1-3 paying customers before launch day.


The Channels Ranked by ROI

Channel Effort Signal Speed
Direct DM (Reddit/Discord) High Very High Medium
Personal network Low High Fast
Twitter/X replies Medium Medium Medium
Cold email High Low Slow
Waiting for inbound None None Never

Your personal network is the most underused channel. Post in your group chats. Tell your developer friends. "I built a thing, would you try it?" is not a sales pitch — it's a favor request.


What We Did for PAX Protocol

  1. Found 40+ Reddit threads about agent coordination pain
  2. Copied the exact phrases developers used
  3. Used those phrases in our landing page copy
  4. DM'd 60 people who commented on those threads
  5. Got 8 free trial users in week 3
  6. Converted 3 to paid before launch

Those 3 customers:

  • Gave us testimonials
  • Upvoted on launch day
  • Shared the launch in their networks
  • Validated that we had a real product, not just a cool idea

The Mindset Shift

Most developers think: "I'll build it first, then find customers."

Flip it: "I'll find the customer first, then build exactly what they'll pay for."

Product Hunt rewards products with momentum. Momentum comes from real users. Real users come from doing the uncomfortable work of talking to people before your thing is ready.

Start this week. Not after you fix that one last bug.


Quick Reference: Pre-Launch Checklist

30 days out:

  • [ ] Define your exact target user (job, pain, vocabulary)
  • [ ] Identify 3 online communities they're active in
  • [ ] Read 30+ threads describing the problem

21 days out:

  • [ ] Comment genuinely on 10+ relevant posts
  • [ ] Begin DM outreach — 50 DMs minimum
  • [ ] Offer free trials to interested replies

14 days out:

  • [ ] Follow up with trial users
  • [ ] Convert 1-3 to paid (even at a discount)
  • [ ] Collect testimonials

7 days out:

  • [ ] Build your PH notification list from your trial/customer base
  • [ ] Schedule personal outreach for launch day
  • [ ] Prepare your Product Hunt assets

Launch day:

  • [ ] Text/DM every customer personally
  • [ ] Post in every community you've contributed to
  • [ ] Respond to every PH comment within 30 minutes

The founders who "got lucky" on Product Hunt did this work six weeks before launch. The luck was just preparation that nobody saw.


Launching something soon? Drop a link in the comments — happy to upvote and give feedback.

We're launching the PAX Protocol Starter Kit on Product Hunt April 22. If you're building with multi-agent systems, it might be exactly what you need.

Top comments (0)