How to Get Your First 100 Users Without Paid Ads

The Short Answer

To get your first 100 users, start with manual work instead of paid ads. Find people who already feel the problem, contact them with context, onboard early users yourself, ask what almost stopped them, and track which channels create activated users rather than empty signups.

Most founders do not get the first 100 users from one big launch. They get them from several small channels: direct outreach, warm introductions, niche communities, useful content, small launch surfaces, referrals, and a product experience that gives people a reason to return.

The goal is not to collect 100 names in a spreadsheet. The goal is to find enough real users to understand who needs the product, why they try it, what blocks activation, and which acquisition path can be repeated.

What Counts as One of Your First 100 Users?

Before you chase a number, define what a user means for your product. A visitor, signup, activated user, active user, and paying customer are not the same thing.

For a SaaS product, a user may be someone who completes the core workflow, such as sending an invoice, publishing a page, or connecting a data source. For a developer tool, it may be someone who installs the package, integrates it, and completes a meaningful task. For an AI tool, it may be someone who reaches a useful output, not someone who merely opens the homepage. For a marketplace or community, it may be someone who completes the key participation action.

Choose the definition before you begin. Otherwise you may celebrate 100 signups while only three people ever experience the value you built.

First 100 Users Roadmap

Use the first 100 users as a learning sequence. Each stage has a different job.

This is not a fixed formula. A B2B SaaS with a narrow buyer may grow through founder outreach. A developer tool may need documentation, GitHub examples, and technical communities. A consumer app may depend more on sharing loops and audience-specific communities.

Stage 1: Users 1-10, Learn Before You Scale

Your first ten users should teach you more than they inflate your dashboard. Ten relevant users who feel the pain are better than hundreds of visitors who bounce.

Start by finding people who already show evidence of the problem:

• They asked about the workflow in a Reddit thread, GitHub issue, Slack group, Discord server, forum, or LinkedIn post.
• They are using an awkward workaround, spreadsheet, script, or expensive tool.
• They recently complained about the problem in public.
• They match the narrow user profile you described before building.

At this stage, avoid broad announcements. Send thoughtful one-to-one messages. Offer to help them solve the problem, not to make them sit through a pitch. If they try the product, onboard them yourself and watch where they pause.

Ask simple questions:

• What were you trying to do before you found this?
• What are you using today?
• What made this worth trying?
• Where did you get stuck?
• What would make you use it again?

The job of users 1-10 is not scale. It is clarity.

Stage 2: Users 10-25, Find Patterns

Once a few people have tried the product, stop treating every conversation as unique. Look for repeated words, objections, and activation problems.

Useful patterns include:

• The same user type replies more often than others.
• People describe the pain with similar phrases.
• Several users get stuck at the same onboarding step.
• One community or channel sends better users than the rest.
• People ask for the same proof, integration, export, template, or example.

This is where your positioning gets sharper. Replace vague copy like "manage your workflow better" with the words users actually use. If three people say, "I just need to stop copy-pasting reports every Friday," that is stronger than polished marketing language.

Keep outreach manual, but make the process repeatable. Save where you found each prospect, what problem they mentioned, what message you sent, whether they replied, whether they tried the product, and whether they activated.

Stage 3: Users 25-50, Repeat What Shows Signal

At 25-50 users, you should begin turning one or two working activities into a repeatable process.

Good options at this stage:

• Ask activated users if they know one person with the same problem.
• Write one useful tutorial that solves the manual version of the problem.
• Join discussions where the problem appears repeatedly and answer with real expertise.
• Submit to relevant product directories and launch surfaces.
• Partner with a complementary product, newsletter, community, or open-source project when the audience fit is natural.
• Add a short testimonial only after someone has genuinely used the product and agreed to be quoted.

If you have a launch-ready software product, list it on ShipNLaunch and other relevant discovery channels. Treat these as additional surfaces where interested users can find you over time, not as a replacement for talking to customers.

Stage 4: Users 50-100, Build Early Repeatability

By the time you approach 50 users, you should know which users are valuable and which channels bring low-quality traffic.

Double down on channels that produce activated or returning users. Pause channels that generate attention without usage. A post that brings 1,000 visitors and zero activated users may be less useful than a niche forum answer that brings four serious trials.

At this stage, useful work often looks like:

• Improving the onboarding step where good prospects drop off.
• Publishing content or documentation around problems users already search for.
• Creating examples, templates, sample projects, or walkthroughs that reduce time to value.
• Building integrations only when they unblock a repeated workflow.
• Encouraging referrals where the product naturally helps teams, clients, or peers.
• Preparing a stronger launch on a discovery platform once the product can demonstrate value quickly.

Do not pour more traffic into a product people do not return to. First 100 user acquisition and retention are tied together.

How to Choose Your First Acquisition Channels

Do not choose channels because other startups use them. Choose channels based on where your target user already spends time and whether the channel supports useful discussion.

Ask five questions before picking a channel:

1. Where does the target user already talk about this problem?
2. Can I reach them directly or contribute to the conversation?
3. Can they understand the product quickly?
4. Does the channel let me learn why people do or do not try it?
5. Can I repeat the process if it works?

Founder-Led Outreach Without Spamming

Founder-led outreach works when it is specific, relevant, and respectful. It fails when it feels like a disguised bulk email.

How to find prospects

Look for evidence of the problem before contacting someone:

• Reddit threads where people ask how to solve the workflow.
• Niche Slack or Discord communities where the topic comes up repeatedly.
• GitHub issues, discussions, or pull requests for developer products.
• LinkedIn searches for roles, tools, and pain-specific phrases.
• X conversations where people complain about the problem.
• Specialized forums and industry communities.
• Public communities around existing products that your tool complements.
• Founder networks where people match the exact problem profile.

How to contact them

Use a four-part structure:

1. Context: where you found the problem.
2. Problem observation: the specific friction you noticed.
3. Why you are reaching out: you are building or testing a focused solution.
4. Low-friction question: ask whether the problem is still painful or whether they would critique the approach.

Example:

"Hi Sam, I saw your comment in the analytics thread about exporting trial data into a spreadsheet every Friday. I am working on a small tool for that exact reporting workflow. If this is still annoying, would you be open to telling me where the current process breaks? No pitch, just trying to learn if I am solving the right part."

Customize every message. The point is not to trick people into replying. The point is to find people who already care.

Outreach Math: Track Your Own Funnel

Do not borrow someone else's conversion benchmark. Track your own funnel.

Prospects contacted
-> Replies
-> Product trials
-> Activated users
-> Returning users
-> Paying customers

If you need 10 serious conversations, you may need to contact more than 10 relevant prospects because some people will not reply, some will not have the problem, and some will try the product without activating.

Use a simple worksheet:

Illustrative example: if you contact 40 carefully chosen prospects and get 8 replies, 5 trials, and 2 activated users, the next step is not "send 4,000 emails." It is to understand why three trials failed to activate and whether the target profile was too broad.

Community Acquisition Without Being That Founder

Communities can help you find first users, but only if you participate like a member instead of an advertiser.

Bad: "Hey everyone, check out my SaaS."

Better:

• Answer the question fully even if your product is not required.
• Share the manual workflow, code snippet, checklist, or decision framework.
• Mention your product only when it genuinely solves the problem being discussed.
• Disclose that you built it.
• Keep listening after posting; replies are often more valuable than clicks.

Different channels have different norms. Reddit often rewards direct usefulness and punishes obvious self-promotion. Hacker News is better for technical products, thoughtful writeups, and Show HN launches. Discord and Slack groups can be strong for trust but usually require ongoing participation. LinkedIn can work for B2B workflows when the buyer is identifiable. X can help when your audience already discusses the problem in public.

Not every product belongs on every channel. Choose the communities where the problem is already active.

Launch and Discovery Channels

Launch platforms are distribution channels, not proof of product-market fit. They can create attention, backlinks, early feedback, and discovery, but they cannot rescue a product that users do not understand or return to.

Use each channel for a purpose:

• Hacker News / Show HN: good for technical products, developer tools, infrastructure, open source, and clear demos. Read the Hacker News launch guide before posting.
• Product Hunt: useful for polished demos, visual products, broad software categories, and social launch momentum. Compare options in the Product Hunt alternatives guide.
• Product directories: useful for durable discovery and category-specific search surfaces.
• Niche directories: useful when your audience browses by category, stack, profession, or workflow.
• ShipNLaunch: useful as an ongoing product-discovery surface for SaaS, AI tools, developer tools, and indie software after you have a clear product page. You can browse products or submit your product.

The best launch asset is not a dramatic tagline. It is a product page that quickly explains who it is for, what problem it solves, what the user can do first, and why the product is credible.

Getting the First 100 Users Depends on What You Built

Different products need different acquisition paths.

SaaS

For SaaS, start with problem-aware prospects. The strongest early channels are usually founder outreach, warm introductions, niche communities, practical tutorials, launch sites, and relevant directories. If the idea is still uncertain, validate demand before scaling by using the SaaS idea validation guide.

AI tools

For AI tools, people need to see the output. Use demos, before-and-after examples, workflow-specific prompts, use-case communities, and content that shows the tool doing real work. The AI tool launch guide covers positioning, demos, trust, and distribution in more detail.

