How to Run a Community Launch Without Burning Your Network
Asking people you know to support a launch, once, properly: who to ask, what to ask for, how to phrase it, and why asking for votes backfires.
Published 2026-08-19 · 4 min read
Every founder has a network, and every founder is tempted to spend it on launch day. It can be done once without damage, and the difference between doing it well and burning it comes down to what exactly you ask for.
Asking for a vote spends the relationship and often violates platform rules. Asking for honest attention spends nothing and usually produces more.
The distinction that decides everything
| Ask for this | Not this |
|---|---|
| "Take a look and tell me what you think" | "Please upvote us" |
| "Come ask us questions in the comments" | "We need votes in the first hour" |
| "Share it if you think it is useful" | "Share this with everyone you know" |
| "Does this make sense for your workflow?" | "Can you get your team to vote?" |
Who to ask
- People who have used the product. They can evaluate it, and their attention is genuinely useful to you.
- People with the problem. Even if they will not buy, they can tell you whether the description communicates.
- People who asked to be told. Anyone who ever said "let me know when it launches" — and you should have written those names down.
- Peers in your category. They will look at it properly and their feedback is informed, even though they will never buy.
- Not everyone in your contacts, and not people you have not spoken to in three years. A broadcast is recognisable and it spends the whole network for the return of the least interested part of it.
How to phrase it
- 1
Individually, with a reason
One or two sentences naming why you are asking them specifically. "You mentioned struggling with reconciliation last time we talked" is a reason. "Hey, we're launching!" is not.
- 2
Ask for evaluation, not support
"Would you take a look and tell me if the description makes sense?" gets a real answer and often produces the attention anyway — because a person who looked and liked it shares it without being asked.
- 3
Give them something to do besides voting
"The most useful thing would be a question in the comments" or "tell me what is unclear". A specific ask is easier to act on than a general one.
- 4
Say what it is for
"We're trying to find out whether the description communicates" is honest and makes the request small. "We're trying to hit the top five" makes it large and transactional.
- 5
Make declining easy
"No worries if not — I know it is a busy week." A contact who can decline comfortably stays a contact.
The message, in full
Hi [name] — we're launching [product] on [day]. You mentioned [specific thing] when we last spoke, so I thought you'd have a view. Would you take a look and tell me whether the description actually communicates what it does? If it seems useful, a question in the comments would help more than anything else. No pressure either way.
Timing and volume
- Send the day before, not the morning of. People need time to look, and a same-day request reads as an afterthought.
- Cap it at roughly thirty people. Beyond that it becomes a broadcast, the messages get shorter, and the personal reason disappears — which is the only thing making it acceptable.
- One follow-up maximum, and only to people who replied positively and then did not act.
- Never the same text twice. Copy-paste is detectable in tone, and if two recipients compare notes the campaign is visible.
What to do with the responses
| Response | Do this |
|---|---|
| They looked and asked a question | Answer it properly, in the thread where everyone can see it. This is the highest-value interaction of the day |
| They looked and shared it unprompted | Thank them specifically and privately. Note what they said — it is better copy than yours |
| They said they would and did not | Nothing. Do not follow up about it. The relationship is intact and that is worth more |
| They gave honest criticism | Thank them and act on it. Then tell them what you changed — this converts a critic into an advocate more reliably than anything else |
| They did not reply | Nothing at all. People are busy and this is a small request |
What the network is actually for
Launch day is the least valuable use of the people who know you. The valuable uses are quieter and repeatable:
- Introductions to someone with the problem. A warm introduction to a potential first customer beats a hundred votes.
- Honest feedback on a description or a price. Before it is public, where it can still be changed.
- A reference when someone asks. "Do you know anyone using X" is a real conversation, and a named recommendation from a trusted person is the strongest sales asset a small company has.
- Early hires and collaborators. The people who will work for a company with no revenue are usually already known to the founder.
A network can be spent once or invested repeatedly. Asking for votes spends it; asking for an honest look invests it — and the second usually produces more of the first than asking directly would have.
More in Community playbooks
- How to Find and Join AI Newsletter CommunitiesNewsletter authors and their reader communities are a reachable audience for a new AI product. How to find them, get on their radar, and get mentioned.
- Product Hunt Community: How to Engage Before You LaunchA launch-day platform rewards the people who were already there. How to build standing in a launch community in the months before you need it.
- How to Answer Questions in Public Without SellingThe helpful-answer channel: how answering strangers' questions builds an audience for an AI product, what a good answer contains, and where the line is.