How do you build an audience before launching?

The founders who launch to silence made the same mistake: they treated audience-building as a post-launch problem. Building an audience before you ship means finding the people who already want what you're making, earning their attention, and converting that attention into launch momentum before a single line of production code ships.

Start by solving your own problem — your first audience is already around you

Paul Graham's point about building things you yourself want is more than a quality heuristic — it's an audience-acquisition strategy. When you're solving a problem you personally have, you already know where people with that problem congregate, because you congregate there too. You're in the forums, the subreddits, the Slack groups, the Discord servers. You know the frustrating threads where no one has a satisfying answer. That's not background noise — that's your pre-launch distribution channel.

The implication is direct: before you write a landing page, map the communities where you already participate as a peer, not as a marketer. The people in those spaces share your problem. They're already warmed up to the pain point. When you eventually tell them what you're building, you're not a stranger cold-pitching — you're a fellow sufferer who found a way out.

This starting point also filters out a common trap: building an audience for a product that nobody actually wants. If you can't find any community of people who experience the problem you're solving, that's a signal worth taking seriously before you've invested months in the product. Your early audience research is also your market validation.

Document the problem publicly before you have a solution

One of the most underused pre-launch strategies is publishing your thinking about the problem space before you have anything to sell. Write about the frustration. Analyze why existing solutions fall short. Post the research you wish existed when you were first struggling with the problem. This content does three things simultaneously: it attracts people who share the problem, it establishes you as someone who understands the space deeply, and it creates an archive of credibility that will still be working for you on launch day.

The format matters less than the consistency and specificity. A detailed Twitter thread breaking down why current tools fail at a specific workflow will outperform a generic blog post about 'the future of X.' Specificity signals that you've actually lived the problem. Vague content attracts vague interest; precise content attracts the exact person you're building for.

A practical cadence: pick one publishing channel where your target audience already spends time — not where you wish they spent time — and commit to a weekly output. Don't wait until you have something polished. The rougher, more honest posts about what you're learning tend to drive more engagement than finished essays, because they invite conversation rather than just consumption.

Convert readers and followers into a direct list before launch day

Social followers are rented attention. An email list or a private community is owned attention. The goal of everything you publish before launch should be to move people one step further down that ownership ladder. A tweet gets someone's attention for fifteen seconds; a newsletter subscriber has given you permission to interrupt them again. That difference compounds enormously on launch day.

The mechanism is simple: every piece of content you publish should have a single next step that moves an interested stranger toward a more committed relationship with what you're building. At the lightest end, that's a 'follow for updates.' At the heaviest end, it's a waitlist form asking for an email address in exchange for early access. In between, there are options like a private Slack or Discord for people interested in the problem space, a short survey that doubles as a research tool, or a free resource that pre-qualifies the people who want it.

Don't spread across five channels hoping one works. Pick the mechanism that fits your audience's existing behavior. B2B SaaS buyers often respond to an email list and a LinkedIn presence. Consumer apps often grow through short-form video and a Discord server. The right channel is the one where your specific future customer already spends time — not the one that feels most comfortable to you.

Make your building process part of the product story

Building in public — sharing genuine progress, genuine setbacks, and genuine decisions — turns your development timeline into a content machine. The goal isn't performance or founder cosplay. It's giving potential users a front-row seat to the problem being solved, which creates investment. People who've watched you struggle with a hard problem and arrive at a solution feel partial ownership over that solution. They show up on launch day not just as potential customers but as advocates.

The practical version of this is a weekly or bi-weekly update to your early list or community: what you shipped, what broke, what you learned, what you're building next, and — critically — what questions you're still trying to answer. That last part is where the audience becomes collaborators. Ask specific questions. 'Would you pay more for X or Y feature?' gets better responses than 'What would you like to see?' Specific questions show you're serious and reward people for paying attention.

Keep the ratio honest: more problem and user insight, less product feature announcement. Nobody who isn't already your customer cares that you refactored your database schema. They do care that you talked to twelve people who all described the same painful workaround, and here's what that told you about what to build. Lead with the insight, not the output.

Activate your audience for launch with a specific, time-bound ask

A pre-built audience only converts into launch momentum if you make a clear, specific ask at the right moment. Vague updates like 'we're almost ready, stay tuned' bleed energy. A concrete ask — 'we're opening ten spots next Tuesday, reply to this email if you want one' — creates urgency and commitment. The ask should feel like a favor you're doing them, not a sales pitch you're making to them. Early access to something genuinely useful is a reward, not a transaction.

Sequence the launch communication in at least three steps: a heads-up that launch is coming and what they'll get access to, a reminder the day before with a specific call to action, and a live launch message that assumes they've been waiting. Each message should add new information — a feature they haven't seen, a story from a beta user, a specific problem the product solves — rather than just repeating 'we're launching.'

The size of your pre-launch audience matters far less than its specificity. A hundred people who have the exact problem your product solves and have been following your building process will produce better launch results than ten thousand social followers who vaguely remember you exist. Optimize for depth of connection, not breadth of reach, in the months before you ship.

“Since your friends probably have similar interests, this will also get you your initial audience.”

— Paul Graham, source

The one thing to do

Start publishing about the problem you're solving today, point every piece of content toward a single owned channel like an email list, and treat your pre-launch audience as collaborators rather than future customers.

Frequently asked questions

How early should I start building an audience before launch?

Start the day you commit to building something, not the day before you ship. Six to twelve months of consistent publishing gives you enough time to build a real email list, establish credibility in a community, and refine your positioning based on real feedback.

What if I'm in stealth mode and can't talk about what I'm building?

You can publish about the problem space without revealing the solution. Write about the frustrations your target users experience, interview people in the space, share research. When you eventually reveal what you built, you'll already have an audience primed around exactly the pain point you solve.

How many subscribers or followers do I need before launching?

There's no magic number, but a list of 200 to 500 highly qualified people who have the specific problem you solve is more valuable than 5,000 loosely interested followers. Focus on qualification over quantity — ask yourself whether each new subscriber genuinely has the problem your product fixes.

Which platform should I use to build a pre-launch audience?

The one where your specific future customer already spends their time, not the one you find most comfortable. Research where people in your target segment actually congregate — specific subreddits, LinkedIn communities, niche newsletters, Discord servers — and show up there consistently before you launch anywhere else.

Sources

More playbook answers · Growth Prophet home