# Checklist for analyzing competitor comments with AI
> Turn raw LinkedIn comments on competitor posts into specific buyer pain points, then reuse the exact phrases in your outbound messages and follow-ups.
- HTML: https://getkinlead.com/checklist-for-ai-competitor-comment-analysis
- Markdown: https://getkinlead.com/checklist-for-ai-competitor-comment-analysis.md

**Short answer:** To analyze competitor LinkedIn comments, start with posts where people describe a problem, not posts that get likes. Sort the comments into questions, complaints, comparisons and tags, then quote the exact phrase back in your first message. The wording is the asset; a paraphrase of it is not.

## Start with posts where people complain, not posts that get likes

A competitor's page is mostly announcements. Launch posts, hiring posts, a photo from a conference. Those collect likes and nothing else. The posts worth reading are the ones where a customer describes a problem in public, usually under a how-to post or a feature update.

You don't need a tool to start. Open the competitor's page, sort by recent, and read the last twenty posts. Two or three will have a comment thread where someone says the thing doesn't work the way they expected. That's your raw material.

Do this for two or three competitors at once. One page gives you anecdotes. Three pages give you a pattern you can build messaging around, and the pattern is what makes the work worth repeating next month.

1. **Rank posts by comments, not likes.** A post with 40 likes and 12 comments is worth more than one with 300 likes and 2 comments. Likes are cheap. A comment means someone typed a sentence about their own work.
2. **Read the how-to and release posts first.** Tutorials and release notes attract people who are mid-task and stuck. Comments like 'how do I do this for a client account' or 'this broke our sync' are the ones you want.
3. **Check the founder's profile too.** People are more direct on a person's post than on a company page. A founder asking what to build next gets replies that read like a list of complaints.
4. **Save the post URL before you do anything else.** You'll want to quote the post back later, and the comment will be hard to find again in three weeks. Paste the link into a sheet with the comment text next to it.

## Sort comments by what the person actually wants

Most comments are noise. 'Great post' and a fire emoji tells you nothing about the person's job. You're looking for four things: a question about whether the product does something, a complaint about how it does it, a comparison to a tool they chose instead, or a tag pulling a colleague in.

The sort decides who you message first. Someone describing the workaround they built is further along than someone asking a general question. Someone tagging a colleague usually has the problem but isn't always the person who signs.

Read the replies under a complaint too. If the competitor answers with 'please open a ticket', the person is still stuck and now slightly annoyed. That thread is a better opening than the original comment.

| | What they wrote | Example | What it tells you | What to do |
| --- | --- | --- | --- | --- |
| Praise | Love this update, keep them coming | Nothing about their work | Skip |
| Question | Does this work if two people edit at once? | A gap they just hit | Answer it in your first line |
| Complaint | We gave up on the export and do it in a spreadsheet now | They already built a workaround | Message today |
| Comparison | We looked at this and went with Northwind instead | They chose, and they remember why | Ask what tipped it |
| Tag | @sam this is the thing I mentioned | A team problem, not one person's | Message the person who tagged |

## Pull the exact phrase out of the comment

The point of reading comments is to reuse the words. If someone writes that the reporting screen takes forever to load, your message says takes forever to load. Rewrite that as performance concerns and you've thrown away the only part that proves a person read it.

Keep the quote short enough to sit inside a sentence. One clause is usually enough. You're not summarizing their comment, you're handing a piece of it back so they know the message wasn't assembled by a script.

Watch for the difference between a complaint and a preference. 'I wish it had dark mode' is a preference. 'We export to a spreadsheet every Friday because the report won't save' is a complaint with a cost attached. Only the second one is worth a message.

**Rewritten into marketing**

- Hi Sam, I saw you're interested in reporting efficiency. Our platform delivers faster dashboards for teams like yours.
- Noticed you had some challenges with your current vendor's export functionality. We can help with that.

**Quoted back**

