Finding your first customers is the hardest part of building a startup. You do not have social proof yet. You do not have a marketing machine. And most people do not know your product exists.
The good news: your first 100 customers are already talking online - on Reddit, Hacker News, Stack Overflow, GitHub, YouTube, launch sites, and niche forums. This guide covers where to look, how to engage without getting banned, and two patterns that worked for early-stage founders (anonymized).
Conversation demand before SEO content
Your first 100 customers rarely come from a blog calendar built on Google rankings. They come from threads where people already ask for help.
| Stage | Lead with | Add when ready |
|---|---|---|
| Pre-PMF | Reddit, HN, SO searches; ethical replies | One clear landing page |
| Early traction | Weekly conversation sprints + outbound | SEO on page-two topics you almost rank for |
| Scaling | Monitoring + competitor threads | Full SEO topical program |
SEO tools help when you have Search Console footholds. Community research helps upstream - language, intent, and where to show up this week. Full guide: conversation demand vs SEO content.
Further reading: GummySearch alternatives and Reddit research tools · Reddit playbook · Graduate from F5Bot alerts
The 3-Community Test (before you scale channels)
Most founders spread too thin. They open tabs for Reddit, HN, LinkedIn, Twitter, Discord, and three Slack groups - then post nowhere consistently.
Use this test instead:
- Pick three communities where your buyer already asks questions (not where you wish they hung out).
- Search one painful phrase in each - "alternatives to X", "how do you solve Y", "best tool for Z".
- Log ten real quotes (copy exact language, not your positioning doc).
- Reply helpfully on two threads before you mention your product.
- Review after two weeks - which community gave replies, DMs, or demo requests?
If a community fails the test twice, drop it. Double down on the one that returned signal.
| Signal | Action |
|---|---|
| Threads with buying intent | Prioritize outreach and landing page copy from those phrases |
| Lots of pain, no replies when you help | Wrong subreddit or wrong tone - adjust before you promote |
| No threads found | Category may be too early or too enterprise - try GitHub issues or Stack Overflow |
Mini case study: scheduling tool (Reddit + Indie Hackers)
Context: Solo founder building a lightweight scheduling tool for consultants. No ad budget. ICP: independent consultants drowning in back-and-forth email.
What they did:
- Searched Reddit for "client booking nightmare" and "Calendly alternative" in r/consulting and r/freelance.
- Logged phrases: "clients ignore my link", "need something simpler than Calendly", "don't want another subscription."
- Posted one builder diary thread on Indie Hackers with screenshots - no link drop in comments on Reddit for two weeks.
- Replied on three Reddit threads with a checklist for reducing no-shows (no product link in first reply).
Result (6 weeks): 41 beta signups, 9 paying users, $380 MRR. Zero ad spend. Primary channel: Reddit comments → DM → trial.
Lesson: One niche phrase cluster beat a broad "productivity tools" search. They stopped posting on Twitter after week 2 because the test showed no reply rate.
Mini case study: API monitoring (Hacker News + Stack Overflow)
Context: Two-person team building uptime checks for internal APIs. ICP: backend engineers at 20–200 person companies.
What they did:
- Read Hacker News Guidelines and lurked Show HN posts in their category for a month.
- Searched Stack Overflow for questions about "health check best practices" and "monitor internal microservices."
- Drafted a Show HN post focused on a specific failure mode (silent partial outages) with a reproducible demo - not a feature list.
- Left detailed answers on two SO threads linking to their public docs (not the homepage).
Result (10 days post–Show HN): Front page for ~4 hours, 120 trial signups, 4 design-partner calls. SO answers drove steady trickle traffic for months.
Lesson: HN rewards a sharp story and working demo. Stack Overflow rewards answers that stand alone without a sales pitch.
Where your first users actually hang out
| Surface | Best for | Watch out for |
|---|---|---|
| Honest pain, niche B2B and prosumer | Subreddit rules, self-promotion bans - see Reddit content policy | |
| Hacker News | Tech founders, dev tools | Show HN timing, comment quality bar |
| Stack Overflow | Developer pains, how-to questions | No marketing answers - solve the question |
| GitHub | Builders, OSS-adjacent tools | Issues and discussions, not spammy README links |
| YouTube | Tutorial comments, "how I built X" | Signal vs noise in comments |
| Product Hunt | Launch spike, early adopter feedback | Distribution event, not daily research |
| Indie Hackers / niche forums | Builder transparency, MRR context | Cross-post disclosure |
For a deeper Reddit workflow: Reddit customer discovery playbook. For HN: Hacker News playbook for founders.
Outreach that does not get you banned
Help first, sell later.
- Read subreddit rules and Reddit's content policy before posting.
- Disclose affiliation when you mention your product ("I'm building X").
- Prefer comments over new posts when you are unknown in a community.
- Move to DM or email only after someone asks for more detail.
Soft outreach template:
"Hey [name], I saw you mentioned [problem] on [platform]. I'm building something that might help - early stage, but happy to share if useful."
Keep it short. No marketing deck in the first message.
Landing page and email basics
Early landing pages need clarity, not polish:
- One bold problem statement
- One simple solution
- Who it is for
- 3–5 benefits
- Social proof (even beta quotes)
- Clear CTA (Join waitlist / Start free)
For email: ConvertKit, Brevo, or Mailchimp all work. Treat early users as co-builders - progress updates beat promotional blasts.
Where famous startups started (and what to copy)
| Company | First customers | Pattern |
|---|---|---|
| Airbnb | Craigslist hosts in SF | Went where supply already listed |
| Dropbox | HN demo video | One sharp story + working demo |
| Yelp | Friends needing recommendations | Manual, high-touch first cohort |
The pattern is the same today: find people already expressing the problem, meet them on their terms, iterate from feedback.
A weekly workflow (tool-agnostic)
Monday (30 min): Search three phrases across your top two communities. Log new threads in a spreadsheet.
Tuesday–Wednesday: Reply on two threads with genuine help. No product link unless asked.
Thursday: Update landing page copy using phrases from the week's logs.
Friday: Follow up on open DMs. Note which community produced signal.
When manual search becomes repetitive, use a multi-platform search tool (Needle, alerts, or saved Reddit searches) so you run the same queries across Reddit, HN, Stack Overflow, and GitHub in one pass. Needle's Search docs describe how intent-ranked results work; free Trending Problems shows category-wide momentum without an account.
Tool stack for the first 100 (keep it small)
| Job | Examples |
|---|---|
| Community research | Manual search, F5Bot-style alerts, or Needle Search |
| Landing / waitlist | Notion, Carrd, Framer |
| ConvertKit, Brevo | |
| Payments | Stripe, Lemon Squeezy |
| Notes / CRM | Spreadsheet or Notion |
You can reach your first users with a spreadsheet and disciplined tab-hopping. Tools earn their place when you repeat the same research every week.
Final thoughts
If you are asking how to find first customers, where early adopters hide, or how to get first users without ads - they are already describing their problems in public threads. Your job is to listen, help, and show up consistently in the communities that pass the 3-Community Test.
Next steps: Browse free Trending Problems · Reddit playbook · Pre-PMF user discovery