What to Write in a Comment-Led Outreach Comment (7 Templates)

Cold LinkedIn DMs get deleted on sight. Connection requests from strangers with a pitch attached get ignored at rates above 90 percent. The fix is not a better pitch; the fix is to stop being a stranger before you reach out.

[Comment-led outreach](/glossary/comment-led-outreach/) works by making you familiar first. You show up in someone's notifications every day for a week or two by leaving thoughtful comments on their posts. When the connection request finally arrives, they recognize your name. Recognition drives acceptance. Acceptance lets you start a conversation that actually gets read.

But most people freeze when it is time to write the comment. They default to generic praise ("Great post!") that adds nothing, or they overcorrect and write a sales pitch disguised as engagement. Both fail. The comment has one job: make the author glad you showed up. Do that often enough, and the connection request becomes a formality.

What makes a LinkedIn outreach comment effective?

A good outreach comment passes three tests. First, it proves you actually read the post. Specificity is the signal. Reference a line, a number, a example the author used. Generic comments ("Love this!") get skipped because they could have been pasted under any post.

Second, it adds value. Share a related observation, point to an adjacent idea, or ask a question that moves the conversation forward. The author should finish reading your comment and think, "That is a smart person." Not because you flattered them, but because you contributed something worth their time.

Third, it positions you without pitching. A well-written comment lets your expertise show through the substance of what you say. You never mention your product, your service, or your calendar link. The goal is to be remembered, not to close a deal in the comments.

Template 1: The Pattern Spotter

Use this when the post describes a problem, result, or observation, and you have seen the same thing play out elsewhere.

Structure: "We saw the same thing when [specific context]. The thing that made it worse / better was [insight]."

Example: A founder posts about reply rates dropping after their team scaled cold outreach. You write: "We saw the same thing when our SDR team grew past four people. The thing that killed reply rates was templatized personalization, buyers could tell it was mail-merge. What brought it back was narrower list targeting so reps could actually reference the prospect's recent work."

Why it works: You are not bragging or pitching. You are confirming their experience with your own, then offering a variable they may not have considered. It builds credibility and gives them a reason to check your profile.

Template 2: The Adjacent Case

Use this when their post reminds you of a related example from a different industry, channel, or context.

Structure: "This is exactly what [other context] figured out in [time or place]. They [action], and it worked because [reason]."

Example: A sales leader posts about the death of cold email. You write: "This is exactly what B2C brands figured out when SMS open rates collapsed in 2019. They moved spend back to owned channels, push notifications and in-app, because the buyer was already paying attention there. Same principle: meet people where they already know you."

Why it works: You are drawing a parallel that adds perspective. It shows you think across domains, and it reframes their problem as part of a broader pattern. That makes you interesting.

Template 3: The Contrarian (with respect)

Use this when you respectfully disagree with part of the post, and you can back it up with a specific reason or example.

Structure: "I mostly agree, but I have seen [different outcome] when [specific condition]. The difference seems to be [variable]."

Example: A marketer posts that video outperforms text on LinkedIn. You write: "I mostly agree, but I have seen text posts with a bold thesis outperform talking-head video when the audience is senior execs. The difference seems to be reading speed, they can scan a text post in ten seconds; video forces them to commit two minutes they do not have."

Why it works: Disagreement, when it is specific and respectful, is more memorable than agreement. You are not there to argue; you are there to add nuance. The author will remember your name because you made them think.

Template 4: The Practical Extension

Use this when the post shares advice or a framework, and you can offer a concrete next step or a related tactic.

Structure: "One thing we added that made this even better: [specific tactic]. It [result or reason it helped]."

Example: A founder posts a framework for qualifying inbound leads. You write: "One thing we added that made this even better: a single disqualification question in the first email, 'Are you the person who signs the contract?' If no, we route them to a different sequence. It cut our demo no-show rate by half because we stopped booking people who couldn't buy."

Why it works: You are building on their idea, not competing with it. The comment makes their post more useful to everyone who reads it, which makes them look good. They will remember you as someone who helps.

