How to message prospects who share industry content
Turn a prospect's LinkedIn share into a real conversation. Skip generic praise, name the specific point they made, and ask about the problem behind it without sounding like a bot or a script.
Get startedShort answer
Avoid generic praise like 'great share' when reaching out to someone who posted content. Instead, name the specific opinion or problem they highlighted and ask a question that connects that topic to a business challenge you solve. That turns a social interaction into a professional conversation.
Stop using generic compliments
Most sellers send messages like 'great share' or 'insightful post.' Prospects ignore these because they carry no information. The prospect knows you could have sent that message to anyone who posted that day.
A generic compliment also signals that you want something. The reader sees the pattern: praise, then a pitch. They delete it before you get to the pitch.
To get a reply, prove you read the content and understand the context. Reference a specific detail, a quote, or a point of view the prospect expressed in their caption. That shows you are a peer in the industry, not a stranger with a script.
Weak message
- Thanks for sharing this article, it was very insightful!
- I love the content you're posting lately, keep it up!
- Great share on the future of AI, very interesting read.
Strong message
- I saw you shared that piece on supply chain delays. Your point about port congestion in Long Beach is exactly what we're seeing with our clients.
- Your take on the new tax laws in your recent share is interesting. I hadn't considered how that affects mid-sized agencies in the Midwest.
- I noticed you shared the report on remote work. Your comment about 'culture debt' is a problem we're currently solving for a few teams.
Find the bridge to your offer
Use the article as a bridge to a business problem. If you only talk about the content, you are having a social conversation. To make it a sales conversation, connect the content to a pain point your product solves.
Look for the gap between the ideal state described in the post and the reality the prospect faces. That gap is where your value lives. A post about faster onboarding points to a slow handoff. A post about better forecasting points to messy pipeline data.
Write down the problem in one sentence before you message. If you cannot name the problem without mentioning your product, you are not ready to send.
- 1
Read the caption and the comments
Find the sentence where the prospect adds their own opinion. That sentence is usually more useful than the article itself.
- 2
Name the business problem
Turn the topic into a daily frustration. If they shared a post about employee burnout, the problem might be manual work that keeps the team late.
- 3
Connect the problem to a result you can discuss
Link the frustration to an outcome your product supports, such as fewer manual reports or faster handoffs. Keep the claim small and true.
- 4
Ask a diagnostic question
Ask how they handle that problem today. A question gives them a reason to reply and gives you information for the next message.
Write the first message
Keep your first message short. You do not have room for a full pitch. Your goal is to get them to acknowledge that you understand their problem and are worth talking to.
Avoid formal language or corporate jargon. Write the way you would speak to a colleague at a conference. Use a hook to prove you read the post, a bridge to name the problem, and a low-pressure ask to start the conversation.
Do not ask for a meeting in the first line. Ask about their situation first. If they confirm the problem, you have a reason to offer a call.
Example
- You
Saw you shared the article on warehouse automation. Your comment about the struggle with legacy software integration caught my eye.
- You
Usually, when people struggle with that, it's because the API documentation is outdated or the vendor is slow to respond. Are you seeing that happen at Northwind, or have you found a way around it?
- Prospect
Actually, that's exactly what's happening. Our current vendor takes two weeks to answer a ticket.
- You
That's a common frustration. We built a way to bypass that manual sync. Would it be worth a 10 minute chat to see if it fits your setup?
Paste this job
I saw your post on [topic]. Your point about [specific detail] stood out. When [problem] shows up, teams often [common workaround]. Is that happening at [company], or have you found another way?
Choose the right outreach path
Choose your engagement method based on how high-value the prospect is. Jumping straight into a direct message can feel aggressive if you have never interacted with them.
A public comment creates a digital footprint. This makes your private message feel like a continuation of a conversation rather than a cold start.
If the post is from a competitor's page, comment only when you have something useful to add. A comment that argues with the post can hurt your chances.
Public comment
- Method
- High-visibility posts
- When to use it
- Build familiarity and visibility
Direct message
- Method
- Private business discussions
- When to use it
- Move to a discovery call
Comment then message
- Method
- Top-tier target accounts
- When to use it
- Start with context before the ask
Handle the reply without pitching too early
When they reply, resist the urge to send a calendar link in the next message. A reply means they are willing to talk about the problem, not that they are ready to buy.
Ask one follow-up question about how the problem affects their team. Then share a small, relevant observation from your work. Keep the focus on their situation.
If they ask what you do, answer in one sentence and connect it back to the problem they described. Then ask if a short call would help.
Weak reply
- Thanks! Let me know when you're free for a demo.
- I can send you a summary. What's your email?
- We help companies solve this. Book a time here.
Strong reply
- That two-week vendor delay sounds painful. Does it block your team from shipping on time, or is it more of a reporting headache?
- We see that a lot with legacy syncs. One team cut the manual step by moving the sync outside the vendor queue. Would it help to compare notes?
- If the delay is costing you a release cycle, a 15 minute call might be enough to see if we can help. Want me to send two times?
Doing this with Kinlead
Finding these conversations manually takes hours. Kinlead's Steal Customers agent 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.
Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Kinlead keeps leads in lead groups, and any campaign can point at any group. Campaigns send at a human pace: each LinkedIn account sends at most one action every 5 minutes, inside daily invite and message limits you set and inside a send window in the lead's time zone. You can pause any campaign.
If you ask for a meeting before you name their problem, the reply usually stops.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to message prospects who share industry content.md