LinkedIn Connection Request Template For Founders

How founders should use these templates

If you are a founder doing your own outbound, these templates are for you. Each LinkedIn connection request template for founders is built around one principle: every sentence has to earn its place under the 300 character note limit.

In our own outreach, the requests that land best:

• Mention one very specific reason for the invite
• Avoid pitching in the first touch
• Sound like a human who did at least 10 seconds of research

Use these as base patterns, wire them into manual or automated workflows, then A/B test. We run all of ours through Ampliflow sequences so we can see which note actually leads to replies.

Templates: founder-tested LinkedIn connection requests

1. Founder to founder in the same niche

"Hey {first_name}, saw you are also building in {niche} at {company}. I am founder at {your_company}, would love to connect with more operators solving {short_problem_phrase}. No pitch, just expanding my {niche} circle."

This works because it puts you in the same bucket as them and disarms sales suspicion with "no pitch". Use it when you are reaching out to other founders in your vertical or adjacent spaces.

Variables to customize

• {niche}
• {company}
• {your_company}
• {short_problem_phrase} (max 3 words, for example "B2B onboarding")

2. Founder to ICP with trigger event (podcast, post, news)

"Hi {first_name}, your {post_type} on {topic} caught my eye. I work with {persona_plural} on {short_outcome}, thought it would be useful to stay connected and swap notes over time. Open to connect?"

You anchor the invite on a concrete trigger instead of a vague "came across your profile". Use this when they recently posted, spoke, or were featured somewhere you can point to.

Variables to customize

• {post_type} (post, talk, podcast, article)
• {topic}
• {persona_plural} (RevOps leaders, SaaS founders)
• {short_outcome} (keeping churn under control, tightening outbound)

3. Founder doing soft discovery, no pitch

"Hi {first_name}, I am digging into how {persona_plural} handle {problem} at {company_size}-person companies. I am founder at {your_company}. No sales agenda, just learning from operators in the trenches. Open to connect?"

Here you make your intent clear: you are doing discovery, not a hard sell. This is ideal when you are still validating a problem and want honest input more than meetings.

Variables to customize

• {persona_plural} (heads of CS, B2B marketers)
• {problem} (onboarding new sales hires, tracking partner leads)
• {company_size} (20, 50, 200)
• {your_company}

4. Founder to investor or advisor

"Hi {first_name}, I noticed you back {portfolio_example} and other {sector} companies. I am building {your_company} around {one_line_thesis}. I am not fundraising now, just connecting with people close to this space. Can we connect here?"

Investors see generic pitches all day. This template names something they actually did, plus clarifies that you are not angling for an immediate raise. Great for building a bench of future angels or advisors.

Variables to customize

• {portfolio_example} (one portfolio company)
• {sector} (B2B SaaS, climate, fintech)
• {your_company}
• {one_line_thesis} (for example "usage-based pricing infra for PLG SaaS")

5. Founder reconnecting after a call or event

"Hey {first_name}, good to meet you at {event_name} earlier. Enjoyed our chat about {topic}. Sending a quick connection request so we stay in touch and can share progress on {your_focus_area}."

You make the invite feel natural by referencing the shared moment. Use right after a conference, meetup, or Zoom call while you are still top of mind.

Variables to customize

• {event_name} (SaaStock, local SaaS meetup)
• {topic} (partner-led growth, product-led onboarding)
• {your_focus_area} (bootstrapping, outbound motion)

6. Founder to prospective partner or integration

"Hi {first_name}, we have a few shared customers using {their_tool} alongside {your_product_category}. I am exploring tighter ways to make {joint_use_case} work. Thought it would be smart to connect here first."

Partnership invites land better when you show you already share a market, even if it is just a pattern you noticed. Use this for integration leads, channel partners, or agencies around your product.

Variables to customize

• {their_tool}
• {your_product_category} (our LinkedIn workflow tool, our billing app)
• {joint_use_case} (outbound reporting, revenue attribution)

7. Founder to job candidate or potential hire

"Hi {first_name}, your background in {skill_area} at {candidate_company} stood out. I am founder at {your_company}, we are quietly building a team around {mission_short}. Would you be open to a light connection here to stay on each other's radar?"

You are not pushing a job description, you are starting a relationship. This works particularly well for senior ICs or leaders who are not actively looking.

Variables to customize

• {skill_area} (demand gen, revenue ops, product engineering)
• {candidate_company}
• {your_company}
• {mission_short} (fixing outbound for small founding teams, modernizing field ops)

8. Founder to prospect via mutual connection

"Hi {first_name}, we are both connected with {mutual_name} from {mutual_context}. I help {persona_plural} with {specific_outcome}. Not pitching anything here, just thought it made sense to connect given the overlap."

Dropping a real mutual contact lowers the guard if you keep the copy light. Use this when you see one strong mutual connection you can credibly reference.

Variables to customize

• {mutual_name}
• {mutual_context} (previous company, local founders group)
• {persona_plural} (RevOps leads, SDR leaders)
• {specific_outcome} (keeping inboxes sane, structuring outreach data)

Quick template chooser for founders

Use this table to pick the right LinkedIn connection request template for founders based on your situation.

In our own workflow boards, we literally tag people by scenario first, then drop in the right template rather than starting from a blank box each time.

How to customize templates without killing response rates

Founders usually go wrong on LinkedIn in one of two ways: they send completely generic connection requests, or they overcustomize and burn an hour per prospect. Neither scales.

Here is what we do in practice:

