# How to handle a case study request in a niche you don't have
> Learn how to respond when a LinkedIn prospect asks for a case study in their niche and you don't have one. Pivot from industry to problem patterns.
- HTML: https://getkinlead.com/handle-prospect-asking-for-case-studies-by-industry
- Markdown: https://getkinlead.com/handle-prospect-asking-for-case-studies-by-industry.md

**Short answer:** When a prospect asks for a case study from their industry and you don't have one, don't apologize or send a generic deck. Name the problem they described, match it to a result from a different sector where the same thing was broken, and ask a small question that lets them say yes.

## Stop hunting for an exact industry match

Most founders treat a case study request like a test they're failing. The prospect names their industry, you don't have a logo from that industry, and the pause before you reply feels like the deal slipping. So you send a general overview and hope the rest of the conversation carries it.

Buyers ask for a case study because they want the risk reduced. They want evidence that someone with their problem got out of it. Industry is the easiest filter to say out loud, which is why they say it. It's rarely the filter that decides anything.

The move is to answer the request honestly and then change the axis of comparison. You're not refusing to give proof. You're offering proof that matches the thing that will actually make them buy.

**What most people send**

- Sorry, we haven't worked with many HVAC companies yet, but here's a general overview of what we do.
- We don't have a case study for your niche, though we've done a lot in the broader home services space.

**What works better**

- I don't have an HVAC case study. I have a plumbing supplier with the same problem you just described, quotes going out fine and nothing coming back. Want the paragraph on what changed?
- The client was in a different sector and the bottleneck was the same one you have. If the fix doesn't map to your setup, I'll tell you on the call.

## Map the problem instead of the industry

Write the request down with the industry word taken out. You're looking for the mechanism: what breaks, in what order, and what it costs. Slow onboarding at a clinic and slow onboarding at a software company lose money in the same place, in the gap between signature and the first useful week. If your fix was about closing that gap, the story travels.

Match on the mechanism, then use the prospect's own words for the problem before you name your client. People keep reading when their own sentence comes back at them.

If a row in the table below has nothing in it, you don't have proof for that problem yet. Say so and offer a different kind of evidence instead of stretching a story that doesn't fit.

| | The industry they named | The problem underneath | Where you may have solved it |
| --- | --- | --- | --- |
| SaaS | Churn inside the first 90 days | Onboarding at a clinic or a gym chain |
| Manufacturing | Too many unqualified demo requests | Qualification work at an agency |
| Logistics | Staff leaving in year one | Retention at a services firm |

## A reply you can send today

Keep the first reply short. No attachment, no link, no PDF in the message. It gets read on a phone, and a wall of text reads like a brochure.

Do four things in order: say what you don't have, name the matching problem, give the result in a sentence, and ask a question they can answer with one word.

- **them:** This looks interesting. Do you have any case studies for companies in logistics?
- **you:** Not logistics. I have one from a staffing firm that spent a year losing warehouse staff inside the first ninety days, which sounds close to what you described with the depots.
- **them:** Staffing is a fair bit different from freight, though.
- **you:** Different sector, same cause: new hires weren't getting a real conversation with a manager until month four in both cases. What changed was the check-in schedule and who owned it, not the hiring.
- **you:** Want the two page write up? It's the fix I'd start with at your depots, and you can tell me where it breaks.

```
I don't have a case study from [their industry].
I do have one from [another industry] where the problem was the same one you described: [problem in their words, one line].
[What changed, one line. No invented numbers.]
Want the short version, or would a call be faster?
```

## What to say when they insist their industry is different

Some prospects push back no matter how clean the match is. Usually the industry claim is a risk objection in a costume. They've been burned by a vendor who didn't understand their world, and naming the industry is how they check whether you'll bluff.

Don't argue. Ask which part is different, then answer only that part. If payroll cycles or compliance reviews change how they buy, say how your approach handles it. If the difference turns out to be surface level, they'll hear it in their own answer.

1. **Agree with the part that's true.** Say plainly that their industry has its own rules. Skipping this makes everything after it sound defensive.
2. **Ask them to name the exact difference.** 'Which part of this do you think wouldn't carry over?' Most people name one thing, and one thing is answerable.
3. **Separate the rule from the workflow.** Show where the industry rule stops and the day to day work starts. Your fix usually lives in the second part.
4. **Ask what would have to be true.** 'If we ran a version of this on one team for six weeks, what would you need to see to call it working?' That turns an objection into a test.

> Never argue that their industry isn't unique. Ask which part is unique and answer only that part.

## Proof that works when you have none from their niche

A case study is one format for proof, not the only one. Keep three or four of these ready and a niche request stops being a problem.

Two rules hold across all of them. Don't dress up a different industry as if it were theirs, and don't invent a number to make the story land. Buyers forgive a gap in your portfolio. They don't forgive a made up result.

- A result from any sector with the same mechanism, told in three lines: what was broken, what changed, what happened after.
- A screen recording of the thing working on a real account, with names and numbers blurred. People trust a live screen more than a designed PDF.
- A reference call with a client from a different industry who will talk about the problem rather than the sector. Set the expectation before you make the intro.
- A scoped pilot on one team with the success measure written down before it starts. This is proof you build together instead of proof you dig up.
- A public teardown or post where you solved the same problem in the open. It's proof you can link to without a logo attached.

## Should you go and build the case study they asked for

Sometimes the honest answer is yes. If three prospects from the same niche ask for the same proof in a month, that's a gap worth closing and a hint about where your next customers sit.

It's faster to get than most founders expect. Ask a current client for fifteen minutes about one outcome, not for a testimonial. Come with a specific question: what changed after the onboarding rebuild, and where did it show up first? Write four hundred words, send them the draft, and publish only what they approve.

Logos and figures take longer than sentences. Start with the sentence and you'll have something to send this week, then let the numbers catch up.

> Ask for the story, not the testimonial. A specific question about one result gets answered. A request for praise gets ignored.

## Doing this with Kinlead

The problem match only works if you can find people already describing the problem. The [Steal Customers](/features/steal-customers) agent watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns the commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about, and what they commented, which is often the problem in their own words.

That gives you a specific first line for a connection note, which is why the note can open with why that person became a lead. Once someone answers, replies from every campaign land in one [unified inbox](/features/unified-inbox) sorted by intent, so a case study question doesn't sit behind thirty connection acceptances.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I make up a case study if I don't have one?**

No. A fabricated result is the fastest way to lose the deal and the relationship. Say you don't have a match from their industry, then offer a real result from a different sector where the same problem was fixed.

**Is a link or a screenshot better when sending results on LinkedIn?**

A screenshot usually works better in the first message. It shows the proof without asking the prospect to leave the app, and they can react to it in the same reply.

**How do I ask a current client for a niche specific testimonial quickly?**

Ask about one outcome instead of asking for a general testimonial. A question like 'what changed after we fixed the handover, and where did you notice it first?' gets a usable answer in a few sentences.

**What if they go quiet after I say I don't have a case study from their industry?**

The pivot has to happen in the same message as the no. If you already sent a flat refusal, follow up once with the matching problem and one sentence on what changed for that client, then leave it.

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