Contents
How to launch a dev tool on Hacker News
If you are marketing a dev tool, especially an open-source infra dev tool, then sharing your product on Hacker News is a must.Â
Now the question is how to do that exactly, as marketing to the HN audience is just really hard.
Obviously, the best thing you can do for your marketing is to actually have a good product to market. But assuming you do, how do you pitch it on HN so that people see it too?
In this post, I am going deep into that:
- I am looking at the HN Launch guidelines from HN admins,Â
- I am going over the best HN launch post ever
- IÂ share a few more tips coming from dev marketing community
- I share top/bottom HN launch and HN show posts that you can compare against those guidelines. Â
And through all that research there seems to be a clear pattern that is pretty much explained openly by Hacker News admins.Â
Rules for launching your product on HN directly from Hacker News admins
So HN Admins actually share the guidelines for Launching on HN directly in this doc:
and
They explain exactly how to write it in there so make sure to read it.Â
But here is a TLDR.
Style:
- “Write in your own voice, not a corporate one.“
- “Talk to HN as fellow builders and engineers. Imagine you're having a drink with a friend you used to work with.”
- “Don't use superlatives (fastest, biggest, first, best). Modest language is stronger.”
- “Don't sell to this audience. If you try, they will close the tab. Instead, interest them, then let them sell themselves.”
Product/Offer:
- Give people an easy way to try it out. For free. Remove all barriers possible. The second best thing is a demo or video.
- “Make your pricing transparent.” and “Say how you make money or plan to.”
- Your CTA should invite people to share their suggestions/experiences/feedback.
Format of the announcement:
- introduce yourselves
- say in one clear sentence what your company does
- explain the problem: how is it hard? why does it matter?
- tell your backstory of how you came to work on this
- explain your solution, giving technical details
- explain what's different about your solution, giving technical details
- invite the community to share feedback
How to comment/answer:
- When you launch be ready to answer comments. And quickly.Â
- Make sure your friends/employees/cofounders DON’T post booster comments.
- Go deep into details. Remember HN community is genuinely curious.Â
- “Answer objections by first finding something to agree with, even if it's just the positive intention behind the comment.”
- “When criticized, act like the critics are doing you a favor. Who knows, maybe they are, and it will win you favor either way.” You won’t convince the critic but you can convince the audience reading it.Â
Let’s look at the highest-upvoted devtool announcement ever through this lens.Â
The best dev tool HN launch ever
I want to go over these guidelines looking at the most upvoted dev tool HN launch of all time: Fly.io.Â
 Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
I will go over all the points from Style, Product/Offer, Format, and Comments subpoints and see how they approached it. Spoiler alert. They did tick all the boxes.Â
Style:
- “Write in your own voice, not a corporate one.“
- “Talk to HN as fellow builders and engineers. Imagine you're having a drink with a friend you used to work with.”
- “Don't use superlatives (fastest, biggest, first, best). Modest language is stronger.”
             Instead of saying “fastest deployment” they just said “deploy servers close to your users” or
- “Don't sell to this audience. If you try, they will close the tab. Instead, interest them, then let them sell themselves.”
Product/offer:
- Give people an easy way to try it out. For free. Remove all barriers possible. The second best thing is a demo or video.
- “Make your pricing transparent.” and “Say how you make money or plan to.”
- Your CTA should invite people to share their suggestions/experiences/feedback.
Format of the announcement:
- introduce yourselves
- say in one clear sentence what your company does
- explain the problem: how is it hard? why does it matter?
- tell your backstory of how you came to work on this
- explain your solution, giving technical details
- explain what's different about your solution, giving technical details
- invite the community to share feedback
How to comment/answer:
- When you launch be ready to answer comments. And quickly.Â
              I saw “mrkurt” answer 53 comments in this thread. Not sure how quickly that was but I presume pretty quickly.Â
- Make sure your friends/employees/cofounders DON’T post booster comments.
             No way to check it but I didn’t see anything fishy.Â
