How to Get Your First Users for Free: Pick the Source by Product Type
Match the free source to the kind of product you built: public complaints and forums for a workflow app, repositories and registries for a developer tool, a platform’s own store search for an extension, and one-to-one messages for a niche business tool. Free costs hours, not money, so spend them on conversations with people who already have the problem, and count a user only when someone finishes the one task your product exists for.
What does free cost, and who counts as a first user?
Free means you pay in hours. That is worth saying out loud, because hours run out quietly. Before you start, write down how many you will spend this week on finding users, for example five, and keep a tally. When the tally is spent, stop and look at what you learned instead of opening a new channel.
A first user is a person who finished the core task once without you doing it for them. A friend who clicked around to be kind does not count, and neither does a visitor who read the page. If you cannot name the core task in one sentence, fix that first; the MVP scope planner is built for exactly that job.
Which free source fits what you built?
The mistake is picking a channel because it is popular. Pick the place where your product’s users already say the problem out loud. The rows below use invented products to show the reasoning.
| If you built | Where the problem is spoken | First free move | What to skip at first |
|---|---|---|---|
| RotaLoop, a shift-swap web app for volunteer coordinators | Coordinator groups and forums, and threads where someone asks how to cover an empty shift | Answer three such questions properly, then mention the tool once and say you made it | A broad announcement to a general maker audience, who do not run volunteer rotas |
| EnvDiff, a command-line tool that compares configuration files | Issue trackers of tools in the same area, package registry searches, developer forums | Write the one command that solves a reported pain and offer it in the thread where it is asked | A polished landing page; developers want the repository and a quick install |
| TabTrim, a browser extension that groups open tabs by project | The extension store’s own search results for the task, and communities of heavy browser users | Make the listing text match the words people type into that store search | Press outreach, which assumes a story you do not have yet |
| A mobile habit app for people who work night shifts | Communities of night workers and the people who answer their questions | Message ten members individually with a specific reason, and ask them to try it | Generic social posts, since the audience is narrow and easy to miss |
| A quoting tool for small roofing firms | Trade forums, supplier groups, and the firms you can name from a local search | Email or call a short list directly and offer to set it up with them | Self-serve sign-up funnels before a single firm has used it |
Your own product will not match any row exactly. Read the left column for the pattern: the further your users are from other makers, the less a maker-heavy board will do for you alone. A public page still helps because the people you message have somewhere to land, so launch your product free as that page rather than as your main channel.
How should the first message read?
Follow a four-part rule. Say where you saw the person, say what you made in one sentence, ask exactly one question, and ask for nothing else. No sign-up request, no vote, no “quick call?” in the first message. If you reply in public to someone’s post, help with their actual question first, then add that you built a tool that does the specific thing, and say it is yours.
Hi Dana, I saw your post asking how to cover a last-minute gap on a volunteer rota. I built a small tool that lets volunteers swap shifts without the coordinator relaying every message. Would it fit how your group works today, or is the swapping not the hard part?
Notice the closing question. It can be answered with a no, and a no is useful: it tells you the problem is somewhere else. If you want more wording, the cold DM templates for first users have variants.
What can you offer a first user that costs nothing?
- Your attention. Promise to read every message and say what you changed because of it. Early users like a maker who answers.
- Access while you are still learning. Free use for now is honest if you say it may change. Do not promise free forever.
- A say in what gets built next. Ask what they would remove or add, and show them the change when it ships.
- Setup done for them. For a business product, import their data or configure it on a call. It teaches you more than any survey.
Do not offer gift cards, prizes or paid reviews for trying the product. They inflate the numbers and tell you nothing about whether anyone would come back unprompted.
When should you change the plan?
Set the test before you begin, so the results cannot talk you into staying. For example: contact twenty people from one source, and if fewer than three try the product, change either the source or the message, never both at once. The numbers twenty and three are placeholders for you to replace; nobody has a measured threshold that holds for every product.
- People reply with “nice” and never try it: the pitch is vague, or the problem is mild. Tighten the one-sentence promise.
- They try it and leave: watch one session and note the exact step where they stop. That step is your next job.
- They try it, return and ask for more: write down the source and send ten more messages there before you try a new one.
- Nobody answers anywhere: read why nobody visited my launch to see whether the break is reach, clarity or tracking.
Keep a plain sheet with the person, the source, the date, whether they replied, whether they finished the core task and whether they came back after a week. A return visit is the figure that matters, because it separates curiosity from use. When a pattern shows, the first 100 users playbook covers the next stage, and the validate app idea tool helps if the answers suggest the problem was never as sharp as you thought. For productivity-style products, browse the productivity ideas already on the board to see how others describe the problem.
Frequently asked questions
Where do I find my first users if I have no audience?
Go to the places where people with your product’s problem already ask for help, such as forums, issue trackers or an extension store’s search, and answer questions there before you mention your tool. Then message a short list individually. A launch page gives them somewhere to land, but it will not bring users alone.
How many first users do I need?
Enough to see a pattern, and nobody can give a fixed number that suits every product. Many makers aim for around ten people who finished the core task, but that is a working target, not a research finding. Set your own number before you start and judge the result against it.
Is it okay to ask friends and family to be my first users?
Ask them only if they genuinely have the problem, and do not count them toward your user number if they are only being kind. Friends tend to say the product is great. A stranger who tried it and returned tells you far more, so aim your effort at strangers with the problem.
Should I pay for ads to get my first users?
Not before you have a message that works in free, one-to-one conversations. Ads multiply whatever your page does, good or bad, and they cost money while you are still learning what to say. If ten personal messages get no replies, an ad will not fix that.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.