Your competitor's comment section is a lead list

Your competitor's comment section is probably a better lead list than anything you can buy. The people commenting under a competitor's launch post, feature announcement, or demo are telling you, in their own words, what they need, what is missing, and what they are working around. Nobody scraped them. They volunteered.

Chirag Venkatesh on our team wrote the original version of this for r/GrowthHacking. This is the longer method we use at PumpGTM to turn those comments into prospects, plus the mistakes that make people waste the signal.

Why comments beat a purchased list

A database row tells you a title and a company. A comment tells you a moment: the person is looking at a product in your category right now, and they had a question the product did not answer. That is the difference between "might be a buyer someday" and "is evaluating this week".

The catch is that a comment is a signal, not a qualification. Most of this guide is about the gap between the two.

Step 1: Choose discussions with enough detail

Start with competitor posts that explain a specific feature or a concrete use case. They give commenters something specific to question. Feature announcements work too, though many replies will just congratulate the team.

Skip, or skim quickly:

• Funding and hiring announcements. Comments are investors, candidates and well-wishers.
• Generic thought-leadership posts. Comments agree or disagree with an opinion, not with a product.
• Anything older than a few weeks. The moment has passed.

Treat post type as a shortcut, not a rule. A detailed buying question under a broad demo is still worth investigating. The comment matters more than the category you assigned to the post.

Step 2: Record what the person actually needs

Look for three kinds of comment:

1. Integration questions. "Does this work with HubSpot?" tells you their stack and a requirement.
2. Limitations. "Wish it could do X" tells you a gap, maybe one you fill.
3. Workarounds. "We do this in a spreadsheet today" tells you the pain is real and current.

Save the comment URL and enough context to understand it later. Then separate observation from interpretation. Someone asking whether a tool connects to their CRM has told you they care about that integration. They have not told you their budget, their timeline, or that they are unhappy with their current vendor. Write down only what you saw.

Step 3: Check buyer fit before you reach out

Read the person's public profile and their company. A sharp question can come from a consultant, a competitor's employee, a student, or someone at a company far outside your market.

Write one sentence: why this person could own the problem you solve. If you cannot write it honestly, put them in a "maybe" list and move on. A short list where every name has a reason beats a long list you cannot explain. This is the same "relevant because" test we apply in the Supermemory prospecting method.

Step 4: Offer help proportionate to the problem

The first message is not a pitch. It is a reply to what they said.

• If their question has an answer, give it, even if the answer is "the tool you were looking at does that under settings".
• If their current setup can solve the problem, tell them what to try.
• If the conversation reveals a gap your product addresses, explain the connection using their words, not your positioning.

People remember the stranger who answered their question. They ignore the stranger who saw their question and sent a deck. For the reply itself, the rules in how to review an AI-written cold message apply.

Step 5: Keep one record per person and track outcomes by source

The same person often comments under several posts. Keep one prospect record and attach every source to it. Do not count a new lead each time you see a familiar name.

Track which discussions led to real replies and which only looked promising. Over a month, that record tells you where research time pays off, and it is a better guide than engagement counts. A post with 500 comments full of congratulations is worth less than a post with 20 comments and three integration questions.

How PumpGTM does this at scale

Doing this for one competitor post takes an hour. Doing it every week across every competitor and your own posts is a job. PumpGTM watches the posts you point it at, pulls the people who commented, writes the "relevant because" line for each one, drafts the first reply from what they said, and gives you the list to approve before anything is sent from your LinkedIn account. The same play works on your own posts; see turning post engagement into a qualified prospect list.

Questions people asked in the thread

Isn't this creepy? Replying to a public comment with a useful answer is normal internet behaviour. Sending a pitch deck to someone who asked a question is what feels creepy. The difference is entirely in the message.

What if the comment is on a competitor's post and they see me replying? Reply on LinkedIn via a connection request or message, not in the competitor's thread. You are researching in public and talking in private.

How recent does a comment need to be? Within two weeks is ideal. Within a month is fine if the problem is structural. Older than that, treat it as background research.

Does this work for B2C? The research does. Cold outreach usually does not. Be useful in the same thread instead.

If you want the first batch run on your own competitors, start at pumpgtm.com and enter your website.