How Freelancers Can Use Claude Skills to Turn a Client Interview Into a First-Draft Case Study

If Claude Skills is new to you

Claude Skills are reusable folders that Claude can load when a task matches the Skill description. A custom Skill usually includes a Skill.md file with metadata, instructions, examples, and optional supporting files. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you will create one private Skill, upload it in Claude under Customize > Skills, enable it, run a trigger test, and then use it on the interview transcript and result notes. The Claude Skills tool hub is useful further reading, but this page includes the setup steps needed for the workflow.

Problem and who this is for

A client interview gives you raw story material, but it is rarely in the order or shape you need for a case study. The narrow job here is to turn an interview transcript and result notes into a first-draft case study with challenge, approach, results, approved quotes, and verification points.

This workflow is for freelancers, agencies, and consultants who need a case study draft from real interview material. It is not a full content marketing engine, campaign plan, or final client-approved case study.

What skill you will use in this workflow

You will build a private custom Skill called case-study-from-client-interview. The Skill tells Claude how to turn a client interview transcript, project notes, and outcome data into a first-draft case study while keeping metrics, quotes, and claims traceable.

This task is repetitive enough to deserve a Skill because case studies usually follow the same shape across clients: client context, challenge, approach, outcome, quotes, proof points, and claims to verify. Before using it, prepare the transcript or summary, result notes, approved quotes, publishing limits, and any client approval rules.

Prerequisites

• Claude with Skills available and code execution enabled.
• Permission to record, transcribe, process, and use the client interview.
• A transcript or detailed summary of the client interview.
• A results note with before, after, timeline, deliverables, proof points, and any approved numbers.
• Approved quote notes, or a clear marker that quotes still need client approval.
• Publishing limits, such as anonymization, restricted client names, restricted metrics, or claims to avoid.
• A final human review pass before sending the draft to the client.

How to gather the source material

1. Confirm that the client approved the interview, recording, transcription, and intended case study use.
2. Export the interview transcript or create a same-day written summary if no transcript exists.
3. If the workflow starts from a recorded call, interview, coaching session, or spoken source rather than clean digital text, Plaud can be a capture option. Note Pro is a good fit for desk or interview-style recordings.
4. Create a short file called results-facts.txt with the timeline, deliverables, measurable outcomes, proof points, and any approved numbers.
5. Create a short file called approved-quotes.txt with exact quotes that are already cleared, or label them as needs approval if they are not cleared yet.
6. If the case study must avoid certain claims, client names, or metrics, put those restrictions in a file called publishing-limits.txt.
7. Save everything as TXT, DOCX, or PDF in one source folder.

Build the custom skill for this workflow

Create a folder named case-study-from-client-interview. Inside it, create a file named Skill.md. Paste the starter content below into that file, then adjust it for your case study style, client approval process, and claim-review rules.

After the folder is ready, zip the case-study-from-client-interview folder itself so the ZIP contains the skill folder at its root. Do not zip loose files by themselves. In Claude, go to Customize > Skills, upload the ZIP file, and enable the Skill. Then run the trigger test below before using it on a live client story.

---
name: case-study-from-client-interview
description: Turn a client interview transcript and result notes into a first-draft case study with challenge, approach, outcome, quotes, and open verification points.
---

# Case Study From Client Interview

Use this skill when the user wants a first-draft client case study from an interview transcript, project notes, and outcome data.

## Required sections
- Client context or challenge
- Work performed or approach
- Outcome or result
- Pull quotes if supported
- Open verification points

## Guardrails
- Do not invent metrics or quotes.
- Keep unverified claims in a separate review-needed section.
- Treat the output as a first draft for human revision and client approval.
- Prefer concrete outcomes over promotional filler.

## Examples
- Turn this client interview transcript into a first-draft case study.
- Use my case study workflow on this transcript and result notes.
- Draft a case study and flag any quote or metric that needs verification.

Treat this as a starter template. Add your own section names, length target, quote rules, client approval language, and claim-review standards before using it on live client material.

Optional official Anthropic skill

Anthropic's official doc-coauthoring Skill is the closest public shortcut when you need help drafting a structured document from source material. It can be useful for a one-time case study draft or for studying how a document-focused Skill is organized.

For repeat case study work, the private case-study-from-client-interview Skill is the better fit. It can hold your recurring sections, quote rules, proof-point handling, and client approval guardrails across projects.

Skill-creator helper

Anthropic's official skill-creator Skill can help draft or refine this private case study Skill. Use it to improve the description, trigger examples, quote guardrails, and verification language.

Why this should be a custom skill, not a one-off prompt

