Where to find early adopters
Last checked 6 August 2026
The standard advice is to find people who feel the problem acutely, which is true and useless. It describes who they are without saying where they are, and where is the entire question.
The reliable version is narrower: your early adopters are the people already solving this problem badly. They have a spreadsheet, a manual routine, a workaround they complain about. That behaviour is visible in public, which means it is searchable.
Find the workaround, and you have found the person
Nobody searches for a product category they have never heard of. They search for help with the manual version — the spreadsheet template, the script, the "how do I keep track of" question. Those searches and the threads that answer them are where your first users are, and they were there before your product existed.
Search for the workaround rather than the category. The threads that come back are simultaneously a list of places and a list of people, and the person who wrote the most detailed answer in each thread is usually the best first conversation you will have.
The four places this actually happens
- Question threads
- Reddit, Stack Exchange, and specialist forums, where the same question is asked every few months and answered with a workaround. Recurrence is the signal: a problem asked once is a person, asked quarterly it is a market.
- Professional communities
- The Slack and Discord groups for a job title rather than a technology. Highest concentration of the right people and the strictest rules — most state plainly that promotion is not allowed, and they mean it.
- The tool they currently misuse
- Every workaround is built on something: a spreadsheet, an automation tool, a note-taking app. That tool's own community is full of people describing your problem in their vocabulary.
- Pre-launch platforms
- BetaList and similar exist specifically for people who enjoy trying unfinished things. A narrower kind of early adopter — enthusiastic, forgiving, and not always representative of who eventually pays.
What to do once you have found the place
The mistake is arriving with the product. The people in these places have seen dozens of founders do exactly that, and the rules exist because of it.
Arrive with the problem instead. Answer the question that brought you there — properly, without mentioning what you are building — and the conversation that follows is the one you wanted. It is slower than posting a link and it is the difference between being welcome and being removed.
When you do mention the product, say it is yours. Every community rule that permits mentioning a product at all attaches that condition, and disclosure is also what makes the mention believable.
How to know they are the right ones
An early adopter who is genuinely in your market does two things: they describe the workaround in detail without being asked, and they ask what it costs. Enthusiasm without either of those is a person who likes new tools, which is pleasant and not a signal.
Ten specific conversations tell you more than a thousand visitors. Have them before you build the next feature, not after.
Questions
- How many early adopters do I need?
- Around ten who use it more than once. That is enough for the same complaint to appear three times, which is the point at which you know what to build next.
- Can I find early adopters on LinkedIn?
- You can find the job titles there, which is not the same thing. LinkedIn tells you who someone is; the communities tell you what they are struggling with this week, and the second is what you need.
- Should I offer early adopters a discount?
- Access and attention work better than a discount. People who came for a discount tell you about your price, and people who came for the problem tell you about your product.