Most founders ask for a case study the same way they ask a favor from a friend: vaguely, apologetically, and too early. The customer says "maybe later" and later never comes. Here is the exact script that gets a real answer, plus what to say when the answer is a nervous no.
Why most case study requests get ignored
A vague ask gets a vague answer. "Would you be open to being featured on our site sometime?" gives the customer nothing to say yes or no to. They cannot picture the time commitment, what they would need to say, or who would see it.
The customers who agree are not the ones who like you most. They are the ones who can already picture the specific result they would be talking about. If you ask before they have a number to point to, you are asking them to do your job of finding the story.
Timing matters more than rapport. Send the ask once the customer has hit one measurable outcome, not once you feel enough goodwill has built up. A customer three weeks into onboarding has nothing to say yet. A customer who just cut a process from four hours to twenty minutes has a sentence ready to give you.
The exact email to send
This is the version that works. Keep it under 120 words. Name the specific result you already know about, not a generic compliment.
Subject: Quick ask about the [specific result] you mentioned
Hi [name],
You mentioned last week that [specific outcome, e.g. "your team cut onboarding time from four hours to twenty minutes"]. That's exactly the kind of result other founders considering us want to hear about.
Would you be open to a 20-minute call where I ask you a few questions about it? I'll write it up, send it back for your edits, and nothing goes live until you approve it.
No pressure either way; totally understand if the timing's off.
[Your name]
Three things make this work: it references something the customer already said, not a fishing question. It states the exact time cost up front, twenty minutes, not "a quick chat." And it hands back control, they approve before anything publishes.
What to say when they hesitate
Four objections come up in almost every case study conversation. Each has a specific response, not a general reassurance.
- "I'd need to check with legal or marketing first." Say: "Totally fine, happy to send over a one-page draft outline first so whoever needs to sign off knows exactly what's involved before you loop them in." This turns an open-ended internal approval into a five-minute review of something concrete.
- "I don't want our competitors to see our numbers." Say: "We can use a percentage or a range instead of the raw number, most customers do that and it still lands." Specificity, not precision, is what makes a case study credible.
- "I don't have time right now." Say: "It's 20 minutes on a call, and I'll write the whole thing. You'll only need another 10 minutes to review the draft." Most people picture a case study as an essay they have to write themselves. Correcting that assumption alone flips a no to a yes.
- "What's in it for us?" Say: "A link back to your site from ours, and I'll tag your team on the LinkedIn post when it goes live." Have this answer ready before you ask. Founders who wing this question lose the deal in the silence after it.
What to do after they say yes
Book the call within a week of the yes, while the memory of the result is still fresh and specific. Waiting a month means the customer shows up with a vaguer version of the story than the one that made you ask in the first place.
Send three to five questions ahead of the call so they walk in prepared, not improvising. Ask for one number and one sentence describing what changed day to day, not just the metric. The number gets the click. The day-to-day sentence is what a reader actually remembers and quotes back to their own team.
Send the draft within 48 hours of the call. A customer who agreed to a case study a month ago and still has not seen a draft starts to regret saying yes. Speed is part of keeping the relationship warm enough for the next ask, whether that is a referral, a renewal conversation, or the next case study a year from now.
Frequently asked questions
When should I ask a customer for a case study?
Ask once they have hit one measurable result, not on a fixed timeline like 30 or 90 days. A customer with a specific number to point to converts far more often than one who has simply been a customer for a while.
What if the customer has no hard metrics to share?
Ask for a before-and-after description instead of a number. A specific change in how their day looks, fewer manual steps, one less tool open, is still concrete enough to carry a case study.
Should I offer an incentive for agreeing to a case study?
It is not required, but a genuine offer, a co-marketing link, an early look at your roadmap, or a discount on renewal, removes the "what's in it for us" hesitation before it becomes a reason to stall.
How long should the case study interview take?
Twenty to thirty minutes. Longer than that and you are asking the customer to do research on themselves instead of just answering questions you already prepared.
What if they agree but then go quiet before the call?
Send one short follow-up referencing the original result you mentioned, not a generic "just checking in." A specific reminder gets a faster response than a polite nudge.
Can I publish a case study without using the customer's real name?
Yes. An anonymized version with a specific industry and result still performs better than a named case study with vague numbers. Ask which the customer prefers before you draft anything.
Getting one great case study is worth more than three vague ones nobody trusts. Send the ask this week, while your last successful customer's result is still fresh enough for them to describe it in one sentence.