Template 5: The Question That Advances

Use this when the post raises an interesting point but leaves a variable unaddressed, and you genuinely want to know the answer.

Structure: "This makes sense. I am curious, how did you handle [specific challenge or edge case]?"

Example: A VP of Sales posts about moving from cold calling to warm intros. You write: "This makes sense. I am curious, how did you handle the timing gap? Warm intros take weeks to orchestrate, but pipeline has to stay full in the meantime. Did you run both in parallel, or did you bank pipeline before you made the switch?"

Why it works: A good question shows you understand the nuance of what they are talking about. It is not a gotcha; it is genuine curiosity. The author is likely to reply, which starts a thread, which makes you visible to everyone following the post.

Template 6: The Specific Praise

Use this when one part of the post is particularly sharp, counterintuitive, or well-stated, and you want to highlight it.

Structure: "The line about [quote or paraphrase] is the whole game. Most people miss that because [reason]."

Example: A consultant posts about why founders should fire bad-fit clients. You write: "The line about 'a bad client blocks the seat a good one could fill' is the whole game. Most people miss that because they only count revenue they have, not revenue they are turning away by staying busy with the wrong work."

Why it works: Specific praise is rare. Most comments say "Great post!" and scroll on. When you quote a line back and explain why it matters, you prove you read carefully. The author notices.

Template 7: The Bridge to Another Idea

Use this when the post connects to a book, article, study, or framework your audience should know about.

Structure: "This connects to [source]. They found [relevant insight]. Same principle."

Example: A founder posts about the importance of showing up consistently in buyers' feeds. You write: "This connects to Robert Zajonc's mere-exposure research from the 1960s. He found that repeated exposure to a neutral stimulus, even a shape, made people rate it more favorably. Same principle: familiarity drives preference, even when the person can't explain why."

Why it works: You are adding intellectual depth without showboating. The author gets a reference they can use in future posts, and you position yourself as someone who reads widely. It is a quiet flex.

How often should you comment on the same person's posts?

Daily visibility builds familiarity without feeling like spam. In Well Met's comment-led outreach method, operators leave comments on a prospect's posts every day they publish, for one to two weeks before sending a connection request.

The cadence matters. One comment every three weeks is invisible. Ten comments in one day is obvious and awkward. One thoughtful comment per post, over the span of a week or two, creates the pattern: this person pays attention, adds value, and keeps showing up.

Familiarity is built through repetition in a natural context. Your name appears in their notifications multiple times, attached to comments that made them think or smile. By the time the connection request lands, you are not a stranger. You are the person who said that smart thing about their pricing post last Tuesday.

What should you never write in an outreach comment?

Avoid anything that feels like a pitch. No "We help companies like yours..." or "I'd love to chat about..." or "Check out our solution." The comment section is not the place to sell. The goal is to be interesting enough that the author clicks your profile after reading what you wrote.

Skip generic praise. "Great post!" and "Love this!" and "So true!" add nothing. They are invisible. If you cannot think of something specific to say, skip that post and wait for the next one. Silence is better than filler.

Do not ask for a connection in the comments. It forces the author to say yes or no in public, which is awkward. Let the value-add comment do its work over time, then send the connection request later when your name is familiar.

How do you scale comment-led outreach without sounding like a bot?

Templates are a starting point, not a script. Every comment must reference something specific from the post you are responding to. That specificity is what proves a human wrote it. If you can copy and paste your comment under ten different posts without changing a word, you wrote a bad comment.

The Pattern Spotter, the Adjacent Case, and the Practical Extension templates all require you to fill in the context from your own experience. That customization step is where the value comes from. A good operator can write a strong comment in under two minutes because they have the templates memorized and the examples ready.

Well Met's done-for-you service handles this at scale by assigning real people to write every comment. Each operated profile or rented agent leaves roughly 100 comments a day, all personalized to the post, all written to build familiarity without pitching. The connection requests that follow convert at rates several times higher than cold outreach because the groundwork was already done.