How do I get my first 100 users after launching a side project?

Start with a clear one-line description

A sharp one-line description is your first filter. It should say who the product is for, what it does, and why that matters in plain language. If people can repeat it without squinting, you are already ahead of the usual launch-page fog machine.

Use that sentence everywhere. It should show up in your outreach, your landing page headline, and your direct messages. If each channel says something slightly different, people will assume you are still figuring out what the product is, because, fair enough, you are.

Turn the description into a simple first-100 plan

Your one-liner is not just copy, it is a routing decision. It tells you where to look for users, which conversations are worth joining, and which channels are a waste of perfectly good evening hours.

If the description is vague, outreach gets weird fast. You end up pitching a product as a tool for everyone, which usually means it feels useful to no one.

Pick one narrow audience first

Start with the smallest group that clearly feels the problem. That makes your message concrete instead of mushy.

For example, do not aim at “creators” if you really mean “solo newsletter writers who post twice a week and hate manual scheduling.” The narrower version is easier to recognize, easier to reach, and easier to talk to without sounding like a brochure.

Match the channel to the audience

Go where that audience already reads, searches, or asks for help. If they hang out in niche communities, start there. If they search for fixes, build your outreach around the words they use. If they solve problems in public, show up there and be useful first.

The point is not to be everywhere. It is to be in the few places where your first users already have the problem.

Make each outreach message point back to the same promise

Your first sentence, landing page headline, and direct message should all point to the same promise. That way people do not have to re-parse the pitch every time they meet your product.

This matters more than people admit. Consistency is boring, but confusion is more expensive.

Build a lightweight acquisition loop

Treat early user acquisition like a loop, not a campaign. Find people, contact them, learn what they understood, then refine the wording and repeat.

If you do this well, each conversation makes the next one easier. If you do it badly, every message becomes a fresh guess, which is a great way to rediscover the same failure seven times.

Find early users through direct outreach

Reach out to people who already show the problem. Then ask whether your description matches what they need before you sell them anything.

That first contact can be short. You are not trying to close a deal in message one. You are trying to learn whether the problem is real, the wording is clear, and the person is even in the target group.

Use communities and public conversations carefully

Communities are useful, but only if you act like a human and not a notification with a sales plan.

Join relevant spaces to answer questions and notice the language people use. Mention your project only when it clearly fits the discussion. If you show up with a pitch in the first minute, people will correctly treat you like an ad wearing sneakers.

Ask for feedback before asking for signups

Early conversations are for learning, not just collecting emails.

Ask whether the one-line description is understandable, memorable, and accurate. If people misread it, change the wording. If they understand it but do not care, that is also useful. Slightly painful, yes. Useful, still yes.

If you are working on the launch page at the same time, What should a software launch page include on day one? helps because the headline, proof, and call to action should all carry the same message.

Worked example: from one-line description to first-user outreach

Suppose the vague version is: “A tool for social media management.” That could mean anything from a tiny scheduler to a sprawling dashboard that eats your afternoon.

A clearer one-liner might be: “A scheduling tool for solo newsletter writers who post the same content across multiple channels and want one place to queue it.”

Now the audience is narrower, the pain is clearer, and the channel choice gets easier. You might look in communities where solo writers talk about distribution, or in places where people discuss newsletter workflows and cross-posting.

A short outreach message could be:

“Hey, I built a simple scheduling tool for solo newsletter writers who reuse posts across channels and want one place to queue them. I’m checking whether that description matches your workflow. If it does, I’d love to hear what would make it useful.”

That message works because it repeats the same promise, asks for a response instead of a commitment, and gives the recipient an easy way to say, “Yep, that is me,” or “Nope, not even close.”

For the launch-page version of this same problem, What should a software launch page include on day one? is the right companion read, because the wording you test in outreach should also work as the page headline.

Avoid the common mistakes that slow first-user growth

Broad positioning is the classic trap. If your pitch tries to cover everyone, it becomes hard for anyone to see themselves in it.

Unclear benefits are another one. If people cannot tell what changes for them, they will move on before you get a chance to explain.

The other big mistake is changing the pitch every other day without learning from the last version. Some iteration is good. Random copy churn is not.

Side projects have even less room for this because they usually start with little trust and little traffic. You do not get many second chances to make the problem sound real.

What to measure in the first 100 users

Keep the metrics simple. You are not running a board presentation. You are checking whether the message opens doors.

Track things like:

• replies to outreach
• conversations that go past one message
• signups
• repeated interest from the same type of user

Those signals tell you whether the description is doing its job. If people reply but do not convert, the wording may be clear but the product promise may be off. If nobody replies, the audience or channel is probably wrong. If the same kind of person keeps asking for the product, that is a good sign you have hit a real nerve.

When to revise the description

Update the one-liner when people keep misunderstanding the product, when the same objection shows up across multiple conversations, or when the audience you are actually attracting is different from the one you meant to reach.

That is the moment to stop defending the original wording and start respecting the evidence. The point of the description is not to sound clever. It is to make the right people say, “Oh, that is for me.”

Related guidance for making the message easier to understand

If you want the launch-page version of this problem, What should a software launch page include on day one? is useful because the same wording should carry from your outreach into the page headline.

There is also a practical product-side example in TimeToPost’s API docs: “Everything you can click, you can script.” That line works because it is short, specific, and immediately tells you what the product is for. The same reference says the API docs use a short, specific line to explain what the product is for. That kind of clarity is exactly what your first-user message needs, just with fewer headers and less JSON.