How to Launch With Cold Outreach: Messages to Strangers That Get Replies
Cold outreach for a launch means writing to a small number of specific people who have shown they have the problem, with a short message that says why you chose them and asks for something small, like a five-minute look. Send in batches of about ten, change one thing per batch, follow up once and measure replies and activated users. Never buy lists, scrape addresses or send identical messages.
When does cold outreach make sense?
When you can describe your user so precisely that you could point to ten of them. A scheduling tool for physiotherapy clinics, a licence-check helper for property managers, a build monitor for open-source maintainers: each has a findable person at the other end. The more exactly you can name who is on the other end, the more cold outreach beats waiting for strangers to find you.
It fits badly when your user is an anonymous consumer with no public trace, such as someone who might download a casual mobile game. You cannot write to them one by one, and trying drifts into mass messaging. Use a public listing and posts in the right places for those, and keep outreach for people you can identify by role, project or a public complaint.
How do you build a list of people to write to?
From public signals that someone has the problem now. Each name on the list should carry a reason you can state in one line. Do not buy a list and do not scrape addresses from sites, since both fail on trust and often on the rules of the places that hold the data.
- People who asked a question in a public forum or thread that your product answers, in the last few weeks.
- Authors of posts or repositories about the exact workaround your product replaces.
- Owners of small businesses in the trade you serve, who list a public contact address on their own website.
- People who left a review of a rival tool that names a frustration you solve.
Keep it in a plain spreadsheet with columns for name, where you found them, the one-line reason, the date you wrote, the reply and the outcome. Start with about thirty names, a number you can adjust. It is small enough to do well and large enough to show a pattern.
What goes in the message?
Four parts, in this order: why you are writing to this person, what you built, what you ask for, and how to say no. Make the ask small. Do not ask for a purchase or a call; ask for five minutes with the product, or one question answered.
Subject: Your question about [specific thing they asked] Hi [name], I saw your post on [where] about [their problem, in their words]. I have been working on [product], which [what it does in one sentence], partly for that reason. Would you be willing to try it for five minutes and tell me where it is confusing? It is free to try at [link]. If it is not useful, tell me and I will not write again. [your name] [where you are based, and how to be left out of future messages]
Hi [name], a quick follow-up on my note from [day]. Since then I have [one real change or fact]. If it is still not relevant, tell me and I will leave it there.
More wording sits in the cold DM templates for first users and the feedback request template. Edit every message so the first sentence could only have been written to that person.
How many messages should go out, and how fast?
In batches of about ten, with a pause to read the results before the next. Within a batch, vary nothing. Between batches, change one thing: the subject line, the first sentence or the ask. That way a difference in the reply rate points to a single cause. Send one follow-up about a week after the first message, and no more. A person who has not answered two messages has answered.
Do not scale up until the pattern is clear. If the right people reply and try the product, extend the list. If they do not reply, rewrite before you send more; sending a bad message to a larger list only lowers your sender reputation and uses up people you could have reached once with a better one.
What rules apply to unsolicited messages?
They vary by country and by platform, so check the ones that apply to you and the recipient. In the United States, the FTC’s CAN-SPAM compliance guide for business covers commercial email: accurate sender details, a subject line that is not deceptive, a postal address and a way to opt out that you honour promptly. We could not open that page with our own automated check, so read it yourself rather than relying on this summary. Other countries have different rules, some stricter about writing to people who have not asked.
- LinkedIn. Its professional community policies (read 13 November 2026) say not to use the invitation feature to send promotional messages to people you do not know, and rule out untargeted, unwanted or repetitive promotional messages.
- Discord. Its community guidelines (read the same day) tell users not to send unsolicited bulk messages.
- Anywhere. Keep a do-not-contact list, remove anyone who asks at once and never write to them again.
Nothing here is legal advice. If you plan to write to people at scale, get advice for your own case.
What should you measure, and what does each number tell you?
| Number | How to count it | If it is low, change |
|---|---|---|
| Reply rate | Replies divided by messages sent | The subject line, the first sentence or who is on the list |
| Useful reply rate | Replies that engage with the problem divided by messages sent | The reason you give for writing to them |
| Tried it | People who opened the product divided by people who replied | The size of the ask or the friction in your first screen |
| Activated | People who reached the key action divided by people who tried it | The product’s first minute, not the message |
Judge each batch against the last one, not against a number from somewhere else. If three batches with different wording get nothing from the right people, the problem is probably who you picked, or whether they care enough. That is useful to know before you spend more weeks on it. If it works, the replies become your first users, and the first 100 users playbook shows what to do next. Put the product on a public page too, because someone you write to will look you up: you can launch your product free with no account and no queue. For problems that people are asking others to solve, see the ideas board.
Frequently asked questions
How many cold messages should I send for a launch?
Start with a list of about thirty names, sent as three batches of ten, then judge by results, not by quantity. A short list of well-chosen people with a specific reason each beats a long list with a generic message. Extend only when the right people reply and try the product.
Is cold outreach the same as spam?
Not when it is targeted, honest and easy to decline, but the line is thin. Writing to a person with a visible need, saying why you chose them, asking for something small and stopping when asked is outreach. Sending the same note to a bought list is spam, and the rules treat it that way.
Should I use email or direct messages on a social network?
Use whichever the person already uses for this kind of contact, and follow that platform’s rules, some of which restrict promotional messages to people you do not know. A public contact address on a person’s own site is a clearer invitation than a private message on a network.
What if nobody replies?
Check who you wrote to before you change the wording. If the people do not match your user, or have no current need, no message will work. Then check the subject line and the first sentence. Change one thing in the next batch of ten and compare reply rates.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.