Practical B2B outreach libraryB2B outreach library outbound

15 LinkedIn message templatesfor better conversations.

Use these templates for connection requests, cold messages, signal-based outreach, follow-ups, referrals, and InMail. Adapt each one around a real reason to reach out—not a mail-merge field.

The short answer

Make every message easy to understand—and easy to answer.

LinkedIn recommends a short, specific note that explains the context, why you want to connect now, and uses a clear, polite tone. A reliable B2B structure has four parts.

01

Context

Why this person, company, or moment?

02

Relevance

What business issue connects that context to your work?

03

Value

What useful idea, resource, or outcome can you offer?

04

Question

Ask for a perspective or permission—not a meeting in the first line.

LinkedIn’s current help page lists a 200-character limit for personalized connection notes. InMail allows a subject up to 200 characters and a body up to 1,900 characters, but more space is not a reason to use it. Read LinkedIn’s invitation guidance.

Copy, then adapt

15 LinkedIn message templates for B2B outreach.

Use the structure, replace every bracket, and remove any sentence you cannot support with real context.

01 · Connection

Simple connection request

Use when: You have a legitimate professional reason to connect, but no strong buying signal yet.

Hi [First name] — I work with [role/team] on [relevant problem]. Your work at [Company] stood out, especially [specific detail]. Open to connecting?

Personalize: Role, problem, and one real detail.

02 · Community

Shared interest or community

Use when: You share a group, event, community, or topic.

Hi [First name] — saw we’re both following [topic/community]. Your point about [specific idea] caught my attention. I’d be glad to connect and compare notes.

Personalize: The shared context and idea.

03 · Engagement

After they engage with your content

Use when: A prospect comments on or meaningfully engages with a relevant post.

Thanks for your take on [topic], [First name]. Your point about [detail] was sharp. We’re seeing something similar with [peer group]. Curious how [Company] is approaching it.

Personalize: The exact comment and a related question.

04 · Company signal

After a relevant company announcement

Use when: The company announces funding, expansion, a product launch, or another event connected to your solution.

Congrats on [announcement], [First name]. That usually creates new pressure around [relevant job]. Is that on your team’s radar this quarter?

Personalize: The announcement and plausible operational consequence.

05 · Role change

New role message

Use when: A target buyer recently started a role.

Congrats on the new role at [Company]. Leaders stepping into [role] often inherit [relevant challenge]. Is that part of your first-90-day focus, or is another priority ahead of it?

Personalize: Role, challenge, and timing.

06 · Hiring

Hiring signal

Use when: The company is hiring for roles that suggest investment in a relevant initiative.

Noticed [Company] is hiring for [role/team]. That often means [initiative] is becoming a priority. Are you already set on the [process/tooling] behind it?

Personalize: The job opening and the initiative it plausibly indicates.

07 · Technology

Technology or workflow signal

Use when: Public evidence suggests the company uses a tool or workflow adjacent to your product.

Saw [Company] is using [tool/workflow]. Teams at that stage often run into [specific gap]. We’ve helped [type of team] handle that with [plain-language outcome]. Worth sharing the approach?

Personalize: Only use verified, non-sensitive evidence.

08 · Cold outreach

Problem-led cold message

Use when: The prospect fits your ICP, but you lack a timely event.

Hi [First name] — I’m speaking with [peer role] teams that are trying to [goal] without [common cost or bottleneck]. Is [problem] something you own at [Company]?

Personalize: Peer group, goal, and ownership question.

09 · Value first

Useful resource

Use when: You can offer a genuinely relevant checklist, benchmark, teardown, or example.

[First name], we put together a short [resource] for [peer group] working on [job]. Your team came to mind because of [specific context]. Want me to send it?

Personalize: Resource, audience, and reason it fits.

10 · Referral

Warm referral

Use when: A mutual contact has given permission to mention them.

Hi [First name] — [Mutual contact] suggested I reach out because you’re working on [initiative]. We help [peer group] with [outcome]. Open to comparing notes?

Personalize: Never name-drop without permission.

11 · Accepted

First message after acceptance

Use when: The prospect accepted your request but has not started a conversation.

Thanks for connecting, [First name]. The reason I reached out: [specific context] made me think [relevant problem] may be timely. Am I reading that correctly?

Personalize: Restate the real reason, not your product pitch.

12 · Follow-up

Follow-up after no reply