- Sam, you wrote that the reporting screen takes forever to load. That's the exact thing we rebuilt, and it's why I'm messaging you.
- You mentioned doing the export in a spreadsheet because the tool couldn't handle it. We do that step in one click now.

## Write the first message from that phrase

The first message has three jobs: show you read the comment, say what you do about that specific problem, and ask something easy to answer. Everything else is filler.

One problem, one line about how you handle it, one question. If you can't fit it in four sentences, the problem isn't specific enough yet.

- **you:** Dana, you commented on Northwind's release post that the bulk import still drops rows when the file runs past a few thousand. Is that still biting you?
- **them:** Ha, yes. We import every Monday and check it by hand now.
- **you:** That manual check is what we removed for a 30-person ops team last month. Worth 15 minutes to see if it fits your setup?
- **them:** Sure, Thursday works.

> If they don't reply, send one follow-up with something new in it, like a detail from a second comment on the same post. Repeating the first message gets you ignored twice.

```
Hi {first name}, you wrote on {competitor}'s post that {exact phrase from their comment}. That's the part of {competitor} we hear about most. We handle it by {one line about what you do}. Is that still a problem for you this quarter?
```

## Keep a pain point map so the work compounds

One comment gives you one message. Twenty give you a picture of where the competitor keeps failing, and that picture is useful past outbound. It tells you what to put on the pricing page and what to build next.

Keep it in a sheet with one row per distinct complaint, not one row per comment. Merge duplicates. When the competitor ships a fix, mark the row dead and stop using it in messages.

The map also stops you from over-claiming. If the most common complaint is about a feature you don't have, you know not to write outreach around it, no matter how many people mention it.

1. **Use one row per distinct complaint.** Columns: competitor, the phrase they used, how many people said it, what you do about it, date last seen. If two people describe the same export problem in different words, that's one row.
2. **Group the rows into themes.** Pricing, speed, integrations, permissions, support. Two themes usually carry most of the complaints, and those are the ones worth writing outreach around.
3. **Recheck the map every few weeks.** Read the competitor's last ten posts and see whether the complaints you logged still show up. A complaint that stopped appearing was probably fixed.
4. **Feed the phrases into your playbook.** The exact wording goes into your sales playbook so every message written from it opens with the same problem instead of a generic line about efficiency.

## Know who to skip

Half the commenters aren't buyers. Someone praising the competitor is not a lead. Someone at a company that's clearly too small, or in an industry you don't serve, isn't either. Someone who commented six months ago and never came back is cold.

The ones worth your time have a title that matches the problem, work at a company the right size, and wrote the comment in the last few weeks. Apply those three filters in that order and most of the list disappears.

The people left over are worth a manual look. Open the profile, read the headline, check whether the company sells something your product touches. Thirty seconds per person, and it saves you from a message that reads well and lands nowhere.

> A comment is a signal, not a lead. Check the person's title and company before you write anything, or you'll send a great message to someone who can't buy.

## Doing this with Kinlead

Kinlead's [Steal Customers](/features/steal-customers) agent watches competitor company pages and any founder or employee profiles you add. It 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 the comment the person wrote, so the phrase you'd have copied into a sheet by hand is already attached. Leads go into a lead group, and any campaign can point at that group.

> Put the complaint wording into the campaign's sales playbook. Messages are written from the goal, tone and that playbook, so the comment detail ends up in the first line instead of a generic opener.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Find leads](https://getkinlead.com/tools/find-leads.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**How often should I analyze competitor comments?**

Do a deep pass once a month to update your positioning, but scan for new posts and complaints weekly so your outreach stays current.

**Should I reply to the comment on the competitor's post?**

No. Pitching in a competitor's comment section looks desperate and often gets you blocked. Move the conversation to a private message.

**What if the competitor replies to the complaint?**

Watch the exchange. If the competitor gives a vague answer or tells the user to open a ticket, that person is likely more frustrated and more open to your message.

**What if I can't find any complaints on their page?**

Check the founder's profile, the support account and any partner or integration pages. People complain where the person who can fix it is listening.

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