TL;DR
Your first 100 SaaS users usually come from solving a narrow problem well, reaching people who already have that problem and making the first product action easy. Start with 10 conversations, then a small group of relevant testers, measure who reaches first value, and repeat what works. Directory submissions and launch boards can help discovery, but they rarely replace direct feedback, onboarding improvements and persistent distribution. “100 users” is a milestone, not a promised timeline.
Key Takeaways
- Define the difference between visitors, signups, activated users and paying customers.
- Find early users where a specific problem is discussed, rather than broadcasting to “startup audiences.”
- Ask for feedback and show a usable demo before requesting a purchase.
- Turn common questions into content that people can find later.
- Track referral sources and the first successful action inside your product.
- Revisit retention before scaling acquisition.
First, Define What a “User” Means
A waitlist email is not a product user. A signup that never completes setup is not an activated user. A person who uses the tool once may not be a retained user. Founders sometimes celebrate 100 signups while nobody reaches the core feature; that number is not particularly actionable.
Choose one activation event that represents real value. For a screenshot tool, it could be a completed capture. For a CRM, creating and using the first deal. For a study app, successfully scheduling and completing the first session. Keep the event understandable and instrument it in your analytics.
Step 1: Find Ten People Who Have the Problem Right Now
Search for the exact job your product does rather than “SaaS feedback.” Look through relevant subreddits, professional communities, product support threads and industry discussions. Start with the person's current workaround: spreadsheet, copy-paste process, WhatsApp message, manual daily report or expensive legacy software.
Make a small evidence sheet:
| Problem mentioned | Who mentioned it | Current workaround | Urgency signal | Permission to follow up |
|---|---|---|---|---|
| Example: onboarding approvals scattered | Agency PM | Chat + documents | Repeated this week | Yes / No |
Do not scrape personal information or send unsolicited messages indiscriminately. A public complaint isn't automatic permission for a sales pitch.
Step 2: Offer a Specific Improvement, Not a Grand Promise
Your first outreach should make it clear why this conversation is relevant. A useful note might be:
> I saw your comment about updating the same client status in three tools. We're testing a workflow that connects the update to the project. Could I show you a 45-second demo and ask whether it solves the part you described?
This is a template; only use it when you genuinely saw the comment. Do not claim to have audited someone's business when you have not.
Ask what happens after they try the tool. Where do they hesitate? What information is missing? Which step makes them return to their old workaround? Those answers are more valuable than a generic rating.
Step 3: Recruit a Small, Coherent Beta Group
Choose a cohort around one use case. Ten HR recruiters testing candidate screening are more useful for a recruiting tool than ten random tech enthusiasts. Share a simple onboarding path, a clear feedback channel and an honest expectation for support or limitations.
For each tester, record:
- how they found you;
- whether they attempted the core action;
- whether it worked;
- what blocked them;
- whether they would repeat the task;
- whether they would recommend it to a colleague with the same problem.
Never invent usage success or publish a testimonial without permission.
Step 4: Fix First Value Before Finding Fifty More People
Suppose 40 relevant people arrive, 12 create accounts and only two finish the first useful task. More traffic may produce more abandonment. Ask one tester to perform the flow without coaching. Watch for confusing labels, excessive forms, unclear sample data, permissions and missing error explanations.
Typical improvements include a sample workspace, starter template, clearer empty state, guided import and a demo that accurately shows what happens. Pick the highest-friction point and test one change at a time.
Step 5: Use Three Different Discovery Channels
Useful Search Content
Write a guide to the problem, including the manual method and where it breaks down. People searching “how to track freelancer approvals without spreadsheets” may be more qualified than those searching “new SaaS launches.” Provide an answer even if they never choose your software.
Relevant Communities
Engage in discussions rather than distributing identical launch announcements. Answer questions, show a real learning and request feedback only when it fits community rules. Avoid paid votes or manufactured engagement.
High-Fit Directories and Launch Boards
A directory can create a lasting profile; a launch board can create a short event. Product Hunt is free; Show HN is for usable projects. Founders of eligible Indian-made software can list free on TechProductIndia. Do not expect any one site to deliver 100 users.
A Simple Illustration of the First 100
Use this as a planning example, not a conversion benchmark. Imagine 800 relevant visitors across a few channels, of whom 160 sign up. If half complete the core action, that's 80 activated users. If another 20 activate through direct demos, you reach 100. The numbers are hypothetical: real products will have different rates.
The value of the funnel is that you can locate the problem. If your visitors are irrelevant, improve targeting. If signups are low, improve the offer or clarity. If activation is low, improve onboarding. If usage drops the next week, investigate retention.
Make Your First Users a Source of Better Distribution
After someone successfully uses the tool, ask what task they completed and how they would describe it to a colleague. With their permission, turn a genuine workflow into a short example. A specific account of how a task was done is stronger than a fabricated “loved by thousands” line.
The next content piece could explain an objection, integration or failure mode that came up repeatedly. This creates a search asset anchored in real user problems rather than keyword padding.
When to Ask People to Pay
Do not delay all commercial conversations until you have 100 users. Ask early prospects whether they have budget, who authorises a purchase and what they pay for the current solution. Your pricing may be wrong even if the product is useful. A small group of paying users who return often can be more meaningful than a large free cohort that never activates.
A Weekly Scorecard
| Metric | Why it matters |
|---|---|
| Relevant visitor source | Where the right people discover you |
| Signup-to-first-value | Onboarding success |
| Repeat use | Whether the problem occurs again |
| Reasons for drop-off | What blocks activation |
| Customer conversations | What you learned about the job |
| Paid intent / conversions | Business viability |
Do not judge the cohort solely by likes, votes or directory submission counts.
The Bottom Line
Start narrow: a real user, a real problem and one completed task. Learn directly, fix the first-use experience, publish evidence and test a few targeted discovery routes. Your first 100 users should teach you why people return—not merely prove you can collect 100 email addresses.
Next: For an eligible Indian-made SaaS, create a free TechProductIndia listing as one trackable discovery source while continuing direct buyer research.


