How to find leads in the comments of company page posts
Watch competitor company pages, read the comments, spot buyers asking real questions, and send a connection request that mentions what they wrote.
Get startedShort answer
Watch the company pages of competitors and adjacent tools, then read the comments on posts about price changes, deprecations and new limits. The people asking detailed questions there are working through a live decision. Check their role, then send a short note that quotes what they wrote.
Pick company pages where buyers actually talk
Any company page with an active comment section can produce leads, but only a few are worth your week. Test each one the same way. Open the last ten posts and read the replies. If the comments come from employees, from people dropping their own links, or from nobody at all, close the tab.
The pages that work have customers in the comments asking how something works, complaining about a limit, or comparing the product to a rival. Those people have a live problem and often a budget behind it. A page where buyers argue about tooling is worth more than a page with ten thousand followers and no replies.
Start with four to six pages and stop there. A short list you read properly beats a spreadsheet of forty pages you never open. Add a page when one goes quiet, and drop the ones that only produce congratulations threads.
If you are not sure where to start, list the companies you lost deals to in the past year, plus the two tools your buyers already use every day. Those pages are where your buyers hang out. A busy page from a company in a different market can look promising and still give you nothing.
Direct competitor
- Page type
- Their users already pay for the job you do
- Why buyers show up
- Feature requests, pricing complaints, migration questions
Adjacent tool
- Page type
- Their customers pair it with something like yours
- Why buyers show up
- Integration questions, gaps in the workflow
Industry publication
- Page type
- A wide mix of buyers read the same posts
- Why buyers show up
- Arguments about standards, tooling choices and budgets
Company you lost a deal to
- Page type
- You already know the buyer profile
- Why buyers show up
- The same objections you heard on the sales call
Filter for posts that force a reaction
Most company posts are announcements nobody reads. The ones that matter share a shape: something changed, and the people who use the product have an opinion about it. A price increase, a deprecated feature, a new limit on an API, a policy change. Anything that makes a customer recalculate.
Read those comment sections properly. You are looking for questions with detail in them, like whether a change applies to annual contracts, rather than one-word reactions. Detail means the person is working through a real decision.
A launch post is not the same as a change post. A launch says we built something new and invites applause. A change post tells existing customers that something they rely on is different. The second one produces the comments you want.
- 1
Open the posts tab and scroll back
Give yourself a month of history. Older posts still hold useful comments and the people in them are usually in the same job.
- 2
Read the posts about change
Pricing, packaging, deprecations, new limits, policy updates. Skip launch hype unless the comments complain about it.
- 3
Weigh comment count over likes
A post with twelve real questions beats one with two hundred likes. Likes tell you nothing about intent.
- 4
Copy the comment and the post URL
You need both when you write the note. Nothing kills a message faster than misquoting what someone said.
- 5
Ignore the noise
Employees saying congrats, vendors pitching their own tool, anyone who only wrote great news. None of them are buyers.
Do this once a week per page, not every day. A weekly pass over five pages takes about half an hour and hands you a batch of people to work through.
Check that the commenter can buy
A comment tells you a problem exists. It does not tell you the person can sign anything. A junior developer complaining about export limits is proof the pain is real, and also not the person who approves a new vendor.
Open the profile and read three things: title, company size, and whether their role touches the budget. A head of engineering at a 60-person company usually decides. A staff engineer at a 5,000-person company usually influences. Both are worth a message, but the second one needs a different message.
Then read the comment again. Someone weighing options writes differently from someone venting. A line like we are evaluating alternatives is a buying signal. A line like this is such a joke is a mood.
One shortcut worth using: check whether the person has commented on more than one post from the same competitor. Two comments in a month is a pattern, and a pattern means they are shopping.
Signals to skip
- Generic praise like great post
- Other vendors pitching their own tools
- Employees of the company page
- Someone asking for a free trial with no company on their profile
Signals worth a message
- A specific question about how a feature works
- A complaint about a limit your product does not have
- A title that matches the person you usually sell to
- A question about pricing or contract terms
Write a note that quotes their comment
The note has room for one idea. Name the post, say what they wrote, and ask a question that continues the conversation. Do not describe your product. That comes after they accept.
Keep it short. Under 200 characters is the limit on a LinkedIn connection request, and the good ones land closer to 150. Cut the adjectives, keep the detail from their comment, and end with a question.
If they accept and stay quiet, send a message that picks up the same thread. Ask what they ended up doing about the problem they mentioned.
Example
- You
Hi Sarah, saw your comment on Acme's post about the new API limits. You asked whether bulk exports still work on the annual plan. Did you get an answer?
- Prospect
Not a useful one. We are pulling data in smaller batches now and it is painful.
- You
That is the same workaround most teams start with. Is the export limit the main reason you are looking at alternatives, or is there something else on the list?
A connection note that would work pasted under any random post is too generic. If it does not name the post and the point they raised, rewrite it.
Keep the pace inside what your account can handle
LinkedIn does not publish exact numbers for invites, messages or profile views, and anyone quoting a precise daily limit is guessing. The limits also shift with account age, acceptance history and how many people report your messages.
What you control is the shape of the activity. Keep the number of pending invitations small enough that you can withdraw the ones that go stale. Send inside a window that matches the lead's working hours. Write each note by hand for the first month so you learn what gets accepted.
Twenty focused minutes on two pages beats two hundred invites fired off on a Monday. Anyone who has watched an account get restricted will tell you the same thing.
- How many invitations are still pending, and how old the oldest one is.
- Your acceptance rate for the past two weeks, not for all time.
- Whether someone replied and you missed it, which is the expensive mistake of the three.
If a note only makes sense when you send it a hundred times, it reads like volume. Rewrite it until it reads like one person writing to another.
Handle the reply like a person
The first reply decides whether this becomes a conversation or a dead thread. Answer the thing they asked about in their comment before you mention a meeting. If they asked whether bulk export is possible, answer that question.
Then ask for a specific slot. Skip let me know when works. A day and a time gives them something to accept or move.
If the reply is a no, take it. Thank them, ask what would have made it a yes, and move on. That answer is worth more than another fifty connection requests and it costs you one message.
Log the reply somewhere you will look again: name, the post, what they said, the next step. If two weeks pass with no answer, one short follow-up is fine. After that, leave it.
Paste this job
Hi {{first_name}}, thanks for accepting. You mentioned on Acme's post that bulk exports were the sticking point. Teams in that spot usually end up pulling data on a schedule instead of on demand. Have you looked at that? I have 20 minutes on Thursday at 10 or Friday at 2 if it is easier to talk it through.Doing this with Kinlead
The Steal Customers agent watches competitor company pages and optional founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads, and each lead keeps the post URL, what the post was about and what the person wrote. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead, and replies from every campaign land in one inbox. The workflow is described on the Steal Customers page.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to find leads in the comments of company page posts.md