You launched. You have a URL, a waitlist form, and approximately zero users. You're refreshing your analytics dashboard watching a number that refuses to move.
The instinct is to run ads. Throw $500 at Google or Meta, see what sticks. But paid acquisition before product-market fit is usually a fast way to burn money on unqualified traffic that doesn't convert and teaches you nothing useful.
The first 100 users are different. They're not a scaling problem — they're a targeting problem. You need to find exactly the right people, reach them directly, and give them a reason to care. That's a manual, high-precision operation, not a spray-and-pray campaign.
Here's the playbook. And yes — we're doing all of this ourselves right now, building VibeLaunch in public. These aren't theories. They're our current weekly to-dos.
The "Build It and They Will Come" Myth
The myth persists because occasionally it's true. Someone posts on Hacker News, the post lands on the front page, and 800 signups arrive overnight. Everyone cites that story. Nobody cites the 99 founders who posted on Hacker News and got 12 upvotes.
Distribution is the job. Not a nice-to-have — the job. The product earns the right to be distributed. Distribution actually gets it in front of people.
"The first 100 users aren't a scaling problem. They're a targeting problem. You need to find exactly the right people and reach them directly."
The good news: you don't need a budget to get your first 100. You need time, consistency, and a system. The channel mix looks roughly like this:
Let's break down each channel.
The Playbook
-
Directory Submissions
There are hundreds of directories, aggregators, and "SaaS tools" roundup sites that your target customer is already browsing. ProductHunt, BetaList, Indie Hackers, There's An AI For That, Futurepedia, AlternativeTo, SaaSHub — and dozens of niche ones specific to your category.
What to expect: Most submissions drive 5–30 visits each. ProductHunt on a good day can deliver 500–2,000. The compounding effect comes from the long tail — 50 directories at 10 visits each is 500 visitors who found you because they were actively searching for a solution.
What the timeline looks like: Expect 48–72 hours for most approvals. ProductHunt has a queue. BetaList takes 1–2 weeks. Start submitting day one — these are backlogged, not instant.
The bottleneck isn't finding the directories. It's the repetitive copy-paste of name, description, tagline, URL, screenshots across 50+ forms. Most founders do five directories, feel productive, and stop. The full list never gets done. This is exactly the kind of work that the autonomous layer handles — not because it's hard, but because it's relentless.
-
SEO Blog Content That Compounds
Paid ads stop the moment you stop paying. SEO compounds. An article that ranks for "how to get first users without ads" in month three will still be sending traffic in month thirty.
The keyword strategy: Ignore head terms. "CRM software" is unwinnable for a new site. Go long-tail: "CRM for solo consultants who hate spreadsheets." Lower search volume, lower competition, higher intent, faster to rank.
How to pick topics: Think about every question your ideal user Googles before they know products like yours exist. "How do I track leads without a spreadsheet?" "What should I do after launching my SaaS?" These are the articles that intercept them at the problem-aware stage.
Internal linking matters. Every new article should link to two or three others. It distributes authority across your site and keeps visitors reading. We do this across all five of our articles — including back to this one from our post-MVP growth guide.
The cadence: One article per week, minimum. The compounding effect doesn't kick in for 90 days. Every week you skip is a week you're not compounding.
-
Cold Outreach That Doesn't Feel Spammy
The word "cold outreach" makes founders wince. They imagine blasting 500 generic emails and getting reported for spam. That's not what this is.
The formula: Find 20 people who have the exact problem you solve. Write 20 genuinely personalized emails. Reference something specific — their recent tweet, a post they wrote, the problem their company is publicly trying to solve. Lead with value: a relevant insight, a relevant article (one of yours), or a direct question about their situation. No pitch deck attachments. No "I'd love to hop on a 30-minute call."
A good cold email looks like this: "Hey [Name] — saw your post about [specific thing]. We built something that handles exactly that. Happy to share early access if it's useful." Seven words of context, one specific offer. That's it.
Expected response rate: 10–25% if genuinely personalized. Under 2% if templated. The personalization is the product.
Follow-up matters. Most replies come on the second or third touch. One email is not a campaign. Three emails over two weeks — spaced, thoughtful — is.
-
Twitter as a Distribution Channel (Not a Marketing Channel)
There's a wrong way to use Twitter: as a broadcast antenna for your product announcements. Nobody reads those threads. Nobody shares them. They feel like ads because they are ads.
There's a right way: post what you're actually learning, in public. Build in public means sharing the messy reality — the problems you're solving, the metrics you're watching, the mistakes you're making. This article is an example. We're not promoting VibeLaunch — we're documenting the distribution playbook we're running right now.
What actually gets traction: Specific numbers ("We went from 0 to 47 waitlist signups in 10 days — here's exactly what worked"). Contrarian takes with receipts. Detailed teardowns of your own failures. Genuine engagement on other people's posts before you ever ask anyone to look at yours.
The best founders on Twitter are the ones who make you want to follow their journey, not just use their product. Those are different things.
The Compounding Effect — Why Consistency Beats Virality
Every first-100-users success story has a lottery ticket in it somewhere — the tweet that went viral, the ProductHunt launch that hit the front page, the Hacker News post that trended. The problem with planning around lottery tickets is that lottery tickets are not a strategy.
What's actually happening in the background of most traction stories is months of invisible work that made the lottery ticket possible. The SEO articles that had been compounding for 90 days. The directory listings that were already sending a trickle. The Twitter audience that had been growing from genuine posts for weeks before the viral one.
Consistency is the strategy. Not because it's virtuous — because it's the only reliable mechanism. A founder doing five directory submissions a week, publishing one SEO article per week, and sending 15 personalized cold emails per week will reliably reach 100 users in 60–90 days. No viral moment required.
The founders who don't reach 100 users aren't unlucky. They're inconsistent. They launch, do a burst of activity, check the numbers, get discouraged when nothing goes viral, and stop. The system needed two more weeks to compound. They stopped in week three.
"Consistency is the strategy. Not because it's virtuous — because it's the only reliable mechanism."
The Honest Problem with This Playbook
Everything above is true. It works. It's also a lot of work — the kind of grinding, repetitive, non-glamorous operational work that founders burn out on after two weeks.
Directory submissions take 20–30 minutes each. Done across 50 directories, that's 25 hours. Cold outreach research takes 10–15 minutes per prospect to personalize properly. Blog articles take 3–5 hours each. Twitter engagement is a daily habit, not a weekly task.
This is roughly 15–20 hours per week of growth work, every week, on top of the product work. For a solo founder, that math often doesn't work.
This is exactly why we built VibeLaunch. The things that kill vibe-coded apps aren't product problems — they're operational ones. The playbook exists. The work is known. The bottleneck is having something that actually runs it, every day, without burning out.
VibeLaunch handles the directory submissions, the outreach cadence, the SEO content calendar, and the analytics tracking that tells you which channel is actually working. Not as a set of templates to execute manually — as an autonomous system that runs while you're building the product.
If you're curious what the first 30 days of post-launch growth actually looks like operationally, read why vibe coding fails at business — it covers why the tool that built your product can't run it.