When early-stage founders discuss customer acquisition, they frequently jump straight to tactics designed for companies with ten thousand customers: Facebook ad funnels, programmatic SEO scripts, affiliate networks, and automated cold email sequences.
For your first twenty users, every single one of those channels is either too expensive, too slow, or dangerously misleading.
If you spend $500 on paid ads and get zero conversions, you have learned almost nothing. Did the copy fail? Did the targeting fail? Was the pricing too high? Was the product broken? Did people bounce because the landing page was slow?
Paid advertising provides numerical aggregates when what you desperately need is qualitative conversation.
Your first twenty users must be recruited manually, one human being at a time. Here is the exact methodology for finding them without spending a dollar on advertisements.
Why 'Getting Users' Is the Wrong Target
The phrase "I need to get users" is dangerously unspecific. A user could be:
- A curious hobbyist who clicks around for ninety seconds and never returns.
- A competitor inspecting your UI elements.
- A bot filling out your free trial form.
- A paying business owner whose daily workflow depends on your software.
If you aim for "users," you will celebrate 100 signups from a viral social post, only to discover two weeks later that your weekly active user count is zero.
For your first twenty users, your objective is not volume. Your objective is finding people with high problem urgency.
A user with high problem urgency:
- Experiences the pain at least two or three times every single week.
- Is actively seeking a workaround or already cobbling together an imperfect combination of spreadsheets, manual scripts, or expensive enterprise software.
- Has the authority and willingness to switch tools if your software actually works.
Twenty users who fit this profile will teach you more about your roadmap than two thousand casual drive-by visitors.
Defining an Ultra-Narrow Target Profile
Before you send a single message, write down a one-paragraph description of the specific individual who needs this software today.
Narrow down by three criteria:
- Their exact role: Not "marketers," but "solo marketing managers at B2B companies with 10 to 50 employees."
- Their existing toolchain: What software do they open at 9:00 AM? (e.g., "People who manage their client tasks inside Notion and struggle to export time-tracking into QuickBooks.")
- Their triggering event: What bad thing just happened to make them look for help? (e.g., "They just spent Sunday evening manually copy-pasting numbers across two browser tabs for four hours.")
When your target is that specific, you know immediately where to look for them, and your outreach copy writes itself.
Non-Spam 1:1 Outreach That Actually Works
Most cold outreach fails because it reads like a desperate sales pitch written by an automated script. It starts with sycophantic flattery ("I love what you're doing at Company X!"), launches into a self-absorbed product summary ("We are the revolutionary AI platform for..."), and concludes with an aggressive call to action ("Can I have 15 minutes on your calendar tomorrow?").
Throw that template away.
Effective founder outreach is conversational, specific, and humble:
The Problem-First Message Template
"Hi [First Name], saw your discussion in the [Group/Thread] about how painful it is to [specific friction, e.g., keep PostgreSQL schemas in sync across dev staging].
I built a lightweight open-source CLI over the last few weeks to handle that specific synchronization without running manual migrations.
If you're still dealing with that issue, I'd love to share the GitHub repo / link. Zero sales pitch—I just want to see if it solves your workflow edge cases or if my approach has blind spots."
Notice what this note accomplishes:
- It references an actual public statement they made.
- It identifies a shared technical problem.
- It asks for technical critique, not their money or their calendar.
- It gives them an easy out.
Send five of these tailored messages every morning. If you do this consistently for two weeks (50 total messages), you will easily generate ten to fifteen substantive conversations.
The Power of Founder-Led Onboarding
When someone agrees to try your product, do not simply send them a login link and hope for the best. Offer to onboard them personally:
"The app is live at [link], but if you have 10 minutes, I'd be happy to hop on a quick screen-share and set up your account with your real data so you don't have to waste time figuring out the configuration."
Founder-led onboarding is an unfair advantage for two reasons:
- You witness real usability friction in real time: You will see them hesitate before clicking a button you thought was obvious. You will see an error message that you didn't anticipate. You will see them look for a feature in a place you didn't put it.
- It drastically increases activation: A user who is guided through their first successful output by the creator is vastly more likely to return tomorrow than one who stared at an empty dashboard and got confused.
Do this for your first ten to fifteen users. The product insights you gather on these calls will reshape your UX far faster than any analytics dashboard.
Participating in Communities and Forums
Do not join online communities (Reddit, Discord, Indie Hackers, specialised Slack groups) merely to drop your product link in every relevant thread. Community moderators will ban you, and members will ignore you.
Instead, practice problem-centric participation:
- Search for recent discussions where community members ask technical questions you know how to answer.
- Write a detailed, comprehensive answer that completely solves their problem without requiring them to use your software. Give away the manual recipe, the open-source snippet, or the operational breakdown.
- Only at the very end, mention your tool casually as a relevant side note:
"If you want to do this automatically without running the script manually, I built a small tool called [Product Name] that handles the background polling: [link]."
This builds goodwill, demonstrates domain competence, and drives high-intent traffic from people who read the thread weeks later.
Leveraging Permanent Discovery Platforms
Social media feeds are ephemeral. A tweet or LinkedIn post has a useful shelf life of roughly twelve to twenty-four hours before it sinks beneath the algorithmic surface.
For sustainable early momentum, register your product on structured discovery engines like ShipNLaunch.
Why structured discovery platforms matter for early-stage products:
- Canonical indexing: Your product page is permanently organized under appropriate categories like SaaS, Productivity, or Marketing.
- High-intent search traffic: Visitors exploring maker discovery directories are actively seeking new tools to test in their daily workflows, unlike casual social media scrollers.
- Organic backlink authority: A clean listing provides an indexable signal to search engines that your domain exists and has been published.
Take thirty minutes to craft an accurate submission on ShipNLaunch, selecting clear categories and uploading screenshots that show your tool solving the problem.
Diagnosing the True Problem: Acquisition or Product?
As you interact with your first twenty prospects, you must constantly discern whether your difficulty stems from customer acquisition or from product utility.
Here is how to tell them apart:
| Signal | What It Means | Correct Operational Action |
|---|---|---|
| People eagerly open the link, sign up, but drop off after 2 minutes. | This is a Product / Activation Problem. Your value proposition resonated, but the product either failed to deliver the promised value quickly or the UI was too confusing. | Stop doing outreach. Talk to the people who signed up and ask where they got stuck. Fix the onboarding cliff. |
| Nobody replies to your outreach notes, or they reply saying 'We don't really have that problem.' | This is an Acquisition / Proposition Problem. You are either targeting the wrong persona, or the problem you are solving is an occasional annoyance rather than an acute pain. | Refine your target customer profile or reposition the core problem statement. Do not write more code yet. |
| Users try the tool, use it repeatedly, but resist paying when asked. | This is a Value / Pricing Problem. They appreciate the utility, but it does not save enough time or money to justify an ongoing expense, or your price tier is mismatched with their budget authority. | Adjust pricing structure or investigate higher-value workflow integrations. |
Diagnosing this correctly prevents you from rewriting your codebase when the only issue was messaging, or spending weeks on marketing when the product itself was broken.
What NOT to Automate in the First 20 Users
In the early days of a software company, automation is often an act of premature cowardice. Founders automate because they want to avoid the emotional awkwardness of talking directly to strangers.
Resist the urge to automate:
- Do not automate customer support: Answer every email or chat yourself within minutes.
- Do not automate onboarding emails with a generic 7-part drip campaign: Send personal emails from your actual inbox asking: "Did the CSV export work for your format, or did you hit an error?"
- Do not automate user feedback collection: A 1-to-5 star survey will tell you nothing. A 10-minute Zoom call or a three-paragraph email exchange will tell you everything.
Embrace the manual labor. The manual phase is where you earn the deep operational knowledge that competitors cannot copy.
Actionable 20-User Outreach Checklist
Execute these concrete steps this week:
Once you have twenty users who actively rely on your software and give you candid feedback, you have a foundation you can scale.
