Most Product Hunt launch strategy advice reads like a checklist: build a teaser page, line up your hunter, post at 12:01am Pacific. What it doesn't cover is what happens when you do all of that and still stall. Lachlan Chavasse, a real developer who launched his product useDaily on Product Hunt, brought in more than 100 upvotes and spent the entire day stuck at position #26. His public account of what actually happened is more useful than any checklist, because it names the two specific things that quietly worked against him.

What actually happened

Chavasse had prepared for months. He lined up his network, briefed his existing users on what to say in the comments, and skipped paying a hunter (something he noted Product Hunt's own guidelines discourage even as the platform seems to tolerate it in practice). Launch day brought in over 100 upvotes, roughly half of them with comments he personally answered.

And he stayed at position #26 all day, with fewer than 50 points to show for it.

The gap between "100+ upvotes" and "sub-50 points" is the first real lesson. Product Hunt doesn't count upvotes 1:1. Votes from new accounts and dedicated beta testers, exactly the people most likely to show up for a first-time founder's launch, get weighted down hard. Chavasse estimates something close to a 2:1 ratio of upvotes to points in his case. He only figured this out after noticing that comments from his own network were arriving in his inbox in delayed batches for days after the launch, a sign Product Hunt's spam filtering had flagged that engagement pattern.

The second miss was structural rather than behavioral: he wasn't featured. Product Hunt randomly rotates a set of listings onto its front page during the first four hours after launch, and that placement brings a real, passive boost, an estimated 50 to 100 additional upvotes from bots and automations that watch featured listings specifically. Missing that rotation meant starting the whole day already behind, regardless of what his own network did.

The mistake that looked like the obvious move

The part of Chavasse's account worth sitting with isn't the vote-weighting mechanics. It's the mistake he didn't see coming, because it looked exactly like what every founder is told to do: activate your network on launch day.

He sent roughly 1,000 messages to LinkedIn connections, collected around 60 sign-ups through a pre-launch form, and on launch morning sent out a single email with three direct links: Product Hunt, LinkedIn, and X. Then he kept messaging.

It backfired on both platforms at once. Product Hunt's algorithm read the sudden burst of network-driven traffic as spam-adjacent and throttled his points. LinkedIn, separately, gave the post unusually little organic reach, which Chavasse traced to a specific cause: by pushing his own network to click through via a direct link, he'd removed the chance for the post to be discovered and shared organically, the exact signal LinkedIn's algorithm rewards. The same post, by his own account, was one of his best-performing pieces of content by comment count, but never got the organic push a similar post normally would have.

That's a genuinely counterintuitive result. The instinct to mobilize your network isn't wrong; the direct link is what turned a normal launch tactic into something two separate platforms treated as a signal to suppress.

What he'd actually do differently

Chavasse's own plan for next time is concrete. He'd still tell his network the launch is happening, even notify them again on the day, but without a direct link attached, accepting that this makes the ask bigger and probably limits it to a smaller, closer circle rather than a thousand-person blast.

He'd also build a core group in advance, something like 20 regular Product Hunt users who already have standing on the platform, people whose votes carry full weight and who can meaningfully move a listing in the crucial first four hours. And he'd launch something small earlier, purely to get established in Product Hunt's own system before the launch that actually matters.

None of this requires a bigger budget or a hunter. It requires treating the platform's actual mechanics, vote weighting, featured-placement selection, spam detection, as real constraints to plan around rather than assuming effort and network size are what decide the outcome.

This is the same discipline behind a real, disclosed build-in-public account: a channel's stated rules and its actual behavior aren't always the same thing. The founders who do well are usually the ones who found that gap the hard way and wrote it down.

Chavasse did exactly that, pointing readers to Lenny's Newsletter's own Product Hunt guide as further real reading rather than treating his own account as the final word.

The actual verdict

A Product Hunt launch strategy built around "get everyone you know to upvote at once" is optimizing for the wrong variable. What decided Chavasse's outcome wasn't how many people he reached, it was whether Product Hunt's own vote-weighting and featured-placement systems treated that reach as legitimate. Read his full account on Medium before your own launch day.

If you're planning a launch, the actionable version of his lesson is small and specific: skip the direct links, build a handful of real Product Hunt relationships before you need them, and treat launch day as a test of the platform's mechanics first, your network's reach second.