Rodok
Abderrazzak AbouyaalaWhat this signal is
A pain point post is a public post where someone describes a problem your product solves: "We spent three days rebuilding our pipeline report again" or "200 applications and no way to sort them." It's a buying signal because the person has named the problem in their own words, the hardest part of any first conversation.
It sits between a vague interest and a recommendation request. The person feels the problem, but hasn't necessarily decided to buy anything. Our guide to buying signals lists it among the people signals worth tracking.
Why it predicts a purchase
People post about problems that bother them enough to talk about in public. That usually means the problem is recurring, it costs them time, and they suspect others have solved it. Some of these posts are venting; many are a quiet way of asking for help.
The post also gives you the language for your message. You don't have to guess which pain matters to this person: they told you, with numbers and context. That makes the first message easier to write and harder to ignore.
It's medium intent, not high, because feeling a problem and having budget to fix it are different things. Some posters are individual contributors with no say over tools. Others are leaders who will act within weeks. Check who's posting before you treat it as a deal.
How to spot it
- LinkedIn: search posts for the phrases your customers use when they describe the problem, not the name of your category. Nobody posts "we need sales intelligence"; they post "spent all morning looking for who to call." Your sales call notes are the best source of these phrases.
- Job posts: a role description that lists the problem ("clean up our messy CRM data") is the company-level version of the same signal.
- News: rarely, though trade press interviews sometimes quote a leader describing an operational problem.
- Your own data: replies and call notes where prospects described the problem. Reuse their words as search terms.
How to act on it
Reply within a few days while the post is still active. Start in the comments if you have something genuinely useful to add: a tip, a question, a pattern you've seen. Then send a short direct message or email that references the post and offers one idea, not a demo.
Contact the poster if they own the problem. If they're an individual contributor, they can still be your way in: ask who handles that decision, or look up their manager and mention that the team is feeling this.
A first message
Hi Claire, your post about sorting 200 applications for one role stuck with me. That's a common pattern when a team grows faster than its hiring process. A couple of things that tend to help: a short screening question up front, and a shared scorecard. We build tools for exactly this, so I'm biased, but happy to share what's worked for teams your size.
A 3-step follow-up
| Day | Channel | What to send |
|---|---|---|
| 1 | A helpful comment on the post with one concrete tip | |
| 2 | The first message above | |
| 9 | A short example of how a team can fix that exact problem, and a 15-minute offer |
Mistakes to avoid
- Pouncing in the comments with a pitch. People notice, and so does everyone who reads the thread.
- Searching for your category's jargon. Search for the words people use when they're annoyed.
- Ignoring seniority. An intern's frustration is real, but it isn't a budget.
- Quoting the post back word for word. Reference it; don't make them feel watched.
- Treating venting as urgency. Some people just needed to vent. Offer help and let them decide.
Frequently asked questions
How do I find posts about the problem I solve?
Collect the exact phrases prospects use on calls and in replies, then search LinkedIn posts for them, sorted by latest. Run the searches on a schedule so you see new posts within days, not weeks.
Is it okay to message someone because of a complaint they posted?
Yes, if you're helpful and brief. Lead with an idea or a question, say who you are, and don't pretend you stumbled on them by chance.
How is this different from a recommendation request?
A recommendation request says "I'm looking to buy." A pain point post says "this hurts." The first is higher intent; the second is earlier, which means less competition if you reach out well.
What if the person who posted can't buy?
Ask who owns the decision, or find their manager. Mentioning that their team is struggling with a specific problem is a strong reason for the manager to talk.
