Building in Public: Finding Your First 5 Customers Through Community Research

Your first 5 customers won't come from a landing page and a prayer. They come from finding people who are already complaining about a problem you can solve, and showing up in that conversation before you've written a line of code. This is what building in public through community research actually looks like: not tweeting screenshots into the void, but reading threads like a detective until you can name the exact person who needs your product.

Most founders skip this step. They have an idea, they build it, and then they go looking for customers. Flip the order. Find the customers first, in the wild, complaining on Reddit or asking questions on Hacker News, and let their language tell you what to build.

Why Community Research Beats Cold Outreach

Cold outreach asks strangers to care about your idea. Community research finds people who already care about their own problem, then meets them there. The difference shows up in reply rates: a cold DM pitching a SaaS tool gets ignored; a comment that says "I built something for exactly this, want to try it?" on a thread where someone just spent three paragraphs venting gets answered.

Look at the kind of demand signal that actually predicts a sale. In recent scans of developer communities, one thread cluster kept surfacing the same complaint: indie developers wanted to run local LLMs like DeepSeek, Qwen, or Gemma without dealing with cloud API costs and key management, but Ollama's raw setup was too fiddly for daily use. That's not a vague market trend, that's a person, in a specific subreddit, describing their exact workflow friction. A founder who reads that thread and replies with "I'm building a lightweight wrapper that gives you one clean API endpoint over your local Ollama models, want early access?" has a shot at a real signup. A founder who cold-emails "AI developers" from a scraped list does not.

Where to Look, and What to Look For

Each platform surfaces a different kind of signal, and you need to read them differently:

• **Reddit** is where people vent in detail. Subreddits like r/LocalLLaMA, r/selfhosted, r/ObsidianMD, r/PKMS, and r/SaaS are full of threads where someone describes a workflow they've cobbled together out of three tools and a spreadsheet. That cobbled-together workaround is your product spec. One recent example: knowledge workers in note-taking communities repeatedly describing hours lost to manual weekly reviews of notes scattered across paper journals, PDFs, and digital apps, wanting something that just ingests everything and produces a synthesized summary. That's a product idea sitting in plain sight, with the target user and pain level already spelled out by the people who'll pay for it.
• **Hacker News** surfaces technical pain from a more senior, higher-intent crowd. "Show HN" comment threads are gold: people don't just praise or dismiss a launch, they list what's missing, which is a free feature roadmap from your future customers.
• **Product Hunt** comments tell you what almost worked. A founder launching a clickable, embeddable product demo builder (skip the signup wall, add hotspot mapping and drop-off tracking) is answering a complaint that shows up constantly in PH and marketing subreddit threads: founders who lose visitors because their landing page forces a signup before anyone can see the product.
• **YouTube** comment sections under tutorial videos are underused. If a video walks through a manual process (deduplicating support tickets across Discord, GitHub, and email, for instance) and the comments are full of "is there a tool that does this automatically," you've found demand with almost no competition, because most founders never scroll that far.

Turning a Thread Into a Customer

Here's the actual mechanic, step by step, using a real example pattern: developers needing structured, agent-ready JSON extracted from arbitrary URLs so their AI agents stop burning tokens on raw HTML.

1. Find the thread where someone describes the pain in their own words ("I'm paying for a scraping API but half the response is garbage I have to parse myself").
2. Reply with a question, not a pitch: "What fields do you actually need extracted? Just title/price/description, or deeper?" This does two things: it signals you're building for them specifically, and it gives you free product spec.
3. Once you have a rough answer, build the smallest version that solves their exact case, not the general case.
4. Go back to that same thread and say "I built this based on what you described, here's a link, tell me what's broken." You're not launching to a cold audience, you're closing a loop with someone who already told you what they needed.
5. Repeat across 5-10 threads. You don't need viral reach, you need five people who each had a specific, nameable problem.

This works because pain level and specificity matter more than volume. A thread with one person describing high-pain, specific friction (like the CLI/desktop markdown editor with an agent co-editing layer that developers wanted as their default $EDITOR for prompt composition) is worth more than a thousand vague likes on a generic "AI tools" post.

The Build-in-Public Loop

Building in public isn't posting progress screenshots for engagement. It's a loop: research the pain, build the smallest fix, post about it back where you found the pain, repeat. Each cycle should end with you replying inside the same communities where you started, not just broadcasting on your own Twitter or LinkedIn. The person in r/selfhosted who complained about telemetry leaking from their local tools is a better first customer than 500 impressions from a generic launch post, because they already told you, in writing, exactly what would make them say yes.

Do this five times, with five different specific people, in five different threads, and you'll have your first 5 customers, plus a much clearer idea of what to build next, because they'll keep telling you.

If manually scanning Reddit, Hacker News, Product Hunt, and YouTube every day for these signals sounds like a full-time job on top of building your product, that's the exact gap 1U4X was built to close. It scans those communities daily and surfaces the specific, high-pain opportunities so you can spend your time replying to real people instead of searching for them.