Cold DM Templates for Finding Your First Users Without Spamming Anyone
A cold DM to a possible first user works when it is sent to a person who has already said something about the problem, quotes their own words back, asks a question instead of pitching, and is short enough to read in ten seconds. Send one message and at most one follow-up, by hand. Three templates follow: a reply to someone who described the problem, a request for a research chat, and a single gentle follow-up.
Who should get a cold DM, and who should not?
Message people who have left a trace of the problem you solve. That might be a post asking how to do the job, a comment complaining about the tool you are replacing, a question in a forum or an answer in an interview. A trace gives you a reason to write and a sentence to quote, and it separates a conversation from spam. A list of a thousand strangers who merely have the right job title gives you neither.
| Where you found them | What to reference | What to avoid |
|---|---|---|
| A public post asking for help with the problem | The exact thing they asked | Pasting a link before they know who you are |
| A comment complaining about a rival tool | The specific complaint, without naming the rival as bad | Attacking the tool they use |
| Their own writing, such as a blog post or thread | One idea from it you found useful | Flattery with no specifics |
| A mutual connection | The name of the person who suggested them, with their permission | Dropping a name without asking |
Skip anyone who has asked not to be contacted, anyone whose profile says no pitches, and anyone you cannot connect to the problem in one sentence. If you do not know where the right people are in the first place, the first 100 users playbook and the answer on getting first users for free start earlier in the process.
What are the rules before you send anything?
- Read the platform’s rules on unsolicited messages. Each platform and community has its own, including limits on bulk or automated messaging. Breaking them can get an account restricted, and that costs you the channel.
- Send by hand. Automated sequences are against the rules of many platforms and are easy to spot in a reply that says “Hi [first name]” literally.
- One message, one follow-up. After that, stop. A third message is no longer persistence; it is pressure.
- Ten seconds to read. About sixty words. If it needs scrolling on a phone, cut it.
- Do not ask for a favour in the first line. Open with the thing you noticed.
Template 1: to someone who described the problem
This is the one to use most. It proves you read what they wrote, gives them a reason to answer and puts the product second.
Hi [first name], I saw your post about [exact problem, in their words]. I'm building something for that exact annoyance: [one sentence, no adjectives]. It's early, so I'm not selling anything. I'm trying to find out if it actually helps people who [describe their situation]. Would you be up for trying it and telling me where it falls apart? Happy to share it here if you say yes. If not, no problem at all.
Template 2: a research chat, with no product in it
Use this when you are not ready to show anything, or when you need to understand the problem before you build more. The product is not mentioned, which makes it easier to say yes and gives you cleaner answers.
Hi [first name], I'm researching how people handle [the job or workflow]. I read your [post / answer / article] about [specific point] and it matched what I've been hearing. Could I ask you three questions over ten minutes of chat, here or on a call, about how you do it today? I'm not selling anything, and I'll share what I learn from the other people I talk to if you're interested.
If they say yes, ask about the last time the problem happened, what they did, what it cost and what they tried. Ask about the past, not hypotheticals; what people say they would do rarely matches what they did.
Template 3: the one follow-up
Hi [first name], following up once on my note below. Totally fine if it's not for you, and I won't ping again. If you're curious, the shortest way to see it is [one link or one sentence].
Sending that and then genuinely leaving the person alone is part of the technique. People remember who respected their silence, and your next message to someone else in their community may land better for it.
How do you keep a record and learn from it?
Keep a simple list with the person’s name, where you found them, what you quoted, the date you sent it and what happened. After twenty messages, look for patterns: which kind of trace got replies, which opening you used when they replied and which words people echoed back. Those words are your marketing copy.
- Write down the trace before you write the message. No trace, no message.
- Draft the first sentence from their words, not yours.
- Send ten and wait. Learn from the replies before sending ten more.
- When someone says yes, treat them as a guest: give them what you promised in the next hour.
What should you send people to?
A page that makes sense to a stranger without you. A public launch page does that job, and you can launch your product free to get one; its comment thread also gives someone who is curious but shy a way to react without replying to you in private. The wider approach is in the cold outreach playbook. If the people you are looking for work in a field like this one, the board’s real estate ideas show how problems in a trade are described by the people who have them.
Frequently asked questions
Is cold messaging people allowed?
It depends on the platform and the place you found the person. Many platforms restrict unsolicited bulk or automated messages, and some communities forbid DMs for promotion. Read the rules before you send, message by hand, keep it relevant to something they said, and respect any request to stop. Different countries also have rules for commercial email.
How long should a cold DM be?
About sixty words, readable in ten seconds on a phone. Open with the specific thing you noticed, state in one sentence what you are building, and end with one small question. If you find yourself explaining features, cut them; the goal of the first message is a reply, not a sale.
Should I mention my product in the first message?
Sometimes. If the person described the exact problem, one sentence about what you built is fine, framed as a request for their opinion. If you are still learning the problem, leave the product out and ask for a short chat. Either way, do not include a long link list or a pricing page.
What if I get no replies?
Check whether the message quoted a real trace of the problem, was short and asked something easy. Change one thing and try ten more people. Silence from strangers is common. If a different message to a different group also gets nothing, the problem may not be urgent enough, which is useful to know.
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.