Launch day went fine. Some votes, a few kind comments, a nice bump in your analytics. Then Tuesday arrives and the graph is flat again. You have 23 signups, and you know four of them personally.
This is the most normal moment in a product's life. Launch advice tells you how to get attention for a day, not what to do on day eight.
Here's what I'd do. Most of it is slow, manual and slightly awkward, which is exactly why it works when you're small.
I'll use one made-up example throughout: Rosterly, a shift-scheduling app for independent coffee shops. Every number attached to Rosterly is an example to show the arithmetic, not a result anyone got.
Key takeaways
- Pick one narrow audience and politely ignore everyone else for now.
- Personal emails, DMs and onboarding calls bring the best users at this stage, even though they don't scale.
- Launch-week commenters are warm leads. Follow up within days, not weeks.
- Tag every link you share so you can see which channel produces real users, not just visits.
- Give each channel a fixed trial and a target, and stop the ones that miss.
Why 100 users, and why it takes longer than you expect
100 isn't magic. It's useful. With 100 people actually using the product you start seeing patterns: where they get stuck, who would pay. With 20 you're mostly seeing individuals.
Do the arithmetic before you start, because it keeps you honest. Say 400 people visit Rosterly's site in launch week and 8% sign up. That's 32 signups. If half of them publish a schedule, that's 16 real users. At that pace you'd need six or seven weeks like launch week to reach 100 - and launch-week traffic does not repeat on its own.
So the job is improving each step of that chain, and adding channels that keep producing after the spike fades.
Decide what counts as a user before you start counting. For Rosterly, it's a shop that published at least one week's rota. Signups feel good; this number tells you something.
Pick one narrow audience and say no to the rest
"Small businesses" is not an audience. "Independent coffee shops with 5 to 15 staff, where the owner still builds the rota in a spreadsheet every Sunday night" is.
Narrow feels risky. It's the opposite. With a narrow audience you know where they gather (local business groups, barista forums, coffee trade communities), your homepage can speak their language, and every user you win teaches you how to win the next one.
Here's what that does to Rosterly's headline:
- Before: "Smart scheduling for modern teams"
- After: "Your café's weekly rota in 10 minutes, sent to staff by text"
The second makes a café owner stop scrolling and a dentist keep going, which is exactly what you want.
Most advice says to keep your options open early. I disagree. You can widen later, and your first 100 users will tell you which direction - unless they're spread across ten industries.
Do things that don't scale, on purpose
Email every signup personally
Not an automated "Hi {first_name}". A real email from you, written to them. Something like:
Hi Maria - saw you signed up for Rosterly yesterday. I'm the founder. Quick question: what are you using for staff rotas right now, and what annoys you about it? - Kunjan
Short. One question. No links. The replies are the best product research you'll ever get.
Offer a 15-minute setup call
Offer to build their first rota with them on a call. Most won't take it. The ones who do tend to stick around, and you get to watch a real person get confused by your product in real time.
Set up their account for them
If someone sends you their current spreadsheet, import it yourself. The empty first screen is where many new users quietly give up, and you've just removed it.
This stops working past a few dozen users. Good. By the time it hurts, you'll know exactly what to automate.
Turn launch-day commenters into users
Everyone who commented on your launch already raised their hand. Most founders say thanks and move on.
Go back through every comment from launch week and, for each one:
- Reply publicly if you haven't yet.
- If they asked a question or raised a concern, answer it properly or fix it.
- If they fit your audience, send a short direct message: "You mentioned you run a café - would you try Rosterly for one week's rota and tell me where it breaks?"
Speed matters. Turn on whatever comment notifications your launch board offers and reply the same day. Wait two weeks and they've forgotten who you are.
Be honest about who's a fit. Other makers comment generously on launch boards, and most won't be your users. Thank them; don't chase them. If you haven't launched yet, my guide on where to launch a SaaS product covers how to space launches so each wave of commenters sees a better version.
Show up where your users already are
Write in public about what you're learning
Post what you're learning, not what you're selling. "Three café owners told me the same thing about rotas this week" will get more attention than "Rosterly now supports shift swaps!" And the second post lands better when it follows the first.
A rhythm you can keep up:
- One post a week about something a user taught you.
- One post when you ship something a user asked for, crediting them if they're happy to be named.
- A short monthly update with your real, small numbers.
This builds slowly. Don't expect it to bring your first ten users. Expect it to help with users 40 to 100, and to make your next launch easier.
Answer questions where they already hang out
Your users are already asking for help somewhere - a subreddit, a Facebook group for café owners, a hospitality forum, a Slack community. Show up and answer their questions.
The rules I stick to:
- Read each community's self-promotion rules first and follow them exactly. They differ a lot between groups.
- Answer the question fully without mentioning your product. Most of the time that's the whole reply.
- Mention it only when it's directly relevant, and say you built it. "Disclosure: I made a tool for this" is fine. Pretending to be a happy customer is not.
- Give far more than you take. If nine out of ten replies don't mention Rosterly, you're doing it right.
It's slow, but for a niche B2B product it's one of the most reliable channels I know. People who find you while asking for help arrive with the problem already in their head.
The founder welcome email and one simple referral ask
Make the welcome email sound like you
Your first automated email should read like the personal one. Plain text, from your name rather than "noreply". Say who you are, name the one thing they should do first ("publish your first rota"), and ask them to hit reply if they get stuck. Every reply is a conversation you wouldn't otherwise have had.
Ask for one introduction
Don't build a referral program yet. Just ask. When someone has used Rosterly for a few weeks and says something nice, reply:
Glad it's working. Do you know one other café owner who'd want this? Happy to set them up myself.
One person, not "share with your network". A specific ask gets a specific answer, and café owners know other café owners.
Measure each channel, and know when to stop it
Track real users per channel, not visits
Tag every link you share. Use UTM parameters (utm_source, utm_medium, utm_campaign) or a simple ?ref= tag so your analytics shows where each signup came from. Some launch boards do this for you - QikLaunch adds ?ref=qiklaunch and UTM tags to outbound visits - but for your own posts, emails and community replies, it's on you.
Then follow each channel all the way to real users, not just visits. Picture Rosterly's first month: the launch board sends 400 visits and 32 signups, but only 12 publish a rota. Meanwhile 40 personal DMs lead to 20 signups and 14 real users. On visits alone the launch board wins easily. On real users per hour spent, the answer is much closer, and the DM users are the ones who reply to emails and tell friends.
Here's how I'd rate the usual channels at this stage:
| Channel | Effort | Speed | Expected quality of users |
|---|---|---|---|
| Personal emails and DMs | High | Fast | Very high |
| Onboarding and setup calls | Very high | Fast | Very high |
| Following up launch commenters | Medium | Fast | Mixed - high if they fit your audience |
| Answering questions in communities | Medium | Slow | High |
| Writing in public about the build | Medium | Slow | Mixed, improves over time |
| Founder welcome email | Low (once) | Ongoing | Raises quality of everyone else |
| Asking happy users for one intro | Low | Medium | Very high |
| Launch board week | Low to medium | Fast, then fades | Mixed |
When to stop a channel
Give each channel a fixed trial and a target before you start. For example: "Answering questions in two café owner groups should produce five real users in three weeks." If it produces one, either change something meaningful (a different community, a different kind of answer) or stop.
A few signs it's time to stop:
- Lots of visits, few real users. You're reaching the wrong people.
- Good users, but it costs you ten hours each. Fine for now. Not fine at user 300.
- You dread it. You'll do it badly, and people will feel it.
Two exceptions: give slow channels like writing in public longer than three weeks, and never stop personal emails to new signups until you can't keep up.
Common mistakes on the way to 100
- Counting signups instead of real users. Pick your definition of a user and track that.
- Going broad too early. Five industries with five users each teaches you very little.
- Treating communities like ad space. One spammy post can get you banned from the place your users live.
- Quitting a channel after four days, or keeping a dead one for four months. Set the trial length up front.
Your first 100 users checklist
- Write down your definition of a "real user"
- Describe your narrow audience in one sentence
- Rewrite the homepage headline for that audience
- Send a personal email to every signup from launch week
- Reply to and follow up with every launch-week commenter who fits
- Turn the welcome email into a plain-text founder email
- Add UTM or ?ref= tags to every link you share
- Join two communities where your users ask questions, and read their rules
- Schedule one build-in-public post per week
- Ask every happy user for one introduction
- Set a trial length and target for each channel, and review weekly
FAQ
How long does it take to get your first 100 users?
It depends on your audience and how much manual work you put in. For many small products it takes weeks to a few months, not days. Run the arithmetic on your own visits, signup rate and activation rate to get an honest estimate.
Should I pay for ads to get my first 100 users?
Usually not yet. Ads bring visitors, but at this stage you need conversations, and paid traffic rarely replies to founder emails. Once you know which audience and message convert, small ad tests make more sense.
What should count as a "user"?
Someone who did the core thing your product exists for, not just someone who signed up. For a scheduling app that might be publishing a first schedule; for an invoicing app, sending a first invoice. Pick one action and stick to it.
Is it worth launching again to get more users?
Yes, once you've shipped meaningful improvements. A second launch with real fixes and a clearer pitch often does better than the first. Run through the launch checklist for indie makers again before you do.
Start with the 23 people you already have
You don't need a growth strategy for your first 100 users. Email the people who already signed up, fix what they tell you, and ask who else should know. Then do it again next week.
When you're ready for another wave of visitors, you can launch your product on QikLaunch for free and get a full week on the board.
Stay Up