From Customer Interview to Written Case Study

What makes an interview usable for a case study

A good customer conversation is not automatically a good case study. Customers talk about what is on their mind that week: a recent bug, a feature request, a colleague who left. The case study needs something narrower: a clear situation before your product, a decision, what changed, and evidence that it changed.

That is why the interview is best planned backwards from the finished piece. Know which three or four passages you need to come out of the call with, then design questions that make the customer say them in their own words. The transcript then becomes a source you mine, not a script you edit down.

Consent and approval come first

Case studies use a customer's name, logo and words to sell your product, so the permission question has more parts than a typical interview:

• Consent to record, given at the start of the call and captured on the recording. Recording laws differ between countries and states, and some require every party's consent.
• Agreement in principle to be featured, ideally confirmed in writing before the interview, including whether the company name and logo can appear.
• An approval step on the final draft. Many companies route this through their communications, PR or legal team, which can take weeks; plan for it.
• An agreed fallback, such as an anonymized version ("a regional logistics company") if the named version is not approved.
• Clarity about where the story will appear: website, sales decks, ads, translated versions.

Check your own contracts too, since some customer agreements restrict publicity. This is general guidance, not legal advice; ask your legal team when a contract or a regulated industry is involved.

Questions that produce a story

Open questions in chronological order produce the most usable transcript. Closed questions produce "yes" and "it's been great", which are worthless on the page.

1. "Tell me about your role and what your team is responsible for." Sets context in their words.
2. "What were you using or doing before, and what was frustrating about it?" This is your problem section.
3. "What made you start looking for something else, and when?" The trigger is often the most vivid moment.
4. "What else did you consider, and why did you choose us?" Honest answers here persuade future buyers.
5. "Walk me through the first few weeks of using it." Implementation detail makes the story credible.
6. "What is different now? How do you know?" This is where measurable outcomes come from, if they exist.
7. "What would you tell someone in your position who is deciding?" Often yields the closing quote.

Follow up with "Can you give me an example?" whenever an answer stays abstract. The specific example is usually what ends up quoted.

Finding the arc in the transcript

With the transcript open, read once without editing and tag passages by their role. Note the timestamp for each, so you can return to the audio later.

Situation

Who the customer is and what they were trying to do

Problem

The cost of the old way, ideally described with a concrete incident

Trigger

The event that made them act

Choice

Why they picked you, including what nearly stopped them

Change

How work is different now, in practical terms

Evidence

Figures, timelines or observations the customer stated

Advice

A forward-looking line for readers in the same position

Gaps in this table are the most useful thing the tagging pass reveals. If there is no evidence passage, do not paper over it; email the customer a specific follow-up question, or write the story around qualitative change and say so.

A worked example from a 38-minute call

Here is how that call becomes a draft:

1. Transcribe the audio-only export from the meeting app, which is smaller than the video and often cleaner.
2. Tag the passages: the bad Monday story at 07:40 becomes the opening, the receptionist detail at 12:15 becomes the problem, and the comparison of two other tools at 18:30 becomes the choice section.
3. Notice that the evidence row is thin. "Dropped quite a bit" cannot become a percentage.
4. Email the manager: "Do you have no-show figures for a month before and after you switched that we could cite?" She replies with figures from her own reports and agrees to publish them.
5. Draft about 700 words with a headline built on the confirmed outcome, three short sections and two quotes.
6. Check each quote against the audio at its timestamp and fix two recognition errors in the clinic's product names.
7. Send the draft for approval, highlighting the quotes and the figures so the reviewer knows exactly what is attributed to them.

Quoting the customer accurately

Speech is messy, and nobody expects a case study to print "um" and false starts. Light cleanup is standard: removing filler, fixing a stumble, joining a sentence that was interrupted. What crosses the line is changing meaning, combining remarks from different parts of the call into one quote without saying so, or upgrading enthusiasm ("it's been helpful" becoming "it transformed our business").

A practical rule: if the customer read the quote next to the recording, would they say "yes, that's what I meant"? The approval step tests exactly that, so make it easy. Show each quote and its timestamp in the draft you send. For the different conventions that apply when quoting recordings in academic work, see how to cite a video with timestamps. If you want a format that keeps more of the conversation intact, an interview edited into a Q&A article is a better fit than a case study.

Never invent or round up the numbers

Case studies are judged by their numbers, which is exactly why invented or inflated ones do so much damage. A prospect who asks the featured customer about a headline like "halved scheduling time" and hears "I never said that" is lost, and the customer relationship may be too.

• Use only figures the customer stated or provided, and confirm them in writing.
• Do not convert vague phrases into precise ones. "Much faster" is not "3x faster".
• Keep the customer's framing: their timeframe, their baseline, their unit.
• If a number comes from your own product data, say so, and get the customer's permission to publish it.
• When there are no figures, a well-told qualitative change is more convincing than a weak number.

Pitfalls that weaken a case study

• Writing the draft before the interview and hunting for quotes to fit it. Customers notice, and the story sounds like marketing copy.
• Letting your product be the hero. The customer's problem and decision are the story; the product is the means.
• Including feature lists the customer never mentioned.
• Relying on an uncorrected transcript. Names of people, companies and products are where speech recognition errs most, so check them against the audio.
• Skipping the trigger. "Why then?" is often what makes a reader in the same position recognize themselves.
• Publishing a translated version that nobody fluent has read.

How mydubly fits this process

mydubly covers the transcription and, if needed, a translated transcript. Upload the call recording through audio to text, or the video file through video to text; recordings up to 2 hours work, in MP3, WAV, M4A, AAC, OGG or FLAC for audio and MP4, MOV, WebM, MKV or M4V for video. The spoken language is detected automatically, and you get a plain and a timestamped transcript. A 38-minute call costs 38 credits (3.8¢), as transcripts are 1 credit per minute with a 5-credit minimum.

There are limits worth knowing. The transcript has no speaker labels, so mark the interviewer's questions yourself; with a clear question-and-answer rhythm this is quick. Only the audio is uploaded, in compressed chunks over HTTPS, and audio and results are deleted within 30 minutes of the job finishing, which is helpful when a customer asks how their recording is handled.

If the customer was interviewed in another language, choose a target language to get a translated transcript to work from, then have a fluent speaker confirm every quote before publishing. mydubly translates speech, not documents, so it cannot translate the finished written case study; use a professional translator or a text translation workflow with review. For a recorded video testimonial, translated subtitles from the subtitle generator can accompany the translated page. For interview recording itself, the interview transcription use case covers setup.

Decide early whether quotes will be verbatim or lightly cleaned; verbatim vs clean verbatim transcription explains the trade-off.

Book the next interview with the end in mind

Before your next customer call, write the seven questions down, confirm consent and approval in writing, and decide which passages the finished story needs. If remote audio quality has hurt past transcripts, the guide to recording a remote interview is worth a read first.