All field notes
Craft 6 min read

Client Interview Questions for Case Studies: 15 That Work

Client interview questions for case studies: 15 prompts across discovery, story arc, recording, and repurposing to surface quotable numbers fast.

In short

A case study interview is not a testimonial interview. Testimonials capture a moment; case studies capture a story with a beginning, a decision, and a measurable end. These 15 questions walk a client through discovery, decision, and results, and one recorded interview produces the written case study, pull quotes, and short video clips.

A testimonial answers "did it work?" A case study answers "how, for whom, and by how much?" The difference is the interview. Testimonial questions capture a moment; case study questions capture a story with a beginning, a decision, and a measurable end.

The mistake most teams make is running a testimonial interview and calling the transcript a case study. You get five minutes of praise and no story. A case study needs the discovery context (what was broken, what else they tried), the decision narrative (why you, what almost stopped them), and results with numbers the client can defend.

For short testimonial clips, see our 7 video testimonial questions. What follows is the deeper interview for written and video case studies.

The 3-part case study story arc#

Every case study follows the same arc, whether it ends up as 800 words or a 3-minute video:

  1. Discovery (the before): What specific challenge was the client facing, and what had they already tried?
  2. Decision and experience (the pivot): Why did they choose you, what almost stopped them, and how did implementation go?
  3. Results (the after): What measurable outcome or relief did they achieve, and what changed day to day?

Structure the interview in this order. Clients tell better stories chronologically, and you need the before on record before the after makes sense.

Discovery: questions that surface the before state#

These establish credibility and give prospects someone to recognize themselves in.

1. "Can you introduce yourself, your role, and your business?"#

Sets the baseline. Whether you're selling B2B software, running a clinic, or offering coaching, prospects need to see someone in their world before they'll trust the story.

2. "What did your workflow or situation look like right before you found us?"#

Highlights the baseline struggle before your solution entered the picture. Push for a specific scene, not a general complaint.

3. "What other solutions or workarounds had you tried, and why didn't they work?"#

Positions your product as the definitive answer after failed alternatives. This also surfaces competitor names you can reference (carefully) in sales conversations.

4. "What was the single biggest challenge that made you seek out a new solution?"#

Zeroes in on the core pain point that forced a decision. In the written case study, the answer to this becomes your opening paragraph.

Story arc: questions that build the narrative#

These carry the middle of the case study: the decision, the experience, and the concrete results.

5. "What almost stopped you from choosing us?"#

The objection-buster. When a client voices a hesitation and explains how it was resolved, it reassures the exact prospects sitting on the same doubt right now.

6. "Why did you choose us over the other options you evaluated?"#

Forces the client to state your differentiation in their own words. This is usually your best pull quote.

7. "How easy was it to get started, and what surprised you about the process?"#

Covers implementation honestly. Prospects evaluating you are anxious about onboarding; a client saying "we were live by Friday" does more than any feature list. The surprise follow-up surfaces value you didn't know you delivered.

8. "Can you share a specific result, number, or time saving since working with us?"#

Specificity converts. "It saved us 10 hours a week" beats "it saved us time" in every placement. If the client doesn't have a number ready, ask them to look one up after the call. Most will.

9. "What would you tell someone on the fence about trying us?"#

Speaks directly to high-intent readers. This answer usually becomes the closing paragraph of the written case study.

10. "How has day-to-day life or business changed since using our solution?"#

Connects the rational benefit to emotional relief. Case studies that only report metrics read like vendor copy; one line about reduced stress makes the numbers believable.

11. "What did the first 30 days look like after you started?"#

Implementation detail that most case studies skip. Prospects want to know what the ramp actually felt like, not just the steady state.

Closing: questions that sharpen the story#

12. "Who would you recommend this to, and why?"#

Defines your audience through client endorsement. Their answer tells the next prospect whether this story is about them.

13. "If you had to describe the outcome in one sentence, what would it be?"#

Generates the headline for the case study page and short clips for social.

14. "Is there anything you'd warn someone about before they start?"#

One honest caveat makes the whole case study more believable. Readers discount perfect stories; a small warning signals the rest is real.

15. "Can we follow up in six months for an update?"#

Plants the seed for a sequel. Updated case studies with longer-term results are rare and disproportionately persuasive.

Recording: capturing the interview well#

You have two options: live or asynchronous.

Live (20 to 30 minutes on a call) is better when the story is complex or the client is a strong talker. Record with consent, transcribe with any decent tool, and let the client talk. Your job is follow-ups, not questions: "say more about that," "what did that cost you," "how did you measure it."

Asynchronous (a link with the questions on screen) works when the client is busy or camera-shy. They record answers in their browser on their own time, with no scheduling. With Proofly, you put 3 to 5 of the questions above into a collection link, the client records in the browser with no login, and you get video plus a transcript to work from.

Either way: send the questions a day ahead, tell the client which numbers you'd love them to look up, and get explicit consent to publish before you record.

Repurposing: one interview, five assets#

One good case study interview produces:

  1. The written case study (600 to 1,000 words): discovery, decision, results, one pull quote. Lives on your site and goes out as a PDF in sales conversations.
  2. Two or three pull quotes: the differentiation line (Q6) and the results line (Q8) go on the landing page.
  3. A 60 to 90 second video cut: the before (Q2), the decision (Q6), the result (Q8). Embed it on the same page as the written version.
  4. A sales deck slide: one client, one quote, one number. Swap per prospect segment.
  5. Social clips: 15 to 30 second answers (Q7's surprise, Q9's recommendation) perform well as standalone posts.

For the format decision (when a short video beats a written case study and vice versa), see our guide to customer success story tools.

Common questions

How is a case study interview different from a testimonial interview?

A testimonial interview produces a 60-second clip for a landing page. A case study interview produces a structured story: the situation before, why they chose you, what implementation was like, and the measurable result. The questions go deeper on context and numbers, and the interview runs 20 to 30 minutes instead of 5.

How long should a case study interview run?

Twenty to thirty minutes. Shorter than that and you miss the discovery context that makes the story believable. Longer than that and the client starts repeating themselves. Send the question list a day ahead so the client can look up any numbers you need.

Should I record the case study interview on video?

Yes, whenever the client agrees. One recorded interview gives you the transcript for the written case study, pull quotes for the landing page, and short clips for social and sales. If the client won't go on camera, record audio and transcribe it; the questions work the same.