How to Get Your First 100 Users for a SaaS

Your SaaS is live. A few people arrived on launch day, some created accounts, and now the graph has gone quiet. You need users, but another announcement saying "we're live" doesn't give anyone a new reason to care.

This is where the next stage begins.

Here is how to get your first 100 users for SaaS: choose a narrow group, get close enough to understand their work and repeat the routes that lead to useful product usage.

I would treat 100 as a learning milestone. The number matters less than knowing who those people are, why they joined and whether the product helps.

How do you get your first 100 SaaS users?

Start with personal invitations and supported onboarding, then expand one or two acquisition channels that bring suitable users back. A launch can introduce the product; continued distribution and a useful experience give people a reason to stay.

I would work through three stages:

These are planning checkpoints, not a measured formula. You may need to revisit onboarding well beyond user ten.

If the product hasn't launched yet, start with our no-audience launch plan. This article focuses on acquiring and supporting users after access is available.

Define what you mean by 100 users

A hundred email addresses, accounts and paying customers are three different milestones.

Choose a useful first action for the product. For an agency reporting tool, that could be preparing and sharing a client report. Logging in or clicking through a tour doesn't establish that result.

Keep four numbers separate:

• Signups: distinct people who create accounts.
• Activation: distinct users who complete the defined first task.
• Return usage: people who use the workflow again when needed.
• Customers: people or organizations that pay.

For a team product, count organizations alongside seats. Ten colleagues inside one company aren't ten independently acquired customers.

Also distinguish 100 people who have ever activated from 100 active users this month. The first can grow while recent usage falls. Record the observation window so the milestone keeps the same meaning.

Choose one buyer with one reason to act

An early acquisition message gets easier when you can name the situation. "Reporting software for everyone" gives you little guidance. "A workspace for small agencies preparing recurring client reports" points toward specific conversations.

Look for a current trigger: the next reporting cycle, a new client or frustration with an existing process. Ask how the person handles it today and what makes switching worthwhile.

Avoid assuming interest from a job title alone. An agency owner with a functioning workflow may have less reason to try you than an operations manager currently rebuilding reports every week.

Pick the segment as a working hypothesis. Record what you learn and change it if the people who get value differ from those you expected.

Start with beta users and waitlist contacts

Your warmest relevant contacts may already know what you're building. Tell former testers what changed and send waitlist subscribers a clear invitation to use the available product.

Don't ask them to rediscover the promise on a generic homepage. Point to the workflow they expressed interest in and explain any limits, pricing or setup required.

For example:

Hi [name], you mentioned [specific reporting problem] when you joined the list. [Product] now supports [relevant workflow]. You can try it here: [link].

The first task is [concrete result]. [Known limitation or access terms]. If setup gets confusing, reply and I'll help.

Adapt the message to what is true for that person. A signup months ago doesn't establish that the need still exists.

Our waitlist guide covers managing those expectations. The beta recruitment guide covers the earlier testing stage. Here, the task is helping interested people become actual users.

Recruit the first users personally

I would make a short list of people with evidence of the problem and contact them individually. Relevant introductions, professional communities and public questions can provide starting points.

Paul Graham's Do Things That Don't Scale describes Stripe's founders helping willing early users install the product themselves. The lesson is that closing the gap between interest and usage can require direct founder effort.

Your version might be a short setup call or help importing sample data. Offer assistance without taking over the work the user needs to learn.

A simple outreach message:

Hi [name], I saw your question about [specific task]. I built [product] for [audience] to [clear outcome]. It's available now, and I can show you [relevant workflow] if you're interested.

Would a short example be useful? If your current setup already handles this, no problem.

Keep it relevant and easy to decline. Don't scrape a community or turn a request for help into an unrelated sales pitch. Follow the rules of the channel you use.

Fix the first-use experience before increasing reach

Watch several suitable people attempt the task. Note where they stop, what information they need and whether the output meets the promise that brought them in.

If account creation works but connecting data fails, more announcements won't repair the connection. If the output is unclear, another feature may not be the next useful change.

There is research behind taking early experience seriously. In its 2025 B2B product benchmarks, Amplitude reported that 69% of top performers in week-one activation were also top performers in three-month retention.

That is an association in its benchmark data, not proof that any particular onboarding change causes retention or a target for your first 100 users. It supports checking what happens after arrival.

The wider report used anonymized behavior from more than 2,600 companies, covering September 2023 through September 2024. That mix of industries and company sizes is another reason not to treat the finding as a conversion forecast for a newly launched SaaS.

Record whether a user needed help to succeed. Assisted usage is valuable learning, but it isn't evidence that the self-service flow works equally well.

Test one direct channel and one discovery channel

