30 Case Study Interview Questions, and What Each One Gets You

Image URL

Do not index

AI summary

A concise guide to conducting case‑study interviews: 30 questions are organized into five story stages (identity, before, decision, after, result), each with the main question, the expected answer shape, and a follow‑up for thin responses; most users should pick a minimal set of 6–8 questions—typically one from each stage—to avoid overwhelm, use the rescue follow‑ups when needed, and focus on concrete, measurable answers that illustrate the customer’s journey and outcomes.

Title

30 Case Study Interview Questions, and What Each One Gets You

Date

Description

30 case study interview questions grouped by story stage, each with the answer it's designed to produce and a follow-up when it comes back thin.

Status

Current Column

Person

Writer

You have a customer who said yes. You have a blank question set. You have no idea which questions actually return something you can publish.

Most question lists are just that — lists. Thirty items with no guidance on what each one is supposed to produce. You send fifteen, get back a paragraph of "things were fine," and wonder which question failed.

This page is different. 30 questions, grouped by story stage. Each one paired with the answer it is designed to return and a follow-up when it comes back thin.

If you want the full system — pick, invite, collect, write, approve — start with our guide to customer case studies. If you want the six-question minimal set with no-call mechanics, that is running a case study interview without a call. This page is the expanded toolkit.

How to read these

Each question has three parts:

The question — copy-pasteable, designed for async (email, form, or voice prompt)

Returns — the specific answer shape it should produce

If thin — a rescue follow-up when the first answer is generic

Do not send all thirty. Pick 6–8 per interview. The groupings help you decide which stages need depth.

1. Who they are (questions 1–6)

The identity section. A stranger should be able to place this person in one glance.

1. Who are you, and what do you actually do day to day?

Returns: Name, role, company, and one sentence a reader can self-identify with. "[Name], marketing" is not enough. "[Name], the person who owns outbound at a 12-person agency" is.

If thin: "You said [role] — can you say what that actually looks like on a normal Tuesday?"

2. How big is your team, and where do you sit in the org?

Returns: Size and context. A solo founder and a marketing manager in a 200-person company face different problems.

If thin: "Is it just you, or is there a team? Who do you hand work off to?"

3. Who are your customers?

Returns: The customer's customer. Useful when the case study needs to show industry relevance.

If thin: "If you had to describe a typical customer in one sentence, what would you say?"

4. What were you responsible for when you started using [Product]?

Returns: Scope at the moment of decision. Responsibility often expands after a tool lands; this pins the starting point.

If thin: "What was on your plate that quarter — and what were you measured on?"

5. How long have you been using [Product]?

Returns: Timeline. A two-week user and a two-year user tell different stories.

If thin: Rarely thin. If they do not remember, a month or a quarter is honest enough.

6. How did you hear about us?

Returns: Acquisition channel. Useful for marketing but also for framing — "found us on G2" and "a friend sent me" set up different narratives.

If thin: "Was it a search, a recommendation, or something else?"

2. The before (questions 7–12)

Without a before, the rest is praise. This section establishes what was broken.

7. What were you doing about [task] before [Product], and what was broken about it?

Returns: The prior state and the pain. This is the setup for the entire case study.

If thin: "You said [prior tool or process] — what specifically kept going wrong?"

8. How were you handling [task] before you found us?

Returns: The manual or legacy method. Spreadsheets, email threads, "I just remembered."

If thin: "Walk me through what that looked like — what did a normal week involve?"

9. What made you start looking for something different?

Returns: The trigger moment. A deadline, a missed goal, a process that finally broke.

If thin: "Was there a specific moment when you thought 'this has to change'?"

10. What was the cost of not solving this?

Returns: Stakes. Time, money, stress, churn, missed opportunities.

If thin: "If nothing had changed, what would last quarter have looked like?"

11. How much time did the old way take?

Returns: A number, ideally. "Four hours a week" is publishable. "Too long" is not.

If thin: "Can you estimate — even roughly — how many hours per week or per project?"

12. What had you tried before that did not work?

Returns: Failed alternatives. Useful for comparison framing without naming competitors negatively.

If thin: "Were there other tools or approaches you ruled out, and why?"

3. The decision (questions 13–17)

Why they picked you. This section surfaces objections your prospects are having right now.

13. What almost stopped you from picking us?

Returns: The objection they got over. Put this sentence next to your pricing button.

If thin: "Was there anything that made you hesitate — price, timing, a missing feature?"

14. What convinced you to try us instead of [alternative]?

Returns: Differentiator from the customer's perspective, not yours.

If thin: "What was the deciding factor in the end?"

15. What did you need to believe before you could say yes?

Returns: The proof they looked for. Reviews, a demo, a trial, a referral.

If thin: "Did you need to see something working before you committed?"

16. Who else was involved in the decision?

Returns: Buying committee context. Useful for B2B targeting.

If thin: "Did you decide on your own, or did someone else need to sign off?"

17. How long did it take from 'maybe' to 'yes'?

Returns: Sales cycle length from the buyer's side.

If thin: "Roughly — weeks, months, or was it a same-day decision?"

4. The after (questions 18–24)

The Tuesday, not "the platform." Workflow-level specificity.

18. What does [task] look like now, on a normal Tuesday?

Returns: A workflow, a number of tabs, a meeting that disappeared. Not "how has it helped."

If thin: "Can you walk me through the last time you did [task] — step by step?"

