The Fastest Route to Your First Ten Real Users
Growth · 10 min read ·
A short plan for finding ten people who really use your product: who to ask, what to say, how to watch them and what to do with what you learn.
Your first ten users are not a statistic. They are people, and each one can tell you something no analytics chart will. How they found you, what they expected, where they got stuck, what they said to a colleague. The faster you get ten real people using the product, the faster you learn whether it is worth building.
This is a plan for doing that in days, not months, without spending money or pretending to be bigger than you are.
What "real user" means
A visit is not a user. A sign-up is not a user. A real user is someone who has completed the core task for their own purposes and who could tell you, in their own words, what the product did for them.
Early adopters, in the standard description, are the first people to try a new product, often because they are keen on novelty or have a pressing problem that existing options do not solve. They tolerate rough edges because the benefit matters to them. These are the people you want first.
The lean approach to building products emphasises learning quickly from real customers through a build-measure-learn loop. Your first ten users are the fuel for that loop.
Step 1: Describe your user in one sentence
Who has the problem your product solves, in a way you can recognise? Write one sentence: "A freelance designer who sends invoices by hand and forgets to chase them."
The sentence should be specific enough that you can picture a person, and ideally name three people you know who fit it, or know how to find them. If you cannot, narrow it until you can.
Step 2: Make a list of fifty
You need a list of fifty people or places where such users can be found. Not fifty strangers on a mailing list: fifty named people or specific communities.
Sources of names:
- Your own contacts. Colleagues, former colleagues, clients, classmates.
- Communities you belong to. Forums, groups and chats where the problem is discussed.
- People who posted about the problem. Public posts asking for a solution.
- Customers of adjacent products who complain publicly about gaps.
- Introductions. Ask each person on your list who else you should talk to.
Write the list down. A list turns a vague hope into a task.
Step 3: Write a message worth answering
Your first message decides whether anyone replies. A good one is short, specific and easy to decline.
A template, adapted to your own voice:
"Hi [name], I am building a tool that [one-sentence benefit] for [their kind of person]. I saw that you [specific reason you are writing]. Would you be willing to try it for ten minutes and tell me what is confusing? Here is the link: [link]. No obligation, and I will not add you to anything."
Rules:
- Be specific about why them. A generic blast gets ignored.
- Ask for something small. Ten minutes, not a project.
- Make it easy to say no. People respond better when they are not cornered.
- Do not oversell. Say what it does, plainly.
- Do not send the same text to everyone. Adjust the first line at least.
- Respect the rules of the place. Many communities forbid promotion; check, or ask the moderators.
Send ten messages a day for a few days. You do not need all fifty to respond; you need ten who use the product.
Step 4: Watch them use it
Reading feedback is good. Watching is better.
If you can, ask each user to share their screen while they try the product, or sit with them, and say nothing for the first few minutes. Note:
- Where they hesitate.
- What they click that you did not expect.
- What they say aloud.
- Where they give up.
Resist the urge to explain. Every time you explain, you hide a problem that other users will meet without you.
If watching is impossible, ask three questions afterwards: What were you trying to do? What got in the way? What would you tell a colleague about it?
Step 5: Fix the thing that blocks the most people
After three or four users, patterns appear. Pick the one problem that stopped the most people and fix it. Then ask the next user. Repeat.
Do not try to fix everything. The first ten users teach you what to fix first. Some feedback will be a personal preference; set it aside until a second person says the same.
Step 6: Ask each user for one introduction
When someone has had a good experience, ask: "Who else do you know who has this problem?" People who liked a product often introduce others. Keep the request light and optional.
Ask for permission before you quote anyone or mention their name. A short, honest quote with permission is worth more than ten generic claims.
Listings and communities
Public listings and directories can bring early users who find you on their own. Write a clear one-line description, a screenshot and an honest note about the stage of the product. Treat the people who arrive through a listing the same way as those you contacted: thank them, ask for feedback and watch what they do.
Join communities as a participant before you promote. Answer questions, share what you learn and mention your product only when it is relevant and permitted. Google's guidance on helpful content emphasises people-first content; the same spirit works in communities. Be helpful first.
What to avoid
- Buying users or votes. They are not real, and they teach you nothing.
- Asking friends to pretend. Feedback from people who will not use the product is not evidence.
- Spamming. One unsolicited message is a request; five is a nuisance.
- Over-explaining. The product must make sense without you.
- Counting sign-ups as success. Count completed tasks.
- Chasing every request. Look for patterns.
A worked example
A founder building a tool that turns voice notes into task lists defines her user: "A busy manager who records thoughts while walking between meetings." She writes a list of fifty from her contacts and from a community of managers where she is already an active member.
She sends ten personal messages on day one. Four people reply, and two try the product that day. She watches one on a video call and notices that he does not realise recording has started. She adds a clear indicator that evening. On day two she sends ten more messages; five reply. By day four she has seven users. One asks for a feature she had not considered; a second asks for the same thing. She notes it, and does not build it yet.
On day six she asks each of the seven for an introduction; three provide one. By day eight she has ten real users, a list of three fixes already made, a short quote from two of them with permission and a clear picture of who the product is for. She spent nothing and learned more than she would have from a thousand passing visits.
Questions and objections
What if nobody replies? A low reply rate usually means the message is too generic or the problem is not painful enough. Rewrite the first line to refer to something specific about each person, and test a different segment. If three rounds produce no interest, that is information about the problem, not about your persistence.
What if people say they like it but never use it? Politeness is not usage. Ask what they did the last time they faced the problem, and whether they would use the product for the next one. Watch behaviour, not compliments.
Should I offer an incentive? A small thank-you is fine if it does not distort the feedback. Never pay for positive reviews, and do not offer anything that would make people say what you want to hear.
How do I keep track? A simple spreadsheet with a row per person: name, source, date contacted, response, date tried, what happened, follow-up. It takes minutes to maintain and saves you from asking the same person twice.
A note on ethics
Be honest about what you are building and why you are asking. Tell users how their data will be used, keep it only as long as you need and delete it when asked. People who feel respected tell others, and early trust is the cheapest growth there is.
Where the first ten tend to come from
Founders are often surprised by the sources. Direct messages to people with a recent, public problem usually convert best, because the timing is right. Introductions from earlier users come next, because the trust is borrowed. Communities where you have been helpful for a few weeks come third. Cold lists, paid promotion and broad social posts tend to bring many visits and few real users at this stage. Keep a tally of the source of each of your first ten, so that when you start to scale you know which door to widen.
Summary
Ten real users beat a thousand visitors. Define your user in a sentence, build a list of fifty, write a short message worth answering, watch people use the product and fix what blocks the most. Ask satisfied users for introductions, join communities as a helper and never fake demand. In a week or two you will know whether you have something worth building.
Questions and answers
- Why ten users and not a thousand?
- Ten real users teach you more than a thousand passing visitors. You can talk to each of them, watch them use the product and find the problems that matter.
- Where do the first users come from?
- Mostly from people you can reach directly: your network, communities where you already take part and people who have expressed the exact problem you solve.
- Should I charge the first users?
- That depends on the product. The point of the first ten is learning; if you do charge, be transparent about what they get.
- What counts as a real user?
- Someone who completes the core task for a real purpose, not someone who signs up and never returns.