# How to connect with leads based on shared experiences
> Stop using generic alumni hooks. Learn to use professional pain points in LinkedIn requests to get more people to accept your connection invites.
- HTML: https://getkinlead.com/connecting-with-leads-from-shared-experience
- Markdown: https://getkinlead.com/connecting-with-leads-from-shared-experience.md

**Short answer:** To mention shared experience in a LinkedIn request, name a specific professional pain that comes with their job title, company or market. Describe the daily friction of their role in their own words, then say why you want to connect. School ties and mutual connections rarely get accepted.

## Stop using the alumni or mutual connection hook

Alumni and mutual connection hooks are the easiest thing to find on a profile, which is exactly why everyone uses them. If you both went to the same university ten years ago, that's a fact about your past. It tells the reader nothing about why you're reaching out this week.

A connection request works when the reader thinks "this person knows my job." School ties and shared connections almost never produce that reaction. They produce a polite accept and silence afterwards, because the note gave them nothing to reply to.

Start with their current role instead. If you both run sales teams, name what's making this quarter hard. If you both work in logistics, name the part of the job that keeps breaking. Leave the campus out of it.

**Weak hooks**

- I saw we both went to State University. Let's connect!
- We have 5 mutual connections in marketing. Let's network.
- I see we are both in the same industry. I'd love to add you to my network.

**Experience hooks**

- You're managing a remote sales team in healthcare. The timezone gaps are the part I underestimated. Would like to connect and follow how you handle it.
- I noticed you're also dealing with AI-driven search changing B2B lead flow. I'm watching the same shift and would like to see what you're finding.
- As a fellow head of ops, most of my month goes on vendor consolidation right now. Curious whether you're seeing the same friction.

## Identify your shared professional pain

Shared experience in B2B is rarely about shared history. It means you both face the same obstacle or use the same tool, so one sentence about the job lands as true.

Read the headline and the company, then think about the three biggest headaches that role owns right now. Pick the one you can speak to honestly, and describe it the way a person in that seat would.

The strongest hooks use language only an insider would use. A specific compliance deadline, a tool migration, a reorganisation that changed who signs off. That detail proves you looked at their world instead of pulling a line from a template.

1. **Read the headline, skip the bio.** The headline usually names the role and the market. That's enough to guess what the daily work looks like.
2. **List the headaches that role owns.** Pipeline gaps, hiring freezes, overlapping software, audit season. Keep the one you actually understand.
3. **Check their last two posts.** A recent post gives you their own words about the problem. Borrow one phrase so the note sounds like them.
4. **Write one observation sentence.** Specific enough that a peer in the same job would nod. If it could be sent to anyone in the industry, cut it.

## Drafting the request

The wording decides whether you read as a peer or as a salesperson. A peer describes what they're seeing. A salesperson describes what they're selling, and the reader spots it before the second line.

Keep the tone casual. Use words like friction, backlog, headache, mess. Vendor words such as solution, platform or optimize mark you as a seller immediately.

Three lines is enough. If it reads like a paragraph, people assume a pitch and ignore it. The first line should be the observation, the second your reason for connecting, and nothing else.

- **you:** Hi Sarah, as a fellow head of ops I've spent most of this quarter on vendor consolidation. The overlapping SaaS seats are the part nobody warned me about. Would like to connect and keep up with how you're handling it.
- **them:** Hi, you nailed it. It's a mess right now. Happy to connect.

> Never ask for a meeting in the connection request. The only job of that note is to get the accept.

## Common experience templates by role

Different roles carry different pain. A founder worries about hiring and runway. A team lead worries about next week's deliverable. Your hook has to match the level of the person reading it.

Use the table as a starting shape, then replace the specifics with whatever you know about that person or their company. The sentence structure travels. The detail has to be yours.

| | Target role | Shared pain point | Example hook |
| --- | --- | --- | --- |
| SDRs | Gatekeepers blocking cold calls | I'm seeing a real shift in how gatekeepers screen calls in the legal space. Curious whether you're getting the same reception. |
| Founders | Hiring the first few people | Hiring the first five employees in this market has been a strange ride. Would like to connect with other founders in the middle of it. |
| Product managers | Tech debt against new features | The fight between clearing tech debt and shipping new features is loud this quarter. Curious how other PMs are splitting the time. |
| Heads of ops | Vendor and tool overlap | Most of my month is vendor consolidation. I suspect you're looking at the same invoice pile. |

## Research a prospect without losing an hour

You don't need an account brief. Two minutes on the profile and one on the company site gives you enough for a specific line.

Look for the phrasing they use about their own job, any recent post about a problem, and one piece of company news that affects their team. Job postings are useful too: a role they're hiring for tells you what's breaking.

If you use an AI assistant, give it the details and ask for the headache, not the message. Drafting the observation yourself keeps it honest, and honesty is what makes it read like a person.

```
You're helping me find a shared professional pain for a LinkedIn connection note.

Prospect: [job title], [company], [industry]
What I do: [one line]

List the three hardest parts of that job this quarter. Then write one sentence describing the one I'm most likely to understand from my own work. Use their language, no sales words, under 30 words.
```

## After they accept, keep the same thread

The shared experience you used in the invite is your opening for the first message. Bring it back within a day or two while the accept is still fresh in their mind.

Ask one question about their situation and stop typing. A message that ends in a question gets a reply. A message that ends in a pitch gets a profile view.

When they answer, stay on their problem for a few exchanges before you say anything about what you do. If the problem turns out to be real and you can help, say so plainly and offer a short call.

- **you:** Thanks for connecting, Sarah. You mentioned the overlapping SaaS problem. We cut nine duplicate tools last quarter and the process was messier than I expected. How are you sequencing yours?
- **them:** Starting with the ones nobody owns. Legal and finance both pay for the same research tool, which is fun to explain to the CFO.
- **you:** That's the pattern I keep hearing. I have a short checklist we used for the ownership question. Want me to send it over?
- **them:** Yes please, that would help.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below your fit line aren't kept, so the list you write notes for is already narrowed.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages, 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 they commented. That gives you a real shared experience to open with instead of a guess.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. You can supply your own sales script as a playbook and set the tone. Outreach runs from your own LinkedIn account through Unipile, at most one action every 5 minutes, inside the daily limits and send window you set. Queued messages can be read and edited on the Actions page before they send.

## Related

- [Connection request personalization tips](https://getkinlead.com/ai-connection-request-personalization-tips.md)
- [Steal customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI sales playbook guide](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)

## Common questions

**Should I mention my product in the first connection request?**

No. A product mention turns a peer-to-peer note into a pitch. Save it until they've described a problem you can actually help with.

**What if their profile has almost nothing on it?**

Use the job title and the company's industry to make an educated guess about the daily work. A reasoned guess about a real headache beats a compliment about their background.

**How many shared experiences should one note contain?**

One. Two or three makes it read like an application form rather than a casual message from a peer.

**They accepted but never replied. What now?**

Send one follow-up that refers back to the observation in your note and asks a single question. If there's no reply after that, leave it and move on.

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