# How to mention shared interests in LinkedIn outreach
> How to use shared hobbies, alma maters and interests to build rapport on LinkedIn without sounding like a bot. Templates and bridge techniques that work.
- HTML: https://getkinlead.com/linkedin-messages-for-shared-interests
- Markdown: https://getkinlead.com/linkedin-messages-for-shared-interests.md

**Short answer:** Mentioning shared interests works when you use a specific detail from a profile to prove you aren't running a mass template. Then bridge from that commonality to your business reason for reaching out, so the transition doesn't feel forced.

## Finding a hook that isn't obvious

Most people mention the first thing they see. Telling a prospect you both live in Chicago, or that you noticed they're a marketing manager, is just reading their header back to them. It reads like a template because it is one.

A hook worth using takes a second look. You want a detail they chose to put on their profile because it matters to them, not a field LinkedIn filled in for them.

Four places to look, roughly in order of how well they work:

- Comments they left on someone else's post. People write more freely in comments than in their own posts.
- The last two lines of the About section, where people usually put what they actually care about.
- The Featured section, including any article, talk or side project they linked.
- Groups, associations and volunteer roles listed further down the profile.

**Obvious mentions**

- I see we both live in Chicago.
- I noticed you're a Marketing Manager.
- We both went to the University of Texas.

**Hooks that took a second look**

- I read your comment on Northwind's post about rebuild costs. The point about lead times matched what we see.
- Your About section mentions you still race sailboats. That explains the scheduling line in your last post.
- I saw you spoke at the Austin ops meetup about warehouse turnover. I've been chewing on the same problem.

## The bridge from the hook to your reason for writing

The pivot is where most personalized messages fall apart. Three sentences about sailing followed by a request for a meeting about software feels like a bait and switch, and the reader feels it immediately.

You need one sentence that connects the thing you noticed to the work you do. The connection has to be real. If the only link you can find is that you both like coffee, skip the hook and lead with the business reason.

A bridge works when it borrows a trait from the hook, not the topic. A post about rebuilding an engine is about patience and tolerances. A post about hiring three reps is about ramp time. Name the trait, then say why it made you write.

1. **Name the detail.** Say exactly what you saw and where, in one clause. 'I read your comment on Northwind's post about rebuild costs' does that in a dozen words.
2. **Add one line of your own.** A short reaction or a related experience. One sentence. This is what separates a reader from a scraper.
3. **Bridge on the trait.** Use a phrase like 'That same focus on lead times' or 'You're clearly dealing with ramp time' to move from their topic to yours.
4. **Say why you're writing.** One sentence on what you do and who you do it for. No pitch deck language, no job titles stacked three deep.

## Templates for the commonalities you'll actually hit

These are skeletons, not scripts. Swap the specifics and keep the proportions: one clause on them, one line of reaction, one bridge, one line on you.

The most common shared ground on LinkedIn is professional, not personal. Alma maters and hobbies come up less often than a shared conference, a shared tool or a shared hiring problem.

| | Commonality | Skeleton |
| --- | --- | --- |
| Alma mater | I saw we both came through [University]. [One specific memory or detail]. I'm writing because I help [role] at [industry] companies with [outcome]. |
| Niche hobby | Your post about [hobby] caught my eye. I've been doing it for [time] and [specific detail]. You're dealing with [problem] at [company], which is the part I work on. |
| Shared group | We're both in [group]. Your take on [topic] stuck with me. I work with a few members on [problem] and wanted to compare notes. |
| Shared conference | I saw you were at [event]. Did you catch [session]? I ask because [bridge to your work]. |
| Shared tool | Noticed [company] runs [tool]. I spend most of my week on [related problem] for teams using it, which is why I'm in your inbox. |

```
Hi [First name], I read your comment on [company]'s post about [topic]. [One line reaction]. I'm writing because [bridge on the trait], and I help [role] at [industry] companies [outcome]. Worth a short conversation?
```

