How to find leads using company reviews on LinkedIn
Find B2B leads by reading employee feedback and comments on competitor company pages to spot specific, real internal pain points that point to a buyer.
Get startedShort answer
Monitor comments on competitor company pages or the Life tab where staff discuss internal friction. Identify specific complaints about tools or processes, find the manager in that department, and reach out with a solution to that problem.
Spotting the pain in company feeds
LinkedIn does not have a review section the way job sites do. Employees and former staff still leave honest feedback in the comments of official posts, especially on posts about product changes, hiring, or a busy week. Those comments can show where a competitor's product or a company's process is failing.
Look for friction signals. A friction signal is a comment where someone describes a task that takes too long, a tool that gets in the way, or a step they wish did not exist. Public complaints are useful because the person has already decided the problem is worth mentioning. You do not need a dramatic story. A short line about a weekly report or a slow approval is enough to start.
The Life tab is worth a look because the content is less polished. Staff post about training, team rituals, and the tools they use. The comments under those posts often carry the real detail. A post about a busy quarter can turn into a thread about manual reporting or a backlog in support.
- 1
Visit a competitor page
Go to the page of a company that sells a product similar to yours or operates in your target niche.
- 2
Filter for recent posts
Click the Posts tab and sort by Recent. Look for posts about product launches, company milestones, or day in the life content.
- 3
Scan the comments
Read the replies for phrases like too slow, wish this worked better, or still waiting for this feature.
- 4
Check the life tab
Visit the Life tab to see content shared by employees. Staff often post about their daily workflow, and these comments are usually less curated.
Qualifying the complaint
Most comments are noise. A complaint about office coffee or a CEO's motivational post tells you nothing about a buying problem. Skip anything that does not connect to the work your product supports.
A qualified complaint has a subject and a cost. It names a tool, a handoff, a deadline, or a repeated task. It also hints at who feels the cost: a rep who cannot get clean lead data, a recruiter waiting on onboarding paperwork, or an engineer stuck in a slow release process. If you can map the comment to a problem you solve, keep it. If you have to stretch, drop it.
Recency matters. A comment from two years ago may describe a process that has changed. Check the date and look at the person's current role. If they have moved to another company, the pain may still be useful as background, but the lead is colder. Start with comments from the last few months and current employees.
Noise (ignore)
- The management here is totally out of touch.
- I'm so tired of these corporate culture posts.
- Pay is not competitive for this role.
Signals (target)
- The CRM takes ten clicks just to log a single call.
- It takes three weeks to get a contract approved by legal.
- I wish we could automate this weekly report instead of doing it in a spreadsheet.
Mapping the complaint to a buyer
The person who complained is usually not the person who signs the contract. A junior analyst can describe a reporting mess, but the budget often sits with a manager or director. Use the comment as evidence of a team problem, then find the person who owns that team's process.
Search the company page for people with titles that match the work. If the complaint is about reporting, look for analytics, operations, or finance leaders. If it is about hiring, look for talent or people operations. Read their recent posts and profile summary to see what they care about. You want a reason to write that goes beyond the fact that you found them on LinkedIn.
Keep a short list of roles for each problem you sell against. That list stops you from guessing every time. It also helps you decide when a comment is not worth pursuing because you cannot find a plausible buyer.
Junior developer
- Who complained
- Slow deployment cycles
- The pain point
- VP of Engineering
Sales rep
- Who complained
- Poor lead quality
- The pain point
- Head of demand gen
Recruiter
- Who complained
- Clunky onboarding process
- The pain point
- HR director
The pain-first outreach script
When you message the decision-maker, do not sound like you have been reading their employees' comments for sport. Mention the theme, not the person. A line like 'I saw a discussion on your page about reporting delays' is enough. It shows you paid attention without putting anyone on the spot.
Keep the first message short. Name the friction, explain the common cause in one sentence, and ask for a small next step. Do not list every feature. The goal is a reply. Save the full pitch for the call. If the manager asks how you found them, be direct. Say you watch public conversations in their space and the comment matched a problem you hear about often.
Example
- You
Hi Sarah, I saw a discussion on your company page about how slow the current reporting process is for the team. Usually, that happens because data is siloed across three different tools. I built a way to consolidate that into one view. Worth a look?
- Prospect
I didn't know people were complaining about that publicly. We do struggle with the reporting. How does your tool handle the integration?
- You
It pulls from your existing systems so there's no manual upload. I can show you a 5-minute demo of how it works for teams your size. Does Thursday work?
Never name the specific employee who complained. It puts them in a bad spot with their boss and makes you look like a spy.
Turning one comment into a weekly lead list
One comment is a lead. Ten comments across a few competitor pages are a list. Set a weekly habit: open the pages you care about, scan recent posts, and log the comments that match your problem. Do this on the same day each week so it does not turn into a random scroll.
Keep the note short enough that you can use it later. You need the company, the person, the post link, the problem in their words, and the role you plan to contact. That is enough to write a relevant message without rereading the whole thread.
Do not collect every complaint. A list of twenty weak comments is harder to use than a list of five clear ones. Pick the comments that point to a process, a tool, or a delay you can speak about with confidence.
- Company and page where you found the comment
- Person who commented and their role
- Post link and a short note on what the post was about
- The problem in their words, not your summary
- The manager or director you plan to contact
Paste this job
Company: Acme Person: Priya Shah, sales operations Post: Q3 pipeline review Comment: We still build the forecast in a spreadsheet every Friday Buyer to contact: Head of revenue operations
Doing this with Kinlead
Watching competitor pages by hand takes time. Kinlead's Steal Customers agent watches competitor company pages and optional founder or employee profiles. It 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, so you can open with the exact issue.
Outreach runs from your own LinkedIn account through Unipile, a third-party LinkedIn provider. You can set daily invite and message limits and a send window in the lead's time zone. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.
- Kinlead keeps leads in lead groups, and any campaign can point at any group.
- You can read and edit queued campaign messages on the Actions page before they send, and you can pause any campaign.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to find leads using company reviews on LinkedIn.md