Reddit is one of the few places where people complain honestly, without a filter. That makes it a great place to find people with real problems. It is also a place where a badly judged direct message gets you ignored, reported or banned.
This guide shows how to do customer discovery on Reddit without being spammy. You will get etiquette rules, a simple message structure, a copyable template and worked examples. The goal is a real conversation, not a pitch.
Why most Reddit outreach feels like spam
People don't hate being contacted. They hate being treated as a lead.
Spammy messages usually share the same flaws:
- They open with a product name or link.
- They could have been sent to anyone. Nothing shows you read the post.
- They ask for something big, like a demo, a signup or a long call.
- They ignore the context of the community where the person posted.
Customer discovery is the opposite. You are not selling anything yet. You are trying to understand a problem before you build. If your message reads like that, and is honest about it, it lands differently.
Etiquette to follow before you send anything
Settle these points first. They matter more than your wording.
Read the subreddit rules
Some communities ban self-promotion or discourage unsolicited contact. If a subreddit's rules say no, respect that. Plenty of other threads are open to you.
Check the person's post, not just the headline
Read the whole thread and the comments. Maybe the problem was already solved in a reply. Maybe the poster said something that changes how you should ask. Skimming leads to generic messages.
Contact people who described a problem, not people who are selling
Someone venting about a recurring headache is a good candidate. Someone promoting their own tool is probably not. A person asking "what should I use for X?" may welcome a reply in the thread itself.
Send one message, not a sequence
If you get no reply, let it go. A single polite follow-up after a long gap is the most you should consider. Repeated nudges turn curiosity into pressure.
Be a real person
Use your own account, ideally one with some history that isn't only outreach. Don't use fake personas. Don't claim to be a researcher if you're a founder. Say what you are.
Keep the thread in view
Sometimes a public comment is the better first step. A useful reply under the post shows you're engaging in good faith. A message can follow if the conversation goes somewhere.
Choose people worth talking to
A good first message depends on a good target. Look for posters who:
- Describe a specific situation, not a vague complaint.
- Mention what they've already tried.
- Explain the cost of the problem in time, money or stress.
- Wrote recently, so the problem is still fresh in their mind.
Take this post from r/sysadmin, which describes a messy post-acquisition situation:
"8 months post-acquisition and we still have 200 people with active accounts in both tenants. Some line-of-business apps were never migrated."
u/Prestigious-Fun-9680, original thread
That is specific. There's a timeline, a number and a cause. You can ask about it intelligently.
Now compare it with a post from r/webdev:
"one of my client had his payment delayed... it affected my personal account as well. Mine also got deactivated/suspended."
u/Future_Carpenter_910, original thread
Also specific, and clearly frustrating. Both give you something concrete to reference.
The four-part structure of a respectful first message
Keep it to a few short sentences. Someone should be able to read it in ten seconds.
1. Reference their actual post
Name the topic or quote a few words. This proves you read it and tells them why they are getting a message from a stranger.
2. Say why you're reaching out
One honest sentence. For example: you're exploring solutions in this space and want to understand how people deal with it today. Don't be coy about being a founder or builder if that's what you are.
3. Make a small, specific ask
"Would you be open to a quick 10-minute chat?" is easier to answer than "Can we jump on a call to discuss your workflow?" You can also offer to keep it in messages. Some people prefer typing to talking.
4. Lower the pressure
Tell them you're not selling anything and that it's fine to say no. This one line removes most of the spam smell, but only if it's true.
A message template you can copy and adapt
Here is a short pre-written message in the style SaasNiche offers for this kind of outreach. It is the same wording the sample message for the r/sysadmin post uses:
Hey! I came across your post about "Streamlining User Identity Management Post-Acquisition" and found it really insightful.
I'm exploring solutions in this space and would love to hear more about your experience. Would you be open to a quick 10-min chat?
No sales pitch — just trying to understand the problem better before building anything.
Subject line: "Quick question about your post".
It works because it is short, names the post, states the purpose and asks for little. Edit it before you send it. Add a detail that only someone who read the thread would know. That one change moves it from template to real message.
Examples you can adapt
These are original examples built around the two posts above. Treat them as starting points, not scripts.
Example 1: a post with a clear timeline
Hi, I read your post about still having duplicate accounts months after an acquisition. The part about apps that never got migrated stood out. I'm researching how IT teams handle this and I'm not selling anything. Could I ask you two or three questions here in messages? Totally fine if you're too busy.
Why it works: it picks one detail, makes the ask small and offers a text-based option.
Example 2: a post with an emotional charge
Hey, that story about your account getting suspended because a client's payment was delayed sounds really frustrating. I'm trying to understand how freelancers deal with this kind of thing. Would you be open to a short chat about what happened and what you did to fix it? No pitch, just research.
Why it works: it acknowledges the problem as a human before asking for anything.
Example 3: a gentle follow-up in the thread
If messaging feels too forward, reply publicly first:
This is a tough one. Did you find any workaround that actually held up? I'm curious how others here are handling it.
If the poster engages, you can move to a message with context already established.
What to do when someone replies
A reply is not a signal to start selling. It is a signal to listen.
- Thank them for their time.
- Ask about the last time the problem happened, not about hypothetical features.
- Ask what they tried and what it cost them.
- Ask what they'd do if nothing changed.
- Keep notes, and ask before you quote them anywhere.
- If they ask what you're building, answer honestly and briefly.
Avoid leading questions like "Would you pay for a tool that fixes this?" Past behaviour tells you more than polite promises about the future.
When the conversation ends, thank them again. If you have something useful to share later, such as a summary of what you learned, ask whether they'd like it.
Mistakes that get messages ignored
- Pasting the same text to dozens of people with only the username changed.
- Leading with a link to your landing page or waitlist.
- Flattery with no substance, like "great post!" followed by an ask.
- Asking for an hour from someone who doesn't know you.
- Messaging people in communities that forbid it.
- Taking silence personally and following up repeatedly.
A better habit is to send a small number of carefully written messages and learn from the replies. Quality beats volume here, because the whole point is the conversation.
Where a tool can save time
Finding the right posts is usually the slow part. You can search Reddit by hand, but it takes hours to turn threads into a list of people with real problems.
SaasNiche scans Reddit communities to surface pain points, each scored 0–100 for intensity, frequency and willingness to pay, and backed by verbatim user quotes. Each quote shows the username and a source link, so you can check the original post before you write to anyone. From there, you can message the original poster using a pre-written message you can edit before sending.
If you want to try this approach, start with the 7-day trial at saasniche.com, pick one pain point, read the original thread and send one carefully edited message.
FAQ
Is it okay to DM people on Reddit for customer discovery?
Often yes, but it depends on the community and the person. Check the subreddit's rules first, contact people who described a problem relevant to your research, and be clear that you're not selling. If someone declines or doesn't reply, leave it there.
How long should a first Reddit message be?
Short enough to read in about ten seconds. A few sentences is plenty: the post you saw, why you're reaching out, a small ask and a way to say no. Longer messages tend to feel like pitches.
Should I mention my product in the first message?
Usually not. Customer discovery is about understanding the problem. If you haven't built anything yet, say so. If you have, answer honestly when asked, but don't lead with it.
What if nobody replies?
That is normal. Many people won't see or answer messages from strangers. You can try a public comment in the thread, or reach out to other posters who described the same problem. Avoid repeated follow-ups to the same person.
Should I offer something in return for their time?
You can, if it's appropriate and honest. Some founders offer to share what they learn or to answer questions about their own field. Keep any offer modest and don't imply a reward that you can't deliver.