How to Get Your First 100 SaaS Users

Quick answer: Reach your first 100 SaaS users by combining one direct channel, one community or partnership channel and one compounding discovery channel. Recruit users in cohorts, onboard them closely, measure activation and repeat use, and double down only when a source produces qualified users—not merely sign-ups.

The first 100 users are a transition. You still need founder-level observation, but patterns should begin to replace anecdotes. The goal is not the number alone; it is evidence that a defined audience can discover the product, reach value and return through a process you can repeat.

Decide which 100 users count

Define eligibility and success:

• Match the intended customer profile.
• Complete a meaningful activation event.
• Use the product with real data or a real task.
• Consent to appropriate communication.
• Have an opportunity to return within the natural usage cycle.

One hundred accounts created by a giveaway can look impressive and teach almost nothing. Use the onboarding checklist to define first value.

Use a three-channel portfolio

Direct: founder outreach

Contact narrowly matched prospects with a relevant problem statement. Direct outreach gives fast feedback and precise control over audience quality. It should remain part of the mix until you can predict which users activate.

Follow the first 10 SaaS customers guide for discovery and pilot structure.

Concentrated: community or partnership

Find places where the audience already gathers: a professional community, niche newsletter, integration partner, agency network or specialist creator. Contribute useful information before asking for attention.

Good partnership offers exchange real value: an educational workshop, useful template, integration, data analysis or audience-specific benefit. Do not post the same promotional copy across unrelated communities.

Compounding: searchable content or directories

Create an accurate product profile, one comparison or guide tied to the problem, and listings on relevant discovery platforms. These assets can continue to answer research queries after the launch day.

Start with places to launch a SaaS and learn how to use startup directories for distribution.

Recruit in cohorts of 10–20

Do not open a fragile product to 100 people at once. Invite a cohort, observe onboarding, fix the highest-impact problem, then invite the next.

Example sequence:

Release numbers are illustrative. For a high-risk or complex product, cohorts may be smaller.

Build one useful launch asset

Instead of “We launched,” give the audience something that explains the problem:

• a benchmark or original dataset;
• a transparent build breakdown;
• a template or calculator;
• a teardown of current workflows;
• a short demo using a realistic example;
• a migration or setup guide.

The product becomes the next step for people who recognize the job. This performs better over time than a generic founder story with no user value.

Use communities without being promotional

Read the rules and recent discussions. Answer questions with complete, standalone value. Mention the product only when it materially helps and disclose your connection. Hacker News has specific Show HN guidelines; communities such as Reddit may change self-promotion rules, so check current policies before posting.

Community participation is a relationship, not a distribution endpoint.

Turn product usage into invitations

Referrals work when collaboration or sharing is natural. Examples:

• a report shared with a client;
• a public page with optional attribution;
• inviting a teammate to complete a workflow;
• an export that links to a useful interactive version.

Do not add forced branding to paid or sensitive outputs. Track whether invitees activate, not only whether invites are sent. If a waitlist or referral campaign fits, compare SaaS waitlist tools.

Measure the path from source to repeat use

Use a compact table each week:

Add qualitative notes: top promise, top objection and onboarding blocker. A source with fewer sign-ups but better activation may deserve more effort.

A six-week plan

Week 1: Define ICP, activation and instrumentation. Recruit 10 direct users.
Week 2: Fix the largest onboarding failure. Recruit the next cohort.
Week 3: Publish one useful launch asset and submit to relevant directories.
Week 4: Run one focused community or partner activity.
Week 5: Improve repeat use and ask activated users for introductions.
Week 6: Compare channel cohorts and choose one motion to repeat.

The timeline is a working cadence, not a promise that every product reaches 100 in six weeks.

Common mistakes

• Counting unqualified sign-ups as users.
• Launching on many platforms without source attribution.
• Changing the target customer to explain every new signup.
• Automating onboarding before watching real failures.
• Writing broad content unrelated to the product's problem.
• Offering referral rewards before retention exists.
• Failing to contact users who reached or missed value.

Frequently asked questions

Should the first 100 users be free?

Not necessarily. Charge when payment is part of the business hypothesis. You can mix paid customers, design partners and limited free users, but label cohorts clearly.

Is paid advertising useful this early?

Small tests can validate messaging or a known high-intent channel. Ads are risky when activation, retention and customer value are still unknown.

Which launch platform is best for early users?

It depends on audience: Product Hunt for broad tech discovery, Hacker News for technically interesting demos, Indie Hackers for founder context and niche directories for durable discovery. Compare them in Product Hunt vs Indie Hackers vs Hacker News.

What comes after 100 users?

Improve retention, identify the strongest segment and repeat the best source. Do not scale acquisition into a product that users do not repeatedly value.

Sources and further reading

• Hacker News: Show HN guidelines
• Product Hunt: Launch guide
• Amplitude: Activation rate