Connecting with leads unhappy with a competitor

Find and message LinkedIn users who complain about competitor software. Use their specific pain points to raise connection rates and book demos.

Get started

Short answer

Find recent posts from the competitor where customers complain about a specific problem, then send a connection note that quotes that complaint and names the outcome you'd fix. Keep the note under 200 characters and save the pitch for after they accept.

Where unhappy competitor customers actually post

People don't post that they're switching software. They leave a comment under a vendor's announcement, or they answer someone else's question in a group. That comment is the signal, and it's usually more honest than anything they'd put on their own profile.

Start with the competitor's company page. Open the Posts tab and read the comments on anything about pricing, a deprecation, an outage or a roadmap change. Those four topics produce the most public frustration because they land on work people are already doing.

Then widen out. Search LinkedIn for the competitor's name, filter to Posts, and sort by latest. You'll find customers complaining on their own posts and threads where someone asked for recommendations. Category groups work too, though a comment there is harder to tie back to a company.

  1. 1

    Open the competitor's page and go to posts

    Read the last 30 days, not the pinned marketing posts. Pricing changes, deprecations, outages and roadmap posts are where complaints collect.

  2. 2

    Search the competitor name, filtered to posts

    Sort by latest. Customers often complain on their own profile and tag the vendor, which is easier to reference than a comment buried in a thread.

  3. 3

    Copy the post URL and the exact comment

    You need both. The URL is where you found them, and the comment text is what you quote back in the note.

  4. 4

    Write down the date

    A complaint from four months ago has usually been resolved or the person has already moved. Anything older than a few weeks is a weaker reason to reach out.

A comment tells you where to start. It doesn't tell you whether they have budget, authority or a live project.

Qualify the commenter before you spend an invite

Not everyone in a comment thread can buy. A support engineer venting about an API limit may love your product and still have no say in the purchase. Read the profile before you write anything.

Two things matter more than seniority. Does the complaint describe something you actually fix, and is the person still in it? Reporting lag against a reporting tool is a match. A complaint about a color scheme against an API is not, and no amount of clever wording will make it one.

Company size matters less than you'd expect. A five person team that just hit the exact limit you remove will move faster than a large account with a procurement process, and they'll answer the message.

Role

Check
Owns the tool or leads the team that uses it
Worth an invite
Junior, or in a role that never touches it

The complaint

Check
A limit, gap or cost you remove
Worth an invite
A bug you also have, or a preference you can't change

Timing

Check
Posted in the last two or three weeks
Worth an invite
Posted months ago, likely resolved

Wording

Check
Asked for alternatives or asked how others handle it
Worth an invite
Venting with no question and no follow-up from them

Write a connection note that proves you read the comment

The note has one job: show the person you read what they wrote. A pitch in the connection request reads like a scrape, and anyone who works in software recognizes a scrape.

Keep it under 200 characters. Quote one detail from their comment, name the outcome you'd help with, and stop. Ask for the connection, not the meeting.

Skip the word alternative. It's the most common word in these notes and it signals a template. Say what you do instead.

Generic pitch

  • I saw you're unhappy with Acme. We're a better tool with more features and lower pricing. Want a demo?
  • Hi, I noticed you commented on Acme's post. We're the leading alternative to them. Let's connect.

Quotes the comment

  • Saw your comment on Acme's post about export timeouts. We batch exports differently and it stopped the timeouts for us. Open to connecting?
  • You asked on Acme's post whether anyone handles SSO on the lower tier. We do. Happy to show you the setup if it's still open.

Paste this job

Hi {first name}, you commented on {competitor}'s post about {specific problem}. We handle that case differently in {your product}. Open to connecting?

What to send after they accept

An accepted invite gives you permission to say one more thing. It doesn't make them a warm lead. Most people accept without reading the note closely, so repeat the context in the first message.

Lead with the problem they raised and offer something concrete: a workflow, a one page write-up, a screenshot of how you handle that case. Send the calendar link only after they've said the thing is useful.

Send it the same day they accept if you can. The comment is still fresh in their head, and a message that arrives a week later reads like a sequence.

Example

  1. You

    Thanks for connecting. You mentioned on Acme's post that exports time out past about 50k rows. We hit the same wall and ended up batching the job differently. Want the one page write-up of how that works?

  2. Prospect

    Sure. We're not switching this quarter though, just so you know.

  3. You

    That's fine, the write-up is useful either way. If it holds up, the next step is 15 minutes where I show it on your data. If it doesn't, you'll at least know what to push Acme on.

  4. Prospect

    Send it over.

Handle the three replies you'll get most

Most replies fall into a few shapes. None of them are rejections of you personally, and each one has a next step that isn't pushing harder.

  • We're under contract until March. Ask what happens at renewal and whether there's a pilot budget before then. Then set a reminder for eight weeks before the renewal date and stop messaging until it comes up.
  • We're already looking at three other tools. Ask what the shortlist is being judged on. If the criteria match your strength, ask to be added. If they don't, say so and leave it.
  • I don't own this decision. Ask who does and whether an intro is comfortable. Don't ask them to forward a deck for you.
  • Send me some information. Ask which question they'd want answered first, then send one page on that. A full deck goes unread.

A no this quarter is a maybe at renewal. Deleting the lead and losing the date is the expensive part.

Run one competitor before you add a second

Pick the competitor you lose deals to most often. The biggest name in the category is usually the wrong first pick, because their customers are the least likely to be looking.

Give the test three weeks. Count how many notes went out, how many were accepted, and how many replies named the problem you opened with. That last number tells you whether the hook is right. Acceptance only tells you the note was readable.

Add a second competitor when the first is producing conversations. Five pages at once gives you a queue you can't answer, and an unanswered reply costs more than a message you never sent.

Notes sent

What to count
Whether you're running the test or just reading competitor pages

Accepted invites

What to count
Whether the first line earned a look

Replies that name the pain

What to count
Whether the hook matched the problem

Calls booked

What to count
Whether the problem is worth paying to fix

Doing this with Kinlead

Reading competitor pages by hand works for about ten leads a week before it eats the time you'd spend on replies. The Steal Customers agent watches the competitor pages and founder or employee profiles you list, reads 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, so the detail you need for the note is already in front of you.

Leads land in a lead group, and any campaign can point at that group. The AI-written note opens with why that person became a lead. You can read and edit queued notes on the Actions page before they send, and pause the campaign at any point.

  1. 1

    Add the pages you want watched

    Company pages first, then any founder or employee profiles that post product news. Those posts tend to draw the most specific complaints.

  2. 2

    Point a campaign at the lead group

    The connection note stays under 200 characters and opens with the reason that person became a lead.

  3. 3

    Set replies to hand off at the first reply

    You get the conversation while the context is fresh. Replies from every campaign land in one [unified inbox](/features/unified-inbox) classified by intent, with interested ones first, and you get an email when someone replies.

  4. 4

    Set the send window and limits

    Each LinkedIn account sends at most one action every five minutes inside the invite and message limits you set, so a batch of competitor leads doesn't go out in one burst.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? Connecting with leads unhappy with a competitor.md