Menu

Individual skill

case-study-builder

Turn a customer win into a credible case study - interview-driven raw material, a challenge-solution-results arc, and a quantified results section with real customer quotes. Use when someone asks "write a case study from this customer call", "turn this win into a customer story", "what should I ask the customer in the interview", or "make our results section stronger". Do NOT use for collecting short standalone quotes or review snippets - testimonial capture is upstream raw material for this skill. Do NOT use for packaging finished case studies into battlecards and sales collateral - use sales-enablement-kit instead.

skills/case-study-builder/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Case Study Builder

A case study sells by proof, not adjectives - the customer and the numbers do the talking. The costly mistake is writing it backwards: drafting marketing copy first and asking the customer to bless it, which produces approved-by-legal mush with no quotes worth reading and no numbers worth citing. Get the raw material first; the story is assembled, not invented.

## Operating procedure

The order matters: interview before outline, numbers before draft. A draft written before the interview anchors on your product's talking points instead of the customer's actual story.

### Step 1: Gather inputs

1. The customer: company, industry, size, and the buyer persona this case study should persuade (default: mirror the customer's own profile - readers trust stories about companies like theirs).
2. Access: can you interview the customer live (best), send written questions (acceptable), or only mine existing calls/emails/reviews (weakest - flag the limitation)?
3. Any numbers already known: baseline metric, result metric, timeframe. Label estimates as estimates.
4. Distribution target: web page, PDF leave-behind, or sales deck slide (default: one-page web layout).