From Idea to Your First 10 Users

Your first ten users won't come from a launch post, a clever growth hack or an algorithm. They'll come from you, personally finding people with the problem and asking them to try what you built. It's slow, a little awkward, and the most reliable way to start.

This guide is a practical playbook for getting from an idea (or an early product) to ten real users who use it and tell you what's wrong with it.

Why ten, and why by hand

Ten users is small enough to get manually and big enough to see patterns. With two users, every piece of feedback is an anecdote. With ten, you start to hear the same complaint three times, and that's a signal.

Getting them by hand matters because at this stage you need conversations, not traffic. A hundred anonymous signups from a launch spike teach you less than ten people you've emailed, called and watched use your product. Scalable channels come later, once you know who the product is for and what they value.

Step 1: List 50 candidates by name

Open a spreadsheet and write down 50 specific people or organizations who plausibly have the problem. Not personas, names. Columns: name, where you found them, why they fit, contact method, status, notes.

Where names come from:

• Your own network. Former colleagues, clients, classmates, people in your industry. Include "people who know people like that."
• Your validation page. If you ran a validation landing page, the leads it collected are the top of your list. They already raised their hand.
• Public complaints. People who posted about the problem in forums, reviews of competing tools, or Q&A threads.
• Job boards and directories. If you're building for a role, companies hiring for that role clearly have it.
• Competitor communities. Users of an alternative who are unhappy about a specific gap.

Fifty sounds like a lot. That's the point. Many won't reply, and a list of fifty forces you past your comfort zone of five friends.

Step 2: Find where they hang out

For each type of person on your list, figure out where they spend time online and offline. Typical places:

• Subreddits for the profession, hobby or tool.
• Slack and Discord groups for industries, tools, or local tech scenes.
• Forums and communities built around specific software (plugin marketplaces, product forums, user groups).
• Newsletters and podcasts your audience reads or listens to.
• In person: meetups, conferences, trade shows, coworking spaces.

Join a few and participate before you promote. Answer questions, share what you know, and learn the vocabulary people use for the problem. Every community has its own rules on self-promotion; read them and follow them. Getting banned from the one place your users gather is an expensive mistake.

Step 3: Personal outreach that gets replies

Short, specific, and about them. Mention why you're writing to this person, what you're working on in one sentence, and one easy ask. Don't paste a pitch deck.

Example: a warm or semi-warm contact

Hi Maya, I saw your post in the bookkeepers' Slack about spending the last week of every month chasing receipts. I'm building a small tool that pulls receipts from email and matches them to bank transactions automatically. Would you be up for trying an early version? I'd set it up for you and it'd take 15 minutes. No worries at all if not.

Example: a cold contact from a public complaint

Hi Daniel, you mentioned in a review that your current scheduling tool can't handle split shifts. I'm working on something for small restaurants that does exactly that, and I'm looking for three or four managers to try it free and tell me what's missing. Interested in a quick look?

A few rules of thumb:

• Send each message individually. Mass templates read as mass templates.
• Follow up once after a few days if there's no reply, then let it go.
• Offer to do the setup work for them. It lowers the barrier and gets you a front-row seat.
• Track every message in your spreadsheet so you know your reply rate.

Step 4: Onboard by hand (do things that don't scale)

When someone says yes, make their first experience great, even if it takes an hour of your time per user. Things that don't scale but work at this stage:

• Set it up with them on a video call, or do it for them from their data.
• Watch them use it without helping, and note where they hesitate.
• Fix their problems the same day when you can. Speed is your advantage over bigger companies.
• Do parts of the product manually. If a feature isn't built, do it yourself behind the scenes and learn whether it's worth automating.
• Check in after a few days with one question: "Did you use it again? What stopped you?"

Your goal isn't efficiency; it's learning what makes someone come back.

Step 5: Launch in the right places

Once a handful of people are using the product, a public launch can bring the next batch. Choose venues that match your audience, and read each one's rules first.

A launch is a spike, not a strategy. Treat it as a chance to find a few more people for Step 4, and reach out personally to anyone who signs up.

Step 6: Turn waitlist signups into users

If you collected a waitlist, don't just send a mass "we're live" email and hope. Waitlist interest cools quickly, so:

1. Invite in small batches, five or ten at a time, so you can onboard each one properly.
2. Send personal invitations that reference why they signed up, if you know.
3. Offer a short setup call to anyone who wants one.
4. Follow up with non-starters. A simple "Did you get a chance to try it? Anything in the way?" often gets a candid answer.
5. Remove people who ask, promptly and without fuss.

Expect only a fraction of signups to become active users. That's normal; the people who do come through are the ones to learn from.

What to measure after 10 users

Ten users is too few for dashboards full of percentages. Focus on a few questions you can answer by looking at each user individually:

• Activation. Did each person reach the moment where the product did its job for them? If not, where did they stop?
• Return usage. Did they come back in the second week without you prompting them?
• The "very disappointed" test. Ask: "How would you feel if you could no longer use this?" A few "very disappointed" answers are worth more than many "somewhat."
• Willingness to pay. Ask directly what they'd pay, or better, ask them to pay. Even a small amount separates polite interest from real demand.
• Referrals. Did anyone mention it to a colleague unprompted?
• Repeated requests. Which complaint or feature request came up three or more times?

If several of the ten return, would be disappointed to lose it, and would pay, you've found something worth growing. If not, the notes you took during onboarding usually point to what to change: the audience, the promise, or the product.

Getting a head start

If you're still at the idea stage, two things in Ideas can shorten this process. A deep-dive report on an idea includes a "Go-to-market: first 90 days" section, which gives you a starting list of channels and early moves to adapt. And a validation landing page collects leads through a signup form, which gives you the first names for your outreach spreadsheet. See how to validate a startup idea for where each fits.

Whatever you use, the core loop doesn't change: find people by name, talk to them, help them personally, and listen closely to what the first ten tell you.