Once suitable people can finish the task, choose a manageable acquisition mix. I would test a route where you can speak directly to prospects alongside a route where they can discover you independently.

Keep the audience, message and destination consistent enough to interpret what happens. Changing all three after every signup leaves you guessing which change helped.

Agree on a review window before starting. It should suit the channel: a newsletter placement and a search article won't develop on the same schedule.

Use communities to demonstrate the workflow

Share something useful enough to stand on its own: how you organize a report, a mistake you found or a short demonstration answering an existing question.

Explain that you built the tool. Check current posting rules and ask permission when needed. A community full of founders may be useful for a founder tool; it isn't automatically where every SaaS buyer spends time.

Segment provides a concrete example of audience fit. In a Y Combinator interview, co-founder Peter Reinhardt described early users arriving through an open-source library launched on Hacker News. Those users were founders dealing with analytics instrumentation.

The transferable point is the match between the product and the people present. It isn't that Hacker News should be every product's main channel.

For the mechanics of a Product Hunt release, use our launch guide for founders with no followers. Keep the acquisition goal separate from votes or leaderboard position.

Make directory listings earn their place

Directories can introduce a product to people comparing options. Select categories and descriptions around the buyer's task rather than submitting everywhere that accepts a URL.

Use the FasLaunch platform database to build a shortlist, then inspect current listings and eligibility. Send visitors somewhere that explains the same workflow as the listing.

Our guide to how many directories to submit to recommends manageable batches. For this campaign, the useful evidence is what people do after clicking.

A dofollow link or a high Domain Rating doesn't establish that a placement acquired users. Compare profiles and search observations separately from visits, activation and customer outcomes.

What an early founder report actually shows

In November 2022, Supademo founder Koushik Marka reported 340 signups, more than 250 user demos and 10 paying customers after a beta period and a recent public launch. He described Hacker News, Reddit, word of mouth and personal outreach among the routes used.

Those are founder-reported figures from one product at one point in time, not a universal acquisition benchmark. A demo count also isn't necessarily a distinct-user count.

What makes the account useful is the follow-through: conversations, collected feedback, product changes and continued updates. It illustrates why a launch result needs several measures rather than one headline number.

Don't copy its channel mix without checking whether the same people would need your product.

Ask for introductions after someone gets value

A relevant referral request works best when you can name the result the user just achieved. Ask whether they know one peer with the same problem, and offer a short explanation they can forward.

Don't make referrals a condition of getting support. If you test a reward, keep its terms clear and judge referred users by the same activation and return measures as other sources.

Also turn useful customer questions into content. A real explanation of how to migrate a report or compare outputs can help the next prospective user make a decision.

Get permission before publishing customer names, quotes, screenshots or results. A clear example using sample data can still demonstrate the workflow when a customer story isn't available.

Keep one acquisition record you can act on

Track the source, signup date, relevant use case, activation date, help required, return usage and payment status. A small table is enough while you can still recognize the people behind the rows.

For a hypothetical comparison:

Both cohorts need the same observation time. The outreach group is more promising here, but it may require more founder time, and these small invented samples don't predict future conversion rates.

Use our directory traffic tracking guide for source measurement. Keep first acquisition source distinct from the source of a later visit, and don't count one returning person as a newly acquired user.

Spend on evidence, not on a signup target

Paid acquisition can be a test once the offer and workflow are clear. Set a cash limit and decide what would justify continuing before buying traffic.

Include your time when comparing channels. Suppose a hypothetical experiment costs $100 plus three hours valued at $25 each. If five people activate, that is $35 per activated user. It isn't customer acquisition cost unless those five become customers under your definition.

Evaluate payment and retention before assuming that spend is sustainable. Lifetime revenue projections are especially uncertain when you have little history.

If suitable visitors repeatedly fail the same task, pause expansion and fix the blocker. If people succeed and return, test a little more of the source that found them. If one company accounts for most activity, look for independent evidence before generalizing.

If you are considering another public launch after changing the offer or product, use the SaaS relaunch guide to decide what the second attempt should test.

What should you have learned by user 100?

I would want a clear picture of the buyer, the task that activates them, the reason they return and the source that can reach more people like them.

You should also know which work still depends on personal assistance, why some users leave and whether paying customers receive enough value to stay. A hundred accounts alone can't answer those questions.

Use the 30-day post-launch plan to schedule user follow-up, product fixes and a review of what to repeat around this acquisition work. The SaaS launch checklist covers the surrounding operational tasks. When you want a public product page as part of discovery, review the FasLaunch launch options and give the listing a specific job in the plan.

Your first 100 users are an opportunity to learn how acquisition and product value connect. Keep talking to them while you work out what deserves to grow.