How to handle requests for whitepapers or ebooks
Learn how to turn a prospect's request for a whitepaper or ebook into a booked meeting instead of just sending a PDF and losing the lead to a competitor.
Get startedShort answer
When a prospect asks for a whitepaper or ebook on LinkedIn, they are often trying to avoid a call. Instead of sending a PDF and losing the conversation, use the request to qualify their specific pain and offer a tailored walkthrough of the document in a brief meeting.
Why sending the PDF immediately kills the deal
When a prospect asks for a document, it feels like a win. You have their interest and a reason to message them. But sending the file immediately is usually a mistake. You have given them a way to stop talking to you while they read your content alone.
If the prospect reads the PDF without you, they might misunderstand a point or find one detail they disagree with. Without your context, they can dismiss your entire approach. You lose the chance to guide them toward the conclusion that your product solves their problem.
The file itself is fine. The timing is what causes trouble. Send the file after you learn why they want it, or send it with a specific question that keeps the conversation open. A prospect who says send it over is not automatically a buyer. They are a person with a problem who thinks a document is the fastest way to get an answer.
A document request is a signal, not a close. Treat it like a question that needs a conversation. The prospect is telling you the topic they care about. Use that topic to ask what is happening in their business right now.
The passive approach
- Sending the link immediately without asking questions
- Assuming they will read the whole document
- Waiting for them to come back to you after reading
The active approach
- Using the request to qualify their specific pain
- Offering to highlight the most relevant sections
- Positioning a short call as a faster way to get the answer
The qualification first response
The goal is to understand why they want it. That turns a generic request into a discovery conversation. Ask for the specific problem they are solving, and you get the prospect to name a pain point.
Once they tell you the problem, point to a specific part of your whitepaper. This proves the content is valuable and makes a live walkthrough more appealing than a 20 page PDF. Keep the question simple. If you ask three questions at once, most people answer none.
The best question is narrow. Ask about one part of their process, not their whole strategy. For example, ask whether they struggle more with hiring or ramp time. That gives them two choices and makes it easy to answer.
Example
- Prospect
Can you send over that ebook on scaling SDR teams?
- You
I can send that over. To make sure I send the most relevant sections, are you currently struggling more with hiring or with the actual ramp time of new reps?
- Prospect
Mostly ramp time. It's taking us 3 months to get them productive.
- You
That's exactly what page 12 covers. I'm happy to send the PDF, but it's usually faster if I show you the framework for reducing ramp time on a 15 minute call. Does Thursday work?
Offer the document and a faster path in the same message. If the prospect says yes to the call, send the PDF anyway so they have context.
Three ways to pivot to a call
Depending on how the prospect responds, you need a different pivot. Some people are just browsing, while others have a burning problem. Your response should match their urgency.
Present the call as a time saving measure. People do not want to read a long document if they can get the answer in ten minutes. Pick the pivot that matches their answer. If they mention a specific problem, use customization. If they mention a tool or process, use implementation. If they are short on time, use the executive summary.
The table is not a script to paste word for word. Use the phrasing as a starting point and change the details to match the document and the prospect's answer.
If the prospect says they are just curious, do not force a call. Send the document and ask one question. You can pivot later when they reply with a real problem.
Customization
- Pivot type
- When you have multiple versions or a long doc
- When to use it
- I have a few versions of this. Which specific challenge are you facing so I send the right one?
Implementation
- Pivot type
- When the content is theoretical but the solution is technical
- When to use it
- The whitepaper covers the what, but the how depends on your current stack. Want to spend 10 minutes on the specifics?
Executive summary
- Pivot type
- When the prospect seems busy or high-level
- When to use it
- It's a long read. I can send the whole thing, or give you the 3 page summary on a quick call?
Handling the just send it pushback
Some prospects will insist on the PDF and refuse the call. If you keep pushing for the meeting, you will look like a typical salesperson and they will block you. Give them what they want but leave a door open for a future conversation.
Attach the file but ask a question about a specific section. This ensures that if they do read it, they have a reason to reply to you. The follow up matters more than the download.
The goal is to keep the relationship open. A person who says just send it may come back after they read it. Your follow up is the second chance.
- 1
Acknowledge and deliver
Send the document as a PDF attachment or link immediately so you do not seem evasive.
- 2
Direct their attention
Mention a specific page or chart. For example, I've attached the PDF. I think the chart on page 5 about churn will be most relevant to your situation.
- 3
Set a follow up
Tell them you will check back in a few days to see if that specific section answered their question.
- 4
Pivot again later
When you follow up, do not ask if they read it. Ask if they want to see how that specific chart applies to their actual data.
Do not send a link to a landing page with a lead form if they have already asked you for the file on LinkedIn. It creates friction and makes you look like you are trying to capture their email.
How to follow up after they read it
Wait a few days, then send one short message. Do not ask if they read the PDF. That question is easy to ignore and puts the work on them. Ask about the problem the document was meant to solve.
Use a specific section or chart as the anchor. It shows you remember the conversation and gives them something concrete to respond to. If they reply with a detail about their process, offer the walkthrough again. If they ignore the message, wait another week and send one more note with a different insight.
If they still do not reply, move on. A person who asked for a document and then went quiet is not a hot lead. Keep them in a lead group for a later campaign, but do not spend your week chasing a download.
Keep the follow up short. Two or three sentences are enough. If you write a long message, it looks like work and gets pushed to later.
Paste this job
Hi Dana, I sent over the ebook on SDR ramp time last week. The section on the first 30 days is the one most teams ask about. Are you seeing new reps take longer than a month to book their first meeting?
Doing this with Kinlead
You can use the Steal Customers agent to find people who are already interested in this type of content by watching competitor company pages and profiles. It identifies people commenting on competitor posts and turns them into leads, keeping the original post URL for context.
Once you have these leads in a group, you can run a campaign to offer your own content. You can set the AI to handle the conversation until a meeting is booked using your scheduling link, or use hand-off mode to step in personally when a prospect asks for a whitepaper so you can pivot them to a call manually.
All replies land in a unified inbox and are classified by intent, so you can prioritize the people who are asking for documentation and are most likely to book a demo.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to handle requests for whitepapers or ebooks.md