Science of Apps - Launchpad · Playbook

How to find
early adopters

Early adopters are people who have your problem, know it, are actively looking for a fix and will tolerate an unfinished product. Find them where they already search: communities about the problem, people using workarounds, launch sites such as BetaList, Product Hunt and Peerlist, and your own network's introductions. Approach them about their problem, not your product.

By , FounderUpdated 4 min read

Share

Quick answer: How do I find early adopters for my startup?

  1. Who they are: they have the problem, know it, are looking, and tolerate rough edges.
  2. Best sign: they've already built a workaround.
  3. Where: problem communities, launch sites (BetaList, Product Hunt, Peerlist), introductions.
  4. Approach: ask about their problem; offer to solve it personally.
  5. Keep them: fast replies, visible fixes, credit for their input.

Key takeaways

  • Early adopters are defined by urgency, not by age or tech-savviness.
  • Workarounds are the clearest signal: spreadsheets, scripts, hired help.
  • Go to where they already look for solutions; don't wait for them to find you.
  • Doing things that don't scale (personal onboarding) wins the first ones.
  • Treat them as collaborators; they become your first referrals.

Your first users won't be "the market". They'll be a handful of people whose problem is bad enough that they'll put up with your unfinished product to get it solved. Those are early adopters, and they're easier to find than founders think, because they're already looking. This playbook covers who they are, the places they gather, how to approach them without pitching, and how to keep them, drawing on Y Combinator's advice on talking to users and the launch sites' own rules, checked on 17 November 2026.

Who early adopters are

Checklist: Who early adopters are — They have the problem; They know they have it; They're actively looking; They've built a workaround; They tolerate rough edges.
Who early adopters are
  • They have the problem — regularly, not once
  • They know they have it — they can describe it
  • They're actively looking — searching, asking, trying tools
  • They've built a workaround — a spreadsheet, a script, hired help
  • They tolerate rough edges — the problem hurts more than your bugs

The workaround is the strongest sign: someone who has spent effort on a bad solution will try a better one.

Ten places to find them

PlaceWhy they're there
Communities about the problemThey ask for help there
Comment threads on competitor launchesThey're evaluating options
People complaining about existing toolsDissatisfied and looking
Your customer interviewsAsk "who else should I talk to?"
BetaListEarly adopters browsing new startups
Product HuntEarly adopters, makers, product people
Peerlist LaunchpadBuilders, every Monday
Indie HackersFounders sharing and testing
Your own network's introductionsWarm, trusted
A permanent profile found by the problemPeople searching for a fix

Table: Where early adopters gather (launch sites' own descriptions, checked 17 Nov 2026)

BetaList homepage showing Today's featured startups
BetaList: early adopters browsing new startups.Image: BetaList · Screenshot shown for commentary, 17 Nov 2026 · source

How to approach them

Diagram of 5 steps for how to approach them: 1. Lead with their problem; 2. Ask, don't pitch; 3. Offer to solve it personally; 4. Onboard them yourself; 5. Ask for a small commitment.
How to approach them
  1. Lead with their problem — "I saw you're handling X with a spreadsheet. How's that going?"
  2. Ask, don't pitch — what they do today, what it costs (see the interview script).
  3. Offer to solve it personally — "I'm building something for this; can I set you up?"
  4. Onboard them yourself — a call, a shared screen, no self-serve maze.
  5. Ask for a small commitment — weekly use, feedback, an introduction.

How to keep them

Checklist: How to keep them — Reply within hours; Ship their top request; Credit them; Give them a direct line; Invite them to your launch day.
How to keep them
  • Reply within hours — they're doing you a favour
  • Ship their top request — and tell them
  • Credit them — in changelogs, with permission
  • Give them a direct line — a chat group or email
  • Invite them to your launch day — to try and give feedback, never to upvote

Mistakes

Checklist: Mistakes — Targeting "everyone"; Cold pitching; Self-serve only; Ignoring their feedback.
Mistakes
  • Targeting "everyone" — early adopters are a narrow, urgent group
  • Cold pitching — ask about the problem first
  • Self-serve only — the first ones need a human
  • Ignoring their feedback — they leave, and they talk
Science of Apps Launchpad homepage with the headline Launch your product. Get it found.
The Science of Apps Launchpad: found by the problem you solve.Image: Science of Apps · © Science of Apps · source

Ready to be found?

How we know

Launch-site descriptions come from BetaList's, Product Hunt's and Peerlist's own pages, read on 17 November 2026; the approach draws on Y Combinator's Startup School and The Mom Test. The ten-places table is our editorial summary.

Key terms, defined

  • Early adopter: one of the first people to use a new product.
  • Workaround: a makeshift solution people use until a better one exists.
  • Doing things that don't scale: manual effort to win the first users.
  • Champion: a user who recommends you to others.
  • Commitment: time, reputation or money a user gives.

Frequently asked questions

Who are early adopters?

People who have the problem you solve, know they have it, are actively looking for a solution, and will accept an unfinished product because the problem hurts enough. Many have already built a workaround.

Where can I find early adopters?

In communities where people discuss the problem, among people using workarounds, on launch sites like BetaList, Product Hunt and Peerlist, in founder communities such as Indie Hackers, and through introductions from people you interview.

How do I approach early adopters?

Ask about their problem first: how they handle it today and what it costs. If it's a fit, offer to set them up personally. Avoid a cold pitch.

How many early adopters do I need?

Enough to learn and get a few strong references: often ten to a few dozen engaged users who use the product regularly and tell you what's broken.

Is BetaList good for finding early adopters?

It can be: BetaList features startups new to its audience, including pre-launch and beta ones, if selected. Every submission is paid, with an automatic refund if you're not selected.

How do I keep early adopters engaged?

Reply fast, ship their top requests visibly, tell them when you've fixed something they raised, and give them credit. They'll become your first referrals and launch-day supporters.

Sources

  1. BetaList — Help and FAQ (checked 17 Nov 2026)
  2. Product Hunt Help Center — How Product Hunt works (checked 17 Nov 2026)
  3. Peerlist Help Center — How do I launch a project on Peerlist Launchpad? (checked 17 Nov 2026)
  4. Y Combinator Startup Library — How to talk to users (Gustaf Alströmer)
  5. Rob Fitzpatrick — The Mom Test (book site)
  6. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

Early adopters search for fixes: a free, permanent Launchpad profile helps them find you by the problem you solve, ranked by relevance and never by payment, plus a product test with a detailed report.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition