How to Get Your First 100 Users

Your first 100 users usually do not come from large-scale ads.

They come from intense manual validation. You actively find people who may have the problem, talk to them, invite them to try the product, and observe whether they actually get value.

At this stage, scale is not the main goal.

You need to confirm:

Who truly feels the pain
Why they need a solution now
Whether the product solves enough for them to keep using it

If the first 100 users have unclear sources, weak demand, and shallow feedback, later growth will be fragile.

Define “User” First

Do not count visitors, likes, and followers as users.

For the first 100, define users by behavior:

Created an account
Completed the core action
Left feedback
Returned to use it again
Showed willingness to pay, book, or continue

If your product is a tool, the user should complete at least one core task.

If your product is a template or content product, the user should download, fill, apply, or share it.

If your product is B2B SaaS, the user should start a trial, book a demo, or import real data.

Your first users are not people who saw you.

They are people who tried to solve the problem.

Do Not Automate Too Early

Many founders want SEO, ads, short videos, or affiliates to bring the first batch of users.

Those channels can help, but early on they cannot be the whole strategy.

You still do not know:

Who the user is
What words they use for the problem
Why they do not convert
Where they get stuck
Whether they would recommend it

A large share of the first 100 users should come from manual outreach.

Manual outreach gives you reasons, not only conversion numbers.

Automated channels tell you whether people converted. Human conversations tell you why they did or did not.

Start With Five User Sources

Use five sources:

Existing relationships: friends, colleagues, ex-colleagues, community contacts
Target communities: Reddit, WeChat groups, Discord, Slack, forums
Content interactions: X, Xiaohongshu, YouTube, blog comments
Competitor signals: competitor reviews, alternative pages, user complaints
Active search: LinkedIn, GitHub, Product Hunt, industry directories

Do not vaguely say “find target users.”

Turn it into lists:

50 people who may have the problem
20 relevant communities
30 related posts
10 competitor comment sections
10 industry resource pages

First users usually do not arrive by waiting.

You find them one by one.

Open With the Problem, Not the Product

The common cold-start mistake:

Hi, I built a product that can help you...

It sounds like sales.

Better openers:

How do you currently handle this problem?
Which step wastes the most time?
Have you tried other tools recently?
If part of the workflow could be automated, what would you automate first?

You are not selling first.

You are checking whether the problem exists.

If they do not have the pain, do not force it.

If they describe a strong pain, then invite them to try the product.

Break Down 100 Users

Do not treat 100 as one large number.

Break it down:

20 from existing relationships
20 from target communities
20 from content interactions
20 from cold email or DMs
20 from directories, launch pages, and organic search

Each source needs actions.

For target communities:

Answer 5 questions daily
Publish 1 lesson-style post weekly
DM 5 people who express strong demand
Invite 3 users to try the product
Record 10 exact feedback quotes

Now the first 100 users become an execution plan, not a wish.

Give Users a Clear Trial Task

Do not only say “try it.”

Tell users what to do:

Upload one resume and check the match report
Enter one keyword and generate 20 long-tail ideas
Paste one email and generate three rewrites
Import one competitor URL and see review themes
Use the template to write your first cold email

The clearer the task, the more likely users complete it.

Early users should not have to explore everything alone.

Guide them to the aha moment.

Manual Service Is Fine

Do not fear manual work for the first 100 users.

You can:

Import data manually
Generate a report manually
Explain results manually
Follow up manually
Adjust templates manually
Organize feedback manually

This is not embarrassing.

Manual service helps you discover what should be automated.

Many products automate too early and end up automating a workflow users do not care about.

Confirm value manually first, then productize repeated actions.

Build a Feedback Loop

Every early user should go into a feedback table.

Record:

User source
User profile
Original problem
Trial task
Completion
Friction
Favorite part
Rejection reason
Willingness to keep using
Willingness to pay
Next follow-up

Do not only record “registered.”

You need to know why each person came, stayed, or left.

The first 100 users are valuable because of patterns, not only quantity.

When to Scale

Think about scaling when you see:

The same user type appears repeatedly
They describe the pain in similar language
Most users complete the core action
Some users ask about pricing
Some users recommend it to others
Feedback clusters around a few problems
You can clearly describe your best user profile

If these signals are missing, do not rush into paid acquisition.

Paid traffic amplifies problems.

If the conversion path is unclear, more traffic only creates more drop-off.

A 30-Day Plan

Use this:

Days 1-3: define the user standard and core trial task
Days 4-7: collect 200 leads and 20 communities
Days 8-14: contact 20 people daily and aim for 5 conversations
Days 15-21: get 30-50 people to complete the core task
Days 22-26: organize feedback and fix the biggest friction
Days 27-30: follow up for repeat usage, referrals, and payment signals

This is tiring.

But it forces you to face real users.

The first 100 users are not a growth trick.

They are a product truth test.

Summary

Define the first 100 users by behavior, not exposure
Do not rely only on automated channels early on
Open with the problem, not the product
Break 100 users into sources and daily actions
Give users a clear trial task and guide them to the aha moment
Manual service helps you discover what should be automated
Record each user's source, problem, friction, feedback, and next step

Next, we will cover how to find seed users.