Case Study skill
The playbook Moonrank's Writer Agent uses to turn a customer win into a case study a skeptical buyer believes — challenge, solution, and results with the numbers attached.
Download the methodology, see how the agent structures the arc, or run it live inside the Writer Agent.
- Category
- Writer
- Agent
- Writer Agent
- Format
- case-study.md
- Price
- Free to download
The skill file
What is the Case Study skill?
The Case Study skill is how Moonrank's Writer Agent turns a customer result into proof: extracting the before and after numbers, reconstructing the decision the customer made, and writing the arc so the result is verifiable instead of vague.
It's written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Read it to run your own customer interviews, hand it to whoever writes your case studies, or let the Writer Agent draft from your interview notes and data.
Downloading the playbook is free with a Moonrank account. Drafting case studies from real customer data and keeping your proof library current is what the Writer Agent does.
See it in action
“We have a customer who tripled their signups with us. How do I turn that into a case study sales will actually use?”
"Tripled" is a claim; 340 to 1,020 signups a month over 14 weeks is proof. The draft opens with that number in the headline, spends one section on what the old process cost them — 12 hours a week of manual work — and two on the three changes they made. One approved quote, one honest caveat, and a snapshot box sales can screenshot into any deck.
From input to fix list
- 1
You provide the win
The customer, the outcome, and the interview notes or data behind it.
- 2
Moonrank extracts the numbers
The Writer Agent isolates the before-metric, the after-metric, and the timeframe — or flags that the story isn't a case study yet.
- 3
It reconstructs the arc
What the problem cost, what the customer tried first, and the concrete steps that produced the result.
- 4
It drafts for sign-off
A results-first draft with every number and quote marked for the customer's written approval.
Everything it checks
Numbers-first gate
No before/after metrics means no case study — the skill says so and routes you to a testimonial instead.
Result-led headline
Customer plus specific result plus timeframe — never "How X uses Y".
Cost of the problem
What the before-state cost in money, time, or risk, in the customer's words.
Decision reconstruction
What they tried first and why it failed — the section skeptical buyers actually read.
Metrics in context
Baselines, timeframes, and one honest caveat, so the numbers survive scrutiny.
Approval checklist
Every number and quote signed off in writing before anything ships.
When to reach for it
- Turn a customer interview into a publishable case study.
- Give sales a proof asset for a specific vertical or objection.
- Rewrite feature-tour case studies into result-led ones.
- Build a proof library that AI answers can cite by name.
- Standardize how every customer story gets told and approved.