Quick answer

You find your first 100 users by naming a specific person with a specific problem, then reaching them directly in the places they already gather rather than waiting for a broad launch to bring them in. Start from a narrow definition of who the product is for, list the communities and channels where those people show up, and talk to them one by one. Use each conversation to confirm the problem is real and to invite people in. The goal is not scale at this stage; it is a small group of real users whose feedback you can act on.

Start narrower than feels comfortable

A vague target audience is the main reason early growth stalls. "Small teams" is too broad to act on, because you cannot find a single place where all small teams gather or write a message that speaks to all of them. A narrow definition, such as a founder selling a Chrome extension to developers, gives you concrete places to look and a message that fits.

The narrow focus also makes the product sharper. When you know exactly who you are serving, you can decide which features matter and which requests to ignore. The audience can widen later; the first 100 users work best when they share the same problem and speak the same language.

Map where these people already are

Once you know who the person is, list the places they spend time: specific communities, forums, newsletters, events, or professional groups. Aim for a concrete list of channels you can actually reach, not a generic list of social platforms. The best channels are the ones where the problem is already being discussed.

Write down the channel, the kind of conversation that happens there, and how you can contribute. This turns "get users" into a set of specific actions you can work through. A short list of five well-chosen places beats a long list of platforms where your audience barely shows up.

Talk to people before you pitch

Early conversations should be about the problem, not a rehearsed sales pitch. Ask how people handle the task today, what it costs them in time or money, and what they have tried that did not work. The answers tell you whether the problem is painful enough that someone will switch, and they often surface the exact words people use to describe it.

These conversations are also the honest route to early users. Once someone confirms the problem and you explain that you are building for it, the invitation to try it feels natural. People who feel heard are far more likely to give a new tool a real chance than someone who only saw a generic announcement.

Use a simple tracking list

Keep a basic list so you can see progress and follow up. You do not need a complex system at this stage; a table with the person, where you found them, the problem they described, and the next step is enough.

Field What to record
Person Name and how to reach them
Source The community or channel
Problem The pain in their words
Stage Contacted, tried, or giving feedback
Next step The follow-up and when

Tracking prevents the common mistake of having many conversations that never turn into invites, and it shows how many real users you actually have versus warm leads.

Convert conversations into active users

The first 100 should be people who actually use the product, not names on a list. After inviting someone, help them reach a first result, then follow up on what worked and what blocked them. Close the loop by acting on the feedback and telling them what changed, which turns a trial into a retained user. If you want the first impression to land cleanly, Neatico helps a new user turn a single prompt into a finished deck or set of social assets so the first result comes quickly.

This is the practical side of the broader first 100 users guidance.

The bottom line

Define a narrow person with a specific problem, then list the concrete places they gather and talk to them one by one about the problem before you pitch. Track each conversation and turn invites into active users by helping them reach a first result and acting on their feedback. The first 100 users come from specific, repeatable conversations, not from guessing or waiting for a broad launch.