Skip to content
New: a sample workflow audit report
Scenox Studios

Draft case studies from client interviews

An interview recording becomes a structured case study draft with the client's own words, a timeline and a list of every claim to verify. The client and your risk team approve before anything is published. For firms with strong work and few published stories.

Draft case studies from client interviews

6 steps

  1. 01

    Transcribe the interview

    Model
  2. 02

    Draft the case study

    Model
  3. 03

    Build the claims list

    Rules
  4. 04

    Verify and edit

    Person
  5. 05

    Client approval

    Person
  6. 06

    Publish and track

    Rules

At a glance

Trigger
A client interview is recorded and a case study is requested.
Typical inputs
  • Interview recording
  • Engagement summary and approved facts
  • Client permission and naming terms
  • Case study template
Systems it usually connects to
  • Zoom
  • Google Drive
  • Notion
  • DocuSign
How the work splits

2 rules, 2 model, 2 person steps

How it runs, step by step

6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.

  • Rules Fixed logic in code
  • Model AI reads or drafts, with a confidence score
  • Person A named person decides
  1. 1

    Transcribe the interview

    Model

    The recording is transcribed with speakers labeled, and client and project terms are checked against a glossary.

  2. 2

    Draft the case study

    Model

    A model structures the draft as challenge, approach and outcome using only what was said or documented, and quotes the client verbatim.

  3. 3

    Build the claims list

    Rules

    Every figure, date and outcome is pulled into a checklist with the source passage beside it.

  4. 4

    Verify and edit

    Person

    The engagement lead checks each claim against records and edits the narrative.

  5. 5

    Client approval

    Person

    The client reviews the draft and approves the quotes and the use of their name.

  6. 6

    Publish and track

    Rules

    The approved version is stored with its approval record and published to the channels you choose.

Where people approve

The decisions that stay with your team, whatever the confidence score says.

  • The client approves the draft and every quote.
  • Risk or compliance clears confidentiality.
  • A partner signs off before publication.

KPIs to track

What to measure, before and after. Targets come from your own baseline.

  1. 01Days from interview to approved case study
  2. 02Share of requested studies that reach publication
  3. 03Claims changed during verification
  4. 04Sales conversations that cite the study

Questions about this workflow

Can the draft state results that the client did not mention?

It should not, and the claims list is how we catch it. Outcomes appear only if said in the interview or present in your records, and the engagement lead verifies each one.

What about clients who do not want to be named?

The template supports anonymized versions. The approval record shows what the client agreed to, and the system applies the naming terms automatically.

Which steps use rules, a model and a person?

Rules: build the claims list; publish and track. Model: transcribe the interview; draft the case study. Person: verify and edit; client approval. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.

What do we need to start?

Typically: interview recording; engagement summary and approved facts; client permission and naming terms; case study template. You also need read access to Zoom, Google Drive, Notion and DocuSign, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.

Where this fits at Scenox

More use cases like this one

All 60 use cases

Plan how to draft case studies from client interviews with an engineer.

A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.

What happens next

  1. 1

    Strategy call

    We learn how the workflow runs today and what a good outcome would be.

  2. 2

    Workflow audit

    We map the process and measure where a system would save the most time.

  3. 3

    Proposal

    A written scope, timeline and fixed price for your first system. No obligation to build.