LinkedIn scripts for selling to busy founders

Stop sending generic pitches to busy founders. Use short, direct scripts that name a specific problem and ask for a small, easy reply today.

Get started

Short answer

To get a reply from a founder, skip the long introduction and the general claims. Send a short message that names one specific problem you noticed, offers a concrete piece of help, and asks for a small response that takes under a minute to give.

Why founders ignore most LinkedIn messages

A founder reads their inbox between meetings, often on a phone, usually while something else is on fire. They are not looking for a new vendor. They are scanning for anything that might cost them money, time or a customer in the next week.

Most sales messages fail at that scan. They open with a greeting, a compliment and a paragraph about the sender's company. The founder has to do the work of figuring out whether the message applies to them. They rarely bother.

The fix is not a better compliment. It is a specific observation the founder can verify in two seconds. When your message points at a real problem in their business, you stop looking like a pitch and start looking like a heads-up from someone who looked at their product.

Generic and easy to skip

  • Hi Jamie, I've been following your journey and would love to connect to see how we can help you scale.
  • We provide an end to end solution for B2B lead generation and growth. Do you have 30 minutes this week?

Specific and easy to answer

  • Saw your new pricing page. The annual plan link throws a 404 on mobile. Want the screen recording?
  • Three of your competitors are bidding on your brand terms right now. I pulled the list. Want it?

The three-part script structure

A founder pitch should read like a note from a peer, not a sales letter. You are not trying to close anything in the first message. You are trying to get a yes to a very small request.

Keep the whole thing under about ninety words. If it needs scrolling on a phone, it is too long. Three parts move the reader from a fact they recognise to a reply they can send in one line.

  1. 1

    Name the observation

    Start with something you saw: a post, a launch, a job ad, a broken link, a competitor's move. This proves you looked at their business and not just their job title.

  2. 2

    Say what it costs them

    Explain the specific problem that observation creates. Tie it to lost revenue, wasted time or a customer they might lose. Keep it to one sentence.

  3. 3

    Ask for something small

    Ask if they want the details, the recording or the list. Do not ask for a thirty minute call. A founder will say yes to a PDF far more often than to a meeting.

Paste this job

Hi {{first_name}}, saw {{specific_thing_you_noticed}}. It looks like {{problem_it_causes}}. I have {{the_fix_or_asset}}. Want me to send it over?

Templates for common scenarios

Your opening changes depending on how you found the founder. A technical error needs a different tone from a competitor launch or a post they wrote. The structure stays the same: observation, cost, small ask.

Drop phrases like I'm reaching out because or I hope you're doing well. They signal a template and give the founder a reason to stop reading before they reach the useful part.

Broken page or bug

Scenario
Saw your new landing page. The sign-up button does nothing on Safari. I recorded it on my phone. Want the clip?

Competitor launch

Scenario
Noticed Northwind launched a free tier this morning. It targets the same search terms you rank for. I have a short list of the overlaps. Want it?

Their own post

Scenario
Your post on pricing pages matched what we saw across forty B2B sites last quarter. I have the raw notes. Want the summary?

Hiring trigger

Scenario
You're hiring two SDRs. Most teams at that stage lose the first month to list building. I have a checklist we used. Want a copy?

Writing the connection request note

The connection note has one job: get the request accepted. It does not need to explain your product or your company. It needs to show that you looked at the person and have a reason to talk.

Keep it under two hundred characters, which is the limit Kinlead works within for AI-written notes. Start with the reason that person became a lead. That is the whole note.

Note that gets ignored

  • Hi, I help B2B companies grow pipeline with a proven system. Would love to connect and explore synergies.

Note that gets accepted

  • Saw your comment on the Northwind pricing post. I have the benchmark data you asked for. Happy to connect and send it.

If the note does not mention something specific to them, delete it and start again. A blank request is better than a generic one.

Following up without nagging

Founders often read a message, plan to reply, and then get pulled into a call or a customer issue. Silence usually means the message arrived at a bad moment, not that they hate you.

The follow-up should add something or close the loop. Do not ask whether they saw your last message. Do not make them feel guilty. Give them a second chance to say yes without rereading the first note.

Example

  1. You

    Saw your new landing page. The sign-up button does nothing on Safari. I recorded it on my phone. Want the clip?

  2. Suggested reply

    Day 4: Still seeing the Safari bug on your checkout page. I can send the fix over if it is still open.

  3. Suggested reply

    Day 10: Closing this loop. The bug is still live as of this morning. If it is not a priority, no problem. I will leave it here.

Two follow-ups after the first message is enough. After that, move the person to a list you check in a few months, not a sequence that keeps firing.

When they reply

Most replies from founders are short. Want it. Send it. What does it cost. Treat a one word reply as a real opening, because it is. They gave you the hardest thing to get, which is attention.

Answer the question they asked, then offer the smallest next step. If they ask what it costs, give a range and a plain description of what they get. Do not dodge the number. Founders read hesitation as a red flag.

If they say they are not interested, ask one question about what would make it relevant later. Then stop. A clean exit often turns into a referral or a conversation six months down the line.

Example

  1. Prospect

    Send the clip.

  2. You

    Here it is. The button fails on Safari only, so it is probably the form script. Do you want me to send the two line fix to your developer?

  3. Prospect

    Yes. What do you charge?

  4. You

    Nothing for the fix. If you want the full audit of the sign-up flow, it is a fixed fee and I can send the scope. Say the word and I will put it in writing.

Doing this with Kinlead

Writing a specific note for every founder is slow by hand. 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 you are not writing notes for people who were never going to buy. You can read more about lead groups and scoring.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads the comments on 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, so your note can open with why that person became a lead.

Outreach runs from your own LinkedIn account through Unipile. Kinlead sends at most one action every five 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, and any campaign can be paused.

Connection notes can carry an AI-written line under 200 characters. Review the first batch before you let a campaign run, because the opening line is the part founders judge.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? LinkedIn scripts for selling to busy founders.md