About this case study
This is a modeled acquisition workflow built around a goal of 100 users, not a reported customer result or a promise that a specific number of conversations will convert.
Why the first users are a targeting problem
A founder has launched a useful app, but the phrase “get more users” is too broad to guide the next action. Posting the launch link everywhere may create impressions, yet it does not reveal who urgently needs the product or why they would switch from their current workaround.
The first job is to narrow the target from a demographic label to a problem moment. Instead of searching for “freelancers,” for example, the founder can look for people who say they lose track of invoices, chase late payments manually, or cannot see which client owes what.
Those phrases are valuable twice: they identify conversations worth joining and give the founder customer language that can improve the landing page, onboarding, and future content.
Define the user before searching for the channel
The founder can turn a vague acquisition goal into one focused campaign:
- Add the app website and a plain-language description of the problem it solves.
- Choose one ideal customer profile rather than trying to reach every possible user at once.
- Write down disqualifiers, such as enterprise buyers, students, or people looking for a free one-off solution.
- Generate problem-shaped search queries, then edit any phrase that sounds like marketing copy instead of a real complaint.
- Start with one use case and one promised outcome so responses can be compared meaningfully.
Build a weekly high-intent conversation queue
Amplispect can search public Reddit posts and comments, score each result against the campaign, and place the stronger signals near the top of the lead queue. A high score is a review shortcut, not proof that the author will buy.
On each weekday, the founder reviews a small batch, opens the original thread, and checks whether the problem is current, specific, and appropriate for a reply. The best response should solve part of the problem in public. A product mention belongs only where it genuinely adds to the answer.
Replies, direct responses, and lead status remain tied to the original conversation. At the end of the week, the founder can group what they learned: which pain produced replies, which objections repeated, and which words users chose without prompting.
The modeled operational outcome
The “first 100 users” target becomes a measurable acquisition practice: one narrow audience, a ranked queue of active problems, five review sessions, and a weekly record of messages that did or did not earn a response. Sign-ups remain an outcome to measure, not a number the workflow can guarantee.
The outreach guardrail
Do not treat Reddit as an email list. Respect community rules, disclose relevant affiliations, avoid repetitive promotion, and make every reply useful even if the reader never visits the app.
Frequently asked questions
What is the best way to get the first users for an app?
Start with a narrow problem and find people already discussing it. Founder-led conversations are useful early because they can create distribution and customer research at the same time. The right channel depends on where that audience naturally asks for help.
Does Amplispect guarantee the first 100 users?
No. Amplispect helps find and prioritize relevant public conversations. Conversion still depends on product fit, the usefulness of each reply, the landing page, onboarding, pricing, and follow-up.
Should every high-scoring lead receive a product link?
No. Open the source conversation and use human judgment. Some threads need a helpful answer without a link, while others are not appropriate to enter at all.
What should a founder learn from the first acquisition campaign?
Track which problem statements earn replies, which objections repeat, which audience segments show urgency, and where users drop between the conversation, landing page, and activation.