# How to find buyers in professional group threads
> How to find buyers in LinkedIn group threads: which posts signal real intent, how to check the person can actually buy, and what to send first.
- HTML: https://getkinlead.com/find-leads-via-professional-group-discussions
- Markdown: https://getkinlead.com/find-leads-via-professional-group-discussions.md

**Short answer:** To find buyers in LinkedIn group threads, look for posts where someone describes a problem your product solves or asks for a recommendation. Check the person's role and company size before you spend a connection request, then open with the sentence they wrote.

## Start with threads where someone describes a problem

Most of what happens in a LinkedIn group is people sharing articles and thanking each other for sharing articles. None of that is a lead. The posts worth your time are the ones where someone describes something broken in their week and asks how other people handle it.

A request for a recommendation is the strongest signal you'll find in a group. The person has already decided the problem is worth money and is now choosing a tool. A complaint with no question is weaker, but it still tells you what to ask about when you get in touch.

Sort by recent. A thread from eight months ago has been solved, or the person has moved on. You want something from the last week or two, while the problem is still costing them time.

To find groups worth watching, search LinkedIn for the words your buyers use, not your product category. "RevOps" and "agency owners" surface different rooms than "sales automation". Check the newest post before you join. A group whose last post is from a year ago is a dead room.

**Skip these**

- Excited to share that I've joined Northwind as Head of Growth.
- Great piece on the state of B2B buying, thanks for sharing.
- Does anyone have a template for a quarterly business review?

**Reply to these**

- Does anyone know a tool that handles multi-currency invoicing without manual exports?
- Our CRM falls over every time we upload more than 500 leads. What are people using instead?
- How are you tracking which LinkedIn ads turn into pipeline? Ours is a mess.

> The template request is the trap. Someone asking for a template wants a free document. Someone asking for a tool has budget behind the question.

## Check the person can actually buy

A good thread from someone who can't sign a contract is a conversation, not a lead. Before you spend a connection request, open the profile and answer two questions: do they own this problem, and can they pay for it.

The headline matters more than the job title. "Head of Ops at a 30-person agency" tells you what you need. "Operations" at a company you've never heard of tells you nothing until you open the company page.

1. **Read the headline and the company page.** You want a role that owns the problem and a company size that matches who you sell to. If your product suits teams of 20 to 200, a 4,000-person employer will route you to procurement and you'll lose a month.
2. **Look for a pattern, not a one-off.** Someone who posts about invoicing every few weeks owns that problem. Someone who commented once on a stranger's question is probably just being helpful.
3. **Check when they last posted.** A quiet profile can still be a lead, but the thread you're referencing will feel like old news. Recent activity gives you a reason to write.
4. **Decide what you'd ask them.** If you can't think of a question worth asking, you don't have a lead yet. You have a name.

## Read the replies before you write anything

Group threads get answered fast. Several vendors will have replied within the hour, and one of them may have already given the poster what they needed. If the question is answered, your message arrives as noise.

Read the whole thread and note two things: whether the poster replied to anyone, and the exact words they used. "Our CRM falls over when we upload more than 500 leads" is a hook you can use. "CRM issues" is not.

If the poster replied to a vendor and then went quiet, that's a signal too. It usually means the conversation moved to a direct message or the person got busy. A short, specific question two weeks later is welcome. A pitch is not.

One more thing to check: whether the person asking is the person who has the problem. In larger groups, a junior marketer often posts on behalf of a manager. You can still write, but ask who owns the process before you assume anything.

> Copy the sentence they wrote into your notes word for word. Paraphrasing is how "our CRM falls over at 500 leads" becomes "CRM challenges" and stops working.

## Write a connection request that names the thread

The note that goes with a connection request is under 200 characters. That's enough for one specific sentence. Spend it on the thread they started.

Don't pitch in the note. The goal is a yes to the connection, and the reason for the yes is that you clearly read what they wrote. A useful reply in the thread first makes the note easier, because your name is already next to something helpful.

