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

Your first 10 customers aren't hiding. They're posting in r/jobs right now complaining that Simplify wants $40/month to auto-fill LinkedIn applications. They're in r/artificial asking why every "free" AI video generator quietly paywalls 1080p after your third render. Finding your first 10 customers through community research isn't a marketing tactic you bolt on after building — it's the thing that tells you what to build in the first place, and it's how you get the people who validated the idea to become your first users.

Most founders get this backwards. They build first, then go looking for an audience. Building in public works better in the other order: find the complaint, engage with the people making it, build the smallest thing that fixes it, and bring it back to the exact thread where the problem started.

Start where the complaints already are

You don't need customer interviews to know what people want. You need to read what they're already typing into a search box. Every day, threads on Reddit, Hacker News, Product Hunt, and YouTube comments surface the same handful of patterns: someone is paying for a tool they resent, or doing something manually that should be automated, or can't find a free version of something that used to be free.

A few real examples from recent scans:

• **r/jobs and r/cscareerquestions**: job seekers venting about proprietary LinkedIn auto-apply tools like Simplify, wanting an open-source script that scrapes listings and submits resumes without a subscription. That's not a vague "job search is hard" complaint — it's a specific, buildable feature request with a named competitor to undercut.
• **r/artificial and r/StableDiffusion**: video creators frustrated that free AI video tools (Veo, Kling, Gemini's video features) keep moving the goalposts on what resolution is actually free. The ask isn't "build a new video model" — it's "build a directory that tells me which free tool still works today."
• **r/selfhosted and r/opensource**: developers asking for a Codex-style coding assistant that runs locally, no API key, no usage meter. Same energy in r/LocalLLaMA every week.
• **r/socialmedia and r/marketing**: people tired of paying Buffer or Hootsuite prices for scheduling and wanting a self-hosted alternative they can point at their own server.

Notice the shape of these: someone names a specific paid tool, states exactly what it's missing or overcharging for, and describes the alternative they'd use instead. That's a product brief, written for free, by your future customer.

Engage before you build

When you find a thread like this, don't lurk and build in silence for three months. Reply. Ask the person what they've already tried, what they'd pay, what would make them switch today. This does two things: it sharpens the spec, and it puts you on record as the person who was there when the problem was raised — which matters enormously when you come back later with a working product.

The founders who get their first 10 customers fastest are the ones who treat the thread as the customer discovery call, not a proxy for one. If ten people reply "yes, I want this" to a comment on a two-day-old post, you already have more signal than most founders get from a month of cold outreach.

Ship small, then return to the source

Build the narrowest version that solves the specific complaint you found — not the platform, not the roadmap, just the one thing. Then go back to the original thread (and adjacent ones) and post it. "You mentioned wanting an open-source LinkedIn auto-apply tool a few weeks ago — I built a rough version, here's the repo, would love feedback." This is the core loop of building in public done for customer acquisition rather than vanity: every post is a callback to a real conversation, not a cold announcement into a void.

This is also why Product Hunt and Hacker News launches work better when they're not your first move. If you've already got five people from Reddit threads using your tool and giving feedback, your Show HN or Product Hunt post has actual users to reference instead of a demo GIF and hope.

Keep the loop running after 10 customers

Getting to 10 doesn't end the research — it changes what you're listening for. Instead of scanning for the original complaint, scan for the follow-up complaint: what your new users are frustrated by now that they've adopted your tool. A BeePub-style Calibre reading companion, for instance, started as a request for a read-only sync layer — the next round of demand (CJK font handling, offline mode) only shows up once real users are pushing on the edges of version one. The same community research muscle that found your first customers is what finds your next feature, and your 11th through 100th customers.

The pattern holds across every category we track: open-source alternatives to paid SaaS, local-first tools replacing cloud dependencies, and workflow glue between tools that don't talk to each other. The demand is loud and specific if you're reading the right threads at the right cadence.

That cadence is the hard part — nobody has time to read five subreddits, Hacker News, and Product Hunt every morning. That's the gap 1U4X fills: it scans those sources daily and surfaces the specific, sourced product opportunities like the ones above, so you spend your time building instead of scrolling.