How to launch on Product Hunt with Flo Merian
You can't launch a podcast on Product Hunt. Flo Merian, who's run dozens of Product Hunt launches for dev tools, walks through it live using Jack's own unlaunched podcast as the test case — starting with the reframe that gets it past the front door at all.
Flo Merian is a developer marketer, a maintainer of the Developer Marketing community, and has run Product Hunt launches for numerous developer tools, including Documento and Specify.
This episode is a live case study: Jack hadn't launched Scaling DevTools on Product Hunt, so we walk through the real questions in order — what you're even allowed to launch, how the first four hours of the 24-hour cycle work, why blasting your network is the wrong move, and the scheduling mistake that quietly kills a launch before it starts.
The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.
Can you actually launch something like a podcast on Product Hunt?
No — you can't launch a podcast, a book, or just a list of tools on Product Hunt directly. But it really comes down to the angle you give it. Something like Scaling DevTools isn't just a podcast, it's a collection of lessons learned from dev-first founders, and that framing is genuinely valuable to the Product Hunt community. So the move is to share the vision and mission behind it — position it as something that goes beyond just being a podcast, in a way that actually fits what the product and community are looking for.
What actually makes a launch do well on Product Hunt?
AI is obviously trendy right now, but there are always counterexamples in both directions — you'll read plenty of stories of both successes and failures regardless of topic. One of the biggest lessons from spending time around Product Hunt is that there's no secret sauce: if you have a good product and an existing engaged audience of product users, launching will probably work no matter what your topic is. It really comes down to those two things.
So does most of the traction come from your own existing community?
For most launches, at least at the start, yes. Think of Product Hunt as a 24-hour marathon — you want to maximize exposure in roughly the first four hours, because if you land in the top five during that window, there's a high chance of organic growth in upvotes and comments after that. Most people who visit producthunt.com will see the first five products of the day, vote on them, or click through if the tagline grabs them. So having an audience that can give you that initial kick is really the starting point for performing well on launch day.
The launch happens at a specific time — does that favor certain regions?
It launches at 8am CET, which is midnight PST. That gives an edge to European, and also Caribbean, Indian, and other Asian founders, because during those first four hours, European and Asian users are the ones who are most active — Americans are asleep. Then once the American audience wakes up and starts voting, that's the moment you can really feel the organic growth kick in, assuming you've held a strong position through those first hours.
Is the strategy basically messaging everyone you know to ask for support on launch day?
Please don't do that — that's not my advice at all. I think people and products that push their brand too hard on launch day risk damaging it in the long run rather than helping it. The real objective is to be helpful, intentional, and thoughtful in how you approach the launch and its promotion, rather than DMing everyone directly. It's really about warming up your own audience beforehand — sharing publicly what you're working on, behind-the-scenes images, fun facts — so people are excited and ready by the time launch day actually arrives.
Can you give a concrete example of what that warm-up looks like?
I worked with the Documento team — an open-source DocuSign alternative — on their first and second launches. Before their first launch, they hosted an AMA on Product Hunt the week before, which got them engaging with the Product Hunt community early, and they leveraged that on social media, especially Twitter, to start raising awareness ahead of time. When they actually launched on the Sunday, people, myself included, were genuinely excited and watching how the community reacted. That's the kind of thing that starts warming up a launch well in advance.
What actually goes into an AMA if you've never hosted one before?
It's genuinely simple — something like: 'I'm Jack, I host Scaling DevTools, I've interviewed dozens of founders of their first companies, ask me anything' is a great topic on its own; people will be curious enough to ask almost anything. It's also completely free — there's a dedicated section on Product Hunt for community discussions, and anyone can join and post one. Combined with engagement on Twitter, that can work really well.
Could you host the AMA the same day you launch, rather than a week ahead?
If you're a solo founder, hosting the AMA on launch day itself probably isn't ideal, since you'll already have dozens of comments and a lot of attention to manage that day. A better approach is to start the AMA a week ahead, say 'this is me, I'm launching in a week, drop your questions and I'll reply on launch day' — that tends to perform well, and it also means you don't need to be constantly active on Product Hunt in the meantime. It gets people to save the date and show up ready to support you when you actually launch.
Beyond your own audience, are there other places worth promoting a launch — Slack channels, Reddit, that kind of thing?
Again, I wouldn't push your brand too hard anywhere, because it can damage it. There's a quote I really like from Harry Dry at Marketing Examples: your launch day is the day your karma comes full circle. If you drop a link into a community or place where you have little to no karma — a Reddit thread, a random Slack, a Discord — you probably won't get any real engagement from it. But if you're genuinely engaged somewhere, like actively on Twitter or in a community like Developer Marketing, focusing there makes far more sense than posting somewhere you've never really shown up before. When I worked at Specify, an API company, our best launch results came from the communities we were already regularly engaged in — Reddit, where we weren't already active users, gave us basically nothing by comparison.
How do you actually build up that kind of reciprocity before you need it?
I feel that the more you give, the more you receive — it's just reciprocity, a basic psychology principle. If you want people to reciprocate and give back, you have to give first. In our own community, you can tell the people who log in only to post and promote their own stuff, and it just doesn't work as well as genuinely giving to the community first and expecting reciprocity to follow from that.
Are there dev-tool-specific pitfalls when writing your Product Hunt copy?
Product Hunt is a global audience, not just developers, so your tagline and description need to be genuinely easy to understand and digest — clickable, but not bullish or hypey. Plain English, as simple and straightforward as possible, is a good rule for both the tagline and the description.
What's the biggest scheduling mistake you've seen kill a launch before it even starts?
Not anticipating the review process. The Product Hunt team reviews hundreds of submissions every day, and if you submit your product planning to launch the very next day, there's a high chance it won't get featured in time. One of our community members did exactly this — scheduled the launch for the next day, and ended up waiting eight hours to get featured, by which point it was already buried in the day's ranking, killing the momentum before it began. You want to submit well in advance so the team has time to actually review and process it, and get featured right at 9:01am CET when the day resets. Beyond that, prep as much of your launch-day content — tweets, LinkedIn posts — ahead of time too, because launch day is genuinely exciting, with a lot of adrenaline, and you don't want to waste that energy scrambling to write copy at the last minute. You want to be free to actually enjoy it.