Use when: Your first message was relevant, but the prospect did not respond.

Circling back with one useful detail: [brief insight, example, or result]. If [problem] is not a priority at [Company], no need to reply. If it is, I can send the two-minute version.

Personalize: Add new value; do not write “just bumping this.”

13 · Close loop

Breakup message

Use when: You are closing a short sequence after multiple thoughtful attempts.

I’ll close the loop, [First name]. I reached out because [reason]. If [problem] becomes a priority later, happy to share what we’re seeing across [peer group].

Personalize: Keep it polite and pressure-free.

14 · Partnership

Partnership message

Use when: There is a concrete overlap in audience, product, community, or distribution.

Hi [First name] — [Company] and [Your company] both work with [shared audience], from different angles. I see a possible fit around [specific collaboration]. Worth exploring, or is someone else closer to partnerships?

Personalize: State the overlap and one credible collaboration idea.

15 · InMail

InMail for a high-value prospect

Use when: You have a strong reason to contact a high-value prospect outside your network.

Subject: Idea for [Company]’s [initiative] Hi [First name] — [specific trigger] suggests [initiative] may be important at [Company]. We help [peer group] [outcome] by [brief mechanism]. I have a short idea tailored to [context]. Should I send it here?

Personalize: Use InMail space for clarity, not length.

Before you send

Personalize without sounding automated.

A template preserves structure. Evidence supplies the reason to reach out.

01

Confirm ICP fit

Make sure the person and company match the audience the message was written for.

02

Verify the context

Use current, professionally appropriate evidence you can explain if asked.

03

Keep the problem plausible

Ask whether the issue exists instead of asserting private knowledge.

04

Use one idea and one question

Make the next step easy to understand and easy to answer.

05

Lower the pressure

The first touch should earn a conversation, not demand a meeting.

Signal to message

Use the signal as context—not as surveillance.

The best angle explains why the topic is relevant while leaving room for the prospect to correct your assumption.

Signal 01

Commented on a post

Ask about the idea they expressed rather than treating the engagement as consent to pitch.

Signal 02

Started a new role

Connect the role to an early priority without assuming what is broken.

Signal 03

Hiring for a team

Ask whether the underlying initiative already has the process and tooling it needs.

Signal 04

Funding or expansion

Focus on the operational change created by the announcement, not the headline alone.

Signal 05

High-intent activity

Use the business topic implied by the activity; avoid language that feels like surveillance.

Signal 06

Followed your company

Thank them for the interest and ask what prompted it.

Where NetworkHQ fits

Turn a message structure into timely outreach.

NetworkHQ monitors web buying signals, checks prospects against your ICP, researches the person, drafts contextual LinkedIn messages, runs sequences, and centralizes replies.

That turns the manual workflow behind these templates into one process: detect the reason, verify the fit, write the message, and follow up.

01Detect web buying signals
02Qualify against your ICP
03Draft contextual messages
04Run sequences and centralize replies
Frequently asked questions

Direct answers about LinkedIn messages.

01

What should I write in a LinkedIn connection request?

+

Write one sentence of context, one reason to connect, and a polite close. Keep it specific enough that the recipient understands why you chose them.

02

How long should a LinkedIn message be?

+

Use only the space needed to establish context and ask one easy question. LinkedIn’s current help page lists 200 characters for a personalized connection note; InMail allows more, but brevity still helps readability.

03

Should I pitch in the connection request?

+

Usually no. A connection request should establish relevance and permission to continue, not compress a full sales pitch into a short note.

04

How do I personalize a LinkedIn sales message?

+

Use one verified detail about the person, company, or timing and connect it to a plausible business issue. Avoid generic compliments and private-feeling tracking language.

05

How many follow-ups should I send?

+

There is no universal number. Use a short sequence in which every follow-up adds context or value, then close the loop politely.

06

Can I automate LinkedIn messages?

+

LinkedIn limits invitations and may restrict accounts for prohibited tools or behavior. Review LinkedIn’s current policies and keep outreach thoughtful, relevant, and human-reviewed.

Signal-first LinkedIn outreach

Write every message around a real reason to reach out.

NetworkHQ finds the signal, checks the fit, drafts the message, and keeps follow-ups and replies in one workflow.

Start free

Cookies

We use essential cookies to keep NetworkHQ working. With your permission, we use non-essential cookies to improve your experience.