**Reads like a mailshot**

- Hi Sarah, I help companies 10x their pipeline with AI. Would love to connect and share how.
- Hi Sarah, I saw we're both in Ops Leaders. Let's connect!
- Hi Sarah, I noticed you're a leader in operations. I'd love to add you to my network.

**Reads like a person**

- Hi Sarah, your question in Ops Leaders about scoring leads by hand is one I've answered badly before. Happy to swap notes.
- Hi Sarah, the 500-lead upload crash you mentioned in RevOps Guild, we hit the same wall last year. Curious how you're handling it now.

- **them:** Does anyone know a way to automate lead scoring without spending 10 hours a week in spreadsheets?
- **you:** We scored on job title and company size first, then layered in behaviour once that was stable. Happy to share the scoring sheet if it's useful.
- **draft:** Hi Sarah, saw your question in Ops Leaders about scoring leads without the spreadsheet grind. I've been through that exact mess. Would be good to connect.

## Keep one list of who said what

You'll be watching a handful of groups, and within a week you'll forget which person complained about what. Keep a single list and update it the same day you send the request.

The column that matters is the sentence they wrote, copied exactly. Two weeks later that sentence is the reason you're allowed to message again without starting over.

If two people on your team are doing this, the list also stops you opening the same thread twice and writing the same message to the same person from two accounts.

| | Lead | Where they posted | What they said | Next step |
| --- | --- | --- | --- | --- |
| Priya Raman | RevOps Guild | Our CRM crashes on uploads over 500 leads | Follow up Thursday, ask if they switched |
| Tom Okafor | Ops Leaders | Scoring leads by hand, 10 hours a week | Send the scoring sheet, no pitch |
| Dana Whitfield | SaaS Founders | Churn spikes in month two | Ask what changed after onboarding |

## Follow up with a question instead of a pitch

Most people who accept a connection request don't reply to the first message. That's normal. Send one follow-up with something useful in it: a short answer to their original question, or a question about how they solved it.

Don't send a calendar link in the first few messages. Ask whether the problem is still there. If it is, the meeting is the obvious next step and they'll often suggest it themselves.

When someone does reply, answer within a few hours if you can. Group threads go cold fast, and a reply the next day reads like you weren't that interested.

```
Hi {{first_name}}, you mentioned in {{group}} that {{their_sentence}}. Did you end up fixing it, or is it still on the list?

If it's still there, I can send over the {{thing}} we used. No call needed, just thought it might save you the afternoon.
```

## Doing this with Kinlead

Kinlead doesn't read LinkedIn group threads. The same job, watching a place where buyers describe problems in public, is what the [Steal Customers agent](/features/steal-customers) does on competitor pages. It watches competitor company pages and any founder or employee profiles you add, reads the comments on their 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.

Leads land in [lead groups](/features/lead-groups-and-scoring) and get scored 0 to 100 against the customer you described. Anything below the fit line is dropped, so you're not reading through noise. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.

Outreach runs from your own LinkedIn account at one action every 5 minutes, inside the daily limits and send window you set. Replies from every campaign land in one inbox, classified by intent, and you get an email when someone answers. You can pause any campaign, or read and edit queued messages before they send.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Can I message someone from a group without connecting first?**

Where LinkedIn lets you message a fellow group member directly, the message still lands cold. A connection request that names their thread reads like a reply from a person.

**How many groups should I watch?**

Two or three where your buyers actually post is enough to keep you busy. Joining twenty groups fills your feed with noise and makes the one thread that matters harder to spot.

**What if the thread is old?**

Skip it. A problem from eight months ago has been solved or abandoned. You want something from the last couple of weeks, while it's still costing them time.

**Should I reply in the thread or send a connection request?**

Reply in the thread first if you have something useful to add. It puts your name next to the answer, and the connection request afterwards has context.

**What if they never reply to the connection request?**

Leave it and move to the next thread. One follow-up after they accept is fine. Chasing a pending request reads as pressure.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
