---
name: case-study-interview-questions
slug: case-study-interview-questions
description: This skill should be used when the user asks to "interview for a case study", "case study interview questions", "what to ask in a case study interview", "customer interview for case study", "case study questionnaire", "questions for customer success story", "how to conduct a case study interview", "case study interview template", or any variation of preparing, conducting, or structuring customer interviews for B2B SaaS case studies.
category: general
---

# Case Study Interview Questions

The case study interview is where you extract the story, data, and quotes that make a case study persuasive. A bad interview produces vague platitudes ("Great product, highly recommend!"). A good interview produces specific metrics, named challenges, and quotable moments that close deals.

The quality of the case study is 90% determined by the quality of the interview. Get this right and the writing is easy.

## The Interview Framework

### Structure: 4 acts, 30-45 minutes

| Act | Focus | Time | Goal |
|-----|-------|------|------|
| 1. Context | Company background and role | 5 min | Understand who they are so the reader can self-identify |
| 2. Before | The problem before your product | 10-15 min | Extract specific pain, failed attempts, cost of the problem |
| 3. During | Selection and implementation | 5-10 min | Why they chose you, how onboarding went |
| 4. After | Results and impact | 10-15 min | Specific metrics, quotes about impact, what changed |

---

## The Questions

### Act 1: Context (5 minutes)

Set the stage. Make the customer comfortable. Get the facts that help readers self-identify.

| # | Question | Why you're asking |
|---|----------|------------------|
| 1 | "What does your company do, and who do you serve?" | Reader needs to know if this company is like theirs |
| 2 | "What's your role, and what does your team look like?" | Establishes the buyer persona |
| 3 | "How big is the team that uses [product]?" | Helps readers gauge relevance to their team size |

### Act 2: Before — The problem (10-15 minutes)

This is the most important section. The problem creates the emotional hook and the "that's me" moment for the reader.

| # | Question | Why you're asking |
|---|----------|------------------|
| 4 | "Before [product], what were you using to handle [the job our product does]?" | Identifies the status quo they left |
| 5 | "What was broken about that approach? Walk me through a typical week." | Forces specifics about the pain, not generalities |
| 6 | "Can you put a number on the cost of that problem? Time wasted, revenue lost, deals missed?" | Extracts quantifiable pain — this becomes the "before" metric |
| 7 | "What was the moment when you realized something had to change?" | Gets the turning-point story — the best quote often comes from here |
| 8 | "Did you try anything else before finding us? What happened?" | Shows they tried other solutions (makes your solution more credible) |
| 9 | "How did this problem affect other teams or departments?" | Broadens the impact story beyond one person |

**Follow-up probes for Act 2:**
- "Can you give me a specific example of when that happened?"
- "How often was that happening?"
- "What did that cost you, roughly?"
- "How did that make your team feel?"

### Act 3: During — Selection and implementation (5-10 minutes)

| # | Question | Why you're asking |
|---|----------|------------------|
| 10 | "How did you first hear about [product]?" | Attribution data + social proof of discovery |
| 11 | "What other options did you evaluate?" | Shows due diligence (reader is comparing too) |
| 12 | "What made you choose [product] over the alternatives?" | The differentiator — this is gold for sales enablement |
| 13 | "What was onboarding like? How long did it take to get set up?" | Addresses implementation risk (a common objection) |
| 14 | "Was there anything about the transition that surprised you?" | Surfaces honest friction (builds credibility) |

### Act 4: After — Results and impact (10-15 minutes)

This is where you extract the metrics and quotes that make the case study usable by sales.

