Reverse-engineering Kilo's recent Product Hunt launch

Last week, launched for the fourth time on Product Hunt, introducing a new VS Code extension. The product ranked #1 Product of the Day and #1 Product of the Week.

I had the opportunity to work on . Here's a breakdown of what we did and how to apply it to your launch.

TL,DR

  • Keep the tagline relatable to your audience

  • Show the product in your image gallery

  • Engage with the community thoughtfully

Reverse-engineering Kilo's recent Product Hunt launch

  1. Straightforward tagline. The 60-character tagline might be the most important part of a launch. It's the first thing you see on the front page. Here, we highlighted the features, not the benefits.

  2. Minimalist visual assets. The image gallery is the first impression of your product. It sets expectations. We highlighted 3 images. No stock images, no marketing fluff. Just product screenshots. Show the product.

  3. Feedback first. Like the tagline and the visual assets, we kept the first comments simple. No looooooong background stories - the objective is to start the conversation. We upvoted and replied to every comment, curious about what the community thinks of the release.

Keeping the momentum

"Momentum is the new metric." - Source:

There's one more thing we experimented with for this launch. Post-launch, the team started running a display ad campaign. The objective is to keep the momentum going.

Stay curious!

How to apply this to your launch

  • Keep the tagline relatable to your audience

  • Show the product in your image gallery

  • Engage with the community thoughtfully

Wrapping up

That's it! hope you find this thread helpful.

What are your key learnings from your previous launches? What worked, what didn't work from your perspective? happy to swap notes.

launched last week on .

550 views

Add a comment

Replies

Best

Curious whether s.s alone performed better than polished graphics in terms of click-throughs.

FWIW when first launched on Product Hunt last year, they got 337 points and ranked #5 Product of the Day. Last week, They got 669 points and ranked #1 Product of the Day ().

I wonder if Product Hunt users are getting more resistant to "marketing-looking" launch assets lately.

"I wonder if Product Hunt users are getting more resistant to "marketing-looking" launch assets lately."

In the context of a developer-first product, yes. No marketing fluff. Show the product.

Interesting that you focused on features over benefits. Was that based on previous launch data?

Interesting that you focused on features over benefits. Was that based on previous launch data?

Great question. is for developers first, and technical people are resistant to anything that looks, sounds, or smells like marketing. Keep it simple and straightforward.

Honestly, I still think distribution matters more than launch presentation in most cases.

definitely a combination of both a good product, how you frame it, and how you leverage networks.

in another thread, we detailed the playbook we used and TL,DR: we keep it simple, with a focus on existing channels.

[1]: (2025)

Preparing a launch soon and this confirms something I’ve been noticing: clear positioning beats polished marketing.

For technical products, real screenshots, simple words, and honest community engagement probably create more trust than a “perfect” launch page.

"For technical products, real screenshots, simple words, and honest community engagement probably create more trust than a “perfect” launch page."

 exactly, keep it simple and straightforward. "Talk is cheap. Show me the product."

 Do you think users are starting to trust unpolished graphics more because they feel more authentic?

“Show the product” is honestly underrated advice. a lot of launches try too hard to look like ads instead of making people instantly understand what the product actually does. Launching CogniFocus on June 1 actually 😭 first indie project too, so I’m basically learning all of this in public right now. let’s see where it goes

 exactly - keep it simple and straight to the point.

In your context, and for inspiration, you might also enjoy reading this thread:
hope it helps! enjoy your launch, rooting for you

 appreciate that 🙏 trying really hard to keep the launch focused on “what the app actually does” instead of fake productivity marketing lol and thanks for the thread recommendation, I'll definitely go through it

 enjoy! rooting for you

Appreciate it🙏

Interesting evolution—this pattern is emerging across many AI-layered dev tools. The move toward agentic workflows is becoming a clear theme. Curious which parts of the dev cycle are actually sticking in real projects vs still experimental or too risky.

Great breakdown. I think a lot of founders underestimate how important community engagement is before launch.

People can usually feel the difference between someone building relationships vs someone only showing up to promote.

Really insightful thread 👏

"People can usually feel the difference between someone building relationships vs someone only showing up to promote."

 You're spot on. This was the 4th launch from here in 12 months. They take seriously.

Thanks for sharing, definitely useful information - we'll keep this in mind for the next launch :)

thank you - looking forward to your launch! keep it simple, enjoy

Are the graphics as crucial as the product images, or can simple product images suffice as well?

"Are the graphics as crucial as the product images, or can simple product images suffice as well?"

 In this context of a developer-first product, just product screenshots. Show the product.

 That makes sense for dev tools. For a product targeting non-technical small business owners, would you lean more toward polished mockups showing the output, or still keep it raw?

 good q - I really focus on developer tools tho. what would make the most sense for your target audience from your perspective? keep it simple

 For my audience — small business owners who've never built a page before — I think polished mockups showing the actual output make more sense. They need to trust the result before they trust the tool. Thanks for the framework, genuinely helpful.

12
Next
Last