# Targeting former customers of your competitors on LinkedIn
> Find and attract users unhappy with your competitors by monitoring LinkedIn comments and signals for active buyers ready to switch providers.
- HTML: https://getkinlead.com/how-to-target-former-customers-of-competitors
- Markdown: https://getkinlead.com/how-to-target-former-customers-of-competitors.md

**Short answer:** Monitor comments on competitor company pages and executive posts for people complaining about pricing, support or a missing feature. Those comments are public signals that someone is unhappy, and unhappy users are the ones most likely to look at a different provider.

## Identify the right competitor targets

Don't watch every competitor page. Pick three to six where friction is visible: a company that changed its pricing last year, one that bought a smaller product and folded it into its own, one still running an interface nobody has rebuilt. If a page is full of praise, you'll spend your mornings reading testimonials.

Start with the competitors you already lose deals to, then add the legacy tool that appears in every job posting for your buyer's role. Those are the two places where a public complaint is likely to mean something.

Check that their customers talk on LinkedIn at all. Tools bought by agencies and marketing teams get discussed in comments. Tools bought by IT departments often don't, and you'll find one comment a month.

Find the posts that get comments. Follow the company page, then follow the founder and any product lead who posts. Turn on notifications for the founder's posts, not the company's, because people complain where a person might answer.

| | Competitor type | Why they're a target | What to look for |
| --- | --- | --- | --- |
| Direct competitors | Solve the same problem for the same audience | Feature gaps or pricing complaints |
| Legacy players | Older software with an interface nobody has rebuilt | Complaints about speed or missing basics |
| High-churn services | Known for slow support or regular price rises | Frustration with account managers |
| Niche alternatives | Small tools that users have outgrown | Requests for features you already have |

## Spot the switch signals in comments

Most comments are noise. People tag a colleague, thank the author, or repeat the post's point back at them. The comment you want describes a gap between what the person needs and what the tool does.

Two types matter more than the rest. One is the person asking whether anyone found a workaround. The other names a specific limit: seats, API calls, exports, storage, a report that takes an hour to run. 'Great tool' tells you nothing. 'We've been waiting on this for a year' tells you where they're stuck.

Time matters. A complaint from eight months ago has been solved, accepted, or forgotten. Work on comments from the last two to four weeks, before the person signs a renewal and stops caring.

Write down the exact phrase they used, not your summary of it. You'll quote it back when you open the conversation, and it stops you inventing a pain they don't have.

**Ignore these**

- Great post, thanks for sharing!
- Interesting take on the market.
- We use this every day and love it.

**Act on these**

- Anyone found a workaround for the export limit? We hit it every week.
- Is there a better way to do this? Our current process takes two days.
- Third outage this month. Support keeps closing the ticket.
- Looking for an alternative that doesn't need a six-month implementation.

```
Sort these LinkedIn comments for a B2B seller.

Buyer signals: names a limit, asks for an alternative, says they are waiting on a fix, mentions cost pressure, asks for a workaround.
Not signals: praise, tagging a colleague, questions about how a feature works, job posts.

For each comment return: name, company, the exact phrase, signal type, and one line on why it counts. Skip anything you are unsure about.
```

## Check that the commenter can actually buy

A complaint is not a lead. The person might be a junior analyst with no budget, a contractor passing through, or someone at a company ten times your size that your pricing doesn't fit.

Read three things on the profile: the title, the company size, and how long they've been in the role. Someone new to a Head of Ops seat is often reviewing tooling. Someone six years in the same seat is usually defending the stack they built.

Check your own side too. Mutual connections, past conversations with that company, an old colleague who works there. A warm path decides whether you send a connection request or ask for an introduction.

1. **Audit the profile.** Open the commenter's profile and check their current role and seniority.
2. **Check the company fit.** Look at the company page for industry and headcount. If they're far outside your market, skip them however unhappy they sound.
3. **Look for repetition.** Scan their recent activity for the same complaint on other posts. Two mentions in a month means the problem is still live.
4. **Find a warm path.** Check mutual connections before you send anything. One shared contact changes your opening line.

## Open with their words, not your pitch

The first message has one job: get them to describe the problem. Lead with your product and you sound like every other seller who read the same comment.

Mention the specific thing they said. Not the competitor's name, not a comparison, just the limitation. Then ask something they can answer in one line.

Send it a day or two after the comment, not the same hour. Same-hour messages read as monitoring.

- **you:** Hi Sarah, I saw your comment on their post about API limits. That ceiling catches most teams around the same point.
- **them:** It's a nightmare. We hit it every day and support just tells us to move to enterprise, which is five times the price.
- **you:** That's a steep jump for the same product. Are you running scripts to work around it now, or just living with it?
- **them:** Manual scripts, and they break. Do you know anything that handles this without the enterprise tier?

> Never name the competitor in the first message. Describe the limitation they mentioned and let them bring up the comparison.

## Read the reply before you send a calendar link

Replies come in a few shapes, and each needs a different answer. Send a booking link to someone who just asked what you do and you'll get silence.

Answer the question they asked first. Then offer a next step that costs them little: a two-line comparison, a screenshot of the setup, a short call.

| | What they sent | What it usually means | What to send back |
| --- | --- | --- | --- |
| A detailed description of the problem | Evaluating, not buying yet | One follow-up question, then an example of how you solved it for a similar team |
| What do you do exactly? | They want the pitch, kept short | Two sentences on what you do and who it's for, plus a question about whether the problem is still live |
| Nothing for a week | Timing or priority moved | One nudge with something useful, then leave it |
| We just renewed | Out for now | Ask when the renewal comes up, note it, move on |

> Write down every conversation with the date and the phrase they used. When the renewal comes around, the second message writes itself.

## Doing this with Kinlead

Reading comments by hand across a few competitor pages is a daily chore. The [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 the person commented.

Leads sit in lead groups, and any campaign can point at any group. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Outreach runs from your own LinkedIn account at a human pace, one action every 5 minutes at most, inside the daily limits and send window you set.

Replies from every campaign land in one [inbox](/features/unified-inbox), classified by intent, with interested replies first. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.

1. **Point the agent at your competitors.** Choose the company pages to watch, plus a founder or employee profile where complaints tend to appear.
2. **Check the leads.** Open the lead group and read the stored comment before you build a message around it.
3. **Build one campaign.** Aim the campaign at that lead group and let the connection note open with the reason they became a lead.
4. **Work the inbox.** Answer interested replies first and move the conversation to your scheduling link.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Can I message someone right after they comment?**

Wait a day. Same-hour messages feel like you were watching, and the person is still in the middle of the thread.

**Should I reply to the comment publicly first?**

No. Pitching in a competitor's comments reads as spam and gives them a reason to block you. Keep it in direct messages.

**What if the competitor answers the complaint well?**

Then you've lost this one. Note the account and check back when the next complaint appears. A good public response often buys the competitor another year.

**What if I find no complaints at all?**

Their customers probably don't discuss the tool in public. Watch the founder's posts instead of the company page, or pick a different competitor.

**How many competitors should I follow?**

Three is enough to start. More than that and you'll skim, and skimming is how you miss the comment that names a real limit.

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