Favors.dev
You launch a SaaS with no audience the same way you'd throw a party in a town where nobody knows you: you don't wait until you're famous — you borrow a crowd. Launching with no audience isn't about building a following first. It's about getting temporary access to people who already trust someone else, earning support by giving it first, and converting both into a small list you keep — all before launch day.
That reframe matters because the usual advice — "build an audience first" — quietly assumes you have a year to spare. You don't. This playbook is the faster route: borrow, earn, convert, launch. Let's start with why the cold version fails so reliably.
Why launching with no audience usually fails
A cold launch fails because distribution compounds, and compounding from zero is just zero. When you post a launch to nobody, the funnel math is brutal in a way that's easy to ignore until it happens to you. Walk it through honestly:
The cold-launch math
You tweet your launch to 40 followers, most of them friends and bots. Say 15% actually see it — that's 6 people. Maybe 2 click through. At a generous 2% landing-page conversion, you need 50 visitors for a single signup, so 2 visitors gets you zero. You post the same thing to a subreddit where nobody knows you and it's removed for self-promotion. By the end of launch day you've had 11 visitors and no signups — and you conclude the product is the problem.
The product usually isn't the problem. The launch was a distribution event with no distribution. Every channel that works nowassumes an audience you don't have yet: social reach assumes followers, email assumes a list, "just post it" assumes someone's listening. There's a 2026 tailwind that makes arriving cold even riskier. Search is going answer-first — AI referral traffic to the top thousand sites surged past 1.13 billion visits in a single month last year (Similarweb, via TechCrunch), yet those engines pass publishers less than 1% of their referral traffic even when they cite them (Chartbeat/Conductor, via eMarketer). Fewer stray clicks wander in by accident than ever. If you want people on launch day, you have to bring them yourself.
Borrowed, owned, and earned: the three audiences
The way out is to stop thinking about "an audience" as one thing you either have or don't. A founder launching from zero has three different audiences available, and the whole strategy is using them in the right order: borrow reach to seed an owned list, and earn the support that makes launch day land.
Borrowed
Someone else's audience you get temporary access to — a community, a newsletter swap, a co-launch, a podcast.
Owned
A direct line you control — a waitlist, an email list, a small Discord. No algorithm or gatekeeper between you and them.
Earned
Support you've banked by helping first — reviews, shares, feedback, and backlinks other founders owe you back.
Each has a different speed and a different catch. Put them side-by-side and the sequence becomes obvious — you can't start with the slow owned channel, so you lead with borrowed and earned and feed the owned one as you go:
| Audience | How fast | The catch |
|---|---|---|
| Borrowed | Fast (days–weeks) | It's rented, not owned. The reach disappears the moment the host moves on, so you must convert it into something you keep. |
| Owned | Slow (weeks–months) | It compounds, but from zero it grows painfully slowly. You can't start here cold; you seed it with borrowed reach. |
| Earned | Fast (days), if you've given first | You have to give before you can collect. Done casually it fizzles; done with bookkeeping it's a real, repeatable channel. |
How to borrow an audience before launch
Borrowing an audience means putting your product in front of a group someone else has already earned trust with — and you have more ways to do it than you think, none of which require a following of your own:
- Communities where your buyers already are.Show up in the two or three rooms your users live in — a relevant subreddit, Indie Hackers, a niche Discord — and be useful for weeks before you ever mention your product. The trust you build there is the audience you're borrowing.
- Newsletter swaps and co-launches.Find a founder at your size — not a huge one — and trade mentions, or launch something together so each of you brings the other's readers. Two tiny lists pointed at each other beat one list alone.
- Other people's stages.A guest podcast episode, a Show HN written as a genuine lesson, a teardown post on someone's blog — each borrows an established audience for an afternoon and leaves a link behind.
The non-negotiable rule for all of it: every borrowed moment has to feed something you keep.Borrowed reach evaporates — so point it at a waitlist, a signup, an email capture. Otherwise you've rented a crowd and let it walk out the door.
Building a tiny owned list before you launch
Build the smallest owned list that counts as "not zero," and build it from the borrowed reach above. You don't need thousands of subscribers to launch — you need a few hundred, or even a few dozen, real people who asked to hear when you go live. That tiny list is the difference between launching to silence and launching to a warm room.
Keep it mechanically simple. Stand up a one-field waitlist and a public page for your project on day one, so every borrowed moment has somewhere to send people. Then do the unglamorous thing: actually talk to everyone who signs up. Early, a list of 30 people you've had real conversations with converts better than 3,000 cold emails — and those 30 become your first reviewers, testimonial sources, and launch-day supporters. This is also where you gather the kind of compounding, no-budget marketing assets that keep working long after launch week.
The reciprocity shortcut: earn support by giving first
The fastest way to arrive at launch with a crowd is to earn one in advance — by helping other founders before you need anything back. This is the channel the "build an audience first" advice always skips, and for someone launching from zero it's the most important one, because it needs no prior following, no budget, and it compounds.
The logic is simple. The actions that make a launch land — an honest review, a share from a real account, structured feedback that sharpens your pitch, a backlink from a site with its own authority — are all things other founders can do for you, and that you can do for them. Each of you brings exactly what the other lacks: a second audience, a credible voice, a website that already ranks. And those same favors are the signals answer engines disproportionately cite — reviews, community discussion, named-author articles — so earned support does double duty in an answer-first web.
The catch — and the reason ad-hoc "support my launch" groups always collapse — is that goodwill without bookkeeping turns into a handful of generous people carrying everyone else. The askers outnumber the givers, the givers burn out, the group goes quiet. The fix isn't more goodwill; it's structure.
That's the specific problem Favors.dev was built to solve. It's a marketing co-op for founders where reciprocity is enforced by a points economy instead of goodwill: you earn points by helping other founders launch — reviews, shares, feedback, testimonials, backlinks — and you spend them to get the same help back. You can't spend what you haven't earned, so free-riding isn't a moderation headache, it's mathematically impossible, and every action is verified before points move. Browse the founder directory and you'll find your launch-day crowd is a group of people in exactly your position, ready to trade real support.
A 30-day no-audience launch runway
Here's the whole thing as a four-week sequence. Each week sets up the next, so by launch day the audience you didn't have is assembled from borrowed reach, a tiny owned list, and earned support.
Decide exactly who your first 50 users are and name the 2–3 places they already gather. Set up your project's public page and a one-field waitlist. Don't pitch anything yet.
Outcome: A target, a home base, and a place to capture interest.
Show up daily in those rooms answering questions and giving honest feedback on other people's work — no link-drops. Start trading favors: review and share other founders' projects so the support is already owed back to you.
Outcome: Recognition, goodwill, and a balance of earned support.
Line up 2–3 borrowed-audience moments for launch week: a newsletter swap with a peer at your size, a co-launch, a Show HN or community post written as a lesson, not an ad. Collect waitlist signups from every one.
Outcome: Pre-launch reach pointed at a list you keep.
Pick a date, rally the founders who owe you support and the list you built, then launch on Product Hunt or a directory on top of that base. Follow up the same day with everyone who showed up.
Outcome: A launch that opens warm instead of into silence.
None of this requires you to become an influencer first. It requires you to be useful, on purpose, for about a month before you launch — and to keep the receipts. When the day comes, set your date on the launch calendar, rally the founders who owe you support, and run your Product Hunt launch on top of a base instead of into a void. For the channel-by-channel view of week one and beyond, the first-100-users playbook picks up exactly where this one ends.
Frequently asked questions
Can you really launch a SaaS with no audience?
Yes — but not by launching cold. Launching a SaaS with no audience means borrowing and earning access to people who already trust someone else, then converting that temporary reach into a list and a base of support you keep. The founders who do this well don't skip the audience problem; they solve it with other people's audiences and traded favors before launch day, so they arrive with a crowd instead of shouting into an empty room.
How long does it take to launch without an audience?
Plan for about four weeks of runway, not four months. You don't need to build a large following first — that's the slow path most advice assumes. The faster path is to spend roughly a week finding where your buyers gather, a week being genuinely useful and banking earned support, a week lining up borrowed-audience moments, and launch week itself. The exact timing flexes, but the sequence — borrow, then earn, then convert, then launch — is what matters.
Should I build an audience before launching or launch first?
Build a tiny owned list before launching, but don't wait to build a big one. A large personal audience takes a year you don't have, and 'launch first, figure it out later' usually means launching to 11 visitors and zero signups. The middle path wins: seed a small waitlist using borrowed reach and earned favors over a few weeks, launch to that warm base, and let the launch grow the audience rather than requiring one.
Where do I get my first users with no following or budget?
From three places that need neither: communities where your buyers already are (relevant subreddits, Indie Hackers, niche Discords), borrowed audiences via newsletter swaps and co-launches with peers, and earned support from other founders who'll review, share, and link to you because you did it for them first. Cheap paid shortcuts like BetaList exist, but the free, reciprocal channels are what assemble a crowd from zero.
How is trading favors different from spamming communities?
Spamming is taking without giving — dropping your link in a room and leaving. Trading favors is the opposite: you give real help first (an honest review, useful feedback, a share) and the support comes back because it's owed. On Favors.dev that exchange is enforced by a points economy — you earn points by helping other founders and spend them to get help back, and you can't spend what you haven't earned — so the reciprocity is real and free-riding is mathematically impossible.