Case Study Interview AI Prompts for Content Marketers
A case study is only as good as the interview that produces it. The customer conversation is where vague impressions become specific metrics, where general satisfaction becomes a quotable story, and where the marketing team’s assumptions are either confirmed or shattered.
The problem is that case study interviews are hard to run well. Customers are busy. They say things like “it was great” when you need “we reduced churn by 23%.” They tell anecdotes when you need data. They want to talk about everything except what makes your case study compelling.
AI prompts help you prepare for interviews, extract maximum value from each conversation, and transform raw transcript into the material you need for a compelling case study.
TL;DR
- Interview preparation determines interview quality — the time you spend preparing questions determines the quality of answers you receive
- Metrics questions require specific framing — “how did it go?” produces vague answers; “what was your metric before and after?” produces numbers
- Story structure matters more than quotes — a great quote in the wrong context is useless; a complete narrative arc is compelling
- The right question order unlocks honesty — establish rapport before asking for criticism
Introduction
Case study interviews are different from sales discovery calls or customer success meetings. The goal is not to understand the customer’s needs or ensure their success with your product. The goal is to extract the material that will convince future customers to buy.
This shifts the interview dynamic. You are asking customers to talk about results, which requires them to think critically about their experience. You are looking for specific metrics, which requires digging past their initial answers. You are building a narrative arc, which requires understanding not just what happened but why it mattered.
AI prompts help you prepare interview guides, probe for metrics, and extract maximum value from each conversation.
Table of Contents
- Preparing for the Case Study Interview
- The Opening Framework
- Extracting Metrics and Numbers
- Building the Narrative Arc
- Asking for Criticism and Risk Factors
- Post-Interview Processing
- Frequently Asked Questions
Preparing for the Case Study Interview
Preparation is where most case study interviews fail or succeed.
The interview preparation prompt:
I need to prepare for a case study interview with [CUSTOMER NAME]
from [COMPANY].
CUSTOMER CONTEXT:
- Their role: [ROLE]
- Company industry: [INDUSTRY]
- Company size: [SIZE]
- Customer since: [DATE]
WHAT WE SOLD THEM:
- Product/service: [WHAT THEY BOUGHT]
- Implementation date: [DATE]
- Key features used: [FEATURES]
WHAT WE ALREADY KNOW:
- What they told our CS team: [NOTES FROM CS CALLS]
- Any public statements: [IF ANY]
- Metrics they mentioned: [IF ANY]
WHAT I NEED FROM THE INTERVIEW:
1. The specific problem they had before our solution
2. The metrics before and after
3. What made our solution different from alternatives
4. The specific results they achieved
5. A quotable story about the transformation
THE INTERVIEW PLAN:
1. OPENING (5 minutes):
Build rapport and explain the purpose.
What to say: [SCRIPT]
2. CONTEXT SETTING (10 minutes):
Understand their situation before our solution.
Key questions to ask:
- What was your situation before [PRODUCT]?
- What was the cost of the problem you were solving?
- Who was impacted and how?
3. THE DECISION (5 minutes):
Why they chose us over alternatives.
Key questions to ask:
- What alternatives did you evaluate?
- What made [PRODUCT] stand out?
- Who was the decision maker?
4. THE IMPLEMENTATION (10 minutes):
What it was like to implement.
Key questions to ask:
- How long did implementation take?
- What was the hardest part?
- What surprised you?
5. THE RESULTS (15 minutes):
The actual outcomes.
Key questions to ask:
- What metrics can you share?
- What results exceeded your expectations?
- What would you tell a peer considering [PRODUCT]?
6. THE QUOTE (5 minutes):
The memorable soundbite.
Key questions to ask:
- In one sentence, what did [PRODUCT] make possible?
- How would you describe the impact to a peer?
Interviewer notes:
- Do not ask leading questions
- Dig past "it was great"
- Record the call with permission
- Send summary within 24 hours
Prepare specific metric questions for this customer based on their context.The Opening Framework
The interview opening sets the tone for everything that follows.
The interview opening prompt:
I need a script for opening a case study interview.
CUSTOMER: [NAME], [TITLE] at [COMPANY]
OPENING SCRIPT:
"Hi [NAME], thanks for making time for this. I want to start by
explaining what we're doing and why your perspective matters.
We're creating a case study featuring customers like [COMPANY], and
we want to make sure we capture your experience accurately.
This is not a sales call. I want to understand what it was actually
like: the good, the challenging, and everything in between.
Everything you share will be reviewed by you before we publish
anything. You have full approval on quotes and any details that
might identify you.
With your permission, I'd like to record this call so I can focus
on our conversation rather than taking notes. Does that work?
Let's start with you telling me a bit about your role and what
[COMPANY] does."
OPENING FRAMEWORK:
1. PURPOSE: Explain why you are there
2. SAFETY: Make clear they can be honest
3. CONTROL: Set expectations about review and approval
4. PERMISSION: Get recording consent
5. RAMP: Start with easy context-setting questions
After opening, move to:
"The reason I wanted to talk to you specifically is that [REFERENCE
TO THEIR SPECIFIC SITUATION OR USE CASE]. Can you tell me more
about that?"
This focuses them on the relevant story.
Provide the complete opening framework.Extracting Metrics and Numbers
Numbers make case studies credible. Getting them requires specific questioning.
The metrics extraction prompt:
I need to extract specific metrics from a case study interview.
COMMON METRIC CATEGORIES:
1. EFFICIENCY METRICS:
- Time saved: "How many hours per week/month was [TASK] taking before?"
- Process time: "How long did [PROCESS] take before vs. after?"
- Resource utilization: "How many people were doing [TASK]?"
2. FINANCIAL METRICS:
- Cost reduction: "What were you spending on [SOLUTION AREA] before?"
- Revenue impact: "Did this affect revenue? How?"
- ROI: "Do you have a sense of the return on this investment?"
3. QUALITATIVE METRICS:
- Error rates: "How often would [ISSUE] happen before vs. after?"
- Customer satisfaction: "How did [METRIC] change?"
- Employee satisfaction: "How did your team's experience change?"
THE PROBING LADDER:
When a customer says "it was great" or "we improved a lot":
LEVEL 1 - Quantity:
"How much? Can you put a number on that?"
LEVEL 2 - Comparison:
"Compared to before, how much better?"
LEVEL 3 - Specificity:
"Can you give me a specific example?"
LEVEL 4 - Verification:
"If I asked your CFO to pull the numbers, what would I see?"
EXAMPLE INTERVIEW DIALOGUE:
Customer: "The reporting is much better now."
Interviewer: "That's great to hear. Can you help me understand what
'better' means in numbers? What were you looking at before, and
what do you look at now?"
Customer: "Well, we used to spend a lot of time on monthly reports."
Interviewer: "How much time? Was that hours per week, or per month?"
Customer: "Probably about a day every month."
Interviewer: "And now?"
Customer: "Now it takes maybe an hour. We just pull it from the dashboard."
Interviewer: "So that's roughly [20 hours / year] saved. Where does
that time go?"
THE METRIC QUESTION FORMULAS:
For [METRIC AREA]:
- Before: "What was your [METRIC] before [PRODUCT]?"
- After: "What is it now?"
- Change: "By how much did it change?"
- Proof: "Do you have a report or number I can reference?"
For [COMPANY], prepare specific metric questions based on what you
know about their situation. Anticipate answers so you can probe deeper.Building the Narrative Arc
The case study needs structure. Help the interview discover the arc.
The narrative arc prompt:
I need to build a narrative arc for a case study.
WHAT THE CUSTOMER WENT THROUGH:
1. THE BEFORE:
The world before the solution.
- What was broken?
- Who was suffering?
- What did they try before?
Key question: "What was life like before [PRODUCT]?"
2. THE TURNING POINT:
Why they decided to change.
- What triggered the decision?
- Who was pushing for change?
- What alternatives did they consider?
Key question: "What made you decide to do something about this?"
3. THE JOURNEY:
What it was like to implement and adopt.
- What was the process?
- What was hard?
- What surprised them?
Key question: "What was the hardest part of getting started?"
4. THE AFTER:
The world with the solution.
- What changed?
- What became possible?
- What are they doing differently?
Key question: "What did [PRODUCT] make possible that wasn't before?"
5. THE MORAL:
What the story means.
- If they were advising a peer, what would they say?
- What would they do differently if they could go back?
Key question: "What would you tell a colleague who was considering [PRODUCT]?"
FOR [CUSTOMER NAME]:
What is the likely narrative arc based on what you know?
[COMPANY] had [PROBLEM]. They decided to address it when [TRIGGER].
After [IMPLEMENTATION], they now [RESULT].
What specific questions will extract the material for this arc?
- Before questions: [LIST]
- Turning point questions: [LIST]
- Journey questions: [LIST]
- After questions: [LIST]Asking for Criticism and Risk Factors
The most credible case studies acknowledge challenges.
The criticism extraction prompt:
I need to ask for criticism in a case study interview without
damaging the relationship.
WHY CRITICISM MATTERS:
- Case studies that admit challenges are more credible
- Readers trust honest assessments over pure praise
- Risk factors help future customers make informed decisions
HOW TO ASK FOR CRITICISM:
The setup: Frame criticism as valuable feedback.
"Can I ask you a question that might seem odd? What would you tell
someone who was considering [PRODUCT] to watch out for? What are the
things that might surprise them, or that didn't work exactly as expected?"
TYPES OF CRITICISM TO SEEK:
1. IMPLEMENTATION CHALLENGES:
"What was harder than you expected during implementation?"
"What did your team struggle with?"
2. PRODUCT SHORTCOMINGS:
"What would you improve if you could?"
"What features are still missing that you wish existed?"
3. EXPECTATION GAPS:
"What was different from what you expected?"
"What did the marketing or sales process promise that wasn't delivered?"
4. ONGOING CHALLENGES:
"What still isn't perfect?"
"What still takes more time or effort than you'd like?"
HOW TO HANDLE CRITICISM:
When they offer criticism:
1. Thank them: "That's exactly the kind of feedback that helps us improve."
2. Probe: "Can you tell me more about that specific experience?"
3. Quantify: "How significant was that challenge in the overall picture?"
4. Contextualize: "Knowing what you know now, would you still have made the same decision?"
WHAT NOT TO DO:
- Do not become defensive
- Do not explain away the criticism
- Do not move on too quickly
- Do not make them feel bad for being honest
FOR [CUSTOMER NAME]:
What criticism might they offer based on their context?
How should I handle it if they do?
Prepare specific questions for seeking criticism.Post-Interview Processing
The interview is just the raw material. Processing turns it into a case study.
The post-interview processing prompt:
I just completed a case study interview. I need to process the notes
into usable material.
INTERVIEW SUMMARY:
[PASTE INTERVIEW NOTES OR KEY POINTS]
PROCESSING FRAMEWORK:
1. QUOTE EXTRACTION:
Find the best quotable moments:
- Direct statements about transformation
- Specific praise or criticism
- Memorable phrasing
- Emotionally resonant language
For each quote:
- Quote: "[EXACT QUOTE]"
- Context: [WHAT THEY WERE RESPONDING TO]
- Credibility: [STRONG/MEDIUM - WHY]
2. METRIC VERIFICATION:
List all metrics mentioned:
- Metric 1: [STATEMENT]
- Metric 2: [STATEMENT]
For each metric:
- Verified with number: [YES/NO]
- Can be verified: [YES/NO/PROBABLY]
- Need to follow up on: [YES/NO]
3. NARRATIVE GAPS:
What questions remain unanswered?
- [GAP 1]
- [GAP 2]
Follow-up needed:
- Who to contact: [CUSTOMER/INTERNAL]
- Specific question: [WHAT TO ASK]
4. STRUCTURE ASSESSMENT:
Does the material support a clear narrative arc?
- Before: [SUMMARY]
- Turning point: [SUMMARY]
- After: [SUMMARY]
What is the single-sentence story?
5. PUBLICATION READINESS:
- Is there a strong enough quote to headline? [YES/NO]
- Are there specific metrics? [YES/NO]
- Is there a complete arc? [YES/NO]
- What is missing that would make this publishable?
6. APPROVAL NEEDED:
What needs customer review before publication?
- Quotes to verify: [LIST]
- Numbers to verify: [LIST]
- Any sensitive claims: [LIST]
Provide the processing framework output.Frequently Asked Questions
How do I get customers to agree to case study interviews?
The key is timing and framing. Ask during moments of success (right after a win, when a metric improves, when they publicly praise your product). Frame it as helping other customers and the community, not as marketing for you. Make the process easy: offer to work around their schedule, handle all the writing, and give them full approval on everything before publication.
What if the customer cannot provide specific metrics?
If metrics are unavailable, focus on qualitative outcomes. Instead of “reduced churn by 23%,” you might get “our customer success team noticed that customers onboarded with [feature] are much more likely to expand.” While less compelling than numbers, qualitative insights can still make a strong case study. Always indicate when metrics are estimates or impressions.
How do you handle a customer who is not quotable?
Some customers are better on the phone than others. If you have limited quotable material, compensate with strong narrative structure and specific details. A case study can be compelling without a headline quote if the story is complete and specific. Alternatively, ask for a brief email summary they write themselves; sometimes customers express themselves better in writing.
Should you interview the customer or let them review a draft?
The best case studies come from interviews. Customers often surface insights they would not have thought to write down. However, always offer review before publication. Send them the draft with specific questions: “Does this accurately represent your experience? Please flag anything that isn’t right.” Customers appreciate the chance to be accurate, and it protects you from misrepresentation.
How long should the case study interview be?
Thirty minutes is usually sufficient for the core story. You can extend to forty-five minutes if the customer is particularly articulate and has a complex story. Do not exceed sixty minutes; fatigue sets in and the quality of responses drops. If you need more time, schedule a follow-up call rather than extending the first.