LinkedIn gives you 300 characters to convince a stranger to let you into their network. That's about two sentences. Most people use those two sentences to talk about themselves. That's why most connection requests get ignored.
The requests that get accepted have one thing in common: they're about the other person. They reference something specific. They feel like a human wrote them. And they don't ask for anything.
Here's how to write them.
Why 90% of connection requests fail
Open your LinkedIn right now and look at your pending requests. You'll see the same patterns over and over:
- "Hi [Name], I'd love to connect and explore synergies between our companies."
- "I came across your profile and thought we could benefit from connecting."
- "I help companies like yours achieve [vague outcome]. Would love to connect."
These all fail for the same reason. They could be sent to literally anyone. There's nothing in the message that proves the sender knows anything about the recipient. It's a template. The recipient knows it's a template. And they click ignore.
The bar for getting accepted is lower than you think. You just have to prove you're a real person who spent 30 seconds looking at their profile.
The 300-character advantage
Most founders see the 300-character limit as a constraint. It's actually a gift.
300 characters forces you to be specific. You can't fit a pitch in 300 characters. You can't fit your company's value proposition. You can't fit "I'd love to schedule a call to discuss how we might..." That's all too long. So you're forced to write something short, direct, and human.
The best connection requests are 2 sentences. One about them. One about why you want to connect. That's it.
3 templates that get 50%+ acceptance rates
Template 1: The post reference
This is the highest-converting template. You reference something they actually posted on LinkedIn.
[Name], saw your post about [specific topic]. Been
thinking about the same thing from the [your angle]
side. Would love to follow your work.Why it works: it proves you actually read something they wrote. That alone puts you in the top 5% of connection requests they receive. The "would love to follow your work" is a genuine reason to connect that asks for nothing.
Where to find posts: go to their profile, click "Activity," and look at their recent posts or comments. Even a comment they left on someone else's post works. You just need one specific thing to reference.
Template 2: The company signal
Use this when you noticed something happening at their company but couldn't find a specific post from the person.
[Name], saw that [Company] [specific signal: raised
funding / launched a new product / is hiring for X].
A few [their role type]s I know are navigating similar
things. Looking forward to connecting.Why it works: it references a real event, not a job title filter. "Saw that Acme just raised a Series A" is specific and timely. It shows you're paying attention to their company, not just adding names from a database.
Template 3: The mutual context
Use this when you share something in common: a group, an event, a mutual connection, an industry.
[Name], noticed we're both in [group/space/industry].
Your work on [specific thing] caught my attention.
Would be great to connect.Why it works: shared context creates instant trust. Being in the same LinkedIn group, attending the same event, or working in the same niche gives the recipient a reason to say yes beyond just your message.
What to never say in a connection request
Some phrases are instant rejection triggers. Avoid these:
- "I'd love to connect" without any reason why. This is the default LinkedIn text. It signals zero effort.
- "I help companies like yours..." This is a pitch disguised as a connection request. Everyone sees through it.
- "Let's explore synergies" or any corporate buzzword. It sounds like a bot wrote it because a bot probably did.
- Your job title and company description. They can see your profile. You don't need to introduce yourself in 300 characters.
- A meeting request. "Would love to grab 15 minutes" in a connection request from a stranger is way too aggressive. Save that for after they accept and you've had a conversation.
The simplest test: read your connection request and ask "could this be sent to 100 other people by swapping the name?" If yes, rewrite it.
The 2-minute workflow for every request
- Visit their profile. 10 seconds.
- Check their recent activity. Look at posts, comments, articles. 20 seconds.
- Pick one specific thing. A post topic, a company event, a shared group. 10 seconds.
- Write 2 sentences. Reference the specific thing. Say why you want to connect. 30 seconds.
- Send it. 5 seconds.
Total: under 2 minutes per request. At 10 requests per day, that's 20 minutes. And your acceptance rate will be 2x to 3x higher than someone blasting generic requests from an automation tool.
The math works out. 10 personalized requests at 50% acceptance = 5 new connections per day = 25 per week = 100 per month. That's 100 people in your network who accepted because you said something real, not because they accidentally clicked the wrong button.
Those are the connections that turn into conversations. And conversations turn into customers.