# How to get your first 50 app users (when nobody knows you exist)

*Fifty people you know by name beat five thousand strangers.*

> How to get your first 50 app users with no audience: hand-picked beta users, manual onboarding, a 14 day plan, an invite template and an interview script.

Source: https://www.appgrowthmarketer.com/playbooks/first-50-app-users
Author: Ar.Bhavesh Panse, AI App Growth Marketer (https://www.arbhaveshpanse.com)
Published: 2026-09-26 · Updated: 2026-09-26

to get your first 50 app users when nobody knows you exist, hand-pick them. list people who have the problem your app solves, invite each one personally, onboard them yourself on a call, and talk to every single one. fifty users you know by name will teach you more than five thousand strangers from a launch.

## Why the first 50 users are a learning problem

the first 50 users are not a growth problem, they are a learning problem. you are not looking for a channel that scales. you want to find out whether people come back, which moment makes the app click, and how they describe it. that only works if you know each user well enough to ask them directly.

Paul Graham's essay [Do Things that Don't Scale](https://paulgraham.com/ds.html) makes the same point: early on, founders have to "recruit users manually". it feels slow, but every user becomes a conversation, not a row in a dashboard.

## Start with people you can name

your personal network is the right first source, used the right way. do not blast a link to everyone you know. write a list of people who actually have the problem, message each one personally, explain why you thought of them, and make it easy to say no. friends without the problem give polite, useless feedback.

how to build the list in one evening:

1. go through your phone contacts, LinkedIn, old group chats, alumni groups and past coworkers. write down every name that has the problem your app solves.
2. mark each one: has the problem now, had it before, or knows someone who has it.
3. start with "has it now". these are your first invites.
4. aim for roughly twice as many names as users you want (illustrative: 100 names for 50 users), because many will be busy or not a fit.
5. end every onboarding call by asking for one introduction to someone with the same problem.

asking for introductions without being awkward is covered in [getting your first 100 users from your network](https://www.appgrowthmarketer.com/playbooks/first-100-users-from-your-network).

## Hand-pick your beta users

a good beta user has the problem today, has already tried to solve it, and will tell you the truth. hand-pick for those three traits instead of accepting anyone who signs up. ten users who fit beat forty who do not, because only their behavior tells you whether the app solves a real problem.

| trait | why it matters | how to spot it |
|---|---|---|
| has the problem now | they will use the app for real, not as a favor | they can describe the last time it happened |
| already tried to fix it | they can compare you with something | they name a tool, a spreadsheet or a workaround |
| honest | you need criticism, not compliments | they have disagreed with you before |

to get the app onto their phones, use a beta track. on iOS, [TestFlight](https://developer.apple.com/testflight/) lets you invite up to 10,000 external testers by email or a public link. on Android, Google Play's [internal testing track](https://support.google.com/googleplay/android-developer/answer/9845334) covers up to 100 testers you add by email. either is plenty for 50.

## A message template to invite a beta user

a good invite is short, personal and easy to refuse. say why you picked this person, what the app does in one line, how much of their time you are asking for, and what they get back. never paste one message to fifty people. write the first line fresh every time, because it is why they reply.

> hey [name], i remember you mentioning [the problem] when [specific moment]. i have been building a small app that [does one thing] and i am looking for 10 to 20 people who deal with this to try it before anyone else.
>
> it would take a 20 minute call where i watch you try it, then a week of using it normally. you would get [free access / a direct line to me / your feature ideas built first].
>
> totally fine if the timing is bad, just say so. want me to send the beta link?

## Onboard every user by hand

manual onboarding means you sit with each new user, on a video call or in person, while they open the app for the first time. you watch, you stay quiet unless they are completely stuck, and you write down every pause. it takes about 20 to 30 minutes per user and finds problems faster than any analytics tool.

what to write down during each session:

- the first moment they hesitate, and what they tapped instead
- the moment their face or voice changes, positive or negative
- whether they finished the core action once

after five sessions the same pause will repeat. fix it before the next batch.

## A one-page user interview script

talk to every one of your first 50 users, ideally twice: once after the first session and once after the first week. use the same short script so answers are comparable. ask about what they actually did, not what they might do, because people are kind about ideas and honest about their own past behavior.

> **the problem (5 minutes)**
> 1. tell me about the last time [the problem] happened. what did you do?
> 2. what have you tried before to fix it? what was annoying about it?
>
> **the app (8 minutes)**
> 3. walk me through the last time you used the app. why did you open it?
> 4. when, if ever, did it first feel useful? what was on the screen?
> 5. what almost made you stop using it?
>
> **their words (5 minutes)**
> 6. how would you describe this app to a friend with the same problem?
> 7. if the app disappeared tomorrow, what would you use instead?
> 8. who else do you know who deals with this? can i mention you when i message them?

write answers to questions 4 and 6 word for word. they are your aha moment and your future marketing copy.

## What to learn from these 50

from the first 50 users you need three answers: do they come back without a nudge, what is the moment the app first felt useful (the aha moment), and what words do they use for the problem. write these down every week. later they become your onboarding, your store subtitle and your first ad hooks.

| what to learn | how to find it | what you do with it |
|---|---|---|
| retention | check who opened the app again in week two without a reminder from you | if almost nobody returns, fix the product before adding users |
| the aha moment | question 4, plus where their mood changed during onboarding | move that moment as early in the first session as you can |
| their words | question 6, copied word for word | reuse the most repeated phrases in your store page and posts |

retention is the share of users who come back after a set number of days. the [app growth metrics guide](https://www.appgrowthmarketer.com/learn/app-growth-metrics) shows how to track it.

## What not to do yet

do not run paid ads, do not do a big public launch, and do not build referral programs yet. each one sends strangers to an app whose first session is not proven. you burn money, or your one good launch day, on people who leave, and you learn less than you would from ten honest conversations.

paid is the most expensive mistake. in my experience, install costs of $3 to $15 kill an app whose early users are worth cents. also skip for now:

- launch sites and press, until people come back on their own
- vanity numbers like total signups or waitlist size
- features nobody in your 50 asked for

## A 14 day plan to your first 50 users

the plan below takes you from zero to around 50 hand-picked users, assuming the app already works on a phone. it costs almost no money and about two to four hours a day of your time. the goal at day 14 is not the number 50. it is three clear answers about retention, the aha moment and user language.

| day | what to do | time |
|---|---|---|
| 1 | build your list of names and mark who has the problem now | 2 to 3 hours |
| 2 | set up the beta build and basic analytics for opens and the core action | 2 to 4 hours |
| 3 to 4 | send the first 20 personal invites using the template | 1 to 2 hours a day |
| 5 to 7 | run onboarding calls and take notes on every pause | 2 to 3 hours a day |
| 8 | review notes, find the most common stuck point, fix it | a full day |
| 9 to 10 | send the next 20 to 30 invites, including introductions from the first group | 1 to 2 hours a day |
| 11 to 12 | run week-one interviews with the first group | 2 to 3 hours a day |
| 13 | ship the fixes from interviews and onboard the second group | a full day |
| 14 | write one page: who came back, the aha moment, the top ten phrases users used | 1 to 2 hours |

## When you are ready for the next stage

you are ready to move on when a clear share of your first 50 come back in week two without a reminder, you can name the aha moment in one sentence, and you have a page of their exact words. then stop recruiting by hand only, pick two channels, and follow the [first 100 users guide](https://www.appgrowthmarketer.com/playbooks/first-100-app-users).

if the answers are weak, the next two weeks belong to the product, not to marketing.

## Frequently asked questions

### How do I get my first 50 users with no audience?

start with people you can name. list everyone who has the problem your app solves, from your contacts, old coworkers, classmates and the groups you already belong to. message each one personally, onboard them yourself on a short call, and ask each one for a single introduction. fifty hand-picked users take effort, not an audience.

### Should I launch on Product Hunt to get my first users?

not yet. a big launch sends a spike of curious visitors to an app whose first session is not proven, and most of them leave for good. use your first 50 users to fix onboarding and find the moment the app clicks. launch once people come back without being reminded, so the attention lands on something that works.

### What should I learn from my first 50 users?

three things: whether they come back without a nudge, the exact moment the app first felt useful to them, and the words they use to describe their problem. those three answers shape your onboarding, your store page and your first ads later. almost everything else you could measure at this stage is nice to know, not need to know.