For founders deciding how to get first app users, the most practical starting point is direct outreach to a narrow audience, followed by supported onboarding and careful attention to repeat use. This article sets out a low-cost route towards the first 100 users, treating recruitment as a way to test the product rather than simply increase registrations.
Key takeaways
- Define a specific audience with a recognisable problem before choosing channels, writing launch announcements or building more features.
- Recruit the earliest users through individual conversations, offering help with a real task rather than asking for general feedback.
- Make the first useful action easy to complete, and observe where new users need explanation or additional support.
- Use relevant communities and small partnerships to repeat successful recruitment, rather than relying on a single launch-day traffic spike.
- Measure activation and repeat use alongside acquisition, so the first 100 users provide evidence about demand and product quality.
What is first-user acquisition?
First-user acquisition is the process of finding people with a relevant problem and helping them try a new app to solve it. For an early-stage product, success means reaching suitable users who complete a useful action and have a reason to return, rather than collecting registrations alone.
The first 100 users are a working learning group, not proof of product-market fit. Their behaviour can reveal whether the problem matters, whether the product explains itself and whether its proposed pricing deserves further testing.
Define what counts as a user before recruitment begins. A waitlist subscriber has expressed interest; an activated user has experienced the app's central benefit. Keep those categories separate when reporting progress.
How to get first app users by choosing a narrow audience
A small audience is usually easier to reach than a broad demographic. “People who want to be more organised” offers little direction. “Independent tutors who arrange weekly lessons and chase payment confirmations” points towards particular communities, existing habits and identifiable frustrations.
Describe the intended user through their task, circumstances and current workaround. A founder should be able to explain when the problem occurs and what the person does about it today. If the answer is unclear, recruitment conversations should precede further development.
Use a simple audience brief:
- Person: who performs the task and decides whether to adopt a new tool?
- Trigger: what event makes the problem noticeable or urgent?
- Workaround: which spreadsheet, message thread or manual process currently fills the gap?
- Outcome: what useful result should the first session produce?
This brief should shape the MVP as well as its messaging. A scheduling app for tutors might initially prioritise arranging the next lesson, rather than reporting, public profiles and several payment options. Recruitment becomes easier when the promise is concrete.
A short landing page and waitlist can test whether that promise attracts interest before the full build. Explain the intended outcome and current availability honestly. Ask subscribers about their existing process; an email address alone reveals little about likely usage.
How to recruit the first 10 users manually
Start with people who match the audience brief, including relevant professional contacts, introductions and individuals already discussing the problem publicly. Friends can help test basic usability, but their encouragement is not a substitute for evidence from likely customers.
Personal outreach should show why the person was selected. Refer to their role or a relevant discussion, describe one outcome and make a modest request. A short invitation to try a specific task is easier to assess than a request to “check out a new platform”.
- Identify a small group of people with a clear connection to the problem.
- Write individual messages explaining the task the app supports and its current stage.
- Offer a brief demonstration or supported first session, depending on the person's preference.
- Observe the first attempt without explaining every screen in advance.
- Follow up after the next occasion when the person would reasonably need the app.
Keep outreach relevant, respect community rules and stop when someone declines. Repeated unsolicited messages damage trust and provide poor research conditions.
Supported onboarding is useful at this stage because it exposes confusion immediately. Record where users hesitate, what information they lack and whether they complete the intended task. Distinguish product success from founder assistance: completing a workflow after extensive coaching is different from completing it independently.
The first users are most valuable when their behaviour can challenge the product's assumptions, rather than merely confirm that a launch attracted attention.
Where to find early adopters without paid advertising
Choose places where the problem is already discussed. These might include a specialist Slack group, a professional association, a local business network or a focused Reddit community. Audience relevance matters more than membership size.
Read the rules and contribute useful answers before sharing a product. When someone describes a problem the app genuinely addresses, explain the connection and disclose the founder's involvement. Avoid copying the same promotional post across unrelated groups.
Turn useful evidence into public updates
Building in public works best when updates help the intended audience understand the problem. A short explanation of a recurring scheduling mistake, or a walkthrough of an improved setup process, can be more relevant than a development diary. Never publish private user information without permission.
Small partnerships can also provide access to a suitable audience. A newsletter editor, trainer or community organiser may be willing to share a genuinely useful resource or host a short demonstration. Agree the purpose and any commercial arrangement openly.
Product Hunt and Hacker News can expose an app to new people, but audience fit varies and attention may fade quickly. Treat a launch as a testable event, with a clear landing page and onboarding ready, rather than the entire acquisition strategy. Defer paid advertising until the message and activation journey have some supporting evidence.
How to turn early signups into active users
Acquisition spending is wasted if suitable users cannot reach the app's central benefit. Before expanding recruitment, define one activation event: the action that indicates someone has received initial value. For a lesson-planning app, that might be creating and saving a plan for an upcoming lesson.
Remove setup steps that are unnecessary for that result. Explain permissions when they are needed, make errors understandable and avoid presenting every feature during onboarding. Sample content can help demonstrate a workflow, but it should not be mistaken for genuine user activity.
The app must also be accessible through an appropriate release route. A web application may be shared through a link; an iOS beta may use TestFlight, subject to Apple's applicable requirements. Explain installation steps and known limitations clearly. There is little value in recruiting testers who cannot access the build.
Ask about concrete experiences after use: what task was attempted, where progress stopped and what happened instead. “Would this be useful?” invites speculation. “How did the last lesson booking get arranged?” gives the product team something more dependable to examine.
If pricing is part of the business model, introduce the intended approach early. Free access may help recruit testers, but it does not establish willingness to pay.
How to grow from 10 users towards 100
Once suitable people are reaching the intended outcome, repeat the recruitment method in small batches. Keep a simple record of where each person came from, whether they activated and whether they returned. Compare channels by user behaviour, not just signup totals.
Use a review process that separates three questions:
- Acquisition: which sources bring people who actually match the intended audience?
- Activation: which of those people complete the first useful task?
- Retention: do they return when the task next arises?
The right observation period depends on the product. Daily usage may matter for a daily planning tool; a monthly invoicing app requires a longer view. Avoid treating short-term inactivity as failure when the underlying task has not recurred.
After someone receives value, ask whether a colleague or peer faces the same problem. A relevant introduction is often more useful than a generic referral incentive. If uptake remains weak, revisit the audience, promise or product before increasing outreach volume. The methods used for the first few users need not become the permanent growth model.
Frequently asked questions
How can I get app users with no advertising budget?
Start with a narrowly defined audience and recruit through individual outreach, relevant communities and introductions. Offer help with a specific task rather than promoting a broad feature list. Track whether people complete that task and return. These methods require founder time, even when there is no advertising spend.
Should I launch my app before it is finished?
An app can be tested before every planned feature is built, provided its core task works and limitations are clearly explained. Use an appropriate beta or release route, and avoid exposing users to unfinished flows that could cause harm or lose important work. Early testing should inform scope, not excuse preventable failures.
Do waitlist subscribers count as app users?
Waitlist subscribers are prospective users, not evidence of active usage. They have shown enough interest to leave contact details, but may never try the product. Track subscribers, registrations, activation and repeat use separately. Follow-up conversations can help establish whether waitlist interest reflects a pressing problem or general curiosity.
When should a new app start paid advertising?
Paid advertising is easier to assess once the app has a clear audience, a tested message and evidence that suitable users reach its main benefit. Before that, advertising may buy traffic without explaining weak adoption. Any initial test should have a defined budget, a measurable outcome and a stopping rule.
Final considerations
The first 100 users should make the product's next decisions clearer. Their experiences can expose an unsuitable audience, an unclear promise or an onboarding step that blocks otherwise genuine demand. Those findings are useful even when signup growth is modest.
A disciplined launch therefore combines recruitment with observation. Keep the initial task focused, stay close to users' actual behaviour and expand the channels that bring people who return. A smaller group receiving consistent value is a firmer foundation than a larger list of inactive accounts.