Case study drafting repeats the same structure, but the risk is in the details. A custom Skill keeps the same challenge, approach, result, quote, proof, and verification sections available every time. That reduces prompt rewriting and makes it harder for metrics, quotes, or client approval language to get lost.

Skill trigger test

After enabling the Skill, test it with a short transcript excerpt and one result note before the first draft. These prompts should cause Claude to use the case-study-from-client-interview Skill:

• Turn this client interview transcript into a first-draft case study.
• Use my case study workflow and keep unverified metrics visible.
• Draft a case study from this transcript and notes without inventing quotes.
• Use the case study Skill and put unsupported claims in review-needed.

If Claude does not appear to use the Skill, tighten the Skill description and examples with phrases like "case study," "client interview transcript," "result notes," "approved quotes," and "claims to verify."

Numbered workflow steps

1. Gather and clean the source material

Put the transcript, results-facts.txt, approved-quotes.txt, and publishing-limits.txt in one source folder. Remove small talk, unrelated project history, and any sensitive client detail that should not influence the draft.

Keep the result notes separate from the transcript. The transcript supplies story material and client language. The result notes supply the facts that prevent Claude from guessing.

2. Create or enable the custom Skill for this workflow

If this is your first run, build the case-study-from-client-interview folder, add the Skill.md file, zip the folder, upload it in Customize > Skills, and enable it. If you already built the Skill, confirm it is enabled before you start.

The Skill should encode the case study structure: challenge, approach, results, approved quotes, proof points, and claims to verify. It should also encode the guardrail that Claude must not invent metrics, quotes, approvals, or client claims.

3. Run a quick trigger test

Use a short interview excerpt and one result note first. Try:

Turn this client interview transcript into a first-draft case study. Use my case study workflow, keep unverified metrics visible, and do not invent quotes.

Check that Claude uses the Skill structure, flags unsupported claims, and keeps quote or metric uncertainty visible. If it writes a polished sales story before verifying the source, tighten the Skill guardrails before using the full transcript.

4. Run the actual workflow with the Skill active

Attach or paste the transcript, results-facts.txt, approved-quotes.txt, and publishing-limits.txt. Ask Claude to use the case study Skill and draft only from the provided material.

Use a prompt like:

Use the case-study-from-client-interview Skill on this transcript, result notes, approved quotes, and publishing limits. Draft a first-pass case study with challenge, approach, outcome, supported quotes, proof points, and open verification points.

If the interview is long, ask Claude to first produce a source map with challenge, approach, results, quote candidates, proof points, and claims to verify. Review that map before asking for the first draft.

5. Do a human review for metrics, quotes, and approval language

Review every metric, quote, timeline claim, and client approval phrase before sending the draft anywhere. Confirm that numbers match the result notes, quotes are exact and approved, and any unapproved quote remains in the review-needed section.

Also check tone. The draft should be clear and useful, not inflated or overly promotional.

6. Save, send, or reuse the result

Save the reviewed draft in your project folder, case study workspace, or client review document. If you send it to the client, keep review-needed items visible and ask for explicit confirmation on metrics, quotes, and naming. After a few projects, update the Skill with the case study shape and approval language that consistently works.

Tool-specific instructions

Use Claude Skills for the repeatable parts of this workflow: case study structure, quote handling, proof-point extraction, metric caution, and client approval guardrails. The page-specific case-study-from-client-interview Skill should come first because this workflow depends on your case study format and approval process.

For broader setup context, see the Claude Skills hub. For one-off structured drafting, Anthropic's doc-coauthoring Skill may help, but keep repeat case study work in your private Skill. For drafting or refining that private Skill, use Anthropic's skill-creator as a helper.

Quality checks

1. Every metric and factual claim is supported by the source notes.
2. The story order makes sense even if the interview wandered.
3. Quotes are exact, approved, or clearly marked as needing approval.
4. Claims to verify are visible instead of smoothed into the draft.
5. The draft reads like a first working version, not a claim-heavy sales page.
6. Client naming, anonymization, and publishing limits are respected.

Common failure modes and fixes

The story feels thin

Fix: add a stronger results-facts.txt file instead of expecting the interview alone to carry the whole case study.

Metrics become inflated

Fix: require Claude to list approved metrics and claims to verify before drafting the final narrative.

Quotes are paraphrased as exact quotes

Fix: add a guardrail that quotation marks may only be used for exact transcript language or approved quotes.

Only audio exists

Fix: convert the recording to a transcript or structured summary before using the Skill. Use Plaud, a meeting transcript, or your approved transcription process, but do not skip the conversion step.

The Skill does not trigger

Fix: update the Skill description so it includes the exact phrases you use, such as "case study," "client interview transcript," "result notes," "approved quotes," and "claims to verify." Then run the trigger test again.