<!-- Case study writer | install: npx skills add prosyo-ai/gtm-skill --skill case-study-writer | source: https://github.com/prosyo-ai/gtm-skill/tree/main/skills/case-study-writer -->

---
name: case-study-writer
description: "Use this skill when you need a B2B customer case study or success story that sales can use: \"write a case study\", \"turn this customer interview into a story\", \"customer success story for our website\", \"one-pager for sales\". Plans the interview, structures the story (before, trigger, decision, rollout, results, what's next), writes it with real numbers and quotes, and produces versions for the website, a sales one-pager, a cold email paragraph and a LinkedIn post. Every claim is approved by the customer."
license: MIT
metadata:
  title: Case study writer
  category: positioning
  tags: "Marketing, Sales, Founders, Customer Success"
  author: prosyo
  version: "1.0.0"
  keywords: "b2b case study template, write a customer case study, customer success story, claude case study skill, case study interview questions"
  inputs: "Customer interview or notes, Usage and results data, Customer approval status"
  outputs: "Interview guide, Full case study, Sales one-pager, Email and social versions"
---

Use this when a customer has a result worth sharing. The best case studies read like a story a peer would tell, with the buyer's doubts left in.

## Inputs

- Interview transcript or notes with the customer (or run the guide below).
- Results data: before and after numbers, time frames.
- What the customer has approved for publication: name, logo, quotes, numbers.

## The play

### 1. Interview for the story, not the praise
Ask:
- What was happening before? What did it cost you?
- What made you look for a change then?
- What else did you consider? What almost stopped you?
- How did the rollout actually go, including the bumps?
- What changed, in numbers, and how do you measure it?
- What would you tell a peer considering it?

### 2. Structure it
1. **Headline**: the result, with the number. "How Northwind filled 15% more chairs in 90 days."
2. **Snapshot**: company, size, use case, top 3 results.
3. **Before**: the situation and its cost, in their words.
4. **Trigger and decision**: why now, what they compared, why they chose.
5. **Rollout**: what it took, honestly.
6. **Results**: numbers with time frames and how they were measured.
7. **What's next**.

### 3. Use quotes well
Two to four quotes, each doing a job: the pain, the decision, the result. Edit for length, never for meaning, and get approval on the final wording.

### 4. Make the versions
- Website: 600-900 words with the structure above.
- Sales one-pager: snapshot, before and after, three results, one quote.
- Cold email paragraph: one sentence of before, one of after.
- LinkedIn post: the story in 150 words with the turning point.

## What good looks like

- The headline number is specific, time-bound and approved.
- The "before" is vivid enough that a prospect recognises themselves.
- Doubts and bumps are included; they make the result credible.
- The common mistake is a page of praise ("They're a great partner!") with no numbers and no story.

## Rules

- MUST get customer approval for name, quotes and numbers before publishing.
- MUST state how and over what period results were measured.
- NEVER round up results or combine customers into one story.
- NEVER publish an anonymised story with details that identify the customer anyway.

## Example prompts

- "Turn this interview transcript with Northwind into a case study and a one-pager."
- "Write interview questions for a customer who cut onboarding time by half."
- "Make a cold email paragraph and a LinkedIn post from our Contoso case study."
