LinkedIn Outreach · Practical guide · LinkedIn sales messaging
LinkedIn sales message examples: connection requests, first DMs, and follow-ups
A connection note, a first DM, and a follow-up should not repeat the same pitch. Use the connection note to explain why you want to connect, the first DM to find out whether the problem is a current priority, and a final follow-up to offer one optional next step.
Key takeaways
- Give each message one job: establish context, check relevance, or offer a next step.
- Kachilu keeps connection requests short and free of pitches, CTAs, and URLs; it uses no more than one verified profile fact.
- Kachilu schedules reply checks on days one and three after the first DM and sends a short follow-up with the configured CTA URL only at the final no-response check.
- Kachilu's beta result measures next-step progression across the whole workflow. It does not isolate connection acceptance, reply rate, or follow-up lift.
Written by
Kachilu Research
Product research and editorial team
Give each LinkedIn sales message one job
These examples assume you have selected a relevant prospect and have a real reason to contact them. Use them as adaptable LinkedIn message templates, not copy-and-paste scripts. If you need the wider process—from search and qualification to the first conversation—start with the founder workflow linked below. A well-written message cannot make up for weak targeting.
| Stage | Job of the message | Useful input | Leave out |
|---|---|---|---|
| Connection request | Explain why connecting makes sense | One verified post, role, or company fact | Product pitch, CTA, URL |
| First DM after acceptance | Find out whether the problem is a current priority | The same context, one service benefit, one easy question | Long feature list or forced meeting request |
| Final no-response follow-up | Offer one optional next step and close the loop | One relevant benefit, a short reminder, and the configured CTA URL | Repeated nudges or artificial urgency |
- LinkedIn prospecting for founders: from search to the first DM
The broader workflow for selecting prospects and creating context before these messages begin.
Connection request examples: explain the reason, not the product
A connection request should help the recipient answer one question: why does this person want to connect with me? Kachilu drafts a natural, short note, uses at most one verified fact from the profile, and excludes the product pitch, CTA, and URL.
When a post created the context
Your post about [specific topic] was useful, especially the point about [one verified detail]. I work on a related problem and would be glad to stay connected.
When the person's role created the context
I saw that you lead [verified responsibility] at [company]. I work with [relevant team type] on the same issue, so I thought it would be useful to connect.
- Replace every bracketed field with a fact you have checked.
- Use one detail, not a compressed biography assembled from the profile.
- Remove the sentence if it would still work unchanged for almost anyone.
- Do not add a calendar link, product page, or request for a meeting.
- LinkedIn Help: Personalize invitations to connect
LinkedIn's current help page for adding a personal message to an invitation.
First LinkedIn DM examples: check whether the problem is a priority
After acceptance, Kachilu uses an approved template as the structure rather than inventing a new sales script for every prospect. The draft uses two or three short paragraphs: one verified profile fact, one sentence connecting the service to a benefit, and one easy-to-answer question. It does not include a URL.
Ask whether the problem is current
Thanks for connecting. Your point about [verified topic] stood out because [specific reason]. We help [team type] reduce the work involved in [relevant problem]. Is that something your team is working on this quarter?
Offer something useful before proposing a call
Thanks for accepting. I noticed you are responsible for [verified responsibility] at [company]. We have been testing a way for [relevant team] to [specific benefit]. If [problem] is still taking time, I can share the short workflow we use. No need to reply if it is not relevant right now.
- LinkedIn Help: Send messages to connections
LinkedIn's help page describing messages between first-degree connections.
LinkedIn follow-up message examples: check for a reply before sending
Kachilu schedules conversation checks on days one and three after the first DM. When a reply is positive or neutral, Kachilu responds to the specific point raised. A negative, unrelated, or already answered conversation does not receive the no-response follow-up.
At the first check, no response means no new message. Only at the final no-response check does Kachilu send one short follow-up with the CTA URL configured for the campaign. If execution is delayed past the initial window, the delayed check is handled as the final check. This avoids treating every pause as permission to repeat the pitch.
When the prospect replies positively or neutrally
Thanks—that point about [specific part of the reply] helps. The relevant part for your team is [brief answer]. Would it be useful if I sent [one concrete resource or next step]?
When there is still no reply at the final check
One last note in case [problem] becomes relevant later. The approach can help [relevant team] [one related benefit]. This page explains how it works: [CTA URL]. No action needed if it is not a priority.
- Do not send a follow-up at the first no-response check.
- Do not send the final template after any genuine reply.
- Answer the substance of a positive or neutral reply before proposing the next step.
- End the sequence after a negative or unrelated reply instead of arguing with it.
How Kachilu personalizes messages without changing the approved structure
The product does not treat personalization as permission to invent details. For the connection request and first DM, Kachilu may use one profile fact that has already been verified. The approved template determines the purpose and shape of the message; the verified context determines the detail that changes.
We verified this behavior in Kachilu Desktop on August 25, 2026. Product behavior may change in future releases.
| Decision | Kachilu behavior |
|---|---|
| Connection request | Short, natural wording; up to one verified fact; no pitch, CTA, or URL. |
| First DM | Approved structure; two or three short paragraphs; one verified fact; one benefit sentence; one easy-to-answer question; no URL. |
| Positive or neutral reply | Respond to the specific point in the received message. |
| Initial no response | Record the state and wait; do not send another message. |
| Final no response | Send one short follow-up that restates one relevant benefit and includes the campaign's configured CTA URL. |
| Negative, unrelated, or already replied | Do not send the no-response follow-up. |
What the beta result measures—and what it does not
In Kachilu's beta data, 29% of 35,292 initiated outreach attempts reached the campaign-defined next step. Kachilu Scout, the predecessor product, reached roughly 10% using the same funnel denominator. The observed Kachilu rate was 2.9 times the historical Scout rate. This is an aggregate snapshot through August 19, 2026; the source record does not include a beta start date.
This was a comparison across products and periods, not a controlled experiment. It supports testing an engagement-first sequence, but it does not isolate the connection-request acceptance rate, first-DM reply rate, or incremental effect of the final follow-up. Targeting, offer, account condition, timing, audience, and message quality may also have affected the result.
| Question | Required denominator | What may be reported |
|---|---|---|
| Are connection requests accepted? | Connection requests sent in one cohort | Accepted connections divided by requests sent after a fixed observation window |
| Did the first DM receive a reply? | First DMs delivered to accepted connections | Prospects whose first reply followed the first DM |
| Did follow-up add replies? | Eligible no-response prospects who received the final follow-up | First replies after follow-up; causal lift requires a valid comparison group |
- Kachilu beta report: 35,292 LinkedIn outreach attempts
The result, denominator, workflow comparison, privacy treatment, and limitations.
- How to calculate LinkedIn outreach metrics
Definitions for acceptance, replies, next-step progression, and meeting booking rates.
Review the sequence before sending it
- The connection request contains one checked reason to connect and no sales CTA or URL.
- The first DM uses two or three short paragraphs and asks one answerable question.
- Every profile detail is verified; no familiarity, event, or business problem is invented.
- A positive or neutral reply receives a specific response rather than a scheduled template.
- No message is sent at the first no-response check; only the final check may include the configured CTA URL.
- Negative, unrelated, and already answered conversations are removed from the no-response path.
- Acceptance, reply, and next-step metrics keep separate denominators and fixed observation windows.
FAQ
Frequently asked questions
Should a LinkedIn connection request include a product pitch?
No. Use the request to explain the real reason for connecting. Save the service explanation for the first DM after acceptance, where the recipient has enough context to evaluate it.
When does Kachilu send a follow-up message?
Kachilu schedules checks on days one and three after the first DM. It sends nothing at the initial no-response check. If there is still no reply at the final check, it may send one short follow-up that restates a relevant benefit and includes the campaign's configured CTA URL. If execution is delayed past the initial window, the delayed check is handled as final. Negative, unrelated, or already answered conversations do not receive that follow-up.
What should the first LinkedIn sales message say after someone accepts?
Use one verified detail to show why you reached out, connect your service to one relevant benefit, and ask one easy-to-answer question. Keep it to two or three short paragraphs and leave the URL out.
Does the 29% beta result prove that these messages increase replies?
No. The 29% figure is next-step progression across the full Kachilu workflow. The comparison does not isolate connection acceptance, first-DM replies, or follow-up lift, and it was not a controlled experiment.