How to find leads on Hacker News without getting flagged

By MentionLeads · July 14, 2026 · 8 min read

In short: To find leads on Hacker News without getting flagged, monitor Ask HN posts, Show HN discussions, story comments, and hiring threads for people describing a concrete problem your product solves. Reply with a useful diagnosis or actionable solution first, disclose your connection if you mention your product, and avoid repetitive links, generic praise, unsolicited pitches, or coordinated voting.

How to find leads on Hacker News starts with treating the site as a technical community, not a distribution channel. Hacker News readers quickly inspect your history, challenge unsupported claims, and downvote comments that sound like sales scripts. The opportunity is real, but it comes from finding a small number of relevant conversations and contributing enough expertise to earn the right to mention what you sell.

Where do high-intent leads appear on Hacker News?

The best leads rarely announce themselves by asking for a vendor recommendation. More often, they describe a broken workflow, ask how others solved a technical constraint, complain about an incumbent, or reveal that they are building an internal workaround. Those signals appear in four main places.

• Ask HN: Look for questions about tools, infrastructure decisions, operational pain, vendor alternatives, and how other teams handle a process. “How do you manage X?” is usually more valuable than a broad discussion about an industry.
• Show HN: Read the comments on products adjacent to yours. Users often explain missing features, deployment concerns, pricing objections, or why an existing approach does not fit their stack.
• Story comments: A news item may trigger detailed discussions from practitioners dealing with the underlying problem. The article is often less useful than a deeply nested comment describing an active project or constraint.
• Recurring threads: Who Is Hiring, Who Wants to Be Hired, freelancer threads, and launch discussions can reveal growing teams, new technical priorities, and founders looking for help. Treat these as context, not permission to mass-contact participants.

A strong lead has a problem, context, and some evidence of urgency. “Observability is hard” is weak. “We are replacing our current monitoring setup because usage-based pricing became unpredictable” is strong because it identifies the category, trigger, and constraint.

How should you search Hacker News for potential buyers?

Start with the language customers use when they are experiencing the problem. Product-category keywords are useful, but pain phrases usually uncover better conversations. Search for terms such as “alternative,” “migrating from,” “self-hosted,” “too expensive,” “how do you,” “recommend,” “struggling with,” and “built our own,” combined with the systems or workflows your product touches.

Use Hacker News search through Algolia’s HN Search interface to inspect stories and comments by keyword, date, popularity, or author. Also browse the newest, Ask, and Show pages because high-intent posts can be valuable before they accumulate points. A low-scoring question from the right buyer can matter more than a front-page discussion dominated by general opinions.

Create separate searches for three layers of language:

• Category terms: What the market calls the product, such as feature flags, database monitoring, or API testing.
• Problem terms: What users say when the current process fails, such as timeout, manual review, false positives, or surprise bill.
• Trigger terms: Events that create buying urgency, such as migration, compliance review, rapid hiring, an outage, or an incumbent changing its pricing.

Review results manually before engaging. Keyword matches can be misleading: someone explaining a solved problem, researching a hobby project, or criticizing the entire category is not necessarily a lead. For a broader framework, use the intent hierarchy in this social selling guide.

Which Hacker News signals show genuine buying intent?

Buying intent on Hacker News is usually visible in specificity, not enthusiasm. Technical details suggest that the person is close to the problem. Constraints suggest they have evaluated options. A deadline, migration, outage, or growing team suggests the problem has become expensive enough to address.

Prioritize conversations containing several of these signals:

• The author names the current tool, internal system, or manual workaround.
• They explain why the existing option fails on cost, control, performance, privacy, or integration.
• They ask for alternatives, implementation advice, or first-hand experience.
• They mention team size, production scale, a deadline, or an active migration.
• They return to answer clarifying questions, indicating that the request is genuine.

Deprioritize abstract debates, old threads with no continuing activity, students asking for project ideas, and comments where your product only fits after several assumptions. A useful qualification test is: could you write a relevant reply without mentioning your company? If not, the match is probably too weak.

How do you reply without sounding promotional?

Write the answer you would have wanted before building your product. Address the technical question directly, state the tradeoffs, and give the reader something they can use without clicking anywhere. Hacker News tends to reward compressed expertise: concrete enough to verify, concise enough to read, and honest about where the recommendation breaks down.

A reliable reply structure is:

