How to Get Your First 100 Beta Users Without a Marketing Budget

You built the thing. It works (mostly). Now you need humans to use it.

The instinct is to spend money — run ads, hire a marketer, buy a booth at a conference. But you’re a startup founder, which means your bank account looks like a countdown timer.

Here’s the good news: your first 100 users shouldn’t come from ads anyway. Paid acquisition at this stage is like hiring a wedding planner before you’ve met someone. You need to date first.

This playbook covers exactly how to get 100 real beta users without spending a rupee on marketing.

Why 100? The Magic Number

100 beta users is the minimum viable audience. Here’s what it gives you:

• Signal vs. noise — 10 users might be flukes. 100 reveals patterns.
• Enough feedback — you’ll find the 3-5 core issues that matter
• Social proof — “100 founders are already using this” unlocks everything
• Retention data — you’ll see who sticks and who churns (and why)
• Conversion math — with 100 users, you can start calculating real metrics

Don’t aim for 1,000. Don’t aim for “viral.” Aim for 100 people who actually need what you built.

The 100-User Framework: Four Channels That Work

Channel 1: The Watering Hole Method (Users 1-25)

Your future users already hang out somewhere online. Your job is to find those places and become useful there — not to spam your link.

Step 1: Map the watering holes

List 10-15 communities where your target user spends time:

• Reddit subreddits (r/startups, r/SaaS, r/Entrepreneur, niche subs)
• Indie Hackers, Hacker News
• Discord servers (most industries have 5-10 active ones)
• Slack communities (Lenny’s, Product Hunt, industry-specific)
• Facebook groups (yes, still alive for certain verticals)
• Twitter/X circles and lists
• LinkedIn groups (surprisingly active for B2B)

Step 2: Become a regular (1-2 weeks)

Post helpful answers. Share insights. React to other people’s posts. The goal: when you eventually share what you’re building, people recognize your name.

This is not optional. Dropping a link on day one gets you banned or ignored.

Step 3: The problem-first post

Don’t post “I built an app, check it out!”

Instead:

“I’ve been struggling with [problem] for months. Tried X, Y, Z — all sucked. So I built something. It’s rough, but it works. Would love 20 beta testers to break it. Free forever for early users.”

This works because:

• It leads with the problem (relatable)
• Shows you tried alternatives (credible)
• It’s humble (inviting, not pushy)
• “Free forever for early users” creates urgency

Expected yield: 15-25 interested people from 3-5 community posts.

Channel 2: The Direct Ask (Users 25-50)

Cold outreach isn’t dead. Bad cold outreach is. The difference is specificity.

The formula that works:

Hi [Name],

I saw your [specific post/tweet/comment about problem]. I've been 
building [product] that tackles exactly this — [one sentence on how].

It's in beta (rough edges and all). Would you be up for trying it? 
I'm looking for honest feedback, not just nice words.

No strings, no credit card, no newsletter spam. Just the product.

[Your name]

Where to send this:

• Twitter DMs to people who tweeted about the problem
• LinkedIn messages to your target ICP
• Reply to relevant Reddit/HN threads (the poster, not the thread)
• Email to bloggers who wrote about the problem
• People who left negative reviews on competitor products (goldmine)

Volume and conversion:

• Send 10-15 personalized messages per day
• Expect 20-30% positive response rate
• Over 2 weeks: ~200 messages → 50 responses → 25 active testers

Critical rule: Personalize every message. Copy-paste blasts get 2% response. Personalized gets 30%. Do the math.

Channel 3: Build in Public (Users 50-75)

Document your building process. This attracts people who are naturally curious about new tools.

The daily build log:

Post 3-5 times per week on Twitter and LinkedIn:

• Screenshots of the product
• Problems you solved (technical or UX)
• Metrics (even small ones)
• Decisions you made and why
• Mistakes and what you learned

The magic of transparency:

“Day 14: Just hit 43 beta users. Conversion from signup to active is 61%. The onboarding flow is clearly broken for mobile — fixing that this weekend. Here’s what the dashboard looks like right now: [screenshot]”

This does three things:

1. People want to join the journey → they sign up
2. Other founders share it (they relate)
3. It’s authentic content that doesn’t feel like marketing

The launch post:

When you hit milestones (even small ones), write a proper post:

