How to get your first 100 users for a SaaS, one by one
You get your first 100 users by recruiting them one at a time, not by waiting for a launch to send traffic. Pick a narrow group who need your product now, contact them directly, help them set it up, and ask what is missing. Paul Graham's essay "Do Things that Don't Scale" puts it plainly: the most common unscalable thing founders have to do is recruit users manually.
This guide turns that advice into a plan you can run in a month. The quotes and figures come from the essay, read on 8 November 2026. Where something is our own suggestion, we say so.
Why manual recruiting comes first
In his essay on doing things that don't scale, Graham writes that startups take off because the founders make them take off, and that you cannot wait for users to come to you. He points to Stripe, which was famous inside Y Combinator for aggressive early user acquisition: instead of sending a beta link, the founders would set the user up on the spot.
He also argues that launches matter less than founders think. All you need from a launch is an initial core of users, and how well you are doing a few months later depends more on how happy you made those users than on how many there were. That is why a post-launch dip is normal, and why a launch alone is a weak plan. If you want to compare platforms anyway, see Show HN vs Product Hunt.
The numbers are smaller than you expect
Graham suggests measuring progress by weekly growth rate. If you have 100 users, you need 10 more next week to grow 10% a week. Keep that rate for a year and, by his arithmetic, you reach about 14,000 users.
For a plan to reach 100, that means about 10 new users in week one, then rising slowly. Do not compare this to launch-day screenshots on social media.
A four-week plan
These steps are our suggestion, built on the essay's advice.
- Week 1: choose a narrow group. Graham notes that a deliberately narrow market can help you reach critical mass quickly, and that the usual way to find the most promising users is to get some early users and see which kind are most enthusiastic. Write one sentence: "We help [specific people] do [specific job]."
- Week 1: list 50 people who fit. Use communities you already belong to, people who posted about the problem, and customers of tools you integrate with. If you built the product for your own problem, your peers are the first place to look, as Graham says.
- Week 2: contact 10 a day with something specific. Mention what you saw them do or say, state the problem in one line, and offer to set it up for them. Do not paste a template.
- Week 2 and 3: onboard each person live. Watch them use the product. Fix what confuses them the same day if you can.
- Week 3 and 4: ask each user two questions. What nearly stopped you from signing up, and what would you miss if it disappeared? Record the answers in one document.
- Week 4: find the pattern. See which kind of user stayed active and go find more like them.
What to say in the first message
Keep it to four sentences: who you are, what you noticed about them, what the product does for that exact situation, and a low-pressure offer such as "I can set it up with you in 15 minutes." You are after a conversation.
Where to look
- Communities where the problem comes up: forums, Slack groups, subreddits, newsletters. Follow each community's rules on self-promotion.
- Users of adjacent tools. If you build for developers who use Stripe, Paddle or Polar, those are the people to talk to.
- People who comment publicly on the problem. A reply that helps comes before any mention of your product.
- Directories and catalogs where buyers browse. These are one path among many and bring a trickle, not a launch spike. One option is Dealpuffin, which is free to list for products that use Stripe, Paddle or Polar.
If the need is blurry, act like a consultant
In How to Get Startup Ideas, Graham says that when you find an unmet need that is not your own, it may be blurry at first. He recommends acting like a consultant retained to solve one user's problems, since the code you write that way is mostly reusable.
Treat the first users as your best feedback
Graham says that over-engaging with early users is a necessary part of the feedback loop that makes the product good, and that the feedback from your earliest users will be the best you ever get. Take notes after every conversation, even the ones that go nowhere.
A short checklist
- One sentence describing who the product is for.
- A list of 50 people who fit it.
- Ten personal messages sent per day.
- Every new user onboarded in a live session.
- A weekly count of new and still-active users.
- A shared document with every answer you receive.
Frequently asked questions
How long does it take to get 100 users?
It depends on how reachable your audience is. Graham's growth-rate math shows the early numbers look small: at 10% weekly growth from 100 users, you add 10 in the first week.
Should I launch on Product Hunt first?
A launch can give you an initial core of users, but Graham argues that how happy you make them matters more than how many arrive. Recruit by hand alongside any launch.
Is it okay to message people directly?
Yes, if the message is specific, relevant and easy to ignore. Follow each platform's rules, and stop if someone says no.
What if nobody responds?
Check whether your group is too broad, whether the problem is urgent for them, and whether your message names something real about them. Narrow the group before you increase volume.