• Confirm the specific constraint rather than praising the post.
• Explain the likely cause or decision framework.
• Offer one or two practical steps, including a non-commercial option when appropriate.
• Mention your product only if it is a direct fit.
• Disclose your affiliation in the same sentence.

For example: “If unpredictable ingestion costs are the issue, I would first separate retention from query volume and model both against your last month of traffic. You can also reduce cost with sampling or shorter hot retention. I work on a tool in this category; it may fit if you need fixed-price self-hosting, but it will not suit teams that want a fully managed setup.”

That reply works because the useful part survives if the product sentence is removed. It also names a limitation, which gives technically sophisticated readers a reason to trust the recommendation. This is the same value-first principle used in organic lead generation without ads, but Hacker News demands more technical precision than most networks.

What behavior is most likely to get flagged or downvoted?

On Hacker News, downvotes, flags, automated controls, and moderator action are not identical. You may not know exactly why a submission lost visibility, so the practical goal is to avoid behavior that resembles promotion or manipulation.

Common mistakes include repeatedly linking the same domain, posting generic comments to manufacture account history, reviving old threads solely to pitch, and copying one reply template across unrelated discussions. Asking employees, friends, or customers to upvote a submission is especially risky and conflicts with the site’s norms. Using multiple accounts to create agreement is worse.

Do not hide your affiliation. Readers often discover it through your profile, previous comments, or domain history, and concealed self-interest damages credibility more than a straightforward disclosure. “I built this” is acceptable context when followed by relevant evidence; pretending to be an independent customer is not.

Show HN also has a specific expectation: people should be able to try or meaningfully inspect what you built, and you should remain available to answer questions. A Show HN submission that is merely a polished landing page, waitlist, or lead-capture form is likely to frustrate readers. Read the official Hacker News Guidelines and Show HN guidance before submitting because community expectations matter more than growth tactics.

Should you contact a Hacker News user privately?

Private outreach is appropriate only when the person clearly invites it, publishes a contact method for relevant conversations, or asks for help that cannot reasonably be handled in the thread. An HN comment is not automatic consent to enter someone into a cold-email sequence.

If private contact is justified, reference the exact problem, include the useful idea you would have shared publicly, disclose your role, and make the message easy to ignore. Do not use scraped personal details to create false familiarity. One precise message is enough; repeated follow-ups turn a potentially helpful interaction into spam.

Often the better move is to answer publicly. A strong public response helps the original poster, gives other technical readers a chance to challenge your reasoning, and becomes durable proof of expertise. If the author then asks for implementation details or a demo, the conversation can move naturally.

How can you build a repeatable Hacker News lead workflow?

Use a small, auditable process rather than automating publication. Maintain searches for category, problem, competitor, and trigger terms. Review new matches, score them for problem specificity and urgency, then draft only the replies where you can contribute first-hand knowledge.

Track the thread, author, intent signal, proposed contribution, affiliation disclosure, and outcome. Outcomes should include useful conversations and product feedback—not only demos booked. Hacker News is a relatively small community, so reputation compounds in both directions.

Automation is safest for discovery, deduplication, and drafting. Keep a human approval step before every comment because context determines whether a product mention is helpful or intrusive. If you are comparing monitoring options, see this overview of AI lead generation tools.

Frequently asked questions

Can I link to my product in a Hacker News comment?

Yes, when the product directly answers the question and the surrounding comment provides standalone value. Disclose that you are the founder, employee, or creator, and avoid linking the same domain repeatedly across marginally related threads. If the answer works without a link, consider mentioning the product name only.

Is Show HN a good way to generate leads?

Show HN can generate qualified conversations when the product is usable, technically interesting, and the maker actively answers questions. It is a poor fit for collecting emails from a teaser page or presenting a conventional advertisement. Treat feedback and technical objections as the primary output; leads are a possible consequence.

How quickly should I reply to a potential lead?

Reply while the discussion is active, but do not sacrifice relevance for speed. A thoughtful answer several hours later is usually better than an immediate generic pitch. For older threads, contact the author only when you have genuinely new information and a reasonable channel for doing so.

Start here

• Build five searches combining your category with phrases such as “alternative,” “migrating,” “too expensive,” and “built our own.”
• Review ten matching threads and label each as research, weak intent, or active problem before writing any reply.
• Draft one public response that gives a concrete solution, names a tradeoff, and discloses your affiliation if your product appears.

If you want to monitor Hacker News for intent signals and approve value-first replies before anything is posted, start with MentionLeads.