First message after LinkedIn connection templates

Most people wreck the relationship in the first message after LinkedIn connection by pitching before they have any context. The fix is simple: write like a human who remembers why you connected, then let the pitch wait a step.

These templates are for founders, SDRs, and consultants who want to run outbound at scale without sounding like a bot. The single principle that makes them land: your first message should feel like a continuation of the connection request, not a cold email pasted into LinkedIn.

If you already tuned your connection requests using something like the LinkedIn Connection Request Template For Founders or Connection request templates for SDRs that get replies, these are the natural follow-ups.

Templates for your first message after LinkedIn connection

1. Founder-to-founder: context + light curiosity

Hi {first_name}, appreciate you accepting the request.

Saw you are building {company} in {industry_niche}, curious what you are focused on this quarter: growth, product, or hiring?

Happy to share what we tried at {your_company} if useful.

This works because it acknowledges the connection, shows you did minimal homework, and asks a forced-choice question that is easy to answer. Use it when you are a founder connecting with other founders or senior leaders and you actually have experience to share.

Variables to customize

• {first_name}
• {company}
• {industry_niche} (eg “B2B SaaS”, “logistics”, “dev tools”)
• {your_company}

2. SDR to ICP: tie back to the trigger

Hey {first_name}, thanks for connecting.

I reached out because you mentioned {trigger_event} and you are leading {team_type} at {company}.

Are you already working with anything to handle {pain_point_short}, or still figuring it out?

Here you reference a specific trigger, which makes the outreach feel less random, and you ask a yes-or-no style question that opens the door without a long pitch. Use this right after they accept if your connection request mentioned a trigger like hiring, fundraising, or a recent post.

Variables to customize

• {first_name}
• {company}
• {trigger_event} (eg “hiring 5 AEs”, “opening a second warehouse”)
• {team_type} (eg “sales”, “ops”, “revops”)
• {pain_point_short} (eg “ramp times for new reps”, “no-show rates on demos”)

3. Soft nurture: content first, no meeting ask

Hi {first_name}, glad to connect.

You mentioned {topic_from_profile_or_post}, so I thought you might like this short {asset_type}: {link}. It is what we give new hires at {your_company} to get them up to speed.

No need to reply, just hit save if it is useful later.

Instead of pushing for a call, you give something plausibly useful and explicitly remove pressure to respond, which lowers the guard. Use this if they accepted but have never engaged with your messages, or if your audience is skeptical of outbound.

Variables to customize

• {first_name}
• {topic_from_profile_or_post} (eg “PLG motion”, “account-based marketing”)
• {asset_type} (eg “checklist”, “Notion doc”, “5-slide teardown”)
• {link}
• {your_company}

4. Event or webinar follow-up: connect the dots

Hey {first_name}, good to meet you around {event_name} last week. Thanks for accepting the connection here.

I am still thinking about your point on {their_point_or_question}. If you want, happy to send over how we handled something similar at {your_company}.

Either way, hope {event_name_short} gave you a few ideas to test.

Referencing a shared event makes this feel like a warm continuation of an offline or online touch, not fresh outbound. Use this in the first week after a conference, webinar, or community session where you either spoke or had a short interaction.

Variables to customize

• {first_name}
• {event_name} (full event name)
• {event_name_short} (short or acronym)
• {their_point_or_question}
• {your_company}

5. Recruiter / talent angle: clear and honest ask

Hi {first_name}, appreciate the connection.

I am working with {role_type} who have done {short_achievements} at companies similar to {company}.

Would it be totally off for me to send you 2-3 quick profiles to keep on your radar for {timeframe}?

Recruiting outreach needs a direct but respectful ask. This message sets expectations, anchors on relevance, and asks permission before sending more info. Use it when your ICP owns hiring decisions and you want to start with a light talent pipeline conversation.

Variables to customize

