"Send me some case studies": diligence or stall? The answer decides your next move

Objection Handling Playbook · September 11, 2026

How do you handle "can you send references or case studies?" First find out what the proof is for: "Absolutely, what would a convincing case study need to show for this to move forward?" A specific answer (same industry, same team size, a metric) means real diligence, deliver exactly that. A vague answer means the request is a stall wearing a suit, treat the hidden objection instead.

What proof actually does in a deal

Proof doesn't sell. It de-risks. A prospect asking for references is telling you they're past "do I want this?" and into "will I regret this?" That's progress. But generic proof doesn't reduce specific fear: a logo wall means nothing to someone worried their SDR team won't adopt the tool. The reference has to match the anxiety.

The treatment, step by step

Say yes, then aim it. "Of course. So I send the right one, what would it need to show?" The diagnostic question again: specifics = diligence, vagueness = stall.
Match proof to fear, not to industry vanity. Worried about adoption? Send the story about week-four usage. Worried about ROI? Send numbers. The prettiest case study that answers the wrong fear is noise.
If the answer is vague, name the pattern kindly. "Happy to send materials, and honestly, if there's a concern behind the request, I'd rather address it directly. Is something not sitting right?" You'll often get the real objection on the spot.
Never let proof replace momentum. "I'll send it today, and let's book Thursday to walk through how their setup maps to yours." Proof that travels alone gets filed; proof with a meeting attached gets discussed.
When you're new and short on logos, offer live proof. A trial on their own calls beats someone else's testimonial: "instead of trusting another company's story, run three days and write your own."

Prospect: "Do you have case studies from companies like ours?"
Rep: "Yes, and so I pick the right one: what would it need to show to be convincing? Industry match, team size, a specific number?"
Prospect: "Mostly that reps actually use it."
Rep: "Then forget the PDF, let's have your two most skeptical reps try it for three days and you'll have your own answer."

FAQ

What if I don't have case studies yet?

Offer live proof instead: a short trial on the prospect's own calls, with success criteria they define. Early-stage products win on 'measure it yourself'. It's more credible than a polished PDF, not less.

Should I connect prospects directly with existing customers?

For late-stage, high-value deals, yes, a live conversation converts better than any document. Protect your customers' time: reserve intros for deals that have earned them, and brief the customer on what the prospect worries about.

How does Objeq prove itself without a long reference list?

The product demos itself: run the 3-day trial on your team's real calls and judge the whispers live. Your own transcript is the case study.

Handle it live, not in the postmortem

Reading about objections is training. Handling them is a live skill under pressure, which is why Objeq whispers the treatment to your rep during the call, in under two seconds, visible only to them. See pricing or how it compares to Gong.

Start free, 3-day trial

From $99 / seat / mo after the trial · card up front, charged only when the 3 days end · cancel in one click