Next to the Connect button on LinkedIn there is a smaller link most people never touch: Add a note. Skipping it is usually the difference between an invite that sits in someone's pending list for six weeks and one that gets accepted before lunch.
A bare invite asks the other person to do the work. They see your name, your headline, maybe a mutual connection, and then they have to guess. Who is this? Is this a sales thing? Most people answer by doing nothing, and every so often they clear the whole pending list in one go.
A note removes the guesswork. It does not have to be clever. It has to answer one question: why you, why them, why now.
Work inside the character limit, do not fight it
LinkedIn gives you roughly 300 characters for the note. That is two or three sentences. Not a cover letter, not a pitch deck, and definitely not the place for your career history.
Two things to know before you plan a big outreach week. LinkedIn has periodically capped how many personalised invitations a free account can send per month, so check what yours allows before queueing up fifty. And the note gets read on a phone, in a notifications list, between two other things. If your first seven words do not land, nothing after them will.
So structure it tight:
- Line 1 - the connection point. School, employer, event, a post of theirs, a mutual contact.
- Line 2 - why you want to be connected, in plain words.
- Line 3 (optional) - a small, low-pressure opening. No ask attached.
Drop the greeting if you are short on room. "Hi Sarah" costs ten characters a specific detail would use better, and nobody has ever declined an invite for lacking a salutation.
Before any of this, look at your own profile the way they will: they click your name, read your headline, and decide in about two seconds. If it still says "Seeking new opportunities", fix that first with a headline that gives people a reason to click, then run through the profile checklist.
Situation 1: Same school, same programme, same alumni network
This is the easiest note to write, because the connection point is already true and verifiable. Be specific about the overlap. "We went to the same uni" is weak. The department, the year group, or a professor you both had is strong.
Hi Marta - I did the same MSc at Warwick, three intakes after you. I am moving into product analytics and your path from research into product is the one I keep reading about. Would be glad to be connected.
Fellow Leeds engineering grad here. I saw you now lead the reliability team at Monzo - that is the direction I am aiming for from my current ops role. Happy to connect.
Notice what neither note does: ask for coffee, ask for a referral, ask for thirty minutes. The invite is the ask. One ask at a time.
Situation 2: Same employer, or the same corner of the industry
If you overlapped at a company, say when and where, even if you never met. If you did not overlap, say what you have in common instead - the same tooling, the same client type, the same conference circuit.
Hi Tom - I was in the Manchester finance team at Sage until last spring, two floors down from yours. Just joined a smaller SaaS company doing the same job with a tenth of the headcount. Would like to keep in touch with people from that world.
We have never met, but we are both on the unglamorous side of logistics tech - I run warehouse integrations at a 3PL and your posts on WMS migrations are the only ones I actually save. Connecting.
Hi Priya - your team and mine shared the same agency last year and I heard your name on every call. Thought it was overdue that we were actually connected.
The third one only works if it is true. Never invent a shared project. People check.
Situation 3: You met at an event
Send it within 48 hours, while your face is still attached to your name in their memory. Name the event and one thing you actually discussed. If you cannot remember anything, name the event and be honest about it.
Hi Alex - we talked about the pricing panel at SaaStock yesterday, near the coffee stand. You said something about usage-based billing breaking finance teams that I have not stopped thinking about. Good to meet you.
We were on the same table at the Thursday product meetup in Lyon. You are the one who recommended the Teresa Torres book - I bought it on the train home. Connecting so I can tell you whether it helped.
Small, concrete detail beats warmth every time. "Great meeting you, let's stay in touch" reads like it was sent to forty people, because it usually was.
Situation 4: A total stranger whose work you follow
This is where most invites die. No shared history, so the note has to earn the accept on its own. Be specific about the thing of theirs you actually read, then stop.
Hi Nadia - your write-up on migrating off Segment is the reason my team did not spend six weeks building our own pipeline. Reading you regularly at this point, so connecting properly.
I have followed your posts on B2B onboarding since the one about the 14-day trial that nobody finished. I am a PM working on the same problem at a smaller scale. No ask, just would like to be in your network.
Hi Ben - I used your open-source rate limiter in a side project and it survived a weekend of me abusing it. Thank you for that. Connecting.
"No ask, just would like to be in your network" is worth the characters. It defuses the exact suspicion the person is having as they read.
Situation 5: A recruiter or a hiring manager
Here you can be direct, because direct is what they deal in all day. Recruiters read invites as inbound supply, hiring managers as potential interruption. Adjust accordingly.
Hi Chloe - I see you hire backend engineers for the payments team at Qonto. I am a Go developer with five years on payment rails, currently at a company half that size. Open to a conversation whenever one is relevant.
Hi David - you are hiring a senior designer and I am not applying today, I want to understand the team first. I have shipped design systems at two fintechs. Connecting so I can follow what your team puts out.
Recruiter in med device myself, on the client side. I like your posts on candidate experience and disagree with about a third of them, which is the good kind. Connecting.
If a recruiter accepts, do not paste your CV into the chat. The first message after the accept is a separate skill, and there are scripts that beat improvising. Approaching your would-be manager has its own rules.
What gets you ignored, deleted, or reported
Four patterns show up again and again in the invites people complain about publicly.
The mass-blast tone. "I would like to add you to my professional network" is the default text from a decade ago. Anything that could be sent unchanged to any human being reads as automation, and automation gets cleared in batches.
The instant pitch. The note says hello, the message thirty seconds after the accept says "quick question - are you the right person for procurement decisions?" People remember that. Some of them report it. A connection request is not a sales sequence step, even when you are selling.
Flattery with nothing behind it. "Love your content, so inspiring, your insights are incredible." If you cannot name one specific thing they published, you did not read it, and they can tell. Specific praise is generous. Generic praise is a tell.
The pre-loaded favour. Asking for a referral, an introduction, or a call inside the note itself. You are asking a stranger for a favour before they have agreed to know you. Get the accept first, then read how to ask for a referral without making it awkward.
There is a slower failure too: twenty invites a day to people with nothing in common with you. It works for nobody, and it makes your profile look like a bot to anyone who checks.
Once it is accepted, the follow-up
You got the accept. The temptation is to cash it in immediately. Do not.
The first message after acceptance should do one of three things: say thank you and close, give them something, or ask a question so small that answering it costs nothing.
Thanks for connecting, Marta. Nothing needed - I will just be reading. If I come across anything useful on the research-to-product jump I will send it your way.
Thanks Tom. One thing I have been curious about since I left: did the team ever move off the old reporting stack, or is that still running? Genuinely just curious.
Appreciate the connect, Nadia. Since you mentioned warehouse events in that post - we hit the same issue and solved it with a queue in front. Happy to share the write-up if it is useful.
Then leave them alone. Comment on their posts when you have something real to add. Three or four weeks later, when you actually have a request, you are not a stranger - you are the person who asked a decent question and then did not pester them.
That gap between connecting and asking is where most people rush. If the pacing feels unnatural, the wider version of this problem is worth reading about.
Before you hit send
Read it once and check three things. Is there a detail that could only apply to this person? Have you removed every request? Would you accept it from someone you had never heard of?
Three yeses, send it. Otherwise you are about ninety seconds of editing away from a note that works.