• {first_name}
• {company}
• {role_type} (eg “senior backend engineers”, “enterprise AEs”)
• {short_achievements} (eg “Series A to Series C”, “greenfield to 7-figure pipeline”)
• {timeframe} (eg “the next 6-12 months”)

6. Consultant / agency: quick audit offer

Hey {first_name}, thanks for accepting. I have a quick one for you.

I took a fast look at {company}'s {area_you_reviewed} and spotted 2-3 things you could test without changing your whole setup.

Want me to send a Loom breaking that down, or should I leave it?

This first message after LinkedIn connection works because it balances specificity with an easy opt-out, and it promises something concrete instead of a vague “value add”. Use it if you actually did a light review and can send a short tailored Loom, not a generic deck.

Variables to customize

• {first_name}
• {company}
• {area_you_reviewed} (eg “LinkedIn profile funnel”, “demo booking flow”, “sales sequence timing”)

7. Warm investor / advisor angle: short and surgical

Hi {first_name}, thanks for accepting.

I am building {your_company}, focused on {one_line_problem}. Since you have backed {relevant_portfolio_or_background}, I wanted to ask one quick question about {specific_question_topic}.

If you are open to it, I can send the question here and keep it under 3 sentences.

Investors and senior operators are hit with generic pitches all day. This template shows you did homework, keeps your intro tight, and asks for something small that respects their time. Use it when you want advice first, not capital on day one.

Variables to customize

• {first_name}
• {your_company}
• {one_line_problem}
• {relevant_portfolio_or_background}
• {specific_question_topic}

8. Low-friction meeting ask for active buyers

Hey {first_name}, glad to be connected.

Talking to {peer_companies} we keep hearing {short_pain_statement}. It sounded similar to what you mentioned around {their_post_or_comment}.

Would a 15-minute working session on Zoom to compare notes be useful, or not a priority right now?

Sometimes you know they are already in-market, and a clear meeting ask is fine. This message ties your ask to social proof and mirrors their own words, which makes “yes” feel lower risk. Use it after they engage with your content or respond to an earlier nurture.

Variables to customize

• {first_name}
• {peer_companies} (eg “other B2B SaaS teams at 50-200 headcount”)
• {short_pain_statement} (eg “pipeline stalling after first call”, “reply rates stuck under your target”)
• {their_post_or_comment}

Quick template selector

Use this table to decide which template to paste for your first message after LinkedIn connection.

How often and how fast to send these messages safely

We run LinkedIn outbound ourselves, and the mistake we keep seeing is sending the first message within seconds of the acceptance at a volume that only an automation script could hit.

We cap our own accounts at roughly 30-50 new first messages per day, with a gap of at least a few hours between connection accepted and first follow-up. That looks like human behavior and gives people time to recognise your name from the request itself.

With Ampliflow, you can build this rhythm into your workflows instead of micro-managing it:

• Use the visual drag-and-drop builder to create a branch like: “Connection accepted” → “Delay 6-24 hours” → “Send Template 2 if ICP” or “Send Template 3 if no trigger data”.
• Add randomised timing jitter so messages do not all fire on the hour, which is exactly the pattern that triggers suspicion.
• Turn on auto-pause on reply, so if someone writes back after the connection but before your scheduled first message, the sequence stops and you can respond manually from the unified smart inbox.

Most competitors can send first messages too, but a lot of them run from browser extensions or local scripts. Tools like Linked Helper, Dux-Soup, and Octopus CRM are cheaper and sit in that camp, and if you are just experimenting at tiny scale that might be enough. We chose cloud execution via the Unipile API for Ampliflow so your laptop can stay closed and your sequences still respect daily safety limits.

If you are comparing price, Ampliflow’s founding member offer at 19 dollars per month sits in a strange spot: it is closer to Linked Helper or Dux-Soup than to cloud tools like Dripify at 79 dollars, Expandi at 99 dollars, or Zopto at 197 dollars. The trade-off is we are in pre-launch beta, not a polished “enterprise stack”, and we are opinionated about safety over raw volume.

