From Launch to Your First Hundred Users

The first hundred users are special. They are not yet a market, and not just friends. They are the people who will tell you, in unfiltered words, what your product is for, and the ones who will show you where it breaks. Most of what you learn about your product in its first year, you will learn from them.

This guide covers the stretch from launch to a hundred real users. It treats it as a stage with its own question, its own methods and its own traps, and not as a smaller version of what comes later.

The question at this stage

After launch, the question is: do strangers who arrive use the product, and do any of them come back? You are not trying to find a growth engine yet. You are trying to find the people for whom the product matters, and to learn why.

That changes how you work. At this stage, doing things that do not scale is not a flaw. It is the point. One conversation with a user teaches you more than a thousand impressions.

Define a user

Decide what counts. A person who visited the page is a visitor. A person who signed up may be a lead. A user, for the purposes of this milestone, is someone who has completed the main action at least once: made the list, sent the invoice, saved the first note.

Write the definition down and stick to it. If you count anyone with an account, you will reach a hundred quickly and learn little. If you count only people who return weekly, the figure is smaller and far more informative. Track both, and be clear which one you are talking about.

Where the first users come from

Early adopters, the people who try new products before most, tend to be reachable through direct, personal routes. The usual sources are:

• People who know you, and whose problems match the product. Not everyone you know, only those who fit.
• Communities where you already take part, where you have a reputation for being useful.
• Direct outreach to people who have publicly described the problem.
• Directories and launch platforms where people look for new products.
• Referrals from the first users, if they like it.
• Your own content, such as a useful guide that solves part of the problem.
• Search, over time, as your pages become findable.

Word of mouth, the informal passing of information between people, is the cheapest and most credible. It is also slow and unpredictable, which is why you pursue several routes while you learn which one works.

A weekly routine

Treat the stage as a series of weeks, each with a simple cycle.

1. Reach out. Each week, contact a fixed number of people who might need the product, in a way that is personal and respectful. Do not mass-send.
2. Onboard. For each who responds, help them get to first use. Watch where they struggle.
3. Listen. Ask each user two or three questions: what were you trying to do, what happened, what would you change?
4. Fix. Pick one or two problems that appear repeatedly and fix them.
5. Record. Log the count of users, where they came from and what they said.
6. Review. At the end of the week, decide what to repeat and what to drop.

The cycle is simple on purpose. It keeps you close to people and moving fast.

The conversations

Talking to users is the highest-value activity at this stage. Do it often, and do it well.

• Ask about behaviour, not opinions. "Tell me about the last time you did this" yields more truth than "would you use this?"
• Listen for the words they use, and borrow them for your page.
• Do not defend the product. When someone criticises it, thank them and ask more.
• Ask who else has the problem, and whether they would introduce you.
• Ask what they used before, and why they stopped.
• Record the call or take notes, with permission.
• Talk to people who left, as well as people who stayed. They tell you what the stayers will not.

A tip for the first few: talk to five and look for patterns before changing anything.

Reading early numbers

With small numbers, be careful.

• Percentages mislead. Three out of five is sixty per cent, but it is five people. Look at the counts.
• One source can dominate. A single mention may account for half your users. Note it, but do not call it a channel.
• Weekly figures bounce. Look at several weeks together.
• Retention beats arrival. A hundred people who never return is a weaker result than thirty who come back every week.

Keep a simple table: week, new users, returning users, source. A few columns tell you most of what you need.

Finding what brings people back

The most important learning at this stage is why some users stay. Ask them. Look at what they have in common: the problem they had, the way they found you, the first thing they did.

Often there is a single feature or moment that makes the product click. For one product it might be the first time a shared link works. For another, it is the first report. Once you know it, restructure the first-use path to reach that moment faster. This is usually the biggest single improvement available.

Traps at this stage

Chasing volume. Buying traffic or posting everywhere may produce a spike, but if the users do not stay, you have learned little.

Building for the loudest voice. One enthusiastic user may want features that nobody else needs. Look for repeated requests.

Ignoring the leavers. Silent departure is the biggest source of lost learning.

Giving up on personal contact too soon. Automating outreach before you understand what works scales the wrong thing.

Counting vanity numbers. Followers and views are comforting and mostly irrelevant here.

Over-promising. Telling early users what the product will do, and then missing it, costs the trust you most need.

Neglecting support. Early users who get no reply tell their friends.

Setting up for the next stage

By the time you approach a hundred, a few things should be clearer.

• Who the product is for, in more detail than before.
• The one or two ways people find you that work.
• The moment at which people see value.
• The most common reasons people leave.
• A short list of what to build or fix next.

These become the inputs for the next stage, repeatable growth, where you try to make arrival predictable. If you cannot answer them, spend more time on this stage rather than skipping ahead.

Public notes

You can share progress openly. A short note on what you have learned, what you have changed and what you are working on next builds trust and often brings in more users. Be honest: say how many you have, and what has gone wrong. Readers value candour from early products, and it makes later successes more credible.

A worked example

A maker launches a tool that helps community gardens manage plot allocations. In week one, he emails twelve garden coordinators he found in a public list, each with a personal note referring to something on their site. Four reply; three try the tool. He watches one on a video call and sees her struggle to find the plot map, which is behind a menu. He moves it to the first screen.

Week two, he posts in a forum for allotment holders, with a short account of why he built it. Eleven people try it, five complete the main action. He calls four of them and learns that the feature that matters is the waiting list, which he had thought was minor. He rebuilds the first screen around it.

By week six he has sixty-two users who completed the main action, thirty-one of whom returned the following week. Two-thirds came from direct outreach and the forum. He notes that people who reached the waiting list in their first session stayed at far higher rates. At about ninety users he writes a short public update and sets his next milestone: ten gardens using the waiting list weekly. He reaches a hundred in week eight, and, more usefully, he knows what the hundred have in common.

Questions makers ask

What if I stall at forty? Look at where people drop out and talk to them. A stall is often a first-use problem or an audience mismatch.

Do I need a public changelog? It helps, and it shows that someone is listening.

Should I charge now? That is a business decision. Charging can teach you about value; free use can teach you about habit. Be clear with users about which you are testing.

How do I handle support? Answer fast and personally. At this scale, it is also a research channel.

Summary

The first hundred users are the most informative you will have. Define a user as someone who has completed the main action, find them through personal and direct routes, and run a weekly cycle of outreach, onboarding, listening, fixing, recording and reviewing. Talk to users, including the ones who leave, read small numbers carefully, and find the moment that makes people stay. Avoid chasing volume and over-promising. By a hundred, you should know who it is for, how they find you and why they stay.