---
name: case-study-writer
description: Write a persuasive customer case study that proves outcomes and sells the next buyer. Use this skill whenever a user wants a case study, a customer success story, a results writeup, or says 'write a case study', 'turn this client result into a story', or 'we have great results but no proof content'. Trigger whenever a client outcome needs to become structured proof that converts prospects.
---

# Case Study Writer

## What this does and why it matters
A case study is the highest-converting proof asset a firm owns, and most are boring recitations that bury the result. This skill writes case studies as a transformation story (problem, solution, quantified outcome) that a prospect sees themselves in, so the study sells rather than just documents.

## Inputs to gather
1. The client, their situation before, and the problem they faced.
2. What was done (the solution and the mechanism).
3. The results, quantified wherever possible, and any client quotes.
4. The prospect this study should persuade.

## Method

### 1. Structure as a transformation
Before, the intervention, and after. Open on the problem the prospect will recognize in themselves, so they lean in immediately. A case study is a story, not a spec sheet.

### 2. Make the before relatable and specific
Detail the pain and its cost. The more precisely the "before" matches a prospect's current state, the more the study sells.

### 3. Show the mechanism, not just the outcome
Explain what was done and why it worked, so the result feels repeatable and credible rather than lucky.

### 4. Quantify the after
Lead with the numbers: time saved, revenue gained, cost cut, hours reclaimed. Specific metrics beat vague praise. Where a hard number is missing, use a concrete qualitative outcome and flag that a metric would strengthen it.

### 5. Let the client speak
A real quote in the client's voice adds credibility no marketing copy can.

### 6. Bridge to the reader
Close by connecting the outcome to what a similar prospect could achieve, with a clear next step.

## Output format
ALWAYS use:

# Case Study: [Client] achieved [headline result]
## Snapshot (client, industry, headline metrics)
## The challenge (before, relatable and specific)
## The approach (what was done and why it worked)
## The results (quantified, with client quote)
## Why it matters for you (bridge + CTA)

## Anti-patterns to avoid
- A dry chronology with the result buried at the end.
- Vague outcomes ("great partnership") with no numbers.
- All outcome, no mechanism, so it feels like luck.
- No bridge to the reader's own situation.

## Example
A study leads with "Firm X reclaimed 30 hours a week", opens on the manual-reporting pain the prospect shares, explains the automation built, quantifies the time and cost saved, and closes bridging to the reader's own reporting burden.