| # | Question | Why you're asking |
|---|----------|------------------|
| 15 | "What changed in the first 30 days?" | Early wins show fast time-to-value |
| 16 | "What are the specific results you've seen? Can you put numbers on it?" | THE key question. Push for specifics |
| 17 | "How does that compare to where you were before?" | Creates the before/after comparison |
| 18 | "Which metric surprised you the most?" | Gets the headline stat and an authentic reaction |
| 19 | "How has this impacted your team's day-to-day work?" | Personal impact adds emotional resonance |
| 20 | "Would you recommend [product] to a peer? What would you tell them?" | The testimonial quote — let them sell for you |
| 21 | "What's one thing you wish you'd known before starting?" | Honest advice builds credibility |
| 22 | "What are you most excited about going forward?" | Forward-looking quote, shows ongoing value |

**Follow-up probes for Act 4:**
- "What's the exact number?" (push past vague answers)
- "Is that per month, per quarter, per year?"
- "How did you measure that?"
- "Can we share that specific number in the case study?"

---

## Getting Better Answers

### Techniques for specificity

| Problem | Technique |
|---------|-----------|
| Customer gives vague answer ("It's much better now") | Ask: "Can you put a number on that? Even a rough estimate?" |
| Customer gives one-word answer | Ask: "Can you walk me through a specific example?" |
| Customer speaks in generalities | Ask: "What does that look like on a typical Tuesday?" |
| Customer is too positive (no nuance) | Ask: "Was there anything that didn't go as expected?" |
| Customer can't remember the before | Ask: "Think about a specific deal or task from before [product]. How would that same situation go today?" |

### Interview logistics

| Best practice | Detail |
|--------------|--------|
| Duration | 30-45 minutes. Schedule 45, aim to finish in 30 |
| Format | Video call (Zoom/Google Meet). Record with permission |
| Preparation | Send questions in advance so they can pull data |
| Recording | Always record (with consent). Transcribe after |
| Follow-up | Send draft for review within 1 week. Get approval before publishing |
| Incentive | Not required but a gift card or co-marketing offer increases participation |

---

## Turning the Interview into a Case Study

| Interview output | Case study section |
|-----------------|-------------------|
| Company description (Q1-3) | Company profile sidebar |
| Problem description (Q4-9) | "The Challenge" section |
| Best quote about the problem (Q7) | Pull quote in the challenge section |
| Why they chose you (Q12) | "Why [Product]" section |
| Implementation details (Q13-14) | "The Solution" section |
| Specific metrics (Q15-18) | "The Results" section — headline stat + 3-5 supporting metrics |
| Testimonial quote (Q20) | Pull quote in results section or social proof on website |
| Before/after comparison (Q17) | Results table (before → after for each metric) |

---

## Pre-Interview Checklist

- [ ] Customer agreed to participate and publish date discussed
- [ ] Interview scheduled for 30-45 minutes via video call
- [ ] Questions sent to customer in advance (let them prep data)
- [ ] Recording permission confirmed
- [ ] Customer's company and role researched (don't ask questions you should already know)
- [ ] Specific metrics to ask about identified (based on product usage data)
- [ ] Interviewer knows the customer's product usage (check CRM, usage data)
- [ ] Draft review process explained to customer (they'll approve before publishing)
- [ ] Legal/marketing approval process for naming the customer confirmed
- [ ] Thank-you follow-up planned (gift card, co-marketing offer, or simple thank-you)

---

## Anti-Pattern Check

- Asking "Are you happy with our product?" → Yes/no questions produce yes/no answers. Ask open-ended questions that force stories and specifics: "Walk me through a typical week before and after [product]"
- Not pushing for numbers → "It's much better" is not a case study metric. Push: "Can you estimate by how much? Even a rough percentage?" The specific number is what makes the case study persuasive
- Sending questions during the interview (no advance notice) → Customers need time to pull data and remember specifics. Send questions 3-5 days before the interview
- Not recording the interview → You'll miss exact quotes, specific numbers, and nuance. Always record with consent and transcribe afterward
- Writing the case study without customer review → Misquotes or inaccurate metrics damage trust and risk the customer relationship. Send the draft for review before publishing
- Only interviewing the champion → The champion sold internally, but the end user has the day-to-day impact story. Interview both if possible — the champion for the business case, the user for the workflow impact