Loading
October 28, 2026
Subscribe
October 28, 2026

LeadBase

Turn LinkedIn engagement into scored leads

Engagement-Led Prospecting: The Half Everyone Runs and the Half With the List (2026)

An open notebook with two blank facing pages lying on a round pale wooden table, photographed from above, with a small green leafy plant at the right edge and a dark patterned rug and brown leather chair arm in the background.

Quick answer: Engagement-led prospecting means you pick who to contact based on engagement, not on a search filter. It runs in two directions. Outbound: you comment on prospects’ posts so your name is familiar before you message. Inbound: you read who reacted to and commented on your own posts and message the ones who fit. Almost every guide covers the first and skips the second, and the second is where the list already exists.

I did this by hand for two years to feed my coaching pipeline, copying reactor lists off my own posts into a spreadsheet, before LeadBase existed. Here is what I got wrong in the first year.

Engagement-led prospecting has two halves

The standard write-up on engagement-led prospecting goes like this: pick fifty target accounts, follow the decision makers, leave a thoughtful comment on their posts three times a week, then send a connection request once they recognise your name. That is the outbound half. It works. It is also slow, it does not scale past the number of comments you can write with a straight face, and it treats your own content as a warm-up act.

The inbound half is the one that gets a sentence, if that. Every post you publish generates a list of people who took an action on it. LinkedIn shows you that list for free: the post analytics page counts reactions, comments and reposts per post, and clicking the reaction count on the post itself shows you who they were. Those people chose to engage with your idea. Some of them fit your buyer profile. Nobody in that list needs a warm-up.

If you only run the outbound half, you are doing the expensive part and throwing away the cheap part.

Why the inbound half gets ignored

Three reasons, from watching myself do it.

It does not feel like prospecting. Reading your own notifications feels like vanity. Commenting on a VP’s post feels like work. So the prospecting time went outbound and the inbound list sat there.

The list is messy. Reactors on any post are a mix: friends, peers, recruiters, people in the wrong country, a few who fit. Sorting takes ten seconds a name, which is fine for one post and tedious for a month of them. Tedious is where a habit dies.

There is no obvious next action. After you comment on someone’s post, the next step is clear: connect, then message. After someone likes your post, most people do nothing, because the first message is awkward to write. I will get to that.

The loop between the two halves

The reason to run both is that they feed each other, and this is the part the two-direction framing makes visible.

When you comment well on other people’s posts, some of them start engaging with yours. That moves them from the outbound queue, where you spend effort to be noticed, into the inbound list, where they are noticing you. When you message that list, some reply, connect, and react to your next post, which grows the next inbound list.

The outbound half seeds the loop. The inbound half harvests it. Run only outbound and you seed forever. Run only inbound and the list stops at whoever already follows you.

When I finally started working my own reactor lists, what surprised me was not that it produced calls. It was that most of the people who booked had never been in my outbound target list. I would not have found them by searching. They found me, and I had been ignoring the notification.

What to actually do with a reactor list

Sort first, write second. This is the step that makes the inbound half survivable, and it is the step most people skip. Every name gets one of three labels off the headline alone: drop, watch, or message this week. Drop is anyone who cannot be a buyer. Watch is a fit who has engaged once. Message is a fit who has engaged twice, or a fit who commented rather than reacted. The routing logic in convert LinkedIn engagement to leads is the long version.

Then the message. The mistake is opening with the engagement: “Thanks for liking my post!” That is a receipt, not a reason to talk. Open with the idea they engaged with, say one specific thing about it, then ask one question. The like earned you the right to be specific about that topic, not a paragraph about how you found them.

The other mistake is volume. A reactor list looks like a lead list, so people treat it like one and blast it. The people on it are warm because they were not treated like a list. Ten thoughtful messages a week off the inbound half will beat a hundred off a search filter, and it will keep your account out of trouble, since invitations are rationed and LinkedIn does not publish the cap. The rest of what gets an account restricted is in LinkedIn automation safe account rules.

Weighting the signals

Not every engagement is worth the same. A comment with an opinion in it beats a reaction, and the full ranking is in LinkedIn buying signals. A repost beats a comment. Two engagements in a month beat one. Someone who reacts and then views your profile the same day is the strongest signal you will get without them messaging you first.

This is where the outbound half helps again. If a fit reacted to your post and you have been commenting on theirs, you already have a thread. You are not a stranger reading a notification. You are a familiar name responding to a conversation both of you are already in. That is the state engagement-led prospecting is trying to produce, and it only appears when both halves run.

I kept a column in my spreadsheet for “have I commented on theirs?” next to “have they engaged with mine?” The rows with a yes in both columns closed at a rate the rest of the sheet never touched. I did not measure it precisely enough to quote a number, and I am not going to invent one. The pattern was obvious enough that I built a product around it.

A weekly routine

  • Monday, 20 minutes: pull the reactor and commenter lists off last week’s posts. Label every name drop, watch, or message.
  • Tuesday and Wednesday, 15 minutes each: send the message pile. One specific point about the idea they engaged with, one question.
  • Every day, 10 minutes: comment on posts from your target accounts. Real opinions, not “great post.”
  • Friday, 10 minutes: check the watch list. Anyone who engaged a second time moves to next Monday’s message pile.

That is under two hours a week, and it covers both halves. If your week only has time for one, run the inbound half. It is the one with a list already in it.

FAQ

How do I see who engaged with my LinkedIn posts?
Open the post and click the reaction count; LinkedIn lists the members who reacted, and the comments are already on the post. Post analytics gives you the counts per post, not the names, so the list comes from the post itself. Tools like LeadBase pull those lists across all your posts and score them so you skip the manual sort.

How long after someone engages should I message them?
Days, not weeks. A reaction is a moment, and referencing a three-week-old like reads as monitoring rather than context. My working rule is inside three days, and I stop mentioning the engagement after about ten.

Does engagement-led prospecting work if I have a small following?
The inbound half scales with your reach, so a small following means a short list. Start with the outbound half to seed the loop, and the inbound list grows as more people you have engaged with start engaging back.

What to do next

See how it works: LeadBase pulls the reactors and commenters off every post you publish into one sorted list, so the inbound half runs without the spreadsheet.

Go deeper: read LinkedIn engagement strategy for how to turn comments and reactions into warm leads, and LinkedIn comment strategy for the 20-minute outbound routine.

Ready to work your own list? Start a free trial and see who is already engaging with what you write.