case-study

---
name: case-study
description: Writes a customer case study with a challenge, solution and results structure, using verbatim quotes and verified metrics, ready for web or PDF. Use when asked for a case study, customer story, success story or to write up a win.
---

# Case study

Generate compelling B2B SaaS case studies that transform customer success data into persuasive proof points. Output structured narratives with quantified results, authentic quotes, and visual sections ready for web pages or PDF downloads.

---

## Claude Code triggers

**Invoke when user says:**
- "Write a case study"
- "Create a customer story"
- "Case study for [customer]"
- "Customer success story"
- "Turn this into a case study"
- "Customer story from [data]"
- "Case study from interview"
- "Win story for [customer]"
- "Success story for [company]"
- "Reference customer content"

**Do NOT invoke when** the user wants testimonial quotes only (extract them directly), sales deck slides, a full campaign, or a video script.

---

## Input requirements

### Required

| Input | Description | Source |
|-------|-------------|--------|
| **Customer name** | Company being featured | User provides |
| **Challenge/problem** | What they struggled with before | Interview, call transcripts, user provides |
| **Solution** | How they used the product | Interview, user provides |
| **Results** | Quantified outcomes | Customer data, interview |

### Optional (improve quality)

| Input | How it helps |
|-------|--------------|
| Customer interview transcript | Authentic quotes, story details |
| Win-loss analysis | Context on decision drivers |
| Usage data | Specific feature adoption metrics |
| Customer logo | Visual asset for header |
| Contact info (name, title) | Attribution for quotes |
| Industry/vertical | Vertical-specific framing |
| Timeline | Duration context (implemented in X weeks) |

### Validation

Before proceeding: customer name + industry known; ≥1 quantified result available; challenge clearly articulated; solution approach understood.

If inputs are missing: ask for customer name, primary challenge, and at least one measurable outcome. Offer to structure interview questions if no transcript — see the premium reference.

---

## Process

The case study runs in 3 phases. Read the premium reference for the full step-by-step (4 extraction steps, 4 structure steps, 3 output steps, plus per-phase checkpoints and the process flowchart).

Phase summary:

1. **Story extraction** — transformation arc, quote library (3-5), metrics table, signature moment
2. **Structure development** — hero statement, section drafts, metrics callouts, pull quotes
3. **Output generation** — pick format (web / PDF / slide), apply template, generate derivatives

---

## Case study structure

### Standard sections

| Section | Purpose | Length |
|---------|---------|--------|
| **Hero statement** | Capture attention, summarize transformation | 1 sentence |
| **Metrics bar** | Immediate proof of results | 3 numbers |
| **Company overview** | Context on customer | 2-3 sentences |
| **The challenge** | Problem + pain articulation | 2-3 paragraphs |
| **The solution** | How they use the product | 2-3 paragraphs |
| **The results** | Quantified outcomes + quotes | 2-3 paragraphs |
| **Closing CTA** | Next step for reader | 1 sentence |

### Metrics bar format

```
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ 3-5x │ │ 40-60 │ │ 20-40% │
│ More creator │ │ Hours saved │ │ Stronger │
│ content/month │ │ per month │ │ performance │
└─────────────────┘ └─────────────────┘ └─────────────────┘
```

### Quote format

```
"[Verbatim quote, one or two sentences, naming the before and after.]"

— [Full name], [Job title], [Company]
```

---

## Anti-hallucination guardrails

1. **Metrics from source only.** Never invent numbers. Mark as `[METRIC NEEDED]` if not provided.
2. **Quotes verbatim.** Use exact customer words. Don't paraphrase into "better" quotes.
3. **Mark unconfirmed details.** Use `[CONFIRM: detail]` for anything requiring verification.
4. **No invented story beats.** The "signature moment" must come from customer data.
5. **Attribution required.** Every quote needs name, title, company.

---

## Quality checklist (pre-delivery)

### Content
- [ ] Hero statement under 25 words
- [ ] At least 3 quantified metrics
- [ ] At least 3 attributed quotes
- [ ] Challenge clearly articulated
- [ ] Solution tied to specific features
- [ ] Results include before/after comparison

### Format
- [ ] All sections complete
- [ ] Metrics bar formatted
- [ ] Quotes properly attributed
- [ ] CTA included
- [ ] Derivatives generated (if requested)

---

## Gotchas

- **Invented metrics.** Creates "3x improvement" or "50% reduction" without sourced data → every metric must come from the customer or be marked `[UNAVAILABLE]`. Never fabricate results.
- **Generic challenge section.** Opens with "Company X was struggling with..." instead of specific, named pain → the challenge must reference the actual problem as the customer described it, not a generic industry pain.
- **Missing customer voice.** Writes the entire case study in third person without direct quotes → at least 3-5 verbatim customer quotes are needed. These are the most credible parts.
- **No clear "before" snapshot.** Jumps straight to the solution without establishing the baseline state → the "before" picture makes the "after" results meaningful. Include specific metrics or processes that existed before.

---

## MCP data integration

**Level:** 2 — PM Execution (customer-specific pulls)

### Pulls fresh

| Source | What to pull | Tool | When |
|--------|-------------|------|------|
| **Granola** | Customer-specific call transcripts | `search_meetings` | Always (per-customer story) |
| **Slack** | Customer success threads | `slack_search_public` | Always (per-customer data) |

### Fallback (no MCP)

- User-provided customer interview transcripts
- Manual success metrics from customer
- Email threads or shared docs with customer quotes