Connection request checklist for new SDRs

A practical verification process for SDRs to ensure every LinkedIn connection request targets the right lead, uses a real note, and hits the right window.

Get started

Short answer

A LinkedIn connection request checklist for SDRs is a short pre-send review: confirm the person fits your buyer profile, write a note that names a real reason for connecting, and send when they are likely to see it. The checklist keeps low-fit invites out of your daily activity and makes each request easier to accept.

Verify lead fit

Sending requests to the wrong people wastes your daily invite limit. A low acceptance rate can make your account look spammy. Confirm the person matches your buyer profile before you type a word.

Don't rely on job titles alone. A Director of Operations at a 10 person company has a different role than one at a 1,000 person company. Check the company page for headcount and industry to see if they actually have the problem your product solves.

Open the profile and read the About section, the headline and the last two or three posts. You are looking for evidence: a team they run, a tool they mention, a problem they describe. If the profile gives you nothing to reference, mark it as low priority and move on.

  1. 1

    Check the job title

    Compare the title against your ideal customer profile. If you target VPs of Sales, a Sales Manager might be a lead, but a Sales Enablement Specialist might not be.

  2. 2

    Confirm company size and industry

    Visit the company page. Make sure the industry matches your target and the employee count fits your range. A 50 to 200 person company usually buys differently from a 5,000 person company.

  3. 3

    Look for activity

    Scroll to the Activity section. If they have not posted or commented in six months, they may not check LinkedIn often. That makes them a lower priority, not a bad lead.

  4. 4

    Check buying authority

    Decide if this person owns the budget or influences the decision. Junior employees can be a way into the company, but they are not the primary target for a demo.

If you cannot name the reason in one sentence, you do not have a reason yet.

Audit the connection note

The goal of a connection request is to get the person to click Accept. Pitching in the invite creates friction. The prospect feels like they are being sold to before they know who you are.

A strong note focuses on the prospect. Mention a specific piece of content they shared or a commonality. If you cannot find a specific reason to connect, it is better to send no note than a generic one.

Keep the note to a couple of sentences. Name the person, name the reason, and stop. Do not ask for a call in the note. That comes after they accept and reply.

Generic and pitchy

  • I'd love to connect and explore synergies between our companies.
  • Hi, I see you're in sales. We help companies like yours grow revenue. Do you have time for a call?
  • I'm looking to grow my professional network with leaders in the SaaS space.

Specific and human

  • Hi Sarah, I saw your comment on Mark's post about remote hiring. I agreed with your point on culture fit and wanted to connect.
  • Hi James, I've been following Acme's growth in the fintech space and liked the recent update on your new API. Would love to stay connected.
  • Hi Elena, I noticed we're both in the B2B Sales Leaders group and wanted to reach out.

Paste this job

Hi {first name}, I saw your {post or comment} about {topic}. I liked your point on {specific detail}. I work on {your area} and wanted to connect.

Timing and send windows

Timing determines if your notification is seen or buried. If you send a request at 2 AM on a Sunday, it will likely be ignored or forgotten by Monday morning.

Send when the prospect is in a work mindset but not facing a deadline. Mid-morning or mid-afternoon on Tuesday through Thursday is a reasonable default for B2B targets. Test your own list. If your prospects work in healthcare or retail, early morning may be better.

Use the prospect's local time. A request that lands at 11 PM their time is a request they see with tomorrow's noise.

Time zone

Factor
Match the prospect's local time
What to do
Prevents notifications from arriving at odd hours

Business hours

Factor
Send between 9 AM and 5 PM local time
What to do
Keeps you near the top of the notification list during work

Days of week

Factor
Use Tuesday to Thursday as a default
What to do
Mondays are for catching up and Fridays are for winding down

A send window is a guardrail, not a guarantee. If your list is global, set the window in the lead's time zone and let the queue handle the rest.

Final pre-send review

A typo in a name or company ruins trust. It tells the prospect you are using a template and did not look at their profile.

Do a final scan before hitting send. Read the note out loud. If it sounds like a robot, rewrite it. Keep it short and focus on the bridge between you and the prospect.

Write the first follow-up before you send the invite. If they accept and do not reply, you already know what you will say. That stops you from sending a blank thanks for connecting message.

  1. 1

    Read it aloud

    If the sentence feels too long or formal, break it up. Use contractions like I'm or don't to sound more natural.

  2. 2

    Double check names

    Make sure you did not misspell the name or use a nickname they do not use on their profile.

  3. 3

    Check the length

    Keep the note to a couple of sentences. Long notes look like pitches and get rejected.

  4. 4

    Plan the next step

    Decide what you will do if they accept without replying. Have a follow-up ready that continues the conversation from the original note.

Example

  1. You

    Hi Mark, saw your post about the shift to PLG. I liked your take on the friction in the sign-up flow. Would love to connect.

  2. Prospect

    Thanks for reaching out. Glad that post resonated.

  3. You

    It did. I'm curious, are you seeing that friction mostly with enterprise users or the self-serve crowd?

What to do after they accept

An accepted invite is not a conversation yet. Most people accept and then go back to work. Your job is to give them a reason to reply without turning the first message into a pitch.

Reply within a day if you can. Reference the note you sent, ask one question about their work, and keep it short. If they do not reply, wait a few days and send one follow-up. If that gets no response, leave them alone for a while.

Move to a call only when they show interest. A question about how something works, a request for a resource, or a comment about a problem they have are all signals. A simple thanks for connecting is not.

  1. 1

    Send a short thank you with a question

    Example: Thanks for connecting, Mark. You mentioned friction in sign-up. Is that mostly a design issue or a handoff issue?

  2. 2

    Wait before the second message

    Give them two or three working days. Then send one follow-up with a useful link or a specific question. Do not send a third message in the same week.

  3. 3

    Hand off to a call when they show interest

    If they ask how something works or describe a problem, offer a short call. Use a scheduling link so they can pick a time.

Doing this with Kinlead

Kinlead finds people who match the customer you describe or your website and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept, so your invite list starts with people who look like buyers.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles. It reads comments on their recent posts and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented. That gives the AI-written note a real reason to open with.

  • Leads live in lead groups. Any campaign can point at any group, and leads can be exported to CSV or imported from a CSV of LinkedIn profile URLs.
  • Messages and follow-ups are written by AI from the campaign goal, tone and an optional sales playbook.
  • Replies from every campaign land in one unified inbox, classified by intent, with interested replies first.
  • Stale pending invitations are withdrawn automatically, and Settings shows pending invitations and acceptance rate with warnings.

Kinlead sends at a human pace: each LinkedIn account sends at most one action every 5 minutes, inside daily invite and message limits you set and inside a send window in the lead's time zone. Queued messages can be read and edited on the Actions page before they send.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? Connection request checklist for new SDRs.md