The founders who launch to a crowd almost always built that crowd months earlier, one conversation at a time. A pre-launch community gives you early users who forgive bugs, honest feedback before you've burned your runway, and people who'll tell their friends on launch day. You can start building one this week with a group chat, a calendar and a willingness to talk to people individually, and this guide walks through how to do it, with examples from companies that did it well and Bay Area events where you can find your first members.
Start with a narrow group you can actually reach
Paul Graham's 2013 essay Do Things That Don't Scale is still the best argument for starting small. He points out that Facebook was only for Harvard students at first, a market of a few thousand people, and that a critical mass signed up because they felt it was built for them. A pre-launch community works the same way. A chat open to "anyone interested in productivity" tends to fill up with strangers who never post, and a group of 40 seed-stage founders who all hate their CRM will have plenty to talk about every day.
Write a 1-sentence description of who belongs, and make it specific enough that some people will read it and realize it's meant for someone else. "Bay Area ops leads at Series A startups who run hiring themselves" gives people an instant sense of who else is in the room, while something as broad as "people who care about the future of work" gives them nothing to rally around.
Recruit your first 20 members by hand
The same essay describes how the Airbnb founders went door to door in New York recruiting new users, and how the Stripe founders would say "Right then, give me your laptop" and set people up on the spot, a move Graham calls the Collison installation. Your version is personal invites. Message people you already know who fit the description, ask each of them for 2 introductions, and keep going until you have about 20 members who've each heard from you directly.
Every invite should say who the group is for, what people get out of it and how often it's active. Skip the pitch for your product entirely at this stage. People join a community for each other, and they'll care about your product later because they trust the group you built.
Pick 1 home base and make it easy to join
Choose a single place where the community lives, and make sure joining takes less than a minute. A group chat works well early because it feels personal and people already check their phones all day. As it grows past 50 or so people, you'll want topics, pins and polls so the chat stays useful, which we cover in our guide to handling large group chats.
Avoid spreading yourself across 4 platforms at once. A Discord server, a Slack, a LinkedIn group and a newsletter, each with 15 people, will feel empty everywhere. We've looked at Slack for community group chats and Discord for community building in earlier posts, and the short version is to pick a space built for ongoing conversation among people who mostly don't know each other yet.
Give people a reason to show up every week
A community needs a rhythm. Pick 1 recurring ritual and keep it going, whether that's a Monday thread where everyone shares their goal for the week, a Thursday question about a shared problem, or a monthly 30-minute video call where 1 member walks through how they solved something. The ritual matters more than the topic, because it teaches people when to come back.
Your job in the first 2 months is to be the host. Welcome every new member by name, introduce people who should know each other, and answer questions fast. When you introduce 2 members who end up helping each other, you've given both of them a reason to stay that has nothing to do with you.
Take it offline in the Bay Area
Nothing deepens a group chat faster than meeting in person. A dinner for 8 or a coffee walk for 5 does more for trust than a month of messages, and our post on why the Bay Area's networking scene is changing looks at what founders are using in place of the old mixer circuit. You can also recruit new members at events where your people already go. Cerebral Valley's calendar lists AI events in San Francisco over the next 2 weeks, including a Gemini 4 Argon hackathon on October 25, Even Day SF on November 5 and the AIE Code Summit hackathon on November 7. StartOut's Demo Day, where LGBTQ-led startups pitch to investors, runs November 12 from 5 to 7 p.m. at the SF LGBT Center.
When you go, skip the business card collecting. Have 3 real conversations, then invite the people who clicked into your chat that same night while the conversation is fresh. Our post on fixing the conference business card problem covers how to follow up so a good conversation turns into an ongoing relationship.
Let the community shape the product
Once you have 30 to 50 engaged members, start sharing what you're building in small pieces. Post a rough mockup and ask what's confusing, run a poll on which feature to build first, or invite 5 people to a private test. Members who helped shape the product feel ownership of it, and those are the people who post about you on launch day without being asked.
Keep the community's value separate from your product, though. If the group only exists to promote your launch, people will feel it and drift away. The communities that last keep helping members whether or not they ever become customers.
Measure the right things
Member count is the least useful number early on. Watch how many people post in a given week, how many conversations happen without you starting them, and how many members invite someone else. When members start answering each other's questions before you get to them, you have a real community.
If you want to see how other founders run their groups, our list of SF tech communities worth joining is a good tour of what works. On Tribe, the Bay Area event builders Tribe is full of people who host founder dinners, meetups and demo nights, and it's a friendly place to ask how they got their first 20 members to keep coming back.
