# How to message prospects who comment on competitor posts
> Turn a prospect's public comment on a competitor's post into a useful sales conversation by naming the post, the specific gap and a clear next step.
- HTML: https://getkinlead.com/message-prospects-who-share-competitor-content
- Markdown: https://getkinlead.com/message-prospects-who-share-competitor-content.md

**Short answer:** When a prospect comments on a competitor's post, treat the comment as a signal about what they care about. Mention the post and the specific point they made, then ask whether that gap shows up in their work. Keep the first message focused on confirming the problem and save the meeting ask for after they reply.

## Read the comment before the logo

Some comments are polite noise. Others point to a live problem. Your job is to sort the comment before you write a message, because the same post can attract a fan, a buyer and someone who wants the post to get more reach.

Look at what the person asked or complained about. A question about a specific feature is a stronger signal than a short compliment. A complaint about setup time, reporting, permissions or cost is stronger still, because it names a friction point you can ask about.

Use the comment as the reason for the message. The competitor's logo is context. The person's words are the opening. If you cannot quote the comment in your first sentence, you probably do not have a reason to write.

| | Comment type | What it sounds like | What it tells you | What to do |
| --- | --- | --- | --- | --- |
| The supporter | Great post! | They like the person or the brand | Skip unless their profile matches your buyer |
| The questioner | Does this work for multi-currency? | They have a live use case in mind | Ask how they handle that today |
| The complainer | Setup took us three days | They hit a real friction point | Ask if that friction is still there |
| The comparison shopper | We use Northwind for this today | They are already comparing tools | Ask what they wish Northwind did better |

## Read the post before you read the comment

The comment only makes sense with the post. Open the post, read the first few lines and note the promise the competitor is making. Then read the comment again. You want to see whether the person is responding to the promise, the demo, the pricing or a detail in the comments.

Check the person's profile before you write. You need to know their role and company so the message sounds like it belongs in their day. A comment from a finance lead on a reporting post reads differently from a comment by a founder on a growth post. If the role has nothing to do with the comment, skip the message.

Write down the exact words you will use. Paraphrasing too much makes the message feel generic. A short quote from the comment is enough to show you read it.

1. **Open the post and note the claim.** Write down the one thing the post says the product will do. Keep it short enough to quote in a message.
2. **Copy the exact comment.** Use the person's words. 'The filter setup takes too long' is better than 'you had concerns about setup.'
3. **Check role and company.** Look at the headline and current company. If the role has nothing to do with the comment, stop.
4. **Decide the question you will ask.** Pick one question that confirms the gap. 'Is that still a problem?' works when the comment is recent.

## Write a first line that proves you read it

The first line has one job: show the person that you are responding to their comment. Generic praise or a product claim makes you look like every other sender. A specific detail from the post or comment gives them a reason to keep reading.

Praise the competitor's point if you mean it. Attacking a tool the prospect uses makes them defend it. Keep the focus on the topic they raised and the gap between the promise and their experience. If the comment is old, say when you saw it or ask whether the problem is still current.

**Weak first lines**

- I saw you like Acme and we are better.
- Stop using Acme, our tool is faster.
- I noticed you are active in the reporting space.

**Strong first lines**

- I saw your comment on Acme's post about automated reporting. You mentioned the filter setup takes too long.
- Your question about multi-currency on Northwind's post is the same one finance teams ask us.
- You wrote that permissions in Acme take a week to change. Is that still true for your team?

## Bridge from their comment to your product

The bridge is the gap between what the competitor promises and what the person experiences. Your goal is to show you understand the specific friction and have a different way to handle it. Proving the competitor is bad wastes the message and makes the prospect defensive.

Keep the bridge short. One sentence about the gap, one sentence about how your product handles it, then a question. If you write three sentences about your product, the message turns into a pitch. The prospect should feel like they are comparing notes with a peer.

1. **Acknowledge their point.** Start with the comment or the post. 'You mentioned the filter setup takes too long' is enough.
2. **Name the gap.** Say what the competitor's approach asks the user to do. 'Most tools in that category make you build filters before you see a report.'
3. **Offer one difference.** Pick one feature or workflow that changes the experience. A list of features dilutes the point.
4. **Ask about their current process.** End with a question that confirms the problem. 'Is that still a bottleneck for your team?'

> Ask about the gap before you describe your product. A confirmed problem is worth more than a polished pitch.

## Put the message together

Use a short message. The person is on LinkedIn and is probably reading on a phone. Open with the comment, add the bridge and finish with one question. If you are sending a connection request, keep the note under 200 characters and make the comment the first thing they see.

If you are already connected, you can add one line of context about your product. Keep the same order: their comment, the gap, your difference, the question. The order matters because it keeps the message about them for the first two sentences.

- **you:** Hi Sarah, I saw your comment on Northwind's post about automated reporting. You mentioned that setting up filters takes too long. Most tools in that category make you build filters before you see a report.
- **them:** Exactly. It took me three days to get the dashboard right.
- **you:** We built our reporting to skip the manual filter step. Is that still a bottleneck for your team, or did you find a workaround?

```
Hi {{first_name}}, I saw your comment on {{competitor}}'s post about {{topic}}. You mentioned {{specific pain}}. We handle that by {{one difference}}. Is {{specific pain}} still a problem for your team?

Connection note version:
Hi {{first_name}}, your comment on {{competitor}}'s {{topic}} post stood out. You mentioned {{pain}}. We help teams with {{one difference}}. Open to comparing notes?
```

## Handle the reply without rushing to a demo

When someone replies, your next message should confirm the problem or learn how they solve it today. A demo ask too early makes the conversation about your calendar. A useful question keeps it about their work.

If they confirm the pain, ask how they handle it now and who else is involved. If they defend the competitor, drop the comparison and ask what they wish the tool did better. If they ask what you do, answer in one sentence and return to their process.

Keep the thread short. Two or three exchanges are enough to know whether this is a real conversation. If they go quiet, leave it. You can follow up later with a relevant post or a specific question.

Track which comments led to replies. Over time you will see which competitor posts attract your buyers and which comments are noise. That tells you where to spend your scrolling time next week.

## Doing this with Kinlead

Kinlead's [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads the comments on their 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.

You can put those leads in a lead group, point a campaign at the group and let AI write a connection note under 200 characters that opens with why that person became a lead. Outreach runs from your own LinkedIn account through Unipile at a human pace, with one action every 5 minutes inside the daily limits and send window you set. Queued messages can be read and edited on the Actions page before they send, and replies land in one inbox classified by intent.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Lead scoring validation](https://getkinlead.com/checklist-for-ai-lead-scoring-validation.md)
- [Founder outbound guide](https://getkinlead.com/use-cases/outbound-for-founders.md)

## Common questions

**Should I mention the competitor by name?**

Yes, if the comment is public and the post is recent. Name the post or the topic so the person knows why you are writing. Keep the tone neutral.

**What if the prospect is a fan of the competitor?**

Focus on the specific use case. Fans of a tool still have gaps in their workflow. Ask if there is one thing they wish the tool did better.

**How many of these people should I message per day?**

LinkedIn does not publish exact limits. Work within the limits your account has, watch pending invitations and keep each message tied to a real comment.

**What if they reply with a complaint about the competitor?**

Ask how long it has been a problem and what they do to work around it. Stay calm. A calm question gives you more information than agreement.

**Can I use this for a connection request?**

Yes. Keep the note under 200 characters and put the comment in the first sentence. Save the product detail for after they accept.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
