Objection handling

Handling the "Send Me a Case Study" Objection

Sometimes genuine proof-seeking, sometimes a graceful exit. Either way, a random case study emailed into the void does nothing — the value is in sending the RIGHT one and booking what happens next.

"Send me a case study"
Why prospects say it

Buyers ask for case studies to reduce risk (show me it worked for someone like me) or to end the call politely. The failure mode is sending a generic success story that doesn't match their situation, then waiting. A relevant case study tied to a scheduled follow-up turns proof into momentum; an untethered one just closes the call.

How to handle it

  • Welcome it, then qualify so you send a genuinely relevant case, not a generic one.
  • Ask which outcome matters most so the case study speaks to their situation.
  • Confirm what would make it convincing (their sector, size, or problem).
  • Attach a scheduled follow-up so the case study leads somewhere.
  • If they can't say what would convince them, test whether it's a soft brush-off.

What you can actually say

Happy to — I've got a few. So I send the right one, is your situation closer to [scenario A] or [scenario B]?
Sure. What would you most want it to prove? I'd rather send the one that speaks to your case than a generic win.
I'll send it today. Can I call you Thursday to hear if it resonates, or raises questions?
Absolutely. Which matters more to you — the [result X] or how they got there? I'll pick the case that shows that.

What to avoid

Don't fire off a generic case study and call it progress — an irrelevant proof point emailed with no follow-up just ends the conversation.

How Tepio helps with this one

Tepio's brief tells you this company's sector and likely pain, so you can promise the case study that actually matches them instead of a random one.

Ready to call better?

Open your workspace and run your first Flash Call today. 14-day trial, no credit card.

Try free