Developer tools

For developer tools, usefulness is often judged through documentation, examples, GitHub activity, package installation, and technical credibility. Good early channels include GitHub, Hacker News, technical forums, open-source communities, docs, tutorials, and the developer tool launch guide.

Consumer or mobile products

Consumer products usually need different sharing dynamics. Founder-led B2B outreach may not be enough. Look for audience-specific communities, creator partnerships, referral loops, clear use cases, and moments where users naturally want to invite others.

How to Learn From Your First 100 Users

The first 100 users should improve your product, positioning, onboarding, and channel strategy.

Ask questions that expose behavior:

• What were you trying to do?
• What were you using before?
• Why did you try this?
• Where did you get stuck?
• What almost made you leave?
• What would make you use it again?
• What would make this worth paying for?

Listen for patterns rather than treating every request as a roadmap item. One person asking for a feature is a clue. Five similar users describing the same blocked workflow is stronger evidence.

Keep a lightweight feedback log with the user's segment, source channel, activation status, quote, objection, and next action. This helps you avoid building for the loudest user instead of the most important pattern.

Retention Before More Traffic

If people arrive but do not return or complete the core workflow, more traffic may simply create more churn.

Watch:

• Activation: did users reach the first useful outcome?
• Repeat usage: did they come back without being pushed?
• Time to value: how long until they see the benefit?
• Drop-off points: where do good prospects stop?
• Support questions: what do users repeatedly misunderstand?
• Qualitative feedback: what do people say almost made them leave?

Pause acquisition when the product clearly fails to deliver the promised value. Keep acquiring when you need more conversations, the product is improving, and a meaningful share of relevant users are activating.

A Practical Four-Week Execution Plan

This plan does not promise 100 users in four weeks. The timeline depends on the market, product type, trust required, price, and audience size. Use it as an execution rhythm.

Repeat the loop until you understand which user, message, channel, and onboarding path produce useful users.

First 100 Users Checklist

Frequently Asked Questions

How do I get my first 100 users?

Get your first 100 users by combining manual founder outreach, warm introductions, niche communities, useful content, launch platforms, referrals, and retention improvements. Start with people who already feel the problem, onboard them yourself, and repeat the channels that produce activated users.

How long does it take to get 100 users?

There is no universal timeline. A simple free tool with a visible audience may reach 100 users quickly. A B2B SaaS that requires trust, integrations, or workflow change may take much longer. Measure learning quality, activation, and retention instead of judging only speed.

Where do startups find their first users?

Startups find first users through founder networks, direct outreach, Reddit, Hacker News, Discord, Slack groups, LinkedIn, X, GitHub, niche forums, product directories, launch platforms, and early content. The right source depends on where the target user already talks about the problem.

How do I get users without paid advertising?

Use channels that create conversation and intent: direct outreach, community participation, tutorials, documentation, referrals, launches, and directories. Paid ads can produce traffic, but early founders usually need qualitative learning before scale.

How do I find beta users?

Find beta users by looking for people already discussing the problem, using awkward workarounds, or asking for recommendations. Be clear that the product is early, offer personal onboarding, and ask for feedback on real workflows instead of vague opinions.

Should I offer the product for free?

Free access can reduce friction for learning, but it can also hide weak demand. If the product saves money or time for a business, test commitment through a paid pilot, small plan, annual discount, or serious time investment before assuming free users will convert.

Should I use Product Hunt for my first users?

Product Hunt can be useful if the product is easy to understand, visually demonstrable, and ready for a public launch. It is less useful if you still need private discovery conversations or the product cannot activate new users quickly.

Is Reddit useful for finding users?

Reddit can be useful when you answer real questions, understand subreddit rules, and avoid link dropping. It works best when the community already discusses the problem and you can contribute useful advice even without mentioning your product.

When should a startup start SEO?

Start SEO when you know which problems your target users search for and can publish genuinely useful pages around them. Early SEO should come from customer language, documentation, comparisons, tutorials, and problem-solving content, not generic keyword pages.

Should I automate cold outreach?

Do not automate outreach too early. First, learn which user profile, problem statement, and message earn real replies. Automation before clarity usually scales bad targeting and weak positioning.

What is more important: acquisition or retention?

Early acquisition and retention are connected. You need acquisition to create learning, but if relevant users do not activate or return, more traffic will not fix the product. Improve retention before scaling a channel aggressively.

What counts as an active user?

An active user is someone who returns to perform the product's meaningful workflow. For SaaS that may be completing a core task. For a developer tool it may be installing and using the integration. For an AI tool it may be producing a useful output more than once.