How to handle prospects asking for more info first

Stop losing LinkedIn leads to generic PDFs. Use the snippet and pivot framework to give real value and move the prospect toward a discovery call.

Get started

Short answer

When a prospect asks for more info, they're usually checking whether you're a spammer or avoiding a call. Don't send a deck. Send one specific result that proves you understand their problem, then ask a qualifying question to move back toward a discovery call.

Why send me more info is usually a soft no

When a lead asks for more information, it feels like a win because they replied. Often it's a polite way to end the conversation without committing to a meeting. The request costs them nothing and gets you off their screen for a few days.

If you send a full company deck or a long feature list, you hand them everything they need to disqualify you without ever talking. A PDF is a dead end. The prospect skims it for ten seconds, finds a feature they don't need or a price they don't like, and stops replying. You also lose the one thing that was working in your favor: their curiosity about how you would handle their specific problem.

Treat the request as a signal rather than an instruction. Something in your first message made them curious enough to reply and not curious enough to book. The job now is to close that gap in two or three sentences.

There is one case where sending the document is right. If the prospect has already told you what they need to see, and it is a specific thing like a security page or a sample report, send exactly that and nothing else.

The PDF dump

  • Sure thing! Attached is our full 15-page company overview and product roadmap.
  • Here is a link to our website and a PDF explaining everything we do.
  • I've attached a deck that covers our pricing, features, and case studies.

The value snippet

  • I can certainly do that. Most agencies I work with are struggling with X, so we focus on Y to get Z result.
  • Happy to. To make sure I send the right info, are you more focused on reducing cost or increasing speed right now?
  • I'll send over a quick example of how we helped a similar team solve X, then we can see if it fits your setup.

The snippet and pivot framework

Your reply has three jobs: confirm you will send something, prove you understand their world in two sentences, and ask a question only they can answer. Do all three in under 60 words. Long replies read like a pitch.

The chat exists to earn the 15 minute call. Whatever you send afterwards should point back to that call, so the prospect reads it as context for the conversation rather than a substitute for it.

Write the snippet before you write the question. If you cannot describe a result in two sentences, you do not have one yet, and the prospect will hear that.

  1. 1

    Acknowledge without desperation

    Confirm you can provide the info. Don't say you'd be honored to send it. Keep it professional and brief.

  2. 2

    Share one specific outcome

    Give a two sentence explanation of how you solve a problem specific to their job title. Focus on the result, not the feature.

  3. 3

    Ask a qualifying question

    Ask about their current process or a specific pain point. This forces them to engage with their own problem rather than your brochure.

What the snippet should say, by job title

The snippet has to sound like it was written for their job, not their industry. A founder cares about a number. A head of sales cares about what their reps do on Monday morning. Pick the version that matches the title on their profile.

Keep it to one example. Two examples turn into a brochure.

If you don't know their title, use the version that fits the problem you opened with. Guessing wrong is worse than being general.

Founder or CEO

Who you're talking to
One number from a company their size, and the change that produced it
What the snippet should contain
Whether that gap is on their list this quarter

Head of sales

Who you're talking to
How you shortened the gap between a lead arriving and someone contacting them
What the snippet should contain
How their team tracks leads today

Marketing lead

Who you're talking to
How you turned existing traffic into booked calls without new spend
What the snippet should contain
Which channel they would fix first if they had a free week

Ops or RevOps

Who you're talking to
How you removed a manual step from their handoff
What the snippet should contain
Where the handoff breaks most often

Agency owner

Who you're talking to
How you kept a client's pipeline full during a slow month
What the snippet should contain
Whether they are carrying that risk themselves right now

Real examples of the pivot

The move from snippet to question has to feel like the next sentence, not a turn in the conversation. If the prospect answers your question, they have described a problem out loud. That is the moment to suggest the call.

Here is what it looks like with a head of sales at a 40 person agency.

Example

  1. Prospect

    Can you send more info?

  2. You

    Sure. Most head of sales I talk to are struggling with lead quality. We usually fix that by scoring leads based on intent, which stops the team from chasing dead ends. Are you currently using a manual spreadsheet to track your leads?

  3. Prospect

    We use a spreadsheet but it is a mess and takes too long to update.

  4. You

    That is a common headache. Would it make sense to spend 15 minutes showing you how we automate that update process?

Notice the question is about their process. The prospect can answer it without knowing anything about what you sell, which is why they answer at all.

Handling the just email me pushback

Some prospects will insist on email. They might be in a meeting, or they genuinely prefer reading. Fighting it makes you look pushy. Agreeing and sending a brochure loses the lead.

Agree, then narrow what you send. Say you will put together one example close to their situation and ask the single detail you need to pick the right one. That question is the pivot. It is small enough to answer from a phone.

The email itself should be short enough to read on a lock screen. One result, one line on how it happened, one question with a day attached.

Never send a 'here is the info' email with no question in it. End with one short question so the thread stays open.

Paste this job

Subject: Example of [Result] for [Company Name]

Hi [Name],

As promised, here is a quick breakdown of how we helped [Similar Company] achieve [Specific Result] in [Timeframe].

We did this by [One sentence on method].

Since every setup is different, would you be open to a brief chat on Tuesday to see if this approach works for your current workflow?

Best, [Your Name]

What to do when they go quiet after you send it

Most prospects who ask for information and get it will not reply. That is normal and it is not a reason to send a message asking whether they got it.

Wait a few days, then send something new. Reference the example, add a detail they did not have, and ask a different question from the first one. Two follow-ups like that is usually the limit before you park them and move on.

Parking them means moving them to a group you revisit in a quarter. Their situation changes, and the example you sent may be the thing they remember when it does.

The follow-up that works gives them a reason to reply that has nothing to do with your calendar.

The nudge that gets ignored

  • Just checking in, did you get the deck I sent?
  • Following up on my last email.
  • Any thoughts on the information I shared?

The follow-up that adds something

  • One thing I left out of that example: the team cut their update time from a day to an hour by removing the manual step. Is that still a problem on your side?
  • I found the note I mentioned. The part that mattered was how they handled leads nobody had touched in 30 days. Do you have a rule for those?
  • Sending this in case it is useful: the same approach applied to a smaller team. Worth 10 minutes next week?

Doing this with Kinlead

Kinlead writes replies from the campaign's goal, tone and an optional sales playbook, which is your own script. Put your snippet and pivot in the playbook and the AI has something specific to say when a prospect asks for more information.

Each campaign chooses how replies are handled. Hand the conversation to you at the first reply, let the AI reply until there is real interest, or let the AI reply until a meeting is booked on your scheduling link. If you want to read everything and approve nothing, use hand-off mode and watch the thread in the unified inbox.

Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to handle prospects asking for more info first.md