Guide
How to Find Customers from Reddit & Hacker News
A founder-to-founder guide: where high-intent threads hide, how to qualify them, how to reply without spamming, and how to turn conversations into paying users.
Most early-stage SaaS teams do not lose because the product is invisible. They lose because the right people are already talking in public—and nobody from the team shows up with a useful answer at the right time.
This guide is about conversation-led acquisition: using Reddit, Hacker News, and similar communities as a source of intent, not as a billboard.
If you want the full workflow in one place, bookmark this page. When you are ready to scan multiple sources, score threads, and tie replies to signups, Blueprinto is built for that loop—start from the homepage or jump to pricing.
The problem: you have no users, not no channels
Cold lists and generic outreach create noise. You send hundreds of emails; a few reply; almost none match your real ICP.
Public threads are different. Someone writes: "We are switching off X—what should we use?" or "Ask HN: tool for Y?" That person is already in motion. They are comparing options, describing constraints, and asking strangers for recommendations.
Your job is not to "do more outreach." It is to intercept those moments with specific, helpful participation—and to measure which threads actually produce clicks and signups.
Why conversations beat vague "awareness"
- Language match — The poster uses their own words for pain, budget, and stack. You can mirror that language in a reply without sounding like a template.
- Timing — A thread from the last 24–72 hours is usually more actionable than an old blog comment nobody reads.
- Permission — Replying in public to a request for help is different from sliding into an inbox uninvited.
- Compounding — Good answers stay indexed. A sharp HN comment or Reddit reply can send traffic for months.
You are not chasing "brand awareness." You are answering buying questions where they already happen.
Reddit: where threads actually matter
Subreddits that often carry intent
Depending on your product, start with communities where people compare tools and workflows:
- r/SaaS, r/startups, r/Entrepreneur — noisy, but searchable; good for B2B SaaS language.
- Niche subs — e.g. r/devops, r/sysadmin, r/ecommerce, r/datascience—match your buyer.
- Role-based subs — where your ICP hangs out and asks "what do you use for…?"
Search habits that work
Use Reddit search with phrases people actually type:
alternative to [competitor]looking for [your category]recommend [problem you solve]
Sort by New when you want speed; Top → This week when you want proof that a topic has demand.
What to skip
- Pure vent threads with no buying question.
- Megathreads that are 90% self-promotion.
- Places where your product is a stretch fit—you will burn trust.
Hacker News: Ask HN and comments
Ask HN posts are disproportionately valuable: the title is often a direct request for tools or approaches.
Show HN threads can be loud, but comments often contain comparisons ("we switched from A to B because…").
Search the wider web with:
site:news.ycombinator.com Ask HN [your keyword]
Read the top-level question and the first few substantive replies. If your product fits, your reply should add a concrete data point or tradeoff, not a slogan.
HN culture punishes fluff. Lead with honesty: who it is for, who it is not for, and a single clear link when it helps.
Mistakes that waste founder time
- Treating upvotes as success — Upvotes reward agreement or entertainment. Signups and trials are the scoreboard.
- Same reply everywhere — Copy-paste reads like spam and gets removed. Each reply should quote their constraint.
- Link-first comments — Lead with help; link when it removes friction.
- Arguing in bad threads — If the OP is not asking for solutions, do not force a pitch.
- No tracking — If you cannot connect thread → click → signup, you will repeat the wrong subreddits forever.
Step-by-step workflow (weekly)
1. Write ten "intent phrases"
Not features—phrases a buyer would type when they need relief this quarter.
Examples:
- "lightweight CRM for two-person team"
- "alternative to Notion for engineering docs"
- "track intent from forums"
If you cannot list these, you will not recognize them in the feed.
2. Run a 30–45 minute scan
Pick three subreddits and one HN search. Same calendar slot every week so it becomes habit.
For each candidate thread, capture:
- Link
- One quoted line of pain or buying language
- Your gut: reply now / save / skip
3. Reply with a simple pattern
- Acknowledge their constraint in one sentence.
- Share something useful—even partial, even if part of the answer is "here is how I'd do it without software."
- If your product fits, mention it once, tied to their exact sentence.
- Use a tracked link if you have one, so you can prove what happened.
4. Review outcomes for 15 minutes
What got clicks, DMs, or signups? Double down on that thread shape next week.
Turning threads into product usage
Public replies are the start of the funnel, not the end.
- If someone engages, answer fast and ask one clarifying question about their setup.
- Prefer low-friction next steps over "book a demo" unless they are clearly evaluating vendors.
- If nothing happens in 48 hours, move on—do not bump your own comment for vanity.
When volume grows, you need aggregation and scoring so you spend time on threads that look like pipeline, not noise. That is the problem Blueprinto solves: scan Reddit, Hacker News, Dev.to, and Stack Overflow, surface high-intent conversations, and connect outcomes back to the thread.
What to do this week
- Write your ten intent phrases.
- Find five threads total (Reddit + HN) that match.
- Reply helpfully to two.
- Track clicks or replies for seven days.
That is the minimum loop. Everything else—templates, tooling, scaling—is built on top of seeing the same language patterns over and over.
Next steps with Blueprinto
If you want to run this loop without living in ten browser tabs, start from the Blueprinto homepage—describe your product once, let the system surface scored threads, draft in your voice, and prove which replies turn into users. See pricing when you are ready to scale beyond manual search.
Examples of threads worth a reply
Switching language — "We are outgrowing spreadsheets for follow-ups. Not enterprise. Something simple." That is a workflow + segment signal. A good reply names one or two approaches, names tradeoffs, and only then mentions a product if it truly fits.
Ask HN — "Tool for managing API keys across staging and prod?" Technical buyers want integration reality, not adjectives. Reply with how you handle rotation, audit, or failure modes—even if your product is only part of the answer.
Comparison threads — "What do you use instead of X for Y?" These are crowded. Your edge is specificity: "If your constraint is Z, we chose A over B because…" Generic "try us" comments lose to one sentence of lived experience.
Skeptical threads — Sometimes the top comment says "they are all the same." That thread still teaches you objections. Use it to fix your landing copy and FAQ, even if you do not reply.
Objections you will hear (from buyers and moderators)
"This is self-promotion." — If you only dropped a link, they are right. If you explained a tradeoff, named two alternatives, and disclosed affiliation when it matters, you are in better territory. Follow subreddit rules and Reddit's content policy; when in doubt, stay in manual review for every post.
"We tried Reddit; it did not work." — Usually the failure mode is wrong threads (entertainment vs intent) or link-first replies. Fix qualification before you blame the channel.
"HN is hostile." — HN is blunt. Treat that as a filter. A thin pitch gets corrected in public; a specific, honest reply earns respect.
"We need enterprise sales, not forums." — Many enterprise deals still start with a practitioner who read a thread six months ago. Conversations are not a replacement for outbound; they are parallel discovery that compounds.
How this connects to validation
You can think of public threads as cheap demand signals. If nobody ever asks for problems near your category, you might have a positioning or category problem—not a "distribution execution" problem.
That is why validation and acquisition are linked: the same language shows up when people complain, compare, and buy. Blueprinto is oriented toward the acquisition side—finding those threads at scale—but the discipline of reading raw posts still makes your positioning sharper.
Summary checklist
- Ten intent phrases written
- Weekly scan on the calendar (same slot)
- Two thoughtful replies per week minimum at first
- Track thread → click → signup
- Kill subreddits and searches that never produce signal
- Upgrade to tooling when manual search becomes the bottleneck
Related deep dives on our blog: find SaaS customers on Reddit & HN, Reddit leads for SaaS, and first 10 users.