How early-stage SaaS founders land their first 20 paying customers

By Tomáš Cina, CEO at Discury · AI-assisted research, human-edited

Editor's Take — Tomáš Cina, CEO at Discury

The thing I keep having to unlearn, in my own work and in conversations with founders, is the idea that acquisition is about finding the right channel. Early-stage acquisition is much more about whether you can describe — precisely, and out loud — the person who should buy, the pain they're feeling this week, and the exact words they'd use to describe that pain. Founders who can do that find customers through ordinary means; founders who can't keep discovering new channels that mysteriously don't work. The channel isn't the bottleneck; the clarity is.

The trap I watch founders fall into over and over is what I'd call "channel tourism." LinkedIn doesn't convert after a week, so they jump to cold email. Cold email feels uncomfortable, so they pivot to content. Each move is framed as strategy, but it's actually avoidance — a way of not confronting the harder question of who the product is for. Every channel works for somebody; the reason none of them work for these founders is that the message hasn't been sharpened against real buyer feedback yet. Two weeks of discipline on one channel with a specific ICP beats six weeks of frenetic exploration across five.

My contrarian take: the best acquisition channel for an early-stage SaaS founder is usually their own inbox. The warm and semi-warm contacts living in a founder's email history almost always produce the first handful of real conversations. Founders resist this because it feels like asking friends for favors. But friends-of-friends willing to take a pitch are exactly the forgiving audience a rough early product needs, and the specific feedback they give is worth more than a thousand cold replies. Start where the trust exists, and only expand outward once you can repeat what worked there.

Case study: u/Lara_Doll on fifteen years of watching bootstrapped acquisition stall

Of the threads we reviewed, the single most useful walkthrough is the thread on early-stage operators plateauing before meaningful revenue. u/Lara_Doll, reflecting on fifteen years of watching bootstrapped founders, builds a coherent argument across the thread about why so many early-stage acquisition attempts stall at the same point — and what the founders who break through actually do differently. Walking the thread in order is the clearest path into the rest of the acquisition argument, because the later threads we cite are essentially corollaries of the points she makes first.

The opening move in the thread is a diagnostic: founders who stall can't tell the difference between a gimmick that spiked once and a channel that works repeatedly. They remember the week a single LinkedIn post got 40,000 impressions and three demo bookings, they try to reproduce it, they can't, and they conclude "LinkedIn doesn't work." What actually failed was the definition of a channel.

"If your lead source can't be repeated every week with predictable output, it's a gimmick, not a channel." — u/Lara_Doll

The second move in the thread is structural: founders chasing volume tend to build homepages optimised for landing-page best practices rather than for a specific audience. High bounce rates follow, and the bounce rate gets blamed on the channel. The concrete fix she lays out is to narrow aggressively — pick one lead magnet, one distribution surface (LinkedIn, a specific subreddit, cold email to a tightly defined list), and run it until the math is predictable or you've proven it doesn't work. The same channel can be a gold mine for one founder and a void for another; the difference is always the ICP definition sitting underneath it.

The third move — and the one most founders miss on a first read — is her point about message-market fit preceding channel-market fit. Every channel works for somebody. If none of them work for you, the channel isn't the bottleneck; the message is. That reframes the typical "which channel should I try next?" question into a much harder one: do you actually know who should buy this, what they'd pay to fix, and what words they'd use to describe the pain? If not, no channel will rescue that.

A secondary thread that sharpens the same point comes from a companion thread on pre-product validation — a founder there describes swapping the useless "would this be useful?" question for a sharper one: "can I send you an invoice for the first month?" A yes, a no, or a specific objection is worth more than weeks of polite interest. That is, in practice, how u/Lara_Doll's "repeatable channel" rule gets turned into something actionable: you're not running a channel until you've turned polite interest into paid rejection or paid commitment, and you can do that on command.

"The thing I wish I started earlier was selling before building. Not in a fake way, but literally describing the solution to potential customers and asking if they would pay for it." — u/its_avon_

A parallel thread on PR spend at a much larger stage is the cautionary tail on the same argument. Even well-funded operators described watching large monthly PR budgets dissolve into execution work — journalist list building, press release editing — rather than anything that moved demand. The lesson isn't that PR doesn't work; it's that broad-reach spend is exactly the wrong tool before a concentrated base of paying customers has told you what's worth amplifying.

