# LinkedIn connection notes for people stuck with a competitor
> How to find LinkedIn users who are unhappy with a competitor's tool, check they can actually switch, and write a connection note that gets accepted.
- HTML: https://getkinlead.com/connection-request-checklist-for-new-vendors
- Markdown: https://getkinlead.com/connection-request-checklist-for-new-vendors.md

**Short answer:** Find people who are already saying something specific about the competitor in public, in their own words, and reach out within days of that moment. The note names what they said and asks to connect. The switch conversation happens after they accept.

## Find the people your competitor is already failing

Displacement outreach usually opens with your product, which is why it gets ignored. Start with a moment instead: someone complained in public, asked a question the vendor skipped, or described a workaround they built themselves. That moment is the reason to reach out this week rather than in six months.

The signal does not have to be dramatic. A comment asking how to export data before a renewal, a thread about a migration that broke reporting, a review titled 'used to be fine' all work. You are looking for effort, meaning people doing extra work because the tool will not do it for them.

| | Where to look | What counts as a signal | What to save |
| --- | --- | --- | --- |
| The vendor's own LinkedIn posts | Comments where someone asks a question the vendor skips, or names a specific part of the product that fails them | The post URL, the comment, and the date |
| Review sites | Reviews that repeat the same complaint, or a rating that dropped after a release | The quote, copied exactly as they wrote it |
| Industry communities | Threads asking for an alternative, or comparing two tools | The link and what they said they need |
| The person's own posts | Posts about a migration, a new process, or a tool they are testing | The date, so you know whether it is still current |

> If you cannot fill in the source, the exact words and the date for a person, do not write the note yet. A name and a company is not a trigger.

## Check that the person can actually switch

A complaint is not a buying signal on its own. The person venting might be an intern, or sitting at a company that just signed a three-year deal. Spend thirty seconds on the profile before you spend a request.

1. **Read the headline and the last two roles.** You want the person who owns the workflow or feels the problem every week. A director who inherited the contract can sign. The analyst who rebuilds the export every Monday can push internally. Someone who left that company a month ago can do neither.
2. **Check company size against your fit.** If your product only makes sense above 100 employees, a 12-person agency is not a lead no matter how angry they are. Disqualify and move to the next name.
3. **Look at what the company is hiring for.** A job post asking someone to own the migration off Acme is stronger than any comment. So is a post about cleaning up reporting or consolidating tools.
4. **Check the date on the complaint.** Something from eight months ago has been solved, absorbed or forgotten. Aim for the last month, or a complaint that keeps reappearing across several posts.

## Write the note around the switch

The connection note has one job: get accepted. People already frustrated with a tool do not want a pitch inside the request. They want to know you saw the same thing they did.

Two sentences and a question is enough. Sentence one is their situation, in their words. Sentence two is who you are and what you do about that situation. The question asks for the connection.

**Reads like a blast**

- Hi, I saw you use Acme. We are the leading alternative and would love to show you a demo.
- Hi, I noticed you work in operations and might be evaluating new tools. Open to a chat?
- Hi, I'd love to learn more about your business and how we can help.

**Names the moment**

- Saw your comment on Acme's post about the reporting delay. I build those same reports without the wait for a few ops teams. Worth connecting?
- You asked in the Acme group how to get data out without a CSV export. That is most of my week. Happy to share what has worked.
- Your note about the support queue at Acme matched what two other teams told me this month. I work on the other side of that problem. Connect?

```
Hi {first name}, saw your comment about {specific problem} on {competitor}'s post.
I do {the same job} for a few {type of team} without that step.
Open to connecting?
```

## Run the note through this checklist

Write the note, then check it against the list below before you send. Most requests that get declined fail on the first item.

1. **Does the opening belong to this person alone?.** If you could swap in a different name and the note still reads fine, it is not specific. Rewrite until it only makes sense for them.
2. **Did you name the problem instead of the category?.** 'Your comment about the export timing out' beats 'your data challenges' every time. Use their nouns.
3. **Is the ask a connection?.** Asking for fifteen minutes inside a connection request gives people a reason to decline. Save the meeting for after they accept.
4. **Would you accept it mid-migration?.** Read it as someone short on time and already annoyed with their current tool. If it sounds like a template, it is one.

> Delete any note you could send to two different people without changing a word. The request box is the one place where vague costs you the lead.

## What to say after they accept

Do not repeat the note. They know why you reached out. Ask one question about how they do the work today and let them answer it.

When they describe the problem, offer one thing: a screen recording of how your tool handles that exact step, a short call, or a comparison of the two setups. One thing, not a deck.

Keep the exchange short. If they ask something you can answer in two lines, answer it there. The moment they ask about pricing or a trial, move to a call or send the link.

- **them:** Accepted, thanks. The reporting thing is real, we lose about a day a week to it.
- **you:** A day a week adds up. Are you rebuilding it in a spreadsheet, or inside Acme?
- **them:** Spreadsheet. The native report won't split by region.
- **you:** That is the exact setup I would want to show you. I can send a two-minute recording of how we split by region, or we can do a short call. Which is easier?

## Keep the account healthy while you do this

LinkedIn does not publish how many invitations or messages an account can send. Anyone quoting an exact number is guessing. What you control is how the account behaves: steady volume, notes written for one person, and a pending pool that does not pile up.

Withdraw invitations that have sat unanswered for a couple of weeks. A large pending pool with a low acceptance rate is the pattern worth avoiding. If your notes stop getting accepted, the fix is better targeting, since more volume only makes it worse.

Send when the lead is at work, not when you are. A note that lands at 2am their time sits under three other notifications by morning.

> Judge acceptance rate per note style, not overall. A drop usually means the targeting got lazy, not that LinkedIn changed something.

## Doing this with Kinlead

Kinlead has an agent that does the watching for you. [Steal Customers](/features/steal-customers) monitors competitor company pages and, if you want, founder or employee profiles, reads the comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented.

Those leads are scored from 0 to 100 against the customer you describe, and anything below the fit line is dropped. Connection notes are written for you, under 200 characters, and open with the reason that person became a lead.

- Outreach sends from your own LinkedIn account at a human pace, one action every 5 minutes, inside the daily limits and send window you set in the lead's time zone.
- Messages and follow-ups come from your campaign goal, tone and an optional sales playbook you provide.
- Replies from every campaign land in one inbox and are classified by intent, with interested replies first.
- If LinkedIn pushes back on an account, Kinlead pauses invites there and emails you.

> Pro is $49 a month after a 7-day free trial, and you can see [Kinlead pricing](/pricing) for seats and everything else. If you would rather watch it run against your own competitor list first, [book a demo](/demo).

## Related

- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI connection note examples](https://getkinlead.com/ai-sdr-connection-note-examples.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I name the competitor in the connection note?**

Yes, when you are referring to something specific they said or ran into. Naming the tool proves you read their situation. A note that names nobody reads like a blast.

**What if they accept but never reply?**

Send one follow-up after a couple of days with something useful about the problem they mentioned, such as how the export works in your tool. If that gets nothing, leave it alone and move on.

**How many of these requests can I send a day?**

LinkedIn does not publish exact limits, so nobody can give you a real number. Keep the volume low enough that you can write a specific note for every person, and watch your acceptance rate.

**Does this work if the competitor is much bigger than us?**

Often yes, because large vendors leave narrow workflows underserved. Pick the one workflow you handle noticeably better and aim only at the people who own it.

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