What to say when someone posts a problem on LinkedIn

Turn public complaints and pain point posts into conversations by offering one specific insight, then use the post itself as the reason to connect.

Get started

Short answer

Don't pitch your product in the comments or connection requests when someone posts a problem. Identify the specific gap in their process and offer one piece of advice or a resource to help. Reference the exact post in your request so they know you aren't using a template.

The mistake most people make

Most sales reps see a prospect venting and treat it as a green light to pitch. They send a request saying they have the perfect solution. This feels like an ambush to a prospect who wants help or empathy, not a sales presentation.

Your first touch should prove you're a peer who understands the problem. If you lead with your product, you're just another vendor. If you lead with a solution to a small part of their problem, you're a resource.

The post is not an invitation to sell. It is a signal that the person is stuck. Your job is to be useful before you are commercial.

The pitch

  • I saw your post about your team struggling with manual data entry. My software solves that exactly. Let's connect to discuss how we can help.
  • Saw your post about X. I've helped other companies fix this. Would love to show you our demo.

The insight

  • I saw your post about the data entry bottleneck. A simple naming convention for your CSVs usually fixes that specific error. Happy to share the template I use if you're interested.
  • Saw your post about the X issue. This usually happens because of a gap in the Y process. I've got a quick workaround for that if you want to connect.

How to analyze a pain point post

Diagnose the post before you type. A vague complaint like "I hate my CRM" is different from "My CRM doesn't sync with my calendar." The second one is a specific technical gap you can actually address.

Look for the emotion and the outcome. Are they frustrated because they're losing money, losing time, or looking foolish in front of their boss? Mirror the urgency of that outcome in your response.

Write down the exact words they used. If they say "reporting is a mess," don't reply with "data visibility." Use their phrase so they know you read the post.

If the post is a pure vent with no detail, don't force it. A short "that sounds frustrating" comment is enough. Save the outreach for posts with a real problem.

  1. 1

    Identify the core frustration

    Isolate the specific pain. Instead of "bad reporting," find the "takes four hours to build one weekly report" part of the post.

  2. 2

    Determine the root cause

    Decide if the problem is a tool failure, a process gap, or a lack of knowledge. This tells you whether to suggest a tool, a workflow change, or advice.

  3. 3

    Find a specific anchor

    Pick one detail they mentioned, like a tool name or a deadline, to prove you read the post and aren't using a bot.

  4. 4

    Pick one useful resource

    Find a tip, a checklist, or a workaround you can give away for free that solves a small piece of the problem immediately.

Writing the connection request

You have limited space in a connection request. Every word must get the request accepted. Avoid filler phrases like "I'd love to connect" or "I'm reaching out because" since they signal a sales pitch.

Start with the post, provide the value, and end with a low-pressure invitation. Make them feel that accepting your request is the easiest way to get the solution you promised.

The note should sound like something you would send to a coworker. Short sentences. One idea. No pitch deck language.

Example

  1. Suggested reply

    Saw your post about the API sync errors. I've seen a middleware setting fix that for a few clients. Thought I'd share it. Connect if you're still digging into this.

  2. Prospect

    Thanks for reaching out. I'm definitely still struggling with this. What's the setting?

  3. You

    It's the Force Sync toggle in the admin panel, but it only works if you clear the cache first. Happy to walk you through it or send a screenshot.

Keep your note short enough to read in one glance. A tight note feels like a quick, human observation, not a pitch.

What to say in the comment before you connect

A comment is public. It should help the person and anyone else reading the thread. Don't dump a link. Don't write "DM me." Give one concrete step they can try today.

Use the same diagnosis you did before the request. Name the specific issue, suggest a small fix, and leave the door open for a deeper conversation. If you don't have a useful comment, skip the post. A weak comment does more damage than no comment.

Don't ask for permission to help. Offer the step and let them decide. "Want me to send the checklist?" is enough.

Paste this job

Try this: [specific step]. I ran into the same thing when [short context]. The part that usually trips people up is [root cause]. If you want, I can share the checklist I use for [task].

Handling the conversation after they accept

The clock starts once they accept. If you immediately pivot to a booking link, you break the trust you built by being helpful. The transition from helpful peer to service provider must be gradual.

Ask clarifying questions. This makes the prospect feel heard and gives you the data you need to make your eventual pitch relevant.

Don't send a calendar link in the first reply. Wait until they ask how you can help or describe the problem in more detail.

Open

Stage
Confirm you understood the problem
What you want
Thank them for connecting and ask one specific question about their setup, like whether they use the free or paid version of the tool.

Add value

Stage
Show you know the nuance
What you want
Send the second piece of advice you promised. Keep it short and tied to their answer.

Offer next step

Stage
Make a meeting feel useful
What you want
Say how you help other teams solve this at scale and ask if they want to see the framework you use.

What to do when they ignore the request

Some people will accept and go quiet. Some will ignore the request. Don't send a second request or a follow-up message that says "just bumping this." That turns a helpful note into a chase.

Wait. Keep engaging with their public posts if you have something useful to add. If they post about the same problem again, you have a natural reason to reply. If they never respond, move on. The list of people posting problems is larger than your time.

Keep the post URL in your notes. When you follow up later, you can reference the exact problem without asking them to repeat it.

  • If they accept but don't reply, send one short message with the resource you promised. No pitch.
  • If they ignore the request, don't withdraw and resend immediately. Comment once more only if you have a real answer.
  • If they say "not now," ask when to check back. Then put a note in your calendar.

Doing this with Kinlead

Finding these posts manually is slow. Kinlead has a Steal Customers agent that watches competitor company pages and optional founder or employee profiles, reads comments on 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.

When you start a campaign, Kinlead can write a connection note under 200 characters that opens with why that person became a lead, referencing their specific comment. You can read and edit queued messages on the Actions page before they send, and replies from every campaign land in one unified inbox.

To see it on your account, book a demo.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? What to say when someone posts a problem on LinkedIn.md