LinkedIn · 2026-07-10 · 9 min
What a Good First Message Actually Looks Like
Most LinkedIn first messages fail before the second line because they ask for something before they have earned the right to. Here is the anatomy of a first message that actually gets a reply.
Open your own LinkedIn inbox and look at the last ten cold connection requests you accepted. Read the first message that followed. Most of them will do one of two things: pitch immediately, or compliment your profile in a way that is clearly automated. Neither earns a reply, and both are the reason so many founders have decided LinkedIn outbound does not work, when what actually failed was the message.
A good first message is not clever. It is specific, short, and asks for almost nothing. That combination is rarer than it sounds, because most of the pressure in outbound pushes the other way: say more, sell harder, ask for the meeting now. Understanding why that pressure is wrong is most of the job.
The job of the first message
The first message has exactly one job: earn a reply that is not "no thanks". It is not there to explain your product, list your features, or make the case for a meeting. If it tries to do all of that, it usually does none of it, because the reader has decided within two lines whether this is worth their next thirty seconds.
Everything else, the pitch, the proof, the ask, comes later in the conversation, once the person has actually engaged. Trying to compress a full sales pitch into a first message is a common instinct and almost always the wrong one, because it treats a stranger's inbox like a landing page instead of a conversation.
Anatomy of a message that works
A first message that lands well has four parts, in this order, and rarely runs past four or five short sentences.
- A specific, verifiable observation about them or their company. Not "I saw your profile", which could be true of anyone. Something that proves you looked: a product launch, a role change, a specific piece of content they published, a technical detail about how their product works.
- Why that observation is relevant to you reaching out. One sentence connecting what you noticed to the reason you are writing, without yet naming your product.
- A soft, low-commitment question. Not "can we book 15 minutes", which asks for calendar time from a stranger. Something that only takes a sentence to answer, like whether a particular problem is something they are currently dealing with.
- Nothing else. No signature block, no three bullet points of features, no attachment.
Example: what not to send
"Hi [Name], I came across your profile and was impressed by your work at [Company]. We help companies like yours increase revenue through our AI-powered platform. Would you be open to a quick 15-minute call this week to explore how we could help you achieve your goals?"
This fails on every count. The observation is generic enough to apply to anyone. The pitch arrives in sentence two. The ask is a calendar commitment from someone who has never heard of you, before they have any reason to trust that the call would be worth their time.
Example: what we would send instead
"Hi [Name], noticed [Company] moved from [old approach] to [new approach] on the engineering blog last month. We work with a few teams that made a similar switch and ran into the same integration gap around [specific detail]. Is that something you are still working through, or did it get resolved internally?"
This is specific enough that it could only have been written for this person. It names something real, connects it to a reason for writing, and asks a question that takes ten seconds to answer either way, with no pressure attached to either answer.
Length is a signal, not just a constraint
A short first message signals that you respect the reader's time and that you did the work before writing rather than after. A long first message signals the opposite, regardless of how good the writing is, because length itself reads as effort spent on you rather than on them.
Three to five sentences is the practical ceiling for a first message. If you find yourself needing more space, that is usually a sign you are trying to pitch too early rather than open a conversation, and the fix is to cut the pitch, not to trim the sentences.
Tone: write like a person, not a brand
The words "leverage", "solutions", "synergy" and "game-changing" all signal template. So does starting with "I hope this message finds you well", a phrase nobody uses in a real conversation with a stranger they are trying to interest. Write the message the way you would actually say it out loud to someone at an event, then cut anything that would sound strange said aloud.
This test catches more problems than any style guide. Most people can tell within a second whether a sentence sounds like something a colleague would actually say or something that came out of a template, and readers apply the same instinct to your messages whether they say so or not.
The connection note is not the first message
Keep the connection request note, if you send one at all, even shorter than the first message, one line at most, or leave it blank and send the real message once they have accepted. A connection note crammed with a pitch reads as desperate before the relationship has even started, and it often costs you the acceptance entirely, which means the first message never gets read at all.
What "good" looks like in aggregate
Across a well-run campaign, a healthy first-message reply rate is a modest but real share of the people contacted, not because the offer is irresistible but because the message respected the reader enough to be worth thirty seconds. If your reply rate is close to zero across a reasonable sample, the fix is almost never volume. It is almost always the first four sentences, and specifically whether they read as written for one person or for a thousand. If you want to see this applied at scale rather than one message at a time, that is the entire premise behind how we run campaigns, and it is the same reasoning behind the results we describe in our case studies.
Next: pull up the last twenty first messages your team sent and count how many contain a detail that could only apply to that one recipient. If it is fewer than half, that is where to start.