# How to message a prospect who commented on a mutual's post
> Learn how to turn a prospect's comment on a mutual connection's LinkedIn post into a real conversation, with filters, message templates and reply handling.
- HTML: https://getkinlead.com/messaging-prospects-after-a-shared-connection-post
- Markdown: https://getkinlead.com/messaging-prospects-after-a-shared-connection-post.md

**Short answer:** Find a comment where the prospect describes a problem, a question or a strong opinion in their own words. Open with that specific comment and ask a short follow-up question. The goal of the first message is a reply, not a meeting.

## Start with comments that give you something to say

Not every comment is worth a message. A comment like 'Great post' gives you nothing to continue. A comment where someone names a tool they tried, a team size that made an approach fail, or a disagreement with the post gives you a real opening. Read the thread before you open a profile.

Look for a specific problem, a question the post did not answer, or an opinion strong enough to invite a follow-up. If the person only thanked the author or tagged a colleague, skip them. You need words you can quote back without guessing what they meant.

A like or a repost is weaker than a comment. A comment has language you can use. A like tells you almost nothing about what the person cares about. Sort the comments, read the first line of each, and stop when you find one that makes you curious.

**Comments with no opening**

- Great post, Sarah.
- This is spot on.
- Thanks for sharing.

**Comments you can work with**

- We tried this with our onboarding team and the handoff step broke down.
- Does this work when the buyer is the CFO and not the head of ops?
- I disagree with the second point. Most small agencies cannot staff that weekly.

## Check whether the comment points to a real problem

The mutual connection matters less than the problem the prospect described. Before you write, read the original post so you know what the comment is responding to. A comment can look useful on its own and mean something different in context.

The post might be a case study, a rant, or a question. If it is a rant, the commenter may be adding their own frustration. If it is a how-to, the commenter may be asking about an edge case. Both can work, but the message changes.

Then decide if your product or service touches that problem. If you sell scheduling software and the comment is about hiring, you do not have a bridge. You have a coincidence. Sending a message anyway teaches the prospect that you did not read carefully.

Write the bridge in one sentence before you open LinkedIn. 'You said X, and I work on X' is too thin. 'You said X, and I am curious whether Y is the reason' gives the person something to answer.

1. **Read the post and the comment together.** Note the author's claim, then the prospect's reaction. The gap between them is often the conversation.
2. **Write the problem in one sentence.** Use their words, not your product language. For example: 'They cannot vet overseas contractors fast enough.'
3. **Test the fit before you message.** If your offer does not change that sentence, stop. Find another lead or wait for a better comment.

> A mutual connection is context, not permission. The comment has to carry the reason for the message.

## Write the first message like a person who read the thread

Open with the comment, not with yourself. Mention the mutual connection once so the prospect knows why the post showed up in your feed. Then quote a few words from their comment and ask a question that continues the thought.

Keep it short enough to read on a phone. Do not explain your product, attach a calendar link or list your credentials. The first message has one job: earn a reply from someone who remembers writing the comment.

Mention the mutual connection once, not as a name drop. 'I saw your comment on Sarah's post' is enough. You do not need to say you know Sarah well or that you worked together. If you have not met Sarah, do not imply you have.

- **you:** Hi Mark, I saw your comment on Sarah's post about hiring overseas. You said vetting was the part that kept breaking. Is that a process problem on your side or a problem with the agencies you tried?
- **them:** Mostly the agencies. We get profiles fast, then the first two weeks show whether anyone actually checked the work.
- **you:** That matches what I hear from ops leads. What are you using now to test the work before a full hire?

> Do not ask for a call in the first message. Ask one question that a busy person can answer in two sentences.

## Handle the reply without rushing to a demo

A reply is not a buying signal by itself. Some people answer because they like talking about the topic. Others answer because they have budget and a deadline. Your next message should sort that out without turning the thread into an interrogation.

Ask what they have tried, who owns the problem and what happens if it stays unfixed. If they give short answers, do not pile on more questions. Offer one useful observation and let them decide whether to keep going.

When they describe a current project, a deadline or a person who owns the problem, you can ask if a short call would help. Keep the ask tied to the problem they named. Do not send a calendar link in the first reply unless they ask for one.

If they ask for a deck, send one page tied to their comment. Do not send a generic PDF and ask them to find the relevant part. That shifts work to the buyer and usually ends the thread.

| | What they reply | What it usually means | Your next move |
| --- | --- | --- | --- |
| Thanks, we already fixed it. | They are closing the loop. | Ask what fixed it. Keep the door open, then stop. |
| We are looking at tools now. | There is an active project. | Ask what the shortlist looks like and what made them start looking. |
| Can you send info? | They want to control the pace. | Send one short note tied to their comment, then ask if a call makes sense. |
| Not a priority this quarter. | The timing is wrong. | Ask when it usually comes up and whether you can check back then. |

## Use a short template you can adapt

Templates are fine if you change the part that proves you read the comment. The template below has four slots: the mutual connection, the topic, their words and your question. If you cannot fill the quote slot with real words, do not send it.

Keep the tone close to how you talk. Remove phrases like 'I hope this finds you well' and 'I would love to pick your brain.' They make the message sound like a mail merge.

If they do not reply, one follow-up is enough. Add a new detail, such as a related post or a question about what changed. Do not send 'just bumping this' or a second pitch.

The follow-up should not repeat the first message. If the first message asked about the agency problem, the follow-up can ask whether they changed the vetting step or whether the problem moved to another part of the process.

> If the message still makes sense after you remove the mutual connection's name, it is probably a pitch. The comment should be the reason you wrote.

```
Hi {{first_name}}, I saw your comment on {{mutual_name}}'s post about {{topic}}. You said {{quote_from_comment}}. I'm curious: {{one_question}}?
```

## Doing this with Kinlead

Kinlead can find the commenters for you. The 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, so you have the quote before you write.

Leads are scored from 0 to 100 against the customer profile you describe, and leads below the fit line are not kept. You can put them in lead groups and point a campaign at the group. Connection notes can be AI-written under 200 characters and open with why that person became a lead. See [Steal Customers](/features/steal-customers) for the setup.

Replies from every campaign land in one inbox classified by intent, and each campaign can hand the conversation to you at the first reply.

## Related

- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I comment on their comment before messaging them?**

Yes, if you can add something useful to the thread. It makes your name familiar so they recognize you when your message arrives.

**Do I need to be connected to the mutual friend first?**

It helps, but it is not required. Referencing a public post still works, though the bridge is weaker if you are not connected.

**What if the prospect does not remember the post I am talking about?**

Quote their specific words. If you say 'I saw your comment about X,' they will remember the thought even if they forgot the post.

**How long should the first message be?**

Short enough to read on a phone without scrolling. Two or three sentences that name the comment and ask one question are usually enough.

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