# How to message prospects who post about a pain point
> A prospect posts about a problem on LinkedIn. Here is how to comment without pitching, move to a DM, and write a first message they will answer.
- HTML: https://getkinlead.com/messaging-prospects-who-post-about-problems
- Markdown: https://getkinlead.com/messaging-prospects-who-post-about-problems.md

**Short answer:** Don't pitch in the comments when a prospect posts about a problem. Add something useful in public so they know who you are, then send a private message that quotes their own words and offers one small next step.

## The public response

Your first instinct when a prospect posts about a problem is to tell them you have the fix. Do that in the comments and you look like every other vendor in the thread. People reading it, including the person who posted, clock it as a pitch and scroll past.

The comment has one job: show that you understood the problem. Validate the frustration, add a detail from your own experience, and leave the product out of it. That earns you the right to send a private message they'll actually open.

Keep it to two or three sentences. If you have a quick tip that helps them today, give it away in full. Don't tease it and ask them to DM you for the rest. Then say plainly that you're sending a message with more.

**The vulture**

- I can help with this! Our platform solves exactly this problem. DM me for a demo.
- This is why you need a proper tool. Check our site to see how we fix it.

**The peer**

- That sounds frustrating. I saw the same lead leakage at a 40-person agency last year, and it turned out the handoff between marketing and sales was dropping records. Sending you a note with what they changed.
- This usually shows up once a team passes ten people and everyone starts keeping their own list. I'll send over the checklist a founder friend used to fix it.

## Moving to the DM

Most people lose the thread at the transition. They comment well, then send a message that reads like a template, and the prospect realizes the comment was bait.

Anchor the message in their words. If they wrote that reporting is a nightmare, use nightmare. If they said the pipeline is a mess, say pipeline. It proves you read the post and didn't scrape a job title.

Don't ask for thirty minutes in the first message. Someone who just posted about a stressful problem has no appetite for a calendar link. Offer one asset, one piece of advice, or a yes or no question.

1. **Name the post.** Say which post you saw and roughly when. One line is enough, and it stops them wondering how you found them.
2. **Use their words.** Repeat the problem in their phrasing, not yours. If they wrote that their reps hate the CRM, don't translate it into adoption challenges.
3. **Give one concrete thing.** A checklist, a screenshot of a process, a two-line answer to the actual question. Something they can use without replying.
4. **Ask something easy.** End with a question that takes ten seconds to answer. Asking whether they want the checklist works better than asking for a call.

## Writing the message

Write like a person who happens to have solved this before. Skip the openings about hoping this finds them well or wanting to introduce yourself. Nobody talks like that, and it signals a sequence.

Talk about the outcome. If you sell CRM software, the interesting part is that the team finally logs their calls, not that the platform runs in the cloud.

A connection request note has to fit under 200 characters, so cut everything except the reason you're reaching out. The reference to their post does most of the work.

- **you:** Hi Sarah, saw your post about getting the team to actually use the CRM. The bit about reps keeping a second spreadsheet in parallel hit close to home.
- **you:** I worked with a founder in the same spot last spring. What worked was cutting the required fields down to four and having managers log calls in the same view as everyone else.
- **you:** Want me to send the one-page version of what they changed?
- **them:** Yes please. We've tried three tools and nothing sticks, so I'm open to it being us.

```
Hi {first name}, your post about {problem in their own words} stuck with me. {One sentence on a similar situation and what actually changed for them.} I wrote up the short version. Want me to send it over?
```

## Handling the response

When they say yes, send the thing. Don't reply with an offer to walk them through it on a call and make them chase you. Send the asset in the next message, then ask if they want help applying it.

If they're only venting, let it be. A short note that it's a rough one and you've been there, with no ask attached, keeps you in their mind without costing you anything. They'll remember that you didn't pounce.

No reply is normal. People post during a bad week and then get pulled into the thing they posted about. One follow-up a few days later, framed as a check-in rather than a nudge, is enough. If that goes unanswered, leave it.

| | What they said | What you do | What you're after |
| --- | --- | --- | --- |
| Send it over | Send the asset in the next message, with no call ask attached. | Deliver value, then ask about applying it. |
| Just venting | Acknowledge it and stop. No link, no ask. | Stay familiar for when it turns into a project. |
| No reply | One follow-up after a few days asking whether they sorted it. | Find out if the door is still open. |

> Never put a calendar link in the first message. It asks for their time before you've given them anything.

## When to skip the post

Not every complaint is a buying signal. Someone posting about a bad week, a layoff, or a personal setback is not a lead, and treating them like one is how you get blocked.

Skip posts where the person is announcing a decision already made, like a note that they just signed with a new vendor. Skip posts where the pain sits outside what you sell. Skip posts from people who can't buy, unless you have a reason to build a relationship with them anyway.

The posts worth answering have three things: a specific problem, a person with budget or influence over it, and a tone that suggests they're looking for a way out. If two of those are missing, wait for the next post. Reading intent this way is a skill you can practise, and there's a longer breakdown of [identifying buyer intent in comments](/identifying-buyer-intent-in-comments) if you want the signals.

> If you can't name the specific change you'd make for them, you don't have a reason to message yet.

## Doing this with Kinlead

Reading competitor posts and comment threads by hand takes an hour a day and you'll still miss most of them. The [Steal Customers agent](/features/steal-customers) watches competitor company pages and any founder or employee profiles you add, 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 the person commented, so the context is already there when you write. You can point a campaign at that lead group and let AI draft from your own sales playbook, or set the campaign to hand replies to you at the first response.

Outreach goes out from your own LinkedIn account through Unipile, one action every five minutes inside the daily limits and send window you set. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.

## Related

- [Identifying buyer intent in comments](https://getkinlead.com/identifying-buyer-intent-in-comments.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I send a connection request or a message first?**

If you're already connected, message. If not, send a request with a short note that names their post, since a cold DM to a stranger usually lands somewhere they never open.

**How soon after they post should I reply?**

Same day if you can. A comment within a few hours reads as timely, and a message within 24 hours still lands while the problem is fresh.

**What if the post is a week old?**

You can still reach out. Acknowledge that you saw it later and say why it stuck with you, rather than pretending you caught it live.

**Should I mention my product in the comment at all?**

No. The comment is there to show you understood the problem. The product belongs in the DM, and only after you've given them something useful.

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