A Show HN post succeeds when it is specific, honest, and technically interesting. The Hacker News community is primarily engineers and technical founders who read dozens of Show HN posts per week and have a highly calibrated sense for which products are genuinely useful versus which are just noise. The posts that reach the front page consistently have three characteristics: they explain exactly what the product does and why the author built it, they acknowledge trade-offs and limitations honestly, and the author is present and willing to discuss technical details in the comments. Posts that fail almost always fail for the same reasons: marketing language, vague value propositions, or an author who disappears after posting.
I have posted to Hacker News multiple times for Zlyqor and related projects. Here is the complete guide.
What HN Readers Respond To
Technical specificity. HN readers are engineers. If your product does something technically interesting, explain it. "We built a task scheduler that uses a modified version of the deadline-monotonic algorithm to prioritize time-sensitive work items" is more interesting to HN than "we built a smart task manager."
Honest trade-offs. The HN community respects founders who acknowledge what their product does not do well. "This works great for teams under 20 people. Above that, the real-time sync architecture starts showing latency issues we are still working on" is the kind of honesty that HN readers respect and will upvote.
Real numbers. Any time you can provide actual performance data, usage numbers, or concrete results, include them. "We reduced our API response time from 800ms to 120ms by switching from N+1 queries to a single aggregation pipeline" is more credible than "we optimized our backend."
The builder's perspective. HN readers like to know why you built the thing. Not the marketing version of "why" (a problem statement designed to make the product sound essential) but the actual reason. "I built this because I was doing manual time tracking in a spreadsheet and kept forgetting to log hours until Friday afternoon" is more compelling than "teams waste 20% of their time on administrative tasks."
Technical depth in the comments. Some of the most successful Show HN posts gain traction not from the post itself but from the author's responses in comments. When someone asks a hard technical question and you give a thorough, honest answer, other readers upvote both the question and the answer, which drives the post higher.
What Kills Posts
Marketing language. Words like "powerful," "intuitive," "seamless," and "game-changing" are processed by HN readers as noise. The moment your post sounds like a press release, readers move on.
Vague value propositions. "A better way to manage your projects" tells a HN reader nothing. What specific problem does it solve? For whom? How does it solve it differently from the 50 other project management tools?
Asking for feedback but not wanting it. HN readers will critique your product, your technical decisions, and your business model. If you post "looking for feedback" but then respond defensively to every critical comment, the post will get downvoted.
Poor timing. HN traffic peaks on weekday mornings US time. Posts submitted at 2 PM PST on a Friday get buried quickly. The best time to post is 7-9 AM PST on Tuesday, Wednesday, or Thursday.
Over-formatting. Long markdown-heavy posts with headers and bullet points are unusual on HN and sometimes read as corporate. HN posts are traditionally plain prose. A well-written three-paragraph post often performs better than an exhaustively structured five-section post.
No author presence. HN rewards discussion. If you post and do not engage with comments in the first few hours, the post will not trend. Plan to be available for 3-4 hours after posting to respond to every comment.
Writing the Title
The Show HN title format is: "Show HN: [What it is] ([optional: one compelling detail])"
Good titles:
- "Show HN: Zlyqor, an open-core team workspace (chat, projects, time tracking, invoicing)"
- "Show HN: A time tracker that generates invoices from your logged hours"
- "Show HN: We replaced Jira, Slack, and Harvest with one tool for our 8-person team"
Bad titles:
- "Show HN: The ultimate project management solution for modern teams"
- "Show HN: We built the best time tracker ever"
- "Show HN: Our new SaaS launches today (check it out!)"
The title should describe exactly what the product is. HN readers will decide in 3 seconds whether to click based on the title.
Writing the Post Body
The post body should be two to four paragraphs. Address these points:
What it is. One sentence that describes the product precisely. Treat this like you are explaining it to a technical friend, not a customer.
Why you built it. The real story. What was the actual pain point? Be specific. "I was spending 2 hours per week reconciling logged time with client invoices" is better than "billing and time tracking are disconnected."
What is technically interesting about it. If there is something notable about the technical implementation, mention it here. This is what separates interesting Show HN posts from product announcements.
What you are looking for. End with a specific ask: "Happy to answer questions about the architecture, the business model, or anything else."
Handling Critical Comments
Critical comments on HN are not attacks. They are the community doing what it does: stress-testing ideas.
When someone says "this is just Jira/Asana/Linear with a time tracker bolted on," do not get defensive. Either explain specifically what is different, or, if the criticism is fair, acknowledge it: "You are right that there is significant overlap with those tools. Where we differ is X, and we are specifically targeting teams that need Y."
When someone says "this will not scale beyond 100 users," either explain why your architecture handles that case or acknowledge: "That is a real limitation for now. We are currently building for small teams and will address that as we grow."
The HN community will respect honest acknowledgment of limitations more than defensive rebuttals of valid criticisms.
Real Examples of Successful Show HN Posts
Supabase (Show HN: We built an open source alternative to Firebase): Technical specificity about what they built, honest about what was not finished, active author presence in comments. Made the front page.
Plausible Analytics (Show HN: Plausible, a privacy-first Google Analytics alternative): Very specific value proposition, acknowledged what they did not do (no funnels at launch), author answered every technical question. Drove thousands of signups.
Excalidraw (Show HN: Excalidraw, a virtual hand-drawn whiteboard): Technical explanation of the sketchy rendering approach, immediate demo link, heavy author engagement. Still the most starred Show HN tool I know of.
The pattern is consistent: specific, honest, author-present.
What to Expect
A successful Show HN that reaches the front page will typically drive 200-1,000 unique visitors over 24-48 hours, depending on how long it holds its position. For a developer tool with a strong free tier, conversion to signup from HN traffic is typically 5-15%. The HN audience is technically sophisticated and will find real problems with your product. Consider that a feature, not a bug.
Keep Reading
- How to Market a Developer Tool — The complete playbook beyond just HN
- Product Hunt Launch Guide for Developer Tools — The other major launch platform
- Marketing a Developer SaaS on Reddit Without Getting Banned — Reddit strategy for developer tools
Pristren builds AI-powered software for teams. Zlyqor is our all-in-one workspace — chat, projects, time tracking, AI meeting summaries, and invoicing — in one tool. Try it free.