19. What is different about how your team works now?

Returns: Team-level change, not just individual workflow.

If thin: "Has anything changed in how you hand work off or coordinate?"

20. What can you do now that you could not do before?

Returns: New capability unlocked. Good for feature-specific stories.

If thin: "Is there anything you do now that was not even an option before?"

21. What surprised you after you started using it?

Returns: The unexpected benefit. Often the most quotable line.

If thin: "Was there anything you did not expect — good or bad?"

22. How long did it take to get to that point?

Returns: Time to value. A two-day ramp-up and a three-month implementation are different stories.

If thin: "When did it start feeling like it was actually working?"

23. What do you use [Product] for that we probably did not design it for?

Returns: Edge use case. Sometimes the best case studies are off-label.

If thin: "Have you ever used it in a way that felt a bit hacky?"

24. What would happen if you had to stop using it tomorrow?

Returns: Dependency framing. How embedded is the tool in their workflow.

If thin: "Would you notice right away, or would it take a while to feel the gap?"

5. The result (questions 25–30)

Numbers, proxies, and the limitation question.

25. What has it got you — and if you can put a number on it, do?

Returns: Time, cost, volume, errors. This is the money question.

If thin: "Even if you cannot share a precise figure, can you estimate — 'about half the time,' 'roughly doubled'?"

26. What metric moved the most?

Returns: The single number that matters. Useful when they give you five vague improvements.

If thin: "If you had to pick one thing that changed the most, what would it be?"

27. Can you share a before and after?

Returns: Concrete comparison. "From X to Y in Z weeks."

If thin: "If exact numbers are off-limits, can you give a range or a percentage?"

28. What has not changed (that you thought would)?

Returns: Honest limitation. Builds trust and pre-empts objections.

If thin: "Is there anything you expected to improve that stayed about the same?"

29. Would you recommend this to someone in your exact situation?

Returns: The recommendation with a qualifier. Better than a generic yes.

If thin: "Who specifically would you recommend it to, and who should skip it?"

30. Who should skip this?

Returns: The limitation, stated plainly. I would rather publish "skip this if you need [X]" than a third "highly recommend."

If thin: Rarely thin. If they say "everyone should use it," ask: "Is there a specific situation where it would not fit?"

How many to send

Not all thirty. That is homework, not a favour.

Minimal set (6 questions): 1, 7, 13, 18, 25, 30. Covers identity, before, objection, after, result, and limitation.

Standard set (8–10 questions): Add 3, 10, 21, 28 for deeper context without overwhelming.

Depth set (12–15 questions): When you need a longer case study or have a customer who likes to write. Pull from each section.

Weight the sections based on what your case study needs:

Weak on numbers? Add more from section 5.

Unclear who this customer is? Add more from section 1.

Story feels flat? Add 9 (the trigger moment) and 21 (the surprise).

The short-form four questions that produce a publishable testimonial — not a case study — live on testimonial questions to ask. If you only need a sentence for a landing page, start there.

The six that almost always work

If you are picking a minimal set, these are the six I would send to almost anyone:

Who are you, and what do you actually do day to day?

What were you doing about [task] before [Product], and what was broken about it?

What almost stopped you from picking us?

What does [task] look like now, on a normal Tuesday?

What has it got you — and if you can put a number on it, do?

Who should skip this?

That is one from each section, weighted toward the story beats that make a case study a case study: identity, before, objection, after, result, and limitation.

If you only have time to send six, send these. If one answer comes back thin, use the rescue follow-up from the full list above.

Where questions fail (and it is not the wording)

Three failure modes I keep seeing.

1. Too many questions. Fifteen questions turn a favour into homework. People who said yes to a case study did not say yes to a survey. Six to ten is the ceiling.

2. Abstract questions. "How has [Product] helped your business?" returns "it saved us time." "What does [task] look like now, on a normal Tuesday?" returns a workflow you can publish. Concrete beats abstract.

3. No rescue path. A thin answer sits. The interview closes. You write around the gap or publish something generic. Every question above has a follow-up. Use it.

What makes a testimonial good is specificity in a small space. A case study is the same job with a plot. If your answers are abstract, the question was abstract.

Doing this with Testimonial

The questions above work in an email, a Google Form, or a Notion page you share. You do not need us for them.

What async case-study interviews change is how the answers arrive. You build a question set — pick 6–10 from the list above and add them as questions — and send each customer their own link. No signup required on their side. They type, or they talk; voice is transcribed with ElevenLabs Scribe and dropped into the box as editable text. Answers arrive pre-attributed in the inbox. You can resend, remind, or revoke from one place.

Case Study is on Ultimate +. As of October 2026 that is $95/month/space, or $1,140 a year. Ultimate and Ultimate + are priced per space. The plans and pricing page is the live list.

The builder will let you add more than ten questions. I would not. Completion falls off because you turned a favour into homework. The product will not stop you; this page did.

If you have one customer, they will reply to an email, and six questions is enough. The tool earns its place when the backlog is eight names and you need templates that do not start over every time.

Wrapping up

30 questions, five stages, one rule: every question has a job.

Pick 6–8. Send them without a calendar link. Use the rescue follow-ups when answers come back thin. Write from what they actually said.

If you are stuck deciding which six to send, the whole testimonial pipeline has the system; this page is the toolkit.

Not sure which questions fit your product? Reply with what you sell — I will tell you which six to pick.

Build your question set.