• “How I got my first 50 users without spending a dollar”
• “The MVP I built in 2 weeks — what worked and what didn’t”
• “I asked 50 founders what they hate about [category]. Here’s what they said.”

Expected yield: 20-30 users from consistent building in public over 3-4 weeks.

Channel 4: The Partner/Multiplier Play (Users 75-100)

Find people who already have your audience’s attention and create something together.

Newsletter features:

• Find 10 newsletters in your space (Substack, Beehiiv, etc.)
• Offer to write a guest piece or be featured
• The angle: “I built [X] to solve [Y], here’s the story”
• One newsletter feature can bring 20-50 signups

Micro-influencer trades:

• Find Twitter/LinkedIn accounts with 1K-10K followers in your niche
• Offer them lifetime free access in exchange for an honest review
• 5 micro-influencers × 5-10 signups each = 25-50 users

Complementary products:

• If you built a project management tool, partner with a time tracking tool
• Cross-promote to each other’s user base
• “Works great with [their product]” is powerful

Community launches:

• Product Hunt (plan for a Tuesday-Thursday launch)
• Indie Hackers product launch
• Hacker News “Show HN”
• BetaList, BetaPage, LaunchingNext

Expected yield: 25-40 users from 2-3 partner activities.

The 30-Day Timeline

Total: 100 users in 30 days (conservative — many founders hit this in 2 weeks)

What NOT to Do

Don’t buy users

Facebook ads, Google ads, paid influencers — save it for when you know your product works. You’re still learning. Paid users are expensive lessons.

Don’t build features to attract users

“If we just add [feature], people will come.” No. They won’t. Distribution is the constraint, not features.

Don’t spam

Dropping your link in 50 communities on day one doesn’t work. You’ll get banned, and your product will develop a reputation as spam before anyone even tries it.

Don’t wait for perfection

Your product has bugs. Your onboarding sucks. Your design is ugly. Ship anyway. Early users expect rough edges — they signed up to help you fix them.

Don’t count signups — count active users

100 email addresses ≠ 100 beta users. Track who actually logged in, used the product, and came back. That’s your real number.

The Retention Test: Are They Actually Using It?

Getting 100 signups is one thing. Getting 100 people who actually use the product is another. Here’s how to tell if your beta is working:

Healthy signals:

• 40%+ of signups complete onboarding
• 20%+ use the product in week 2
• Users send you bug reports (they care enough to complain)
• Someone recommends it to a friend without you asking

Warning signals:

• High signup, near-zero activation (onboarding is broken)
• Everyone uses it once and never returns (value prop is weak)
• Zero bug reports or feedback (nobody cared enough)
• Users say “cool!” but don’t use it again (nice-to-have, not must-have)

After 100: What Changes

With 100 beta users, you have enough data to make real decisions:

1. Who are your best users? — Profile the 10-15 who use it most. That’s your real ICP.
2. What features matter? — Look at what people actually use, not what they requested.
3. What’s the activation moment? — Find the action that separates users who stay from users who leave.
4. Should you charge? — If 20+ users would be upset if you shut down, you can start charging.
5. Where to focus? — Cut everything your best users don’t touch. Double down on what they love.

The mvp.cafe Reality Check

Before you start hunting for 100 users, ask yourself these questions:

Is your product actually solving a real problem? → Take the Build Score assessment to find out. It takes 5 minutes and tells you if your MVP is ready for users or needs more work.

Do you know who your first 100 users should be? → If you can’t describe them in one sentence, you’re going to spray and pray. That doesn’t work.

Is your value prop crystal clear in 10 seconds? → If a stranger lands on your site and can’t explain what you do in 10 seconds, fix that before anything else.

Key Takeaways

1. Your first 100 users come from effort, not budget — it’s manual, personal, and slow. That’s the point.
2. Communities first — become useful before you ask for anything
3. Cold outreach works when it’s personal — 15 genuine DMs beat 500 copy-paste blasts
4. Build in public — transparency attracts early adopters
5. Partners multiply your reach — find people who already have your audience
6. Track active users, not signups — vanity metrics kill startups
7. 30 days is enough — you don’t need a year of marketing

The hardest part isn’t getting 100 users. It’s making something 100 people actually want to keep using.

Start there.

Need help figuring out if your MVP is ready for beta users? Take the free Build Score assessment — it evaluates your idea across 6 dimensions and tells you exactly where you stand.