How to connect with people leaving competitor reviews

Find unhappy competitor customers on review sites and social posts, then turn the specific problem they named into a LinkedIn connection and a meeting.

Get started

Short answer

Find people who left public complaints on review sites or under a competitor's social posts, work out which of them can actually buy, locate their LinkedIn profile, and send a connection request that names the specific problem they described.

Where the complaints actually show up

Public complaints about software cluster in a few places, and each one gives you something different. Review sites give you detail and a date. Social posts give you a name and a face. Forums give you the version people write when support has stopped replying.

Start with review sites because the complaints there are structured. A three star G2 or Capterra review usually lists what works and what doesn't, which is the gap you're hunting. One star reviews are often about a billing error or a support ticket that went badly, and those people are angry at a process rather than a missing feature.

Then look at the competitor's own LinkedIn page. Comments under their product posts are the richest source, because people reply there when a feature they were promised still hasn't arrived. A comment asking whether something works with their current setup tells you the person is a real user, technical enough to evaluate tools, and stuck on something.

G2 and Capterra

Source
Three star reviews that name a missing feature or a slow support queue
What to look for
High

Competitor LinkedIn posts

Source
Comments asking about a workaround, an integration or a promised feature
What to look for
Very high

Reddit and industry forums

Source
Threads titled around alternatives to the competitor, or repeated crash reports
What to look for
Medium

Deciding which complaints are worth chasing

A complaint becomes a lead when three things line up: the person can influence a purchase, the problem is one you solve, and the complaint is recent. Check all three before you spend twenty minutes hunting for a profile.

  1. 1

    Check what the person actually does

    A VP of sales complaining about a CRM has budget and a reason to switch. An intern complaining about the same thing has neither. Read the job title on the review and confirm it against their LinkedIn headline before you go further.

  2. 2

    Match the complaint to something you have

    If they're angry about price and you cost more, skip them. If they're angry that the competitor charges extra for API access and you include it, that's a lead you can write to today.

  3. 3

    Check the date

    Anything older than about six months has usually been resolved, worked around, or the person has changed jobs. A review from two years ago is a history lesson, not a lead.

  4. 4

    Look for a switching signal

    Phrases like 'we're evaluating alternatives', 'looking for a replacement' or 'does anyone have a recommendation' are the strongest thing you'll find. Someone already looking needs far less convincing than someone who is merely annoyed.

Finding the person on LinkedIn

Review sites often show a first name, a job title and a company size. That's usually enough. LinkedIn search takes a first name, a company and a location and returns a short list you can work through in a couple of minutes.

Work from the most specific clue to the least. Company plus job title plus city narrows fast. If the reviewer wrote 'head of ops at a 200 person logistics firm in Leeds', you can find them without ever learning their surname.

  1. 1

    Search the reviewer's company first

    Type the company name into LinkedIn search and filter to People. Add the job title from the review. If the company is large, add the city.

  2. 2

    Try the exact phrase

    If the name is common, paste a distinctive sentence from the review into LinkedIn search. People often repost the same complaint on LinkedIn, on X or in a Slack community, and the phrase will surface the profile.

  3. 3

    Confirm before you write

    Read their recent activity. If their last three posts are about a completely different tool, they've moved on and the complaint is dead.

Writing the connection request

The note has one job: show the person you read their specific complaint. Anything else reads like a template with a name swapped in.

Name the problem in their words, say what you do about it in one clause, and ask a question they can answer in a single line. Keep the whole thing under 200 characters so it fits in a connection note without being cut.

Sounds like a script

  • I saw you didn't like Acme and my tool is way better. Want a demo?
  • Hi, I'm the founder of a company that helps with CRM problems. Let's connect.

Names the problem

  • Your note about Acme's reporting export taking four hours matched something we hear weekly. We rebuild that report in one click. Still a problem for you?
  • You asked on Acme's launch post whether the Salesforce sync was fixed. It wasn't, and that's the exact thing we built around. Worth a short chat?

Paste this job

Hi {first name}, your {site} note about {specific problem} is something we hear a lot. We handle it by {one clause about how}. Is that still costing you time?

What to say after they accept

Don't pitch on the acceptance message. The person just let a stranger into their network and is watching to see whether you're a salesperson or someone useful.

Ask a question about the problem instead. If they describe the workaround they built, that's your opening. Ask what the workaround costs them in hours, then offer a short screen share. Ten minutes is easier to agree to than a demo.

Example

  1. You

    Thanks for connecting. Was that reporting issue with Acme ever sorted, or are you still working around it?

  2. Prospect

    Still a nightmare. We export everything to Excel and rebuild it by hand every Monday.

  3. You

    That sounds like a rough start to the week. I can show you how we automate that exact report in about two clicks. Would ten minutes on a screen share be useful?

  4. Prospect

    Yeah, Thursday morning works. Send me a link.

Keeping the list from going stale

Complaints age quickly. Keep a simple record of every lead with the source URL, the date, the exact complaint and their profile link. When you review the list a month later, the date tells you what needs re-checking before you write.

  • Log the quote, not your summary of it. You'll want their exact words when you write the note.
  • Record where you found it. If the person asks how you came across them, you can answer plainly instead of dodging.
  • Remove anyone who replies that the problem is solved. A short clean list beats a long one you don't trust.

Never mention someone's complaint in a public comment or a post. Reference it only in a direct message, and only the part that's relevant to the problem you solve.

Doing this with Kinlead

Kinlead's Steal Customers agent watches competitor company pages and, optionally, founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads, keeping the post URL, what the post was about and what they commented.

Each lead is scored from 0 to 100 against the customer profile you describe, and leads below the fit line aren't kept. You can read how that works on the Steal Customers page.

Connection notes can be AI-written under 200 characters and open with the reason that person became a lead. Sends run from your own LinkedIn account at most one action every 5 minutes, inside the daily limits and send window you set.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to connect with people leaving competitor reviews.md