How to message prospects who share competitor content
Turn competitor engagement into leads by using specific comment hooks to start low-pressure conversations on LinkedIn without pitching too early.
Get startedShort answer
To message someone interacting with a competitor, use the specific point they made in their comment as a bridge to share a different perspective. Avoid attacking the competitor or pitching your product immediately. The goal is to move from a public comment to a private conversation by being helpful.
Identify the gap in the conversation
A common mistake is trying to prove your product is better than the one a prospect is praising. This creates friction because you're telling the prospect their interest is wrong. You don't want to start a feature war.
Look for the gap instead. Every piece of content has a blind spot. A competitor might talk about speed but ignore security, or talk about scale but ignore onboarding. Find the one thing the post didn't mention that actually matters to the person commenting.
The gap is not always a missing feature. It can be a missing step in the process. A post about a new dashboard might skip how teams clean the data before it loads. A post about automation might skip who reviews the output. Those process gaps are easier to discuss in a private message because they are specific and practical.
Offering a new angle on a problem keeps the exchange professional and gives the prospect something useful to consider. You are adding to the conversation, not correcting the person who wrote the post.
The pitch approach
- I saw you liked Acme's post. Our tool is actually much faster than theirs.
- Thanks for commenting on that post. You should check out our platform because we have a better UI.
- I noticed you're interested in Northwind. We do everything they do but for a lower price.
The gap approach
- I saw your comment about Acme's speed. Most people find that speed is great until they hit the reporting phase, where things slow down. Have you run into that?
- Your point about Northwind's automation is spot on. I've found that adding a manual review step at the end of that process prevents a lot of errors. Do you do that?
- I noticed you're looking into how X handles Y. I've seen a few teams struggle with the API side of that specific setup. Happy to share how we handled it.
Decide if the comment is worth a message
Every comment is a data point, even when it is not an invitation to sell. Before you write, check whether the comment gives you something concrete to respond to. A one-word comment like 'Great post' tells you almost nothing. A comment that names a process, a tool, a team size or a delay gives you a way in.
Read the person's headline too. If they work in the function that owns the problem, the comment is a stronger signal. If they are a student or a vendor, skip them. You want people who can describe the problem from the inside.
Look for comments that ask a question, describe a workaround or push back on the post. Those are the ones where a private message can add something the public thread cannot. If the comment is just praise, you can reply publicly and wait. Sending a DM to every 'nice post' turns into spam.
- The comment names a specific step, handoff or tool.
- The comment includes a question about how something works.
- The comment describes a delay, error or manual workaround.
- The person's role matches the part of the business the post is about.
Analyze the comment for a hook
Categorize the comment to determine your angle. If you send the same generic message to everyone, you'll be ignored.
The hook is the bridge between their public statement and your private message. If they've admitted a struggle, your hook is the solution. If they've praised a feature, your hook is the 'yes, and' that expands their thinking.
Write down the exact phrase they used. That phrase goes into your first line. It proves you read the comment and gives the person a reason to keep reading.
The struggle
- Comment type
- They are experiencing a specific pain point.
- What it tells you
- Focus on a fix for that pain that the competitor doesn't prioritize.
The praise
- Comment type
- They value a specific outcome or feature.
- What it tells you
- Agree with the value, then introduce a nuance they might have missed.
The question
- Comment type
- They have a technical or process gap in their knowledge.
- What it tells you
- Answer the question directly in the DM and ask how they currently handle it.
The comparison
- Comment type
- They are weighing two tools or approaches.
- What it tells you
- Ask what they need to see to make a decision, then share a practical test.
Write the first message
The first message must prove you are a human who read their words. Avoid templates that feel like templates. Mention the specific post and the specific words they used.
Keep the request small. Don't ask for a 30 minute demo in the first message. Your only goal in the first DM is to get a response. Offer a quick tip, a checklist, or a different perspective that provides value without requiring a commitment.
End with a low-pressure question. Instead of asking for a meeting, ask about their current process or if they've encountered a specific problem. This makes it easy for them to say yes or explain their situation.
If they don't reply, leave it. A follow-up later can reference the same post without repeating the ask. One unanswered message is not a reason to send three more.
Example
- You
Hi Sarah, saw your comment on the Northwind post about their new automation flow. Your point about the setup time being a hurdle is something I've seen with a few other agencies lately.
- You
I actually put together a short checklist on how to prep the data differently to avoid that setup delay. Would you like me to send it over?
- Prospect
That would actually be really helpful, we're struggling with that right now.
Never tell a prospect they are wrong about a competitor. Agree with their observation first, then introduce the gap.
Paste this job
Hi [first name], I saw your comment on [company]'s post about [topic]. You mentioned [specific point]. I work with [type of team] on [related problem], and I've seen [short observation]. Would it help if I sent over [specific resource]?
Handle the response
Once they reply, the temptation is to pivot immediately to your product. This is where the conversation can stall. If you jump to the pitch too fast, you prove that the value you offered was just a bait and switch.
Stay in the problem space. Acknowledge their answer and ask one more clarifying question. This helps you pinpoint exactly where the competitor is failing them, which tells you whether a call is worth suggesting.
If they describe a real cost, name it back to them. 'So the delay shows up in client onboarding, not just internal reporting.' That shows you listened and gives them a chance to correct you. When they confirm the cost, you have a reason to offer a short call.
If they say the problem is solved, ask what solved it. That answer tells you whether the competitor is safe or the workaround is fragile. Both answers are useful.
- 1
Acknowledge and validate
Thank them for the reply and validate the specific struggle they mentioned. Don't mention your product yet.
- 2
Dig deeper
Ask a question that reveals the cost of the problem. For example, 'Does that setup delay affect your client onboarding time or just your internal team?'
- 3
Share a peer example
Briefly describe how another company solved that specific issue. 'I worked with a 40-person agency that had the same issue; they changed their validation step and got past that delay.'
- 4
The low-friction ask
Suggest a brief call only after they agree that the gap is a real problem. 'Since you're dealing with this, it might be worth a 10 minute chat to show you how that other team structured it.'
Doing this with Kinlead
Kinlead finds people who comment on competitor posts through the Steal Customers agent. It watches competitor company pages and optional founder or employee profiles, reads the comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented.
That gives you the detail to open a message with why the person became a lead. Connection requests can carry an AI-written note under 200 characters that uses that reason. Leads are kept in lead groups, and any campaign can point at any group.
Replies from every campaign land in one inbox, classified by intent, with interested replies first. You can choose hand-off at the first reply, or let the AI reply until there is real interest. You get an email when someone replies.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to message prospects who share competitor content.md