How to Find Your First Customers Before You Build

Most founders build first and look for customers after. That's backwards. The founders who actually win do the opposite: they find their first customers before they build, then let those early buyers shape the product.

The good news is you don't need a network, a mailing list, or a marketing budget to do this. You need to know where your future customers are already talking about their problems — and how to reach them.

Here's the system.

Step 1: Define who you're building for in one sentence

Before you can find customers, you need to know who they are. Not "everyone who needs a better tool" — that's nobody. Be specific:

Who — "solo founders building a SaaS in the first 6 months"
What problem — "they can't tell if anyone wants their idea"
Where they hang out — "Bluesky, indie hacker forums, niche subreddits"

If you can't fill in all three, you're not ready to look for customers. You're still looking for a problem.

Step 2: Find where they already talk about the problem

Your future customers are already posting about their pain — in public, in their own words, every single day. You just need to be in the right place.

Search for the language of the problem, not your product:

"I wish there was a way to..." — an unfilled need, stated directly
"I can't find a tool that..." — active searching, high intent
"I've been doing X manually" — a workaround begging to be automated
"Does anyone know a tool for..." — a public request for a solution
"I'd pay for..." — explicit buying intent

These are demand signals. Each one is a person who has the problem you're solving, cares enough to post about it, and is actively looking for a fix. That's a potential first customer.

Step 3: Cluster signals into a real market

A single post is an anecdote. A cluster of posts is a market.

When you find one signal, don't stop. Search for the same pain in different words. If you find 15–20 people in a month all describing the same frustration with slightly different phrasing, you've found a real, recurring problem — and a pool of people to talk to.

Cluster by the underlying problem, not the surface complaint. "I hate reconciling expenses" and "spreadsheets for invoicing are killing me" are the same problem wearing different clothes.

Step 4: Reach out to the people who posted

This is where most founders freeze. They've found the signals, but they're afraid to reach out.

Don't be. These people posted their problem publicly. They want a solution. A short, honest message works:

"Saw your post about [their exact problem]. I'm building a tool that [solves it]. Would you be open to a 10-minute call to tell me how you handle it today?"

That's it. No pitch, no pressure. You're asking for their expertise, which flatters them, and you're validating your idea with the exact people who'd buy it.

Step 5: Let early conversations shape the product

The people who reply are your first customers — or at least your first product advisors. Ask them:

How do you solve this today? — reveals the workaround you're replacing
What's the worst part? — reveals the feature that matters most
Would you pay for a fix? — reveals actual buying intent
What would you pay? — reveals your pricing ceiling

Their answers are worth more than a hundred surveys. These are real buyers telling you exactly what to build.

The takeaway

You don't need to build first to find customers. You need to listen to the right place — where your future customers are already describing their problems in public.

The demand is already out there. People are already telling you what they want, in their own words, every single day. Find the signals, reach out to the people behind them, and let those conversations tell you what to build.

That's how you find your first customers before you build — and it's how you build something people actually want.