What we learned from hitting #1 on Product Hunt | Brew Blog | Brew

On Tuesday, May 26th, Brew hit #1 Product of the Day , then #1 Product of the Week on Product Hunt.

The badge brought a wave of new customers, opened partnership conversations we'd been chasing for months, and got us picked up by Superhuman AI's newsletter (1.5M+ subscribers) and a dozen other publishers the same week. None of that surprised me.

What surprised me was the analytics dashboard on Monday morning. ChatGPT is now our #1 referral channel.

A Product Hunt #1 in 2026 isn't really a launch. It's a training signal. You're not winning a launch-week popularity contest. You're uploading a structured authority artifact into the same corpus that ChatGPT, Claude, and Perplexity quietly consult every time someone asks them which AI email tool to use, for the next three years.

The playbook

There's no magic to the launch playbook itself. Almost every step below is something other founders have written about before, and most of it will sound familiar if you've followed a Product Hunt postmortem in the last five years. What made the difference for us was executing every one of these steps with intent, especially the unglamorous ones.

Build something people want. The unglamorous one, and the only one that matters. Everything else here is downstream of having a product people want to talk about. We spent a long time on the product before we ever thought seriously about a launch, and that's the part most launch playbooks skip.

The customer calls. We'd done hundreds of calls with users in the months before launch. Some became customers, others were curious founders peeking at what we were building.

Every one of those calls ended the same way. I asked if they'd be willing to support us on Product Hunt when we launched. Everyone said yes. That was the audience.

We tested every angle live before we picked one. Thumbnail, gallery, tagline, maker's comment, the demo videos. We ran different versions of the messaging in front of different audiences in real conditions and watched what landed. By launch day, we weren't guessing about which framing would work for developers versus marketers versus founders. We'd seen each version perform.

The version we landed on. Every word, image, and gallery thumbnail on this page was tested before it got here. Nothing was coincidental.

Launch day was a war room. We cleared our calendars the day before, the day of, the day after. The only thing we didn't pause was customer calls and support, because we weren't going to drop the people who'd actually paid us in the middle of a launch.

Our mighty Brew team in the launch war room, with every calendar cleared except customer support.

The first hour on Product Hunt matters disproportionately. PH launches drop at midnight PST, which is 3am for us in New York. The war room was running by then, with the inner circle lined up to upvote and comment in the first 60 minutes. We personally replied to every comment, often within minutes. Maker presence is half the engagement signal on a launch page, and most launches go quiet by hour three.

We kept going for the Week. Most teams launch and then disappear. We treated each new milestone as its own thing with its own messaging: Day badge first, then a real push for the Week. The Week badge compounds visibility in ways the Day badge doesn't, and almost nobody sustains the energy past day one to fight for it.

That's the playbook. Most of it is unsurprising if you've launched before.

The one tactical thing I didn't see anywhere else. Product Hunt's monthly leaderboard is based on calendar months. We launched on May 26th and ended May at #4 of the month, behind three products that had launched in the first week of May and so had three extra weeks to accumulate upvotes for the monthly contest.

Brew at #4 of May with 878 upvotes, ahead of #2 (864) and #3 (853). The catch: some of those trickled in during the first days of June, after the May ranking had already locked.

By the time I'm writing this on June 2nd, we already have more upvotes than #2 and #3 of May, and it wouldn't surprise me if by the time you read this we've passed #1 too (you can check the leaderboard yourself). The math just doesn't work for a late-month launch.

TL;DR: if you can move your launch date, launch in the first week of the month.<br>If you want the fully tactical version with every other checkbox spelled out, Tally's launch checklist is the most thorough public one I've seen and worth keeping open during prep.

The more interesting story for us is what came out of the launch that we didn't go in expecting at all.

What I didn't expect

The playbook above is what got us the badge. The real story of this launch, for us, is what the badge unlocked once we had it, and three things in particular caught us off guard.

LLMs have made Product Hunt one of the highest-leverage launches of the year

When someone asks ChatGPT what email marketing platform is...