- Go deep into details. Remember HN community is genuinely curious.Â
- “Answer objections by first finding something to agree with, even if it's just the positive intention behind the comment.”
- “When criticized, act like the critics are doing you a favor. Who knows, maybe they are, and it will win you favor either way.” You won’t convince the critic but you can convince the audience reading it.Â
So fly.io HN Launch pretty much ticks all of the boxes. And it didn’t feel unnatural or weird to tick them either. That launch is just descriptive, interesting, and engaging.  Â
More tips for Launching dev tools on HN
In addition to all that there are a few more things you can do to increase your chances of success. Maybe they are not directly coming from the HNÂ Admin guidelines but seen myself and heard them from people in the community.
HNÂ crowd really likes and overindexes on open-source, privacy-first products. So if you actually are an "open-source alternative to X", say it right in the title.
Make the title crystal clear and explicit. It should be obvious right away what you've built. And if there is something that pretty much all successful HNÂ posts have in common, is that it is obvious where you'll go when you click on the link. Make it obvious.
Link out to the GitHub repo. This makes your "offer"Â more HN dev audience-centric by design. The repo hints at it being easy to run yourself, at it being an actual working product/library/framework, and at it being a dev tool. No other website domain brings those expectations.
Conclusions
Ok, so summing up. If you are preparing for the HN Launch or HN Show just make sure to:
- follow the HN Admin guidelines
- look over some more examples (and anti examples) of implementing this below
- if you can positioning your tool as an open-source or privacy-first
- and get your servers ready for more traffic/signups than you hoped for ;)
If you need help with this, reach out, I can help you craft this.Â
APPENDIX top/bottom HN launch and HN show posts
Now, to get a better feel I looked at the last 4 years of HN dev tool Launch HN and Show HN posts and copy-pasted top/bottom Launch HN and top/bottom Show HN in here.Â
You can compare them against the guidelines I mentioned but generally, they seem to hold water. I am planning on actually scoring all of them against these guidelines and looking into this data but this is a TODO.Â
Top Launch HN devtool examples
Launch HN: Fly.io (YC W20) – Deploy app servers close to your users
Launch HN: Fig (YC S20) – Autocomplete for the Terminal
Launch HN: Pynecone (YC W23) – Web Apps in Pure Python
Launch HN: Lago (YC S21) – Open-source usage-based billing
Launch HN: Resend (YC W23) – Email API for developers using React
Launch HN: Twenty.com (YC S23) – Open-source CRM
Launch HN: Neptyne (YC W23) – A programmable spreadsheet that runs Python
Launch HN: Chatwoot (YC W21) – Open-Source Alternative to Intercom, Zendesk
Launch HN: Vocode (YC W23) – Library for voice conversation with LLMs
Launch HN: QuestDB (YC S20) – Fast open source time series database
Top Show HN dev tool examples
Show HN: Redbean – Single-file distributable web server
Show HN: GPT-4-powered web searches for developers
Show HN: I'm building an open-source Amazon
Show HN: Imba – I have spent 7 years creating a programming language for the web
Show HN: I wrote my own RTS game engine in C
Show HN: Heynote – A dedicated scratchpad for developers
Show HN: htmz – a low power tool for HTML
Show HN: Warp, a Rust-based terminal
Show HN: OpenAPI DevTools – Chrome extension that generates an API spec
Show HN: Restfox – Open source lightweight alternative to Postman
Bottom Launch HN dev tool examples
Launch HN: Acho (YC S20) – No code data warehouse for big data
Launch HN: Refinery (YC S20) – Edit your React app in-browser and generate code
Launch HN: Corgea (YC S23) – Auto fix vulnerable code
Launch HN: Feroot (YC W21) – security scanner for front-end JavaScript code
Launch HN: Method Financial (YC S19) – API to embed debt repayment into your app
Launch HN: Dioptra (YC W22) – Improve ML models by improving their training data
Launch HN: GradientJ (YC W23) – Build NLP Applications Faster with LLMs
Launch HN: Signadot (YC W20) – Lightweight Test Environments for Microservices
Launch HN: DevCycle (YC W14) – a feature flag platform built for developers
Launch HN: DeploySentinel (YC S22) – End-to-end tests that don't flake
Bottom Show HN dev tool examples
Show HN: The world's most comprehensive Python Accounting Library
Show HN: JavaScript tiny tool; to acquire CSS selector
Show HN: Revolution in CSS With
Show HN: Commitm, a CLI that generates your commit messages for you
Show HN: PGCacheWatch – Elevate PostgreSQL Performance with Smart Caching
Show HN: Hivekit – realtime geospatial API Platform
Show HN: I built an internal linking visualization tool
Show HN: I Made a Laravel Boilerplate to Speed Up Development Process
Show HN: UnWebhook – A tool for working with webhooks in teams and staging
Show HN: I Decided to Build Multiwoven, an Open-Source Reverse ETL
Want more insights? Got more questions?
Subscribe to my newsletter ->Â get 3 dev marketing insights and 1 thing about pears every week.
Join our marketingto.dev slack -> talk to me and 1500+ developer marketing practitioners.
Work with me ->Â I do dev marketing advising, teardowns, and on-demand workshops.
Reach out on Linkedin-> IÂ answer every question and share insights daily.