What warm outreach does that cold acquisition can't

Direct outreach remains the most reliable method for landing initial customers because it forces immediate feedback on the pitch. In a thread on founders leveraging their own networks to land early deals, operators described securing meaningful early contracts by selling consulting or custom engagements to people who already trusted them professionally. Domain expertise and prior relationships are more tolerant of a rough early product than cold prospects will ever be.

In a thread on how to allocate a constrained acquisition budget, u/zazonia's advice lines up with the case study above: put almost nothing into broad ads, and direct the money instead toward email and outreach infrastructure, a lightweight CRM, and the founder's own time on manual lead generation. Broad ads before a defined ICP simply buy you irrelevant traffic faster. A small budget's best use is to buy the infrastructure that lets one founder have many focused conversations per week with the specific people their product should serve.

"I'd spend almost nothing on ads and focus on direct outreach—identify your ICP, send personalized cold emails/LinkedIn messages, and book calls." — u/zazonia

The engineering decisions that quietly determine acquisition

Over-engineering the MVP before a single paying user is one of the most common and least excusable early-stage acquisition failures — because the time you sink into observability and API versioning is time not spent talking to buyers. In a thread on the minimum viable architecture for an early SaaS, u/Novel-Buyer-7210 and others walk through what actually needs to be right at the start: enough tenant isolation to be secure, versioned migrations so the schema doesn't become unmaintainable, and a clean separation between request-handling and background work so long tasks don't block the UI. Everything else — audit trails, elaborate observability — is a distraction until customers whose usage justifies it actually exist.

The exception is multi-tenancy: getting it wrong at the start is expensive to fix later, and founders who cut that particular corner tend to pay for it with a disruptive rewrite at exactly the moment they can least afford one. Everything else can be messy, provisional, and improved in public — as long as customers are using it.

The thread on what investors fund at the MVP stage from u/Swimming-Food-748 sits on top of this: the persuasive metric for investors and early serious customers alike is the proportion of users who reach the moment of value — the "aha" — and how fast they get there. A small team building a Shopify extension tracked only three things: the share of users hitting the core outcome, the time to get there, and qualitative feedback from those who did. Everything else is decoration.

"Investors don't fund clean UI. Or clever tech. They fund momentum, proof, and clarity." — u/Swimming-Food-748

"The absolute worst mistake you can make is to build an amazing product for no one." — u/Desperate-Purpose342

Acquisition readiness scorecard

Rate yourself honestly against each row. Three or more "No" answers means stop looking for new channels — the problem is upstream.

Dimension	Yes	No
ICP clarity	I can write, in one paragraph, the role, company shape, and specific pain of the buyer — in the buyer's own words	My ICP is "small businesses" or "SaaS founders" without a sharper layer underneath
Channel commitment	I've run one outreach surface consistently for 10+ working days with enough volume to judge it	I've tried 3+ channels in the last month, none for long enough to conclude anything
Paid-rejection signal	I've asked "can I invoice you for the first month?" and gotten concrete answers (yes, no, or specific objection) from 10+ prospects	I've only gotten "interesting" and "send me info" from a majority of conversations
Warm-network usage	I've personally contacted every relevant warm or semi-warm contact in my inbox and LinkedIn	I'm avoiding warm outreach because it feels like asking for favours
Budget allocation	Most of my spend is on outreach infrastructure (CRM, email tooling, list building) and my time	Most of my spend is on broad ads or "awareness" content before a defined ICP exists
Product gate	Users who start the product reach the core "aha" outcome at a rate I can state from memory	I don't have a concrete number for how many users reach the moment of value
Engineering discipline	My MVP has tenant isolation, versioned migrations, and async separation, and almost nothing else	I've spent engineering time on audit trails, API versioning, or observability before the first 10 paying users

If you scored mostly "Yes": the acquisition motion exists, and the next move is scaling the channel that's already producing — not picking a new one. If you scored mostly "No": the next two weeks should be spent tightening the ICP paragraph, running one channel with discipline, and replacing "is this useful?" with "can I invoice you?" in every conversation. More traffic won't rescue a fuzzy offer.

Sources

This analysis draws on r/SaaS and r/startups threads surfaced via Discury's cross-subreddit monitoring. Prioritised discussions featured founders reporting directly on manual-first acquisition, constrained budget allocation, the limits of viral channels, and the engineering decisions that matter at the MVP stage.