• Decide 3-5 variables that meaningfully change the copy, everything else stays constant
• Personalize at the segment level, not the individual, for example "RevOps leaders at 20-200 person SaaS companies"
• Edit the first line only when a clear trigger is present, like a post or podcast

In Ampliflow we mirror that by setting variables like {persona}, {niche}, and {trigger_source} in a visual workflow, then running A/B tests on two connection notes at a time. Once one version pulls more replies over a couple of weeks, we retire the weaker one and spin up the next experiment.

If you are doing this manually, you can still structure it:

1. Save these templates in a text expander or notes app
2. Define your standard variable set for the quarter
3. Keep a shortlist of 2 connection templates and 2 follow-up templates and resist the urge to rewrite daily

The only edits we consistently see move the needle are a sharper reason to connect and a more concrete description of who you help. Fluffy mission lines almost always underperform.

Do and don't list for founder connection requests

A realistic checklist from our own outbound and what we see in founder inboxes.

Do

• Do stay under 220-250 characters
  Short enough to scan on mobile, long enough to show you are not a bot.

• Do lead with one clear context hook
  Same niche, shared event, trigger content, or mutual contact. One is plenty.

• Do mention that you are a founder
  "I am founder at {your_company}" changes how people read the note. It signals operator to operator.

• Do avoid links in the connection note
  Links can look spammy and are better reserved for later messages if the person engages.

• Do cap daily requests
  On our own accounts we stay around 20-40 connection requests per day with randomized sending windows. We would not push harder than that without an extremely clean history and strong safety controls.

• Do track which templates actually create conversations
  Whether you use Ampliflow, a sheet, or another tool, keep a simple log: template label, people added, replies over a fixed period.

Don't

• Don't pitch product in the connection note
  The fastest way to get ignored is "Can I get 15 minutes to show you a demo?" before they even know you.

• Don't pretend you read things you did not
  "Loved your last 3 posts" is a tell if you have never liked or commented. Reference one real thing instead.

• Don't send the same template to wildly different personas
  A note that makes sense for a RevOps leader reads strange to a seed investor.

• Don't stack fluff adjectives
  "Innovative, disruptive, world-class" language feels like canned marketing copy. Plain language works better.

• Don't spike volume suddenly
  Jumping from 5 to 80 daily requests overnight is exactly how people end up with warnings or restrictions. Gradual ramps are safer.

• Don't ignore safety if you automate
  Browser plug-ins that click as you can create bursty patterns on your own IP. Cloud tools with jitter and safety scoring are safer for founders who want to run outreach while traveling or offline.

Where Ampliflow fits in your LinkedIn outreach stack

You can use every LinkedIn connection request template for founders on this page manually, but if you plan to send them consistently, tooling matters.

Ampliflow is our own answer to that problem: a cloud-based LinkedIn outreach automation tool for founders and sales teams. Instead of driving a Chrome extension all day, your workflows run in the cloud via the Unipile API, so your laptop can be closed and your IP is not the one hammering LinkedIn.

A few design choices that matter if you are a founder:

• Visual drag-and-drop workflows
  You build sequences like you think: search or import from Sales Navigator, send a connection request with a specific template, wait 3-5 days with a random delay, then branch on "accepted but no reply" or "replied". If/Else logic means you can stop nudging people who are already talking to you.

• LinkedIn search + Sales Navigator import
  We use native searches or Sales Nav lead lists as starting points, then feed them straight into workflows without exporting CSVs and re-uploading.

• Real-time account safety scoring
  Every account has a safety score that responds to anomalies, for example a spike in pending invites or a burst of profile views. We treat that score as a guardrail and auto-throttle or pause when it drops instead of chasing volume.

• Human-like rate limits with timing jitter
  Instead of fixed 9:00 and 9:05 sends, Ampliflow spaces actions within ranges, for example "between 9 and 10" with randomness. It also auto-pauses on reply so you are not sending follow-ups to someone who just answered.

• Unified smart inbox and funnel analytics
  Replies from multiple accounts land in one view. You can tag conversations by campaign, see which templates and branches pull real responses, and adjust your copy without guessing.

Pricing-wise, we wanted something founders can justify long before they build a sales team. Founding members lock in 19 dollars per month for life (first 100 only) as part of the early beta group, with public pricing at launch planned at 39 dollars per month for Starter and 79 dollars per month for Pro. This is pre-launch: the paid beta runs July 2026. It is a paid beta, not a trial, and there is a 30-day refund once paid plans start if it clearly is not for you. You can see the planned tiers on the Pricing page or Join the waitlist if you want in on the founding price.

We are not the cheapest option on the market and we deliberately sit between pure budget tools and the heavy enterprise platforms. Linked Helper or Octopus CRM come in lower on raw price, and if all you need is a simple browser-based auto-connector, they may be enough. On the other end, tools like Expandi, Dripify, Waalaxy, Skylead, and Salesflow offer mature feature sets at higher entry points, usually with more focus on agency use and volume.

Our bias is toward architecture and safety instead of squeezing out a few extra messages per day. If you are comparing, you can read how we think about it in the Dripify Alternative: Cloud LinkedIn Automation From $19/mo and Expandi Alternative: Cloud Outreach From $19/mo | Ampliflow pages. For many solo founders and small teams, the trade-off that matters is "can I run clean, safe outreach from the cloud without babysitting a plug-in", not who can stack the most daily actions on a pricing sheet.

For the templates above, any tool is just a way to consistently send and measure them. The craft still lives in the few words you choose to put in front of the connect button.

Author: Ibrahim, Growth · Operations