# How to find leads from competitor reviews on LinkedIn
> How to watch competitor posts on LinkedIn, spot commenters with a real problem, qualify them fast and write a first message that gets a reply.
- HTML: https://getkinlead.com/find-leads-from-competitor-reviews
- Markdown: https://getkinlead.com/find-leads-from-competitor-reviews.md

**Short answer:** Watch the company pages and founder or product profiles of three to five direct competitors, then read the comments on their recent posts. The people who describe a specific problem with the product are your leads. Qualify them by title and company size, then open with the problem they named rather than a pitch.

## What counts as a buying signal in a competitor's comments

Most comments under a competitor's post are noise. 'Great launch' and 'Congrats to the team' tell you nothing about whether that person has a problem you can fix. Skip them.

The comments worth reading describe the product failing at a specific job. Someone asking why the export times out, or whether anyone has found a workaround for multi-currency invoices, has already done the hard part for you: they named the problem in public.

The person behind that comment is usually one of two things. Either they pay the competitor now and keep hitting a wall, or they've outgrown the tool and are quietly shopping. The first needs a fix. The second needs a comparison.

The posts that produce the best comments are the boring ones. A changelog entry, a pricing update, a 'we're retiring this feature' note. Launch posts attract applause. Change posts attract the people whose workflow just broke.

**Comments to skip**

- Congrats on the funding, well deserved.
- Great post, thanks for sharing.
- Love this team.

**Comments worth a closer look**

- We've opened three tickets about the sync delay and it's still not fixed.
- Does this handle multi-currency invoices without a workaround?
- We're outgrowing this. What are people moving to for a 40-person sales team?

## Build a competitor watch list you can keep up with

Pick three to five competitors. More than that and you'll check none of them properly. Choose the ones whose customers look like the customers you already close, not the biggest names in the category. A 200-person competitor with your buyer is more useful than an enterprise vendor whose commenters all work somewhere that will never sign.

Skip the category leader unless you sell to the same buyer. Their comment sections fill up with people who want to be seen agreeing with a big brand, and you'll spend your 15 minutes reading applause.

Company pages alone aren't enough. Marketing teams moderate those and the sharp comments get answered fast or hidden. The unfiltered conversation usually sits under posts from the founder, the head of product, or a loud account executive.

1. **List the pages and the people.** For each competitor, note the company page plus two or three personal profiles: founder, CEO, head of product, and anyone on the product team who posts often.
2. **Follow and turn on notifications.** Follow the company page and click the bell on the personal profiles. You want their posts in your feed the day they go up, while the comments are still fresh.
3. **Keep a running list of post URLs.** A plain document with a link to each post you're watching and the date you found it. It takes seconds and stops you rereading the same thread.
4. **Block 15 minutes a day.** Open the document, read comments on anything posted in the last two days, and write down the names worth a closer look. That's the whole routine.

## Qualify the commenter before you write anything

A complaint is not a lead. A junior analyst venting about a UI bug has no budget and no say in which tools the company buys. Messaging them spends a slot you could put in front of someone who can sign.

Open the profile and answer four questions. If two of them fail, move on. Being strict here keeps your acceptance rate healthy and your account out of trouble.

One more check before you write: search your own inbox or CRM for the company name. If they're already a customer or in an open deal, this isn't a lead, it's a reason to call your existing contact.

| | What to check | What you're looking for | When to move on |
| --- | --- | --- | --- |
| Job title | They own the workflow that broke, or manage the people who do | An individual contributor with no say in tooling |
| Company size | Fits the range you already sell into | Far outside anything you've closed before |
| How specific the complaint is | Names a task, a step or a missing integration | General grumbling that the product feels slow |
| Recent activity | Complained about the same thing twice, or posted about evaluating tools | One comment months ago and nothing since |

## Write a first message that doesn't sound like eavesdropping

The instinct is to open with the competitor's name and a pitch. That reads as surveillance. They didn't post for you, and they can tell when a stranger has been reading their comments.

Lead with the problem in their words. Say what you do about it in one sentence. Ask whether it's still an issue. No calendar link, no feature list.

If you're sending a connection request rather than a message, the note is short, so cut it to the problem and one line about what you do. The exchange below works as a message once they've accepted.

- **you:** Hi Sarah, you mentioned on Northwind's post last week that the API sync stalls during month-end reporting. Is that still happening, or did they ship a fix?
- **them:** Still happening. We've raised it twice and got told it's on the roadmap.
- **you:** That's the reason two teams I work with moved off it. We pull the data on a different schedule so month-end doesn't queue behind everything else. Want me to send over how that works?
- **them:** Yeah, send it.

> Ask whether the problem is still there before you offer anything. Sometimes they've solved it and you've saved yourself a message.

## What to do when they reply

Replies from this kind of outreach are warmer than cold ones because the problem is already named. Don't waste that by switching into a generic pitch. Keep referring to the thing they complained about.

If they want to talk, book the call and put their original complaint in the invite. It gives the meeting a subject and shows you were listening.

If the conversation gets technical, bring in whoever can actually answer. Forwarding a question to a colleague and coming back with a real answer beats improvising.

**Follow-up that gets ignored**

- Just bumping this to the top of your inbox.
- Wanted to check in and see if you had a chance to read my last message.

**Follow-up that gets an answer**

- Sarah, did Northwind end up fixing the sync issue? The doc I mentioned is here whenever you want it.
- Closing the loop on this. If the reporting problem comes back at quarter end, you know where I am.

## Keep a log so the work compounds

After a few weeks you'll have names, complaints and outcomes. That log is worth more than the leads, because it tells you which competitors bleed customers and which complaints keep coming up.

One row per person, five or six columns. Nothing fancy.

Do this on the first of the month rather than weekly. Patterns need a few weeks to show up, and rereading the same rows every seven days turns into busywork.

Read the complaint column once a month. If the same issue shows up from five different companies, that's your next piece of positioning, and a good post to write.

```
name,profile_url,competitor,post_url,complaint,date_seen,status
Sarah Kaur,linkedin.com/in/sarahkaur,Northwind,<post url>,API sync stalls at month end,2025-03-14,replied
Tom Iversen,linkedin.com/in/tomiversen,Acme,<post url>,No multi-currency invoices without a workaround,2025-03-15,no reply
```

## Doing this with Kinlead

Kinlead's Steal Customers agent does the watching. You add competitor company pages and, if you want, founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like your buyers into leads. Each lead keeps the post URL, what the post was about and what they commented.

Leads are scored 0 to 100 against the customer you describe, and anything below the fit line isn't kept. You can point a campaign at the group and have connection notes open with why that person became a lead. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused. Pro is $49 a month after a 7-day free trial.

Lead search runs on LinkedIn's standard search, so a Sales Navigator seat isn't needed. The [Steal Customers](/features/steal-customers) page covers the setup.

## Related

- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Is it against LinkedIn's terms to message people who commented on a competitor's post?**

Reading public comments and sending connection requests is normal use. What causes trouble is volume and repetition, so keep your pace human and write each note for the person receiving it.

**Should I name the competitor in my message?**

Only as context. Referring to the post they commented on shows you read it. Trash-talking the competitor usually backfires, because they picked it for a reason.

**How often should I check for new comments?**

Daily, or at least every other day. People with a live problem tend to act on it within a week or two, and the first useful reply usually wins.

**What if they never reply?**

Move on and keep the row in your log. Some people switch six months later and come back to the message that made sense at the time.

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