How to get your first app users
Start with one reachable group that experiences the problem your app solves. Show a working task, invite a small number of relevant people to try it where participation is allowed, and watch whether they reach that useful outcome. Use their response to fix the offer or the product before increasing distribution.
This is an experiment for vibe coders and solo app founders with a usable product. It does not promise a particular number of users. If your product is still a waitlist, record interest separately from actual product use.
1. Choose people you can actually reach
“Anyone who needs productivity” does not tell you where to start. Write a specific audience, recurring task and place where that audience discusses the task. For an illustrative invoice app, that could be freelance designers who create invoices after each client milestone and ask peers about late payments.
Read several relevant conversations before promoting anything. Record the problem, source URL and what your app can genuinely do. A community with many developers is useful only if those developers are also your intended customers. Follow its participation rules; some communities do not allow product promotion.
The need behind this guide appears in first-person founder questions such as building an app but struggling to get users and finding the first users for a SaaS. These discussions illustrate the problem; they are not a representative survey or proof that a channel will work for your app.
2. Demonstrate one useful task
Record a short demonstration that starts with the customer’s task and ends with a real result. For the invoice example, show creating and sending a milestone invoice. Avoid a tour of every settings screen. Put the same task, current availability and next action on the destination page.
Invite people to try that task rather than asking them to support your startup. If signup, payment or a device installation is required, say so before they click. Make it easy to contact you when setup fails.
3. Ask for feedback with context
Use a message only where an invitation is welcome, and personalize it with a relevant observation. Disclose that you built the app. Do not scrape contact lists, mass-message communities or invent a relationship.
I built [app] for [specific audience] who need to [task]. I noticed [relevant problem from this conversation]. Here is a short demo of [working outcome]: [link]. If this is a problem you have, would you try [one task] and tell me where it helps or gets in your way? It currently requires [signup/device/payment, if applicable]. No pressure if it is not relevant.
A useful first interaction can also be a conversation about the task without a product link. Ask what people currently use and where that process fails. A polite decline is evidence to investigate audience fit, not an instruction to keep messaging.
4. Record the experiment, not just traffic
Download the free first-user experiment tracker (CSV). Open it in your spreadsheet app and use one row per experiment. It is a blank worksheet with no integrations or automatic tracking. Use aggregate counts and public source links rather than private user details.
- Reached: unique relevant people who received an invitation, if measurable. For a public post, use the platform’s reported reach and note its limits.
- Replied: people who responded. Questions and objections matter alongside the count.
- Visited and signed up: destination visits and registrations, recorded separately with the measurement method you use.
- Activated: people who completed the useful task you defined before publishing.
- Returned: activated people who used the app again within your stated review window.
Do not compare a platform’s impression count directly with unique people from another channel. Leave unknown counts blank. With small samples, preserve the raw numbers and observations; percentages alone can make weak evidence appear precise.
5. Fix the next constraint
If relevant people do not respond, review the audience, invitation and demonstration. If they visit but do not start, inspect the destination page and signup friction. If they start but fail to complete the task, watch a session with their permission and fix the product experience. If they complete it and return, test whether another similar group responds before widening the audience.
Change one main variable in the next experiment and record why. You may need several attempts to learn what matters; a quiet first launch does not identify the cause by itself.
Where AI and Crany fit
AI can group the evidence you provide, draft an accurate invitation and compare experiment notes. Ask it to separate observations from guesses. Our AI app marketing workflow includes a copyable execution brief, and the AI marketing tools guide compares available tools.
Crany.ai is an AI marketing co-founder in development by Tangenix. Its planned role is to strategize, execute marketing with your approval and improve based on results. Launch date, pricing and final integrations have not been announced. You can use this guide today or join the free waitlist for early access updates.
Related guides
- How to get your first 100 users: 10 from people you message, 40 from communities, the rest from posts and creators.
- How to market your app: a step-by-step plan for solo founders, before and after launch, with or without a budget.
- How to promote your app on Reddit: find threads that ask for what you built and reply without getting banned.
- How to find influencers to promote your app: find creators your buyers trust, qualify them and send a pitch they answer.