More detail on where we sit against some of those tools is on pages like Dripify Alternative: Cloud LinkedIn Automation From $19/mo and Expandi Alternative: Cloud Outreach From $19/mo | Ampliflow, if you want a straight comparison.

Do and don’t checklist for first messages after a LinkedIn connection

You can copy any of the templates above, but how you use them matters more than the wording. Here is the practical checklist we follow on our own accounts.

Do

• Do reference the reason you connected in the first place: a post, a role, a mutual event, or a trigger from their profile.
• Do keep the first message under 4 short sentences, and often 2 is enough.
• Do change one line for different segments, for example founders vs ICs, or EU vs US.
• Do add actual specificity: “your post on hiring your first AE” beats “your content”.
• Do leave a clear off-ramp like “or not a priority right now”, so “no” feels safe.
• Do space messages out with real delays. In Ampliflow, we usually use 12-48 hour gaps after acceptance.
• Do A/B test subject lines or first lines inside Ampliflow, not your entire persona, so you can learn without burning your list.
• Do manually reply from the unified smart inbox whenever someone responds, even if the first message was automated.

Don’t

• Do not pitch pricing, features, or a product tour in the first message. Save that for reply 2 or 3.
• Do not send the exact same first message to every persona, platform algorithms pick that up fast and humans notice even faster.
• Do not send the first message immediately after the connection fires at scale, it screams “bot”.
• Do not ask three different questions in one paragraph, it gives them decision fatigue.
• Do not pretend you read every line of their profile if you clearly used a generic template.
• Do not stack connection requests and first messages to hit 100-plus actions per day on a fresh account, that is how you get flagged.
• Do not use fake scarcity or “I only work with 5 clients per month” if that is not true, experienced buyers smell this.
• Do not treat LinkedIn like cold email, people expect shorter, more conversational messages here.

Inside Ampliflow, we bake some of these “don’t” rules into the product itself: human-like daily rate limits, anomaly detection, and real-time account safety scoring. If your workflow pattern starts to look risky, we want the tool to nudge you before LinkedIn does.

How Ampliflow fits into these templates and your pricing options

These templates are designed so you can paste them into any workflow builder or even send them manually. Where Ampliflow helps is taking the boring parts off your plate without pushing you into spray-and-pray volume.

A typical “first message after LinkedIn connection” flow we run on our own accounts inside Ampliflow looks like this:

1. Import a search from standard LinkedIn or Sales Navigator.
2. Send connection requests using a mix of short, context-specific notes pulled from our Connection request with or without a note templates.
3. Create an If-Else branch:
   • If “Founder / C-level” then send Template 1 after a 24-36 hour delay.
   • If “IC or manager” then send Template 2 after a 12-24 hour delay.
   • If “No clear ICP tag” then send Template 3 after a 24-48 hour delay.
4. Auto-pause whenever someone replies, and handle replies from the unified smart inbox.
5. Use funnel analytics and A/B testing to see which first message actually leads to conversations, not just views.

Because Ampliflow is cloud-based with Unipile, you do not need the extension-on-all-day setup that tools like Phantombuster, Waalaxy, or HeyReach often rely on. Those tools are powerful in their own right and might be better fits if you want multi-channel scraping or already run everything from Chrome. We optimised for founders and lean sales teams who care about account safety and clarity more than raw volume.

On price, here is exactly how it works, no tricks:

• Founding members: 19 dollars per month for life, limited to the first 100 who decide to pay during the beta period.
• Public pricing at launch: 39 dollars per month for Starter, 79 dollars per month for Pro.
• Cancel any time, with a 30-day refund window once paid plans start.

We are upfront about one thing: the beta requires payment. What you are getting for committing early is the price lock plus a direct line to influence how features like the visual workflow builder, smart inbox, and analytics shape up.

If you want the detailed breakdown of what Starter and Pro will include, the Pricing page has the current plan sketches, and if you just want to keep an eye on launch timing you can Join the waitlist without setting anything up yet.