How to Reach Out After a Prospect Posts on Linkedin

Why "Saw your post" falls flat

Think about it from her side. She posted to start a conversation with her peers. A DM that quotes her post back to her and pivots to a demo request tells her you read the first line and saw an opening. It's a bit like answering a question someone asked at a dinner table by handing them a brochure.

The fix isn't to hide the fact that you saw the post. It's to respond to what she said, in the place she said it, before you ask for anything. That usually means a public comment first and a DM later, if at all.

There's also the type of activity to think about. A post is the person speaking in their own words, so it gives you the most to work with. A comment on someone else's thread is often sharper, because people say more specific things in replies than in their own posts. A like is the weakest of the three. It tells you what caught their eye, but there's nothing to respond to, so I treat likes as context for later rather than a reason to write today.

Speed helps, but only for public replies

Timing matters most when you're joining a thread. A comment in the first hour sits near the top while the author is still replying to people. The same comment two days later lands under fifty others, and the author has moved on.

That's where alert speed comes in. On our Free plan, refresh is best effort, which is fine to test the idea on one person. Essential and above refresh in near real time, which is what you want if public replies are part of your play. Email alerts work on every plan, and Slack alerts start on Business, so a team channel can see the post while it's still fresh.

DMs are different. Nobody expects a reply to a post in their inbox within the hour, and a message that arrives ten minutes after posting can feel like you were waiting by the door. If you're going to DM, a day or two later is fine, and it lets you reference the conversation that happened under the post.

A first touch in three steps

Once the alert lands, I'd work through it in this order.

1. Read the whole thing, including the replies

Open the link in the alert and read the full post and the top comments. People often clarify their real point in a reply to a friend. In the VP example, she might add in a reply that her biggest problem is ramp time for new hires, which is a far better hook than "SDR onboarding."

2. Leave a comment that adds something

Answer her question from your own experience, or share one specific thing that worked for a team you know. Keep your product out of it. A good test: would this comment still be useful if your company name weren't on your profile?

A comment along these lines works well, with your own numbers in place of these.

We cut first-meeting ramp from about six weeks to four by having new SDRs shadow
discovery calls in week one instead of week three. The calls taught them the
objections faster than any doc did. Curious what's been slowest for your team so far?

The numbers in a comment like that should be real ones from your own experience. Don't borrow a stat to sound credible, because she might ask a follow-up.

3. Decide whether a DM makes sense

If she replies to your comment, you have a natural opening. A DM a day later can pick up where the thread left off: "Following up on the ramp-time thread. We wrote up how three teams structure week one, happy to send it if useful." It offers something, it asks for nothing big, and it's easy to ignore politely.

If she doesn't reply, don't chase the post. Let the comment do its work, and wait for the next signal. One thoughtful comment makes your name familiar, and that's what makes a later cold email less cold.

What to do with comments and likes

Comments on other people's threads need a lighter touch. If a prospect comments on a competitor's post asking how a feature works, jumping into that thread to pitch yourself looks bad to everyone reading it. I'd take that comment as research. It tells you what she's evaluating and what she cares about, and you can use it in your next email without ever mentioning where it came from.

Likes are best handled in bulk. If someone likes three posts about pipeline forecasting in a week, that's worth a line in your account notes. It's not worth a message on its own.

This is also where filtering saves your attention. If you track a buying committee, you'll get a lot of posts about conferences, hires, and holidays. Include keywords on the tracker (a competitor's name, "pricing," "hiring SDRs") let the relevant posts through and drop the rest. Our keyword filter guide shows how include and exclude lists combine. Keyword filters only apply to posts and comments, since likes have no text of their own.

Does the same thing work on X?

Mostly, yes, with two differences. X moves faster, so a reply that's a few hours late often misses the conversation entirely. And replies are a bigger part of how people talk there, so a sharp reply to a prospect's thread can carry more weight than it would on Linkedin.

We track posts and replies on X. We don't track likes on X, since X made likes private in 2024, so you'll only see what people say, not what they react to.

Where this fits in your outreach

None of this replaces your sequences. It gives you a few warm moments a month with the accounts you care most about, and the plan you need depends on how many people that is.

Prices are from our pricing page as of October 2026. For a single rep working a handful of named accounts, Essential's 5 Linkedin profiles covers the decision makers who post. If a team wants the alerts in a shared Slack channel or logged in a CRM, Business is the floor. Our post on logging Linkedin and X activity on HubSpot contacts covers the CRM side.

One limit worth knowing before you plan around this: MultiFollow tracks what people post, comment, and like. It doesn't track job changes, so if a champion moving companies is your main trigger, you'll want an enrichment tool for that.