The best customer case study interview questions recover a specific before-and-after story and the evidence behind it. Ask what the customer was trying to do, what changed, how they know and what else contributed. Then verify the facts and obtain approval for the actual public version. A compelling story does not need an invented percentage improvement.
Start with the job before the product
Ask the customer to describe the workflow in its own language. Who performed the work, what made it difficult and what happened when it failed? Capture a dated example rather than a broad statement such as “everything was manual.” This reveals whether the story is about time, risk, coordination, revenue or another outcome.
Distinguish the person using the product from the person who approved the purchase. A user’s enthusiasm is useful evidence about experience, but it is not a statement about budget, company-wide adoption or financial return.
Use questions that invite evidence rather than praise
Ask open questions first, then follow up for definitions, dates and sources. Avoid feeding the customer the result you want. “How much time did this save?” assumes a saving; “What changed in the time required?” leaves room for no change or additional work.
A case study is not a product testimonial collection. The reader needs to understand the customer’s conditions, the work involved and where the result may not generalize.
An evidence-first interview question set
| Question | Useful follow-up | Evidence to request |
|---|---|---|
| What job were you trying to complete? | Who owned it and why did it matter? | A specific workflow or project |
| What happened before the change? | Which period and people are you describing? | A baseline record or bounded recollection |
| What did implementation involve? | What work did your team still perform? | Timeline, responsibilities and setup notes |
| What changed afterward? | How did you measure that change? | Matched-period figures or a labeled estimate |
| What else changed at the same time? | Did staffing, process or demand change? | Context that limits attribution |
| What did not improve? | Who should approach this differently? | Limitations and practical advice |
| Which statement could we publish? | Who can approve the final wording and figures? | Version-specific approval |
Build a claim ledger before writing the headline
For every outcome, record the claim, unit, baseline, comparison period, source and reviewer. Distinguish observed records from customer estimates and your own interpretation. If a historical baseline is unavailable, say so or write a qualitative story. Do not turn unavailable data into a zero baseline.
Illustrative calculation: a comparable task took 120 minutes before a process change and 90 minutes afterward. That is 30 minutes less, or a 25% reduction relative to the 120-minute baseline. The calculation does not prove the product alone caused the change. Confirm the task, people, measurement method and other changes before using it in a story.
Write a story whose limits are visible
Use a clear sequence: customer context, challenge, implementation, result and practical lesson. Keep the customer’s actual language in approved quotes, and mark paraphrases as paraphrases. Never combine several comments into a direct quote the customer did not say.
Show the work required to reach the result. A story that omits implementation effort may be attractive but unhelpful. If the customer only used one feature or one team participated, keep the claim at that scope.
Approve the actual public version
Confirm permission to record the interview and use the material before collecting it. Then obtain approval for the final copy, quotes, company identity, logos and figures through the customer’s authorized process. Approval to interview is not approval to publish.
Use Finta to coordinate the relationship, source references and follow-up. Aurora can help turn authorized notes into a draft and an evidence checklist. It should not manufacture quotes, decide disclosure rights or publish a customer story without approval.
Case study claim ledger
| Proposed claim | Evidence status | Editorial action |
|---|---|---|
| The workflow took less time | Matched records available | Define task, dates and denominator |
| The team felt more prepared | Customer’s attributed observation | Keep it qualitative |
| The product increased revenue | No verified attribution | Omit or investigate; do not infer |
| Customer quote and identity | Interview completed, public approval pending | Keep private until the exact version is approved |
Try it with Aurora, Claude or Codex
Copy this prompt and add only material you are authorized to use. In Aurora, use the context available in your Finta workspace. Other assistants need the relevant inputs supplied separately.
Turn these authorized customer-interview notes into a case study outline and claim ledger.
Separate direct quotes, paraphrases, measured outcomes and estimates.
For each outcome list baseline, comparison period, unit, source and missing evidence.
Flag alternative explanations and disclosure approvals still needed.
Suggest follow-up questions before writing a headline.
Do not invent a quote, metric, customer endorsement or causal result.Review the result against the original sources before acting. A generated draft is not an approval or a completed external action.
Sources and method
Sources reviewed October 28, 2026. Examples and worksheets are original editorial teaching tools, not customer results.
FTC guidance on endorsements and advertising claims.
Related resources
Informational disclaimer
This content is for informational and educational purposes only and is not legal, tax, accounting, investment or other professional advice. We are not lawyers or accountants. Check with your attorney, accountant or other qualified adviser about your circumstances and any proposed transaction, disclosure or legal obligation.