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

Warning: Case studies can drift into inflated claims if the source material is thin. Keep the draft tied to verified results, quotes, and timeline facts.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

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 fastest path is not to ask Claude for a polished story immediately. The fastest path is to turn the interview into a source map first, then draft the case study from that map.

This workflow is for freelancers, agencies, and consultants who need portfolio-ready proof without spending hours restructuring the story by hand.

Prerequisites

• Claude with Skills available.
• A transcript or detailed summary of the client interview. If you only have audio, create the transcript first with your normal recording or meeting workflow.
• A simple results note with before, after, timeline, and any measurable outcomes.
• Permission to publish the case study and any quote restrictions you need to respect.

How to gather the source material

1. Export the interview transcript or create a same-day written summary if no transcript exists.
2. Create a short file called results-facts.txt with the timeline, deliverables, measurable outcomes, and any approved numbers.
3. Pull in one or two exact client quotes if they are approved for use.
4. If the case study must avoid certain claims or client names, put those restrictions in a file called publishing-limits.txt.
5. Save everything as TXT, DOCX, or PDF in one source folder.

Numbered workflow steps

1) Extract the story structure before you draft the case study

The doc-coauthoring pattern is the best fit here because a case study needs clean story logic: situation, problem, approach, result, and proof. Claude should build that structure before it tries to sound polished.

{
  "task": "Extract a case-study source map from a client interview and result notes",
  "input": {
    "client_interview": "ATTACH OR PASTE",
    "results_facts": "PASTE results-facts.txt",
    "publishing_limits": "PASTE publishing-limits.txt"
  },
  "rules": [
    "Use only approved facts, quotes, and metrics.",
    "Separate story beats: starting point, challenge, work done, result, evidence.",
    "Flag weak or unsupported claims as [SOFTEN OR REMOVE].",
    "Do not draft the full narrative yet."
  ],
  "output": {
    "starting_point": "What was true before the project",
    "challenge": "Problem or friction point",
    "approach": "Work performed",
    "results": "Outcome and evidence",
    "quote_options": "Approved quotes that fit the story",
    "weak_claims": "Claims to soften or cut"
  }
}

2) Review the extracted material before Claude writes the final deliverable

Check the numbers. A first-draft case study becomes dangerous when Claude turns a rough improvement into a hard metric. Keep only the numbers and claims the client approved.

3) Draft the final deliverable

{
  "task": "Write a first-draft client case study from a verified source map",
  "input": {
    "verified_case_study_map": "PASTE THE REVIEWED OUTPUT FROM STEP 1"
  },
  "rules": [
    "Write a clear first draft, not final magazine prose.",
    "Use headings for challenge, approach, results, and takeaway.",
    "Use only approved quotes and approved metrics.",
    "Soften or remove anything marked [SOFTEN OR REMOVE]."
  ],
  "output_format": {
    "type": "case_study_draft"
  }
}

4) Save the output where you actually work

Keep the final deliverable in the same folder as the source package, or paste it into the system you already use. The value here is repeatability. Once your source files and section order are stable, the next run gets much faster.

Tool-specific instructions

Claude Skills helps when you want the same case-study structure every time while still keeping the writing grounded in interview evidence. The public doc-coauthoring skill is the closest production pattern for this workflow.

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 and approved.
4. The draft reads like a first working version, not a claim-heavy sales page.

Common failure modes and fixes

The story feels thin

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

Metrics become inflated

Fix: make Claude list approved metrics before drafting the final narrative.

Only audio exists

Fix: convert the recording to a transcript or structured summary before using the skill.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: Creating custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-creating-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: doc-coauthoring skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/doc-coauthoring

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Claude Cowork, file handling, plan availability, and setup paths.