Most guides to your first 100 users list the same channels in about the same order. Almost none of them says the true thing first, which is that this phase is manual and the ugly ratios are part of the design. The founders who get through it fastest treat the grind as a lab. What follows is our take on how SaaS startups get their first 100 users in 2026, with real numbers wherever founders have shared them, plus a discovery layer the classic guides were written too early to see.
The truth the guides skip
Ask founders what actually got them their first hundred users, and the answers agree with a force that surprised me: nearly all of it came one person at a time. A recent thread asked exactly that, what worked in real life rather than in blog posts, and its top replies set expectations better than most guides.
what actually got you your first 100 users, not what the blog posts say
Just put my thing into beta and I'm trying to get to the first 100 users. Every guide gives the same three answers: post on reddit, do cold outreach, write content. All true, none of it tells me much about what actually moves the number. It...
Someone in there called it "hand-to-hand combat," and the phrase stuck with me. One builder posted the math: they'd contacted north of a thousand creators personally for 33 yeses, and only 6 ever paid. Another founder explained why the grind pays off beyond the users. The manual phase is where you learn which sentence about your product actually lands, and you can't hand that discovery to an assistant or a script, because the reactions are the data.
The scaled channels only start working once a few hundred users exist, and guides describe that part because it's easy to write down. It only feels discouraging if you expected a guide to hold the whole truth. Plan for hundreds of real touches at single-digit conversion, and log every conversation for what it taught you about the pitch.
The rooms where your users already are
Manual doesn't mean random. Your best hours go wherever your target users already ask questions, which usually means your niche's subreddits and Discords, plus its Slack groups and forums.
Everything in our community playbook counts double at this stage. Ten helpful answers in the right room beat five hundred cold emails to strangers, and an answer keeps working after you log off. So read a room's rules before you post, and answer the question someone actually asked, all of it. When the product you mention is yours, say so, and let your profile do the selling.
DMs work too if you're straight with people. Look for someone publicly wrestling with the problem you solve, on X or in a Discord or wherever your niche thinks out loud, and ask what they think of your approach instead of pitching them. Mention the exact post that made you reach out, since specific beats smooth in these messages. Feedback asks turn into users at a surprising rate, because you're offering status and involvement rather than asking for money.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews.
Directories and the new discovery layer
While the manual work runs, give one afternoon to distribution surfaces that keep working while you sleep. Launch platforms and startup directories still send a real trickle of early users. What's new is the AI layer on top of them. Buyers now ask ChatGPT and Perplexity "what tools do X" as often as they Google it, and the engines answer by reading directories and review platforms. That puts the AI-focused tool directories in front of people and the engines' retrieval at once.
We saw it ourselves. RankControl's earliest signups arrived through AI tool directories and referrals from AI engines, before classic Google traffic had moved at all. Young domains keep showing that same pattern of answer-layer visibility arriving before rankings, most of all on comparison-shaped questions. For those, a clear and specific page from a small site can win a citation while it still sits on page four of the SERPs.
So list on the two or three directories your buyers actually browse. Make your homepage say what the product is in one extractable sentence. Then, once a month, check whether the engines can answer "what is [your product]" correctly. It takes five minutes and catches identity problems while they're still cheap.
One piece of proof, not a content calendar
Hold off on the content calendar. What you need is one piece of evidence interesting enough that people pass it along. A benchmark or a dataset works, and so does a teardown, or the unusual thing you learned while building. At this stage it gives your outreach a reason to exist beyond the ask, and it hands the communities you're in something worth mentioning.
It also seeds the third-party surfaces the answer engines read. I'd take one artifact that really gets cited over ten thin posts, because it lets you open with "we measured the thing you're arguing about" instead of "check out my tool."
Your competitors are getting cited by AI. You're not.
Every day without citation tracking is a day your competitors pull ahead in ChatGPT, Perplexity, and Claude.
A week-by-week shape for the first month
All of this fits into a four-week opening a founder can run alongside everything else.
Week one is setup. Pick the two or three rooms your users actually spend time in and start reading them properly, then submit your directory listings. Fix the one-sentence answer on your homepage that same week, and run the five-minute engine check on your own name. Outreach starts in week two, where a steady rhythm beats bursts. Send a fixed daily batch of twenty to twenty-five personalized feedback asks and log each one, with your first helpful community answers going up alongside.
The proof piece ships in week three and goes to work right away. Put it in the rooms where it answers a live question, and use it in outreach as the reason you're worth a reply. Any directory that takes content should get it too.
Week four belongs to the people who came back. Interview everyone who returned without being prompted, then rewrite your core message in their words instead of yours. After that, repeat the middle two weeks until the count says 100. Most founders find the second month goes faster than the first, because the message has improved and the rooms know them.
The message log is the real asset
If I could keep one habit from this post, it'd be the message log. Founders who skip it end up running the same hundred conversations twice. Keep every conversation in one place, and write it up for patterns rather than nostalgia.
Three columns are enough. Note the objection you heard and the phrase that made someone lean in, and in the last column, the competitor or workaround they compared you to. By conversation forty, that log writes your onboarding copy and homepage better than any brainstorm could, and later your content plan, because every line in it was field-tested on a real prospect's face.
Five mistakes that burn the phase
Two of them come from spending before you've learned anything. Buying ads before you have message-fit gets you expensive confirmation that the pitch isn't ready. Launching everywhere at once is the other one. A single platform done properly beats five done at the same time and thinly, and you can only absorb one launch's worth of feedback anyway.
Automating your DMs throws away the reactions, which were the whole point. Pitching when you should be asking is a quieter version of the same mistake, since feedback requests open doors that sales messages close, and at this stage the feedback is worth more to you than the sale. Funny enough, the thread above had someone building a cold-outreach automation tool right in the middle of the discussion.
The fifth is counting signups when you should be counting returners. A hundred is the vanity number, and the one that carries the weight is how many of your first 25 came back on their own.
The checkpoint arrives at user 25
Around user 25 you reach the milestone that matters, since that's when you can see who comes back unprompted. It's also where founders who compound split from those who churn through user counts. One thread gave a six-day-old product advice I'd give anyone. Only 2 of its 25 users were coming back regularly. The reply said those two are the entire curriculum, and that the other 23 don't tell you much yet.
Ask those two what they pulled out of the product and what they were doing right before they opened it. That moment, the trigger and the payoff, is something you can't guess from analytics, and your next fifty outreach messages should be built around it.
If nobody has come back by user 25, pause acquisition. Filling a leaky cohort just burns the rooms you'll want later. Fix the day-three experience first, then go back to the well with something worth returning to. Once those returning users are ready to pay, our guide to getting your first paying customer covers the ask.
When the machine takes over
The manual phase does graduate, and the messages you validated by hand become its inputs. After 100, what scales is the compounding layer. That's content aimed at the questions your first users actually asked, structured for rankings and citations, published steadily and measured every week. Start the trickle earlier than feels natural, because the trust timeline lags months behind the work, and let it inherit everything the grind taught you.
That layer is our lane, so the pitch gets one sentence. When discovery turns into an operation instead of hand-to-hand combat, RankControl runs the content, the publishing and the per-engine citation tracking as one pipeline, and the founders who arrive with 100 hand-won users and a validated message get the most out of that pipeline fastest.
Until then, the advice costs nothing. The first hundred users get earned one at a time, and they're the only ones who can teach you the sentence the next ten thousand will hear. So pick your rooms and start the log this week. Get listed where the engines read, then build the proof piece while you question the people who came back.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
