# How to message prospects who share industry insights
> Use a specific claim from a prospect's post as the reason for your message. Skip generic praise and start conversations that get replies on LinkedIn.
- HTML: https://getkinlead.com/message-prospect-who-shares-industry-insights
- Markdown: https://getkinlead.com/message-prospect-who-shares-industry-insights.md

**Short answer:** Use a specific claim the prospect made in a post as the reason for your message. Skip generic phrases like 'great post' and connect their point of view to a problem your product solves.

## Stop using generic praise

Most sellers open with 'great post' or 'really insightful share'. High-volume posters ignore these. They've seen these exact words in their inbox many times this week, so they know you're using a template or a bot.

Generic praise proves you saw that they posted. It does not prove you read the post. To get a response, you have to prove you processed the information and formed an opinion on it.

The goal is to show you're a peer who understands the specific nuance of the problem they're discussing. That means quoting their words, not describing the post in your own summary.

A good test: if you can send the same message to ten people who posted about the same topic, it's not specific enough. The first line should only work for that person.

**Generic praise**

- Loved your recent post on AI trends. Really insightful stuff!
- Great share on the future of SaaS. Thanks for posting!
- I've been following your content and always find it valuable.

**Specific POV hook**

- Your point about AI replacing middle management in legal firms caught my eye because I'm seeing the same shift with three of my clients.
- I disagree with your take that remote work kills culture, but your point about asynchronous documentation is spot on.
- The part where you said churn is the new normal for seed-stage apps is exactly what we're debating internally right now.

## How to find a usable hook

You don't need to read every post they've ever written. You need one specific anchor point to transition into your value proposition.

Look for parts where the author takes a stand. People care most about their contrarian takes or specific methods. If they're arguing against a common industry practice, that's your opening.

If the post is a repost with no comment from them, skip it. You need their words, not the article's. A post with a named process or a strong opinion gives you something to work with.

Read the first two lines and the last two lines. Most writers put the claim at the top and the conclusion at the bottom. The middle is usually setup.

1. **Find a strong opinion.** Search for phrases like 'I believe', 'The problem is', or 'Stop doing X'. These are the points the author is most proud of.
2. **Isolate a specific noun or metric.** If they mentioned 'time to first value' or 'the four-hour work week', use those exact words. It proves you didn't just skim the headline.
3. **Identify the enemy.** Find what they're arguing against. If they hate 'bloated slide decks' or 'endless Zoom calls', mention your shared dislike to build rapport.

## The transition from POV to pitch

The biggest mistake is the pivot. A seller spends one sentence on the post and then jumps to 'Anyway, I have a tool for that'. It feels like a bait-and-switch.

Use a bridge instead. A bridge connects the author's point of view to a problem your customers face. You are still discussing a shared problem. The product comes later.

The bridge should be one sentence. Name the problem in their language. If they wrote about 'managers who spend all day in status meetings', use that phrase. Don't translate it into 'communication overhead'.

If you don't have a bridge, don't send the message. A hook with no bridge is just a compliment with a pitch attached. Wait for a post where you can name the problem.

- **you:** Hi Sarah, your post said the weekly 1:1 is dead because managers use it as a status update. I'm seeing the same thing with the managers I talk to.
- **them:** Exactly. The meeting becomes a chore and people just tell you what you want to hear.
- **you:** That's the pattern I keep hearing. I'm working on a way to get those check-ins without the calendar slot. Have you found anything that works, or are you still doing them manually?

> Don't ask for a demo in the first message. Ask if they've found a solution to the problem they just complained about in their post.

## Writing the message

A successful message follows a simple flow: specific hook, bridge to problem, low-friction question. Keep it under 100 words. If it looks like a wall of text, they'll archive it.

The wrong way focuses on you and your tool. The right way focuses on their perspective and the problem they've already admitted exists.

Write the first line last. Open with their point, then add the bridge, then ask one question. If you can remove your product name and the message still makes sense, you have a good hook.

One question is enough. Two questions give them a reason to answer the easier one and ignore the other. The question should be answerable in one sentence without a meeting.

| | Element | The wrong way | The right way |
| --- | --- | --- | --- |
| The opening | Hi Jane, great post on remote work. | Hi Jane, your point about the 'death of the 1:1' resonated. |
| The bridge | I have a tool that helps remote teams. | I'm building a way to automate check-ins without losing the human touch. |
| The ask | Want a demo? | Curious if you've tried any tools to fix this? |

```
Hi {{first_name}}, your post about {{specific_claim}} caught my eye because {{reason_it_matters_to_you}}. I'm curious how you're handling {{related_problem}} right now. Are you using a tool for it, or is it still manual?
```

## What to do after they reply

Most replies are short. Treat a short reply as a signal to ask one more question, not as a reason to send a calendar link.

If they answer your question, ask how they handle the problem today. If they ask what you do, give a one-sentence answer and ask if the problem is worth a short call. If they say they already use a tool, ask what it misses. If they give a one-word answer, stop. You can try again in a few months with a different post.

When they reply, don't switch to a script. Use the same language they used. If they say 'we're drowning in messages', don't say 'communication overload'. Say 'drowning in messages'.

- If they answer the question, ask one follow-up about their current process.
- If they ask what you do, answer in one sentence and ask if a short call makes sense.
- If they say they already use a tool, ask what that tool misses. Don't pitch against it.
- If they give a one-word answer, stop. Don't chase.

## Doing this with Kinlead

Finding these hooks by hand takes time. Kinlead's [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, 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.

You can use [AI-written connection notes](/features/ai-linkedin-outreach) under 200 characters that open with why that person became a lead. Outreach sends from your own LinkedIn account through Unipile. Kinlead sends at most one action every 5 minutes inside the limits and send window you set.

Replies from every campaign land in a [unified inbox](/features/unified-inbox) classified by intent, with interested replies first. You can see the workflow at [book a demo](/demo).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**Should I comment on the post before sending a DM?**

Yes. Leaving a thoughtful comment first makes your name familiar. They'll recognize you as someone who contributed to the conversation.

**How many posts should I read before reaching out?**

One is enough if it contains a strong opinion. You need one specific anchor point to start the conversation.

**What if they haven't posted in a few weeks?**

Reference their last meaningful post. Start with 'I was revisiting your post from last month about X and it sparked a thought' to show you're interested in their ideas.

**What if they ask for a demo right away?**

Send a scheduling link and keep the context in the invite. Mention the post and the problem so the call starts with the same hook.

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