ع
Learn Tracks Reference Guides Saved
playbook

Turn a customer interview into an approved case study

Take a raw interview transcript and produce an approved, on-brand case study — narrative, real metrics, verbatim quotes — plus the consent and sign-off pack that gets it cleared, instead of letting your best proof die in a doc.

medium ~1 hour
when to reach for this

Customer stories are your strongest proof and the hardest thing to actually ship — the interview sits in a transcript for months because turning it into an approved, on-brand case study is work nobody has time for. This system does the heavy lift: find the story arc, pull the metrics and the verbatim quotes, draft it in your voice, and produce the consent and approval pack so it clears the customer and legal — fast, and without misquoting anyone. Run it from the Claude Desktop chat; drop the transcript into the file pane and work in plain language.

gather this first
  • The raw material as a file — an interview transcript, recording notes, or your notes from the call.
  • The outcomes the customer agreed you can use, and which numbers are off-limits.
  • Consent status: what the customer has approved to be public (logo, name, specific figures, direct quotes) and what's still pending.
the workflow

  1. Find the story in the transcript

    Open the folder with your transcript in Claude Desktop and ask in the chat. Before drafting anything, get the raw materials of a story — the arc, the real quotes, the hard numbers — straight from the source.

    you ask
    Read interview.txt. What's the real story arc — the before (the pain), the change (what they did), and the after (the outcome)? Pull the 5 most quotable lines exactly as said, word for word, and list every hard number mentioned. Don't write the case study yet.

    what you get back The before/change/after arc, five verbatim pull-quotes, and the metrics — the honest raw material of a story, lifted from what the customer actually said.

    Verbatim is non-negotiable. Never let a quote you'll attribute to a real, named person be paraphrased or "tidied up."

  2. Structure the narrative

    Outline before drafting, mapping every section to real material so the story can't drift into invention. The customer is the hero; you're the enabler.

    you ask
    Outline the case study: a headline that states the outcome, the challenge, the solution (specifically what we did), the results with the real numbers, and a short forward-looking close. Map each section to the quotes and metrics from the last step — flag any section that has no real material behind it.

    what you get back A structured outline grounded in the transcript, with any thin section flagged rather than quietly padded.

  3. Draft it in your voice

    Now write the story, in your brand voice, with every claim traceable. Where you're missing a number or quote, the draft should mark the gap, not fill it with fiction.

    you ask
    Using brand-voice.md, draft the full case study (~500 words) from the outline — the customer as the hero, us as the enabler, every claim traceable to the transcript or the agreed metrics. Mark with [NEED] any spot where I'd have to supply a number or quote I don't actually have.

    what you get back A full, on-brand draft with gaps explicitly marked [NEED] — never invented — so you know exactly what to confirm before it goes anywhere.

  4. Build the consent and approval pack

    This is the step that turns a draft into something publishable. Produce the paper trail and the ask, so nothing ships that the customer or legal hasn't cleared.

    you ask
    Produce the approval pack: every quote and number in the draft listed with the transcript line it came from, what needs the customer's written sign-off, what needs legal or PR review, and a short, warm approval email to the customer with the draft attached. Flag anything I should not publish without explicit written consent.

    what you get back A consent and approval pack — sourced quotes and figures, a clear list of what needs whose sign-off, and a ready approval email — the thing that actually gets the story cleared.

    Consent is the whole game here. The pack exists so a name, logo, quote, or number never goes public before someone with the authority to approve it has, in writing.

  5. Cut the derivatives once it's approved

    An approved story should work everywhere. Cut the channel versions from the one source so you build it once, not five times.

    you ask
    From the approved story, cut: a one-paragraph version for the sales deck, a LinkedIn post, a caption for a pull-quote graphic, and a one-line proof point for our messaging framework. Keep every version inside what the customer approved.

    what you get back The story working across channels — deck, social, graphic, and a proof point — all derived from the single approved source.

make it your own
  • Anonymous story: if the customer can't be named, run the same flow with [Industry] / [Company size] placeholders and no logo — the proof still lands without the name.
  • Proof library: keep approved metrics and quotes in one file the whole team draws from, so the next campaign reaches for vetted proof instead of re-asking the customer (ties to the messaging-framework playbook).
  • Internal win story: the same method works on a lost deal or an internal win for the team — just don't publish it externally.
watch out for
  • Consent is the whole game. Never publish a name, logo, quote, or number the customer hasn't approved in writing, and route it past legal or PR. A misused customer story is a relationship and a legal problem at once.
  • Quotes are verbatim or they're fabricated. Don't let Claude smooth a quote into something cleaner the person never said — attribute only the exact words, sourced to the transcript.
  • Don't inflate the numbers. The figure the customer agreed to is the figure — Claude will happily turn 31% into "over a third." Keep it exact and approved.
  • The customer is the hero. A case study that's really about how clever you are doesn't get shared by the one person whose share matters most — them.

you'll end up with An approved, on-brand case study plus its consent and approval pack and channel cut-downs — your best proof shipped fast, accurately, and cleared, instead of dying in a transcript.

Questions people ask

How does this keep me from misquoting the customer?
Quotes are pulled verbatim in the first step — word for word from the transcript — and then every quote and number is listed with its source line in the approval pack. Claude is explicitly told to mark missing material as `[NEED]` rather than invent it, and never to smooth a quote into something the person didn't say. You attribute only the exact words, sourced.
What if the customer can't be named publicly?
Use the anonymous variation — run the same flow with `[Industry]` and `[Company size]` placeholders and no logo. The before/change/after arc and the metrics still carry the proof; you just lose the named brand. It's a common, legitimate way to ship a story when the customer's policy or legal won't allow attribution.
Does this clear the legal and consent side for me?
No — it builds the apparatus, you and the approvers close it. The playbook produces the sourced quote/number list, the list of what needs the customer's versus legal's sign-off, and a ready approval email. A human still gets the written consent and the legal/PR review before anything publishes. The pack just makes that fast and thorough instead of an afterthought.
Can I reuse one story across channels?
Yes — the last step cuts the approved story into a deck paragraph, a LinkedIn post, a pull-quote caption, and a one-line proof point for your messaging framework. You build the story once and it works everywhere, with every version staying inside what the customer approved.