Messaging prospects who downloaded a whitepaper

How to turn a whitepaper download into a LinkedIn conversation by naming the problem the asset describes, with note templates and follow-up steps.

Get started

Short answer

Don't ask whether they read the paper. Use the topic of the asset to name the problem it describes and ask if that problem is live for them. Move to a meeting only after they confirm the problem.

The download tells you the topic, nothing more

The usual opener is some version of 'Did you get a chance to look at the guide?' That turns a download into homework, and now the buyer has to admit to a stranger that they skimmed two pages on a train. Most people either ignore it or send a polite nothing back.

The download tells you one thing: something in the title matched a problem they were already carrying around. Work from that. Name the problem, ask whether it's live for them, and let the paper sit in the background where it belongs.

Mention the asset once, in the first line, as the reason you're writing. After that it's dead weight. Nobody wants a second paragraph about your content library.

Asking for a review

  • I saw you downloaded our whitepaper on scaling remote teams. Did you find it useful?
  • Thanks for grabbing our guide. Let me know if you have any questions about the content.

Naming the problem

  • You picked up our guide on scaling remote teams. The ops leads I talk to are usually stuck on onboarding people they hired three months ago. Is that the bit that's hurting?
  • Saw you downloaded the churn paper. Most success leaders I speak with can point to the exact month the drop happens but can't say why. Do you know your month?

Match the asset to the problem it points at

A paper about churn attracts people with churn. A guide about hiring in Germany attracts people opening a German office. The topic does the targeting for you, so write the message against the topic and not against the fact that someone filled in a form.

Keep a mapping table for every asset you push on LinkedIn. One row per paper, one question per row. If you can't write the question, the paper is too broad to message against and you should pick a different asset for outreach.

The question in the last column is the whole message. Everything else in the note is a sentence designed to get that question read.

Scaling a remote team

Asset topic
Hiring has outrun onboarding
What the download usually means
Who owns onboarding for the people you hired this quarter?

Cutting churn

Asset topic
A drop-off they can already see in a chart
What the download usually means
Where does the drop land, month one or month three?

Rolling out AI tools

Asset topic
Licences bought, daily usage flat
What the download usually means
Which part of the workflow did the tools never reach?

Opening a second market

Asset topic
Hiring before there's a pipeline
What the download usually means
Are you hiring for the new market yet, or still testing it?

Write the connection note in two sentences

The note has room for a reason and a question. That's it. Skip the company intro, skip the compliment about their recent post, skip 'I'd love to connect'.

The version that works names the specific pain in the paper, says who usually has it, and asks something the reader can answer from memory on a phone.

Example

  1. You

    Hi Sarah, you downloaded the churn guide last week. The success leaders I talk to keep seeing a spike around month three. Is that what you're seeing?

  2. Prospect

    Month two, actually. It's on the roadmap but nobody owns it yet.

  3. You

    Month two usually means the first 30 days set the wrong expectation. Two teams changed their day-14 touch and it moved. Want me to send what they did?

If your note could go to anyone who downloaded any of your papers, it isn't a note about this download.

Run three touches, then stop

A download is a soft signal, and soft signals don't survive a six-step cadence. Three touches is enough to find out whether the problem is real. If it isn't, park the lead and come back when a different asset fits them better.

  1. 1

    Touch one, the connection request

    Reference the asset topic in half a line and ask the problem question from your mapping table. No pitch, no calendar link.

  2. 2

    Touch two, one useful thing

    If they accepted but stayed quiet, send a single observation from the paper or from your own work that they could use this week. One idea, three sentences, no ask.

  3. 3

    Touch three, the small ask

    Offer 15 minutes and say what you'd cover: how two other teams in their position handled the problem they described. Keep it specific enough to accept or decline.

  4. 4

    After that, close the loop

    No reply means the timing is wrong or the problem isn't theirs. Move them out of the sequence and note which asset to try next.

Adjust for how old the download is

A download from Tuesday and a download from March need different openers. Recent downloads can carry the paper in the first line. Older ones can't, because the person has forgotten the file and a reference to it reads like surveillance.

For anything older than a month, lead with the problem and treat the paper as a footnote, or leave it out and open on something they posted instead.

Paste this job

Recent download (under two weeks)
Hi {first}, you picked up our guide on {topic} last week. Most {role}s I speak with are stuck on {problem} right now. Is that on your list this quarter?

Older download (over a month)
Hi {first}, the teams I talk to are still fighting {problem}. When we last crossed paths you were looking at {topic}. Has it moved, or is it parked?

Same person, new asset
Hi {first}, you read our piece on {topic A}. I've been writing about {topic B}, which hits the same problem from a different angle. Want the short version?

What to do with the replies you get

Most replies fall into four shapes, and each one has an obvious next move. You don't need a script for all of them, just a decision about what you're trying to learn.

The one thing to avoid is treating every reply as a buying signal and pushing for a call. A polite no today is worth more than an unanswered calendar link.

  • They confirm the problem and ask nothing back. Send one specific change another team made, then ask for 15 minutes to walk through it.
  • They say it isn't a priority. Ask what moved above it. That answer tells you whether to return next quarter or drop the lead.
  • They ask for the deck. Send two slides rather than twelve, and ask which of the two situations looks closer to theirs.
  • Someone else owns it. Ask for the name and whether they'd make an introduction, and keep the original person on the thread.

Doing this with Kinlead

Export the downloaders with their profile URLs and import the file into a lead group so each asset gets its own group. Kinlead scores every lead from 0 to 100 against the customer profile you describe, and leads under the fit line are dropped, which keeps a mixed list from turning into noise.

Point a campaign at that group and give it your own sales script as the playbook, with the asset topic and the problem written in. Connection notes come out under 200 characters and open with why that person became a lead, which is the same job as the first line you'd write by hand.

Sending runs from your LinkedIn account at one action every 5 minutes, inside limits you set and a send window in the lead's time zone, so a downloaded list doesn't go out in one burst at midnight. Queued messages can be read and edited on the Actions page, and for high-intent downloaders set the campaign to hand over at the first reply so you run the conversation yourself.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? Messaging prospects who downloaded a whitepaper.md