Hacker News is where technical buyers go to be skeptical in public. A thread about your product, or a thread where someone mentions it in passing, is a place where people who have no reason to flatter you say exactly what they think. And every so often, between the nitpicks and the "have you considered" replies, someone writes a sentence that would out-convert anything on your homepage: "we've been running this in production for eight months, zero incidents, it just works." Then the thread ages off the front page, the comment sinks under forty others, and by tomorrow it's effectively gone.
That comment is a testimonial — and for a technical audience it may be the most persuasive kind you can get, precisely because it appeared in the one place a developer trusts because nobody there is trying to sell them anything. The problem isn't that these comments are rare. The problem is that Hacker News is built to bury them, and almost no one has a habit for catching them before they scroll into the archive.
Why an HN comment beats a solicited quote for technical buyers
A developer reading testimonials on a vendor's site discounts every one of them on sight. They assume each quote was requested, edited, and approved by marketing — and they're usually right. For a technical buyer, that discount is close to total. A polished quote from "VP of Engineering, Acme Corp" reads as theatre.
A Hacker News comment defeats that discount completely, because the reader knows the context. The person wasn't asked. They were arguing, or answering, or warning someone off a worse option, in a forum where overclaiming gets torn apart in the replies. The vocabulary is unmistakably peer-to-peer — "in production," "zero incidents," "it just works" — the register of an engineer talking to other engineers, not a customer performing for a vendor. That unguarded specificity is exactly what a technical prospect trusts, and it's the same quality that makes a raw Slack message from a customer more convincing than a carefully staged one.
There's a second layer of credibility unique to HN: the comment survived the crowd. If someone claims "zero incidents in eight months" and it were nonsense, a reply would call it out. A praise comment that sits unchallenged in a skeptical thread has been, in effect, peer-reviewed.
Catch the comment before the thread ages off
Hacker News's weakness as a testimonial source is purely structural: threads move fast, there's no notification when your product is mentioned, and once a submission drops off the front page it rarely gets read again. The comment is real; the artifact is fragile.
Build one small monitoring habit. Watch for mentions of your product name and your domain — HN Search (Algolia) lets you query both, and a saved search or a lightweight alert will surface new threads. When a thread appears, read the whole thing, because the best comment is often not the top one; it's a reply three levels deep where an actual user answers a skeptic with lived experience.
When you find a comment that names an outcome — not just "nice tool" but "cut our build times in half," "replaced our homegrown thing we'd maintained for years," "eight months, zero incidents" — capture it immediately. Copy the exact text, grab the permalink (every HN comment has one via its timestamp), and note the username and the thread. Do this before the thread ages, because unlike a Slack DM you can't retrieve it later from a shared history — you're relying on a public archive that's genuinely hard to search after the fact.
If the comment is warm but vague — "been using this for a while, no complaints" — you have a lead, not a quote. The outcome clause is missing. That's harder to chase on HN than in your own community, but not impossible: a polite reply asking a specific follow-up ("curious what you were using before — did this actually replace it, or run alongside?") sometimes draws out the exact before/after detail that turns a shrug into a testimonial.
Ask permission the Hacker News way
Here's the trap: HN users are allergic to marketing, and the wrong permission ask can turn a fan into a critic in the same thread everyone's reading. The ask has to respect the culture — low-key, honest, no salesmanship.
The cleanest move is a direct, unpolished message. HN doesn't have DMs, but most profiles list an email or another contact, and the person often replies in the same thread if you ask openly. Keep it plain: "Author of [product] here — your comment about eight months in production with zero incidents is genuinely one of the best things anyone's said about us. Would you be OK with us quoting it on our site, with your name or handle, however you'd like to be credited? Totally fine if not." No superlatives, no funnel language. HN rewards founders who show up as humans and punishes ones who show up as brands.
Give them a real opt-out and let them choose the attribution. Some technical users will happily give a full name and company; others will only want their HN handle, and a few will want to tweak the wording to be more precise (engineers care about precision — let them). Honor whatever they choose. The person watching that exchange in the thread is a prospect too, and how you handle the ask is itself a signal.
Publish it as proof — and keep the technical voice intact
Once you have the quote and permission, treat it like any high-value testimonial: pull the outcome clause forward, keep the exact wording, and attach whatever attribution the person approved so a prospect can see a real, findable person said it. For a technical audience, a linkable HN handle or a real name at a real company does more verification work than a generic title ever could — the same logic behind linking a testimonial to a source a prospect can check.
The one thing not to do is smooth it out. The credibility of an HN comment lives in its register — the "in production," the "zero incidents," the slightly blunt phrasing an engineer would never edit into marketing cadence. Rewrite it into corporate voice and you strip out the exact quality that made a skeptic believe it. Publish the sentence close to how it was written, credited the way they asked, near the part of your site where technical buyers decide whether you're real.
The comments are already there, in the toughest room on the internet, written by people with no incentive to be kind. The teams that win from Hacker News aren't the ones who get mentioned more — they're the ones who built the small habit of catching the sentence before the thread ages away.