## Writing it so it doesn't sound like a bot

Automation gives itself away through enthusiasm. Words like passionate, thrilled, excited and huge fan turn up in template messages far more often than in messages people type themselves.

Write the way you'd message a colleague you don't know well. Contractions, uneven sentence lengths, one idea per sentence. Read it out loud. If you wouldn't say it to someone at a conference, cut it.

Keep the personal part shorter than the business part. If most of the message is hobby talk, it reads like you're pretending to be a friend to get a sale.

- **you:** Hi Sarah, saw your post about the Berlin marathon. The bit about the last 10k being a mental game landed, I ran it in 2019 and felt the same. I'm writing because you're hiring reps at Acme and ramp time is what I work on. Worth a short call?
- **them:** Ha, the last 10k is where it all falls apart. Onboarding is a mess here right now, so yes, tell me more.
- **you:** Most of the fix is what a new rep hears in week one and who they shadow. I can walk you through the setup in 15 minutes. Thursday or Friday?

> If you'd be embarrassed to say the personal line to the person's face, don't put it in the message.

## When you can't find anything shared

Most prospects won't give you a hobby, a school or a group in common. That's normal. Don't invent a connection or stretch one until it snaps.

Lead with something professional instead. It's still specific and it still proves you looked, and it doesn't require a fake friendship.

- A post or comment they wrote in the last month, and what it made you think about.
- A hire, a launch or a new market their team is clearly working on.
- A tool or process visible in their job description or their team's job ads.
- A talk or panel they spoke on, if you can find the recording or a summary.

> The test is simple: could you send this message to a different person at a different company with two words changed? If yes, it isn't specific.

## What to do after the first message

The shared interest gets you the reply. It shouldn't carry the whole conversation. Once they answer, move to the problem you wrote about and stay there.

Repeating the hobby in a follow-up is the most common mistake. It signals that the personal detail was a tactic, and it gives them nothing new to respond to.

If they don't reply, one short follow-up is enough. Add something useful: a question about their setup, an observation from another account, or a link to something you wrote. Don't reopen with the marathon.

**Follow-up that repeats the hook**

- Still thinking about that Berlin marathon! Anyway, did you see my last message about onboarding?
- Hope training is going well. Quick nudge on my note from last week.

**Follow-up that adds something**

- One thing I forgot to mention: the teams that fix ramp time fastest usually change what reps do in week one, not the training content. Happy to send the one page we use.
- Saw Acme posted two more sales roles. If onboarding is still the bottleneck, I can share how a 40 person team handled the same jump.

## Doing this with Kinlead

Kinlead's [Steal Customers](/features/steal-customers) agent 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 they commented, so the hook is already in the record when you sit down to write.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. 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 a competitor.** Add the company page and, if you want, the founder or a few employees.
2. **Let it read the comments.** Commenters who match your customer profile become leads, with the post and their comment attached.
3. **Set the note.** The connection note opens with why they became a lead. Keep it under 200 characters.
4. **Review before it sends.** Check the queued messages on the Actions page and rewrite the ones that need a better bridge.

## Related

- [Connection note examples](https://getkinlead.com/ai-sdr-connection-note-examples.md)
- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)
- [Outbound for founders](https://getkinlead.com/use-cases/outbound-for-founders.md)

## Common questions

**Should I mention a shared interest in the first message or wait for a reply?**

Mention it in the first message. It's the reason a stranger accepts a connection request or answers a cold message at all.

**What if I don't have any obvious shared interests with a prospect?**

Use a professional commonality. A post they wrote, a project their team shipped, or a hiring push you can see from the outside all work.

**Is it creepy to mention something from their personal life on LinkedIn?**

It's only creepy if the information isn't on their profile. If they listed sailing in their About section, it's fair game. If you found it somewhere else, leave it alone.

**How long should the personal part be?**

One clause, maybe two. The rest of the message should be about the work problem you're writing about.

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