# How to connect with people in the same LinkedIn workgroup
> Connect with peers in your professional workgroup by using shared technical challenges and industry standards instead of generic networking notes.
- HTML: https://getkinlead.com/connection-requests-for-leads-in-shared-workgroups
- Markdown: https://getkinlead.com/connection-requests-for-leads-in-shared-workgroups.md

**Short answer:** To connect with people in the same professional workgroup, skip the generic networking note. Mention a specific technical challenge, a shared industry standard, or a recent change in your common job function so the person can tell you are a peer.

## Identify your shared professional anchor

Most connection requests read like they were copied from a template. When you target a professional workgroup, you have to prove you belong. You do this with a professional anchor: a specific tool, a regulatory change, or a technical hurdle that only someone in your role would recognize.

A general interest in a field isn't enough. If you're both in marketing, saying you're both marketers is a weak signal. Mentioning a specific shift in how your industry tracks attribution is a strong signal. It shows you're doing the work, not just collecting contacts.

The anchor should create an immediate 'me too' reaction. It moves the conversation from a stranger asking for a favor to a colleague discussing a shared problem. That shift is the whole point. Without it, the note is just another cold ask.

**Generic networking**

- I see we are both in Marketing and I want to expand my network.
- I'm looking to connect with other Project Managers in the area.
- I've been following your profile and would love to stay in touch.

**Professional anchors**

- I see you're also managing the shift to first-party data for your lead gen.
- I'm curious how other PMs are handling the new Jira updates for sprint planning.
- I noticed you're also dealing with the new compliance requirements for the Q3 audit.

## Drafting the connection note

Your note has a small window to make an impression. You don't have room for a long introduction or a pitch. Keep the structure lean: identify the shared role, state the specific observation, and ask a low-pressure question.

Avoid words like 'synergy' or 'opportunity.' Use the language your peers use in private Slack channels or internal meetings. If the industry uses specific jargon for a problem, use it. It acts as a secret handshake that validates you as a peer.

Don't ask for a meeting or a call. Ask for a perspective. People accept invites more often when they feel they're contributing to a professional discussion rather than entering a sales funnel.

Keep the note under 200 characters. That forces you to cut the throat-clearing and get to the shared detail. If you can't fit the anchor and the question, the anchor is too vague.

| | Component | Purpose | Example |
| --- | --- | --- | --- |
| The anchor | Establishes peer status | Fellow DevOps engineer here. |
| The observation | Proves current relevance | I've been struggling with the latest Kubernetes patch. |
| The low-pressure ask | Encourages a reply | Curious if you found a fix or if it's just me. |

```
Hi {{first_name}}, I saw you're also working on {{specific_change}}. We're stuck on {{specific_problem}}. Curious how you're handling {{narrow_question}}.
```

## The workflow for manual outreach

To do this manually, find people who are active in professional discourse. This stops you from wasting invites on dormant profiles.

Search for a combination of a job title and a specific tool or certification. This narrows the field to people who actually use the tools you're discussing. Once you have a list, check for a recent post or a specific certification on their profile to confirm they're current in their practice.

Keep your daily volume sustainable. LinkedIn doesn't publish exact limits, so monitor your own account and stop if you see warnings. Focus on specific notes over bulk sending.

1. **Search by tool and title.** Use the LinkedIn search bar for a job title plus a specific tool, such as 'Account Executive' and 'Salesloft'.
2. **Filter for proximity.** Filter by 'People' and '2nd degree connections' to find those with mutual contacts, which increases trust.
3. **Verify activity.** Visit the profile and check the 'Activity' section to see if they've posted or commented on industry news recently.
4. **Send the peer note.** Send a personalized invite under 200 characters focusing on the shared professional detail you found.

> LinkedIn does not publish exact invite limits. Pick a daily number you can sustain, watch for warnings, and stop when the account pushes back.

## Handling the first response

Once the person accepts, maintain the peer dynamic. If you jump immediately into a sales pitch, you destroy the trust you built with the professional anchor. The first few messages should be about the problem, not your solution.

Ask follow-up questions that let them explain their process. This helps you understand their specific pain points, which you can then use to pivot toward your product or service naturally.

The pivot happens when you link your solution to the specific struggle they just admitted to. This makes the transition feel like a helpful suggestion from a colleague rather than a cold pitch. Wait until they describe a cost or a workaround before you mention what you do.

- **them:** Thanks for connecting. That Kubernetes patch was a mess.
- **you:** It was. I ended up rewriting our health checks. Did you find a workaround or just wait for the next release?
- **them:** Found a script on GitHub that fixed the probe timing.
- **you:** Can you share the link? I'll test it on our staging cluster.
- **them:** Sent it over. Curious what you're running.
- **you:** Three clusters on EKS. The probe timing issue hit us after the last upgrade.

## What to do when they don't reply

Silence after an accepted invite is normal. People accept on their phone and forget. Don't send a second pitch. Send a new observation about the same professional problem.

Wait a few days. Then send a short message that adds something useful: a link to a thread, a workaround, or a question about how their team handled the issue. Keep it peer to peer. No 'just bumping this.'

If they still don't reply, leave it. A non-reply is not a rejection of you. It usually means the timing is wrong or the problem isn't urgent. Move on to the next person in the workgroup.

**Weak follow-up**

- Just following up on my last message.
- Did you see my note?
- Bumping this to the top of your inbox.

**Peer follow-up**

- I found the GitHub script you mentioned. It fixed our probe timing on staging.
- Saw your comment on the Kubernetes release thread. Are you still seeing the API gateway issue?
- We ended up using a different health check. Curious if your team hit the same wall.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles, 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.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Kinlead sends at a human pace: each LinkedIn account sends at most one action every 5 minutes, inside the daily invite and message limits you set and inside a send window in the lead's time zone.

Replies from every campaign land in one inbox, classified by intent, with interested replies first. You can see the outreach side at [AI LinkedIn outreach](/features/ai-linkedin-outreach).

## Related

- [Find leads tool](https://getkinlead.com/tools/find-leads.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I send a note with every invitation?**

Yes, when targeting professional workgroups. A note with a specific professional anchor proves you are a peer and increases the chance they will accept.

**How do I avoid looking like a bot when mentioning a shared workgroup?**

Avoid generic praise and 'industry leader' language. Use specific technical terms and mention current, real-world problems that a bot wouldn't know about.

**What happens if they accept but don't reply to my first message?**

Wait a few days and send a follow-up that shares a useful resource or a new observation about the shared professional challenge. Don't ask for a meeting in the follow-up.

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