Connection requests for people sharing industry reports

Find people sharing industry reports on LinkedIn, read what they actually said, and send a connection note that starts a real conversation about the data.

Get started

Short answer

Find the post with LinkedIn search, read what the person actually said about the data, and send a connection note that responds to their point. The note has to fit in 200 characters, so it carries one idea: the finding you agree or disagree with.

Find the people talking about the report

Searching by job title gives you a list of people who might care about a report. Searching for the report gives you people who already told you they care. Start with the second one.

LinkedIn's search covers posts as well as profiles. Type the report name, switch the tab to posts, and you'll see the author's announcement, the company page share, and a scatter of people who added their own caption.

Pick a report your buyers would actually read. A generic marketing trends PDF gets shared by marketers who sell to marketers. A report on fleet maintenance gets shared by twelve people, and all twelve buy the thing you sell.

  1. 1

    Search the exact title

    Put the report name in quotes if it contains a common phrase, like "State of Churn 2025". Without quotes you get every post that happens to contain the word churn.

  2. 2

    Switch to the posts tab

    Posts sits next to People, Companies and Jobs. It's the only tab that shows what someone wrote, which is the part you can respond to.

  3. 3

    Set the date range to the past week

    A post from three months ago has a dead comment thread. A post from two days ago still has the person checking notifications.

  4. 4

    Read the comments before the post

    Someone who wrote two paragraphs under a report has an opinion they want to defend. That's a better opening than a reshare with no caption.

If nobody is posting about the report, search the topic instead. "Churn benchmarks" or "retention survey" surfaces people arguing about the same numbers.

Read the post before you write anything

A request that says "saw you shared the report, would love to connect" gets declined because it could have been sent to anyone. You need one detail that only fits this person.

Look at the caption, then at the comments. People share reports to signal something: that they're on top of a trend, that their team already does this, or that they think the report is wrong. Each of those is a different opening.

Then open their profile and read their last two posts. If they write about hiring costs every week and the report is about hiring costs, you have a much better hook than the report alone.

  • The metric they quoted. If their caption says pipeline coverage dropped, that's the number to mention.
  • The question they asked their audience. If nobody answered it well, you can.
  • Their title and company size. A VP at a 2,000-person company reads the same report differently than the founder of a 12-person agency.
  • Whether they disagreed. A person who called the data optimistic is easier to talk to than one who reposted it without comment.

A commenter is worth more of your time than a sharer. The comment is the person's own words, and it's what you can quote back to them.

Write a connection note that fits in 200 characters

Connection notes on LinkedIn are capped, so the note has to carry one idea. Pick the finding you both saw and say what you think about it. Skip the part where you describe your company.

The note works when it reads like something you'd say to someone after the same conference panel. Short, specific, and with a reason to keep talking.

Count the characters before you send. LinkedIn shows the limit as you type, and a note that gets cut off mid-sentence reads worse than no note at all.

Pitch wearing a compliment

  • Hi, I saw you shared the State of Churn report. I help companies cut churn and would love to connect.
  • Thanks for sharing this report, let's connect.
  • I'm an expert in retention and saw your post. Would love to network and learn from you.

One idea, tied to their words

  • Your line about mid-market teams feeling churn first matched what I see at Acme. Curious whether your clients say the same.
  • I thought the pricing section of that report was optimistic. Your caption made me reread it. Happy to connect.
  • You asked whether anyone's retention actually improved last quarter. Ours didn't, for a boring reason. Happy to swap notes.

Paste this job

Template:
[what they said] + [what you saw that matches or contradicts it] + [one line that gives them a reason to accept]

Example:
"You called the retention numbers optimistic. I run CS at a 40-person agency and our Q1 looked nothing like that chart. Curious what you're seeing."

What to do when they accept

The first message after acceptance decides whether this becomes a conversation or a pitch. Don't open with a calendar link. Ask about the thing you connected over.

Keep it to one question. Two questions in one message lets the person answer the easier one and ignore the other.

Reply while the post is still recent. A conversation about a report that came out three weeks ago has already lost its pull, and the person has moved on to the next thing.

Example

  1. You

    Thanks for connecting. You said the AI adoption section felt optimistic. What's the gap you're seeing?

  2. Prospect

    Most of my clients are still stuck getting clean data into the tools. The advanced stuff in that report is a year away for them.

  3. You

    That matches what I see. Teams get to the dashboard stage and find out nobody owns the data going in. Is that the bottleneck for you, or is it something else?

  4. Prospect

    Data ownership, mostly. Nobody wants to be the person who signs off on it.

Now you have something real. If your product touches data ownership, you've earned the right to mention it in the next message. If it doesn't, you've made a contact who'll answer your next question.

Sort the people you find before you spend a request

Most of the people who show up in a report search fall into one of a few groups. Sorting them takes two minutes and saves requests you'd waste on silent reshares.

The table below is the order I'd work in. Start at the bottom of the list only when the top runs dry.

The author

Who you found
Wrote the report and gets asked about it constantly
What it tells you
A question about a finding they didn't cover in the post

Sharer with a caption

Who you found
Has an opinion and a reason to share it
What it tells you
A response to their specific point

Commenter with a paragraph

Who you found
Warmest of the group, already arguing in public
What it tells you
A reply to their comment, then a request

Person who disagreed

Who you found
Thinks the report is wrong and wants to say why
What it tells you
Agreement plus your own counter-example

Silent reshare

Who you found
Clicked share and added nothing
What it tells you
Skip, or wait for a post where they say something

A silent reshare tells you nothing about the person's thinking. Don't spend a request on it.

Work inside whatever limit your account has

LinkedIn doesn't publish how many invitations an account can send. Anyone quoting a number is guessing, and the real ceiling moves with account age, acceptance rate and how many invitations you're already carrying.

What you can control is how the account looks to LinkedIn. Send fewer than you could, clear out invitations that have sat unanswered, and keep the acceptance rate high by writing only to people who posted something you can answer.

A low acceptance rate is the clearest signal you're writing to the wrong people. When it drops, change the targeting before you change the wording.

  • Withdraw pending invitations older than a few weeks. A backlog of ignored requests makes the next one look worse.
  • Spread sends through the working day instead of firing them all at once.
  • Stop a batch when replies dry up and reread the last ten notes you sent.

Doing this with Kinlead

The Steal Customers agent watches competitor company pages and, if you want, founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads, keeping the post URL, what the post was about and what they commented.

Each lead is scored from 0 to 100 against the customer you described, and leads below the fit line aren't kept. Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.

Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused. Sends go out at most one action every 5 minutes, inside the daily limits and send window you set, in the lead's time zone. Stale pending invitations are withdrawn automatically, and replies from every campaign land in one inbox sorted by intent.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? Connection requests for people sharing industry reports.md