Reddit Outreach Templates for Founders

Reddit outreach fails for a predictable reason: it reads like outreach. The platform's entire culture is built on the assumption that a comment is a genuine contribution, not a scripted move, and anything that reads like copy-paste gets called out and downvoted fast, often publicly, in a way LinkedIn or email never does.

That doesn't mean templates are useless - it means the template has to be a structure you fill in with real specifics every time, not a paragraph you paste unedited. Below are six that work, each with the parts you must customize marked out, plus two situations where you should skip the template entirely and write from scratch.

1. The public reply to a recommendation request

Been using [Product] for [specific use case] for about [timeframe] - the [specific feature] has been genuinely useful, though [honest limitation] if that matters for your case. Happy to answer questions if you want more detail.

Customize: the timeframe and use case need to be true and specific, not generic. The honest limitation is not optional - a reply with zero downside reads as a plant, and experienced Redditors will say so in a reply of their own.

2. The cold DM after a good public interaction

Hey - saw your comment in [thread] about [specific thing they said]. I work on [Product], which handles [specific relevant capability]. Not trying to sell you anything here, just thought it might be relevant given what you mentioned - happy to share more if useful, no worries either way.

Customize: reference something they actually said, specifically. A DM that could have been sent to anyone reads as spam even when the product is genuinely relevant. Only send this after a public interaction, never cold to someone who's never engaged with you - unsolicited DMs from strangers are one of the fastest ways to get reported.

3. The founder-transparency reply on a "who built this" question

Full disclosure, I'm the founder of [Product] - didn't want to reply without saying that upfront. [Answer the actual question they asked, honestly, including if the honest answer is "we don't do that yet."]

Customize: disclosure goes first, every time, not buried at the end. Reddit tolerates founders replying about their own product far more than it tolerates the disclosure feeling like an afterthought.

4. The follow-up after someone tries your product from a thread

Hey, saw you signed up after [thread] - just wanted to check if you had any questions getting started, and genuinely curious what prompted you to look in the first place if you don't mind sharing. No pitch here, just want to make sure it's actually useful for what you needed.

Customize: only send this if you can plausibly know they came from that thread (a UTM-tagged link, a self-reported source). A generic version of this sent to every signup reads as automated the moment it lacks the specific reference.

5. The comparison-thread reply

[Tool A] is solid for [specific use case] but [specific limitation]. [Tool B] is better if [different use case]. We built [Product] for [specific gap between A and B] - not right for everyone, but worth a look if [specific condition] is your situation.

Customize: you have to actually know something true about the other tools named. Skipping them to only talk about your own product is the single fastest way to get a comparison reply flagged as evasive. See how to reply to Reddit posts as a founder for the full breakdown of this post type and six others.

6. The re-engagement on an old thread that's still getting traffic

Realize this thread's a bit old, but it's still showing up when I search [topic], so leaving this for anyone who finds it later: [update or answer, written to stand alone without needing the original context].

Customize: write it to make sense to someone arriving from a Google search years later, not just to the original poster. Old, still-ranking threads get meaningful ongoing traffic, and a well-placed reply on one keeps working long after the original conversation ended - this is part of why Reddit threads outrank fresh content on Google in the first place; see why Reddit is outranking your SaaS on Google for more on that dynamic.

Two situations where you should not use a template

• Someone is venting about a competitor, upset or emotional. Templates read as cold exactly when warmth is what the moment calls for. Write a one-off, specific acknowledgment before anything else - see the competitor-complaint template in the reply-by-post-type guide for the shape of it, but don't paste it verbatim into an emotionally charged thread.
• A long, detailed thread where several people have already given thoughtful answers. A templated reply here adds nothing over what's already there. If you don't have something genuinely new to add - a real number, a disagreement, a trade-off nobody's mentioned - it's better to skip the thread than post filler.

The real bottleneck isn't the template, it's finding the thread in time

Having the right template ready solves the "what do I say" problem. It doesn't solve the harder problem: finding the thread while it's still active, before three other replies have already answered the question and yours reads as an echo. ThreadyGo surfaces high-intent Reddit threads as they happen and drafts a reply tailored to the specific post, so you're adapting a real starting point instead of writing cold every time. Try it free to see it against your own market.