# How to respond when a prospect asks for a case study
> Stop sending generic PDFs on LinkedIn. Learn how to qualify a request for a case study to send targeted proof that actually books meetings with buyers.
- HTML: https://getkinlead.com/respond-to-prospect-asking-for-case-study
- Markdown: https://getkinlead.com/respond-to-prospect-asking-for-case-study.md

**Short answer:** When a prospect asks for a case study on LinkedIn, don't send a generic PDF. Ask them which specific problem they are trying to solve first. This lets you send a targeted example that proves you can solve their exact pain point, which increases the chance of a meeting.

## Why generic case studies fail

Most people answer a request for proof by sending their most impressive PDF. It's usually the document about their biggest client. The prospect wants to see their own situation in the story. Your biggest client is rarely the right mirror.

When a prospect skims a generic case study, they look for reasons it doesn't apply. If the company size is different or the industry is slightly off, they dismiss the result as a fluke. You lose the chance to show you understand their specific problem.

The goal of a case study in a LinkedIn chat is to create a bridge to a discovery call. You do that by narrowing the focus until the proof feels inevitable for their situation.

A generic case study also invites the wrong conversation. The prospect asks about the client in the PDF, not about their own problem. You end up defending a result from two years ago instead of learning what they need today.

**The data dump**

- Sending a link to a general 'Our Work' page
- Attaching a 10 page PDF without a summary
- Saying 'Here is our best case study' and stopping

**The targeted bridge**

- Asking for the specific goal before sending
- Sending a 3 sentence summary of a relevant result
- Linking to one specific example that mirrors their pain

## Ask one question before you send anything

When a prospect asks for a case study, they're giving you an opening to qualify them. Use it to find out what's actually broken in their business.

A clarifying question shifts the dynamic from a vendor providing a brochure to a consultant diagnosing a problem. The eventual case study feels like a solution instead of a sales pitch.

Keep the question binary or focused on two common pain points. That makes it easy to answer quickly on mobile. If you ask 'what are your biggest challenges?' you'll get a vague answer or silence.

- **them:** Do you have any case studies for this?
- **you:** I have a few. To send the one most relevant to you, are you more focused on reducing churn or increasing lead velocity right now?
- **them:** Definitely churn.
- **you:** Got it. Here is how we helped a 40 person agency in your space cut churn over ninety days (Link).

## How to package the proof

Most prospects won't open a PDF or click a link to a long page if they don't know what they're looking for. Sell the result inside the chat window first.

The summary should follow a strict Problem, Action, Result format. The prospect sees the value without leaving the conversation. If the summary hits home, they'll read the full document to see how you did it.

Once you deliver the proof, pivot back to their timeline. That prevents the conversation from stalling after the 'thank you' message.

Keep the summary short enough to read on a phone. Three sentences is the limit. If you can't fit the result into three sentences, you don't understand the result well enough to send it.

1. **Write a three sentence summary.** State the specific problem the client had, the one main action you took, and the measurable result achieved.
2. **Attach the proof.** Provide the link or PDF only after the summary has established the relevance.
3. **Ask about their timeline.** End with a question like 'Are you looking to fix this before the next quarter?' to keep the momentum.

## When they ask for everything

Some prospects push back and ask to see all your work or a full portfolio. That's often a deflection tactic to avoid a call, or a sign they're just browsing.

Avoid the urge to send a folder of documents. A data dump makes you look like a commodity vendor. It also gives the prospect too many options to find something they don't like, which creates unnecessary friction.

Frame your refusal as a way to save their time. Position yourself as the filter who ensures they only see what matters.

> If a prospect insists on seeing everything, they're usually not yet convinced of your value. Stop sending documents and try to book a five minute call to narrow down the selection for them.

```
I have a library of examples, but to save you from digging through a dozen PDFs, I want to pick the two that match your current setup. Do you have five minutes tomorrow to tell me about your stack so I can send the right ones?
```

## What to do when you don't have a formal case study

Plenty of good sales teams don't have a polished case study for every situation. You can still send proof. A screenshot of a result, a one line quote from a customer, or a before and after number works in a chat.

The key is to match the proof to the question. If the prospect asks about implementation speed, send a timeline. If they ask about ROI, send a cost comparison. Don't send a general document when a specific fragment answers the question.

Be honest about what you have. Say 'I don't have a written case study for that industry, but I have a client with the same problem who saw this result.' Prospects respect the direct answer more than a padded PDF.

If you have a case study that's close but not exact, say so. 'This client was in a different industry but had the same routing problem' is more useful than pretending the match is perfect.

| | Proof type | When it works | What to send |
| --- | --- | --- | --- |
| A named case study | Prospect has the same problem and a similar company size | Three sentence summary plus a link |
| A single result screenshot | Prospect needs to see the number, not the story | Cropped dashboard image with the client name hidden |
| A customer quote | Prospect trusts peers more than vendors | One line quote with role and company type |
| A before and after | Prospect is stuck on whether change is possible | Two numbers side by side in the chat |

## Following up after you send the proof

Don't ask 'did you read it?' That puts the prospect on the spot and invites a polite no. Ask a specific question about the result instead.

Wait two days, then send a short message that connects the case study result to their situation. If they don't reply, you can try one more time with a different angle, then move on.

The follow up should be about their decision, not your document. 'Is that result something you'd consider a win for your team right now?' is better than 'Any thoughts on the case study?'

If they say the case study was helpful but they need to think about it, ask what would make the decision easier. That question often surfaces the real objection, which is rarely about proof.

- **you:** The agency in that example cut churn after they fixed onboarding. Is onboarding the part that's leaking for you right now?
- **them:** Partly. We also have a problem with renewals.
- **you:** That's useful. The same client had a renewal playbook. Want me to send the two slides that cover it?

## Doing this with Kinlead

Kinlead finds people who match your customer profile and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept. That means the case study requests you get are more likely to come from people who resemble your best clients.

You can set a campaign to hand the conversation to you at the first reply. When a prospect asks for proof, the message lands in the [unified inbox](/features/unified-inbox) and you can send the targeted example and the qualification question yourself.

Kinlead sends outreach at a human pace. Each LinkedIn account sends at most one action every 5 minutes, inside the daily limits you set and inside a send window in the lead's time zone.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [Pricing plans](https://getkinlead.com/pricing.md)

## Common questions

**Should I send a link or a PDF?**

Links are better because you can track if they clicked and you can update the content. Only use PDFs if the prospect explicitly asks for a file they can share internally.

**What if I don't have a case study for their specific industry?**

Focus on the problem, not the industry. Say, 'I don't have a client in [Industry], but I have a client with the exact same [Problem] who saw [Result].'

**How do I handle a prospect who ignores the case study after I send it?**

Wait two days and send a short follow up asking if the result in the case study is something they would consider a win for their team right now.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
