Connecting with leads who posted about a problem
Find prospects posting about pain points on LinkedIn, then send connection requests that quote their own words so more of them get accepted.
Get startedShort answer
Find a post where a prospect describes a specific struggle, then send a connection request that quotes a phrase they used. The quote is the proof you read their words, and it's what separates your request from the automated ones in the same inbox.
Start with problems, not names
Most lead lists start with a job title and a company size. That works when you already know exactly who buys. It fails when your buyer is anyone with a specific headache this week, and LinkedIn is full of people describing those headaches in public, in their own words.
The catch is that a post about a problem is not a buying signal on its own. Someone venting about a spreadsheet has not decided to buy anything. What the post gives you is the exact language they use for the problem, and that language is what makes a connection request read like a person wrote it instead of a sequence.
So the work is two steps. Find the post, then write something only that person could receive. Skipping the second step is why most pain-point prospecting turns into the same generic note with a different name at the top.
- 1
Search for complaint phrasing
LinkedIn search accepts quoted phrases. Try "any recommendations for", "how do you handle", "still fighting with" and "wish there was a better way". Add a category word, so "any recommendations for" plus "payroll", then filter the results to Posts.
- 2
Read the comments, not just the post
The author is one lead. The people replying with "same here" or their own version of the problem are usually two or three more, and they get a fraction of the attention.
- 3
Check the date and the ending
A post from eight months ago may be resolved. Sort by latest and read the last few comments to see whether they found a fix. If they did, you have nothing to offer them.
- 4
Copy the phrase before you do anything else
Paste the sentence you'll reference into your notes. If nothing in the post is worth quoting, skip the lead. There will be another one tomorrow.
If you can't quote a specific sentence from their post, you don't have a reason to connect yet.
Which posts are worth a connection request
Not every complaint deserves a note. Sort them by how close the person is to doing something about the problem, then spend your notes on the ones near the top.
Venting about a tool or a process
- What you see
- Frustration is current, no decision made yet
- What it tells you
- Connect with their phrase and ask what they've tried
Asking for recommendations
- What you see
- They're actively comparing options
- What it tells you
- Connect and ask what they picked. Don't name your product in the note
Sharing a workaround they built
- What you see
- They've invested time and will defend it
- What it tells you
- Skip unless you remove the manual step they built
Announcing a new role or team
- What you see
- New budget and a mandate to change things
- What it tells you
- Connect, reference the post, ask what they're fixing first
Commenting on someone else's problem post
- What you see
- Same pain, lower profile, less competition
- What it tells you
- Often the better lead, since the original poster gets all the pitches
Write the note from their words
A connection note has one job: show that you read the post. Who you are, what you sell and why they should care all wait until they accept.
The shape that works is short. Name the post, quote or paraphrase their phrase, say why it caught you, then stop. No question that demands an answer, no meeting ask, no link.
Notes that get ignored
- Hi Sarah, I help agencies fix their reporting. Would love to connect and share how.
- Saw you're struggling with client onboarding. We solve that for teams like yours. Open to a quick call?
- I'm building a tool for exactly the problem in your post. Let's connect.
Notes written from the post
- Your line about rebuilding the same report every Friday hit home. I've watched three ops people do that this month. Would like to follow what you figure out.
- You asked for invoicing recommendations and got forty replies, most of them from vendors. Curious what you actually picked.
- Your comment about the handoff spreadsheet being held together with tape is the most accurate description I've read. Following along.
Paste this job
Your post about [their exact phrase] is the clearest version of [the problem] I've read this month. [One line about why it caught you]. Would like to connect.
What to do when they accept
Accepting gives you room for one more question. It doesn't give you room to pitch. Ask about the problem. Budget and timeline come later, if at all.
Example
- You
Thanks for connecting. Is the Friday report still eating your afternoon, or did you find a fix?
- Prospect
Still eating it. I tried two plugins and both made the formatting worse.
- You
That's the part nobody warns you about. Is it the data entry that breaks, or the reporting side?
- Prospect
Reporting. Four hours every Friday and it's wrong half the time.
Ask about the problem twice before you mention what you sell. The second answer is where the useful detail lives.
When they ask what you sell straight away
Some people skip the small talk and ask what you do in the first reply. Answer in one sentence and hand the question back. A long explanation here ends more conversations than a short one.
The people who ask early are usually the ones who've been pitched badly before and want to know what they're dealing with. Being brief and specific about the problem you solve is what earns the next reply.
Example
- Prospect
Thanks for connecting. What is it you do exactly?
- You
I build reporting tools for ops teams, mostly the Friday-report problem. What did you end up doing with yours?
- Prospect
Nothing yet. I looked at two options and both wanted a setup call before they'd show me anything.
- You
That's a common complaint. Would a ten minute look at your current sheet be useful, or is this a next-quarter thing?
Keep the list small enough to actually work
The usual failure here is collecting three hundred pain-point posts and messaging nobody. Pick ten a week. Ten notes written from ten real posts beat a hundred templated ones, and you can follow the replies.
- One line per lead: name, the phrase you'll quote, the date of the post, what you sent.
- Set a reminder for four days if they don't accept. If they've posted again since, that's a new reason to connect.
- Drop anyone whose post is older than a month unless they've raised the same problem again.
- Keep a no list. Someone who ignored or declined two notes shouldn't get a third.
Doing this with Kinlead
Kinlead's Steal Customers agent watches competitor company pages and the founder or employee profiles you pick. It reads the comments on their recent posts and turns commenters who look like buyers into leads, keeping the post URL, what the post was about and what they commented. That's the research step without the scrolling.
Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead, so the note starts from the post instead of your job title. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.
You can also describe the customer you want and Kinlead scores each lead from 0 to 100 against that profile, keeping only the ones above your fit line. Leads sit in lead groups, and any campaign can point at any group. The Steal Customers agent page covers the rest.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? Connecting with leads who posted about a problem.md