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).

Step 2: Run the interview - get the quote raw material first

Never draft before this step. Ask in this order, and record verbatim answers:

1. "What was breaking, in your own words? What did it cost you - time, money, morale?" (problem + stakes)
2. "What had you tried before? Why didn't it work?" (failed alternatives - this is where credibility lives)
3. "What almost stopped you from buying?" (objection - the most persuasive quote in most case studies)
4. "Walk me through what changed after. What can you do now that you couldn't?" (solution in their words)
5. "What numbers moved? Even a rough range." (results - push politely: "was it closer to 10% or 50%?")
6. "What would you tell someone in your seat considering this?" (the closing quote)

Keep quotes raw. "It was a dumpster fire every quarter-end" outsells "the process presented efficiency challenges." Clean grammar only; never sand off voice.

Step 3: Quantify the results - the no-number rule

Never ship a case study without at least one number in the results section. In order of preference:

1. Exact metric with timeframe: "reduced close time from 14 days to 6 in one quarter."
2. Percentage: "cut onboarding time 57%."
3. A range, when exact figures are confidential: "saved 10-15 hours per week" - ranges are honest; vagueness is not.
4. A countable proxy if no metric exists: headcount redeployed, steps eliminated, tools replaced.

If the customer genuinely cannot provide any of these, pause the case study and go back for measurement - or downgrade the asset to a testimonial (that capture work is upstream of this skill).

Step 4: Build the challenge-solution-results arc

1. The customer - who they are and why a reader like them should care. Two sentences.
2. The challenge - the pain in their words, with stakes and failed alternatives.
3. The solution - what they did, concretely; your product's role honestly scoped. The customer is the hero; the product is the tool.
4. The results - the headline number, secondary outcomes, and a quote. Lead the whole piece with this: put the headline result in the title and pull-quote the key metric, because readers skim.

Step 5: Draft into the skeleton, then get approval

Fill the template below. Send the customer the final draft for approval of quotes and numbers only - do not invite line-editing of your prose, which is how voice dies.

Case study skeleton template

TITLE: How [FILL: customer] [FILL: headline result with number] with [FILL: product]

PULL QUOTE: "[FILL: strongest verbatim quote with a number or stake]" -
[FILL: name, title, company]

THE CUSTOMER (2 sentences)
[FILL: who they are, size/industry, why readers like them should care]

THE CHALLENGE
[FILL: the pain in the customer's words, what it cost them,
what they tried before and why it failed - 2-3 short paragraphs]

THE SOLUTION
[FILL: what they implemented and how, concretely; product's role
honestly scoped; 1 verbatim quote about the buying decision or objection]

THE RESULTS
- [FILL: headline metric - before → after, with timeframe]
- [FILL: secondary outcome with number or range]
- [FILL: qualitative outcome]
"[FILL: closing quote - what they'd tell a peer]"

CTA: [FILL: one soft next step relevant to readers in the same situation]

Results section: bad vs good

Bad: "Since adopting the platform, Acme has seen significant improvements in efficiency and team satisfaction. The tool has become an integral part of their workflow, and they couldn't be happier with the results."

Good: "Acme cut quarter-end close from 14 days to 6 within two quarters - and reclaimed roughly 30 controller hours per month. 'The first close after rollout, I went home on time. My team noticed before I did,' says Dana Reyes, VP Finance."

Why the good one works: a before/after number with a timeframe, a countable secondary outcome, and a human quote that carries the emotion the adjectives were faking.

Deliverable

Produce a one-page case study containing: a headline with the key number, a pull-quoted metric, the challenge-solution-results arc with at least two verbatim customer quotes, a results section with at least one quantified outcome, and a soft CTA - plus the interview notes as an appendix for reuse.

Do NOT

• Do not draft before the interview; you will write your pitch, not their story.
• Do not ship without a number - an unquantified case study is a testimonial wearing a costume.
• Do not replace ranges with vagueness; "saved 10-15 hours/week" is credible, "saved significant time" is filler.
• Do not make the product the hero; readers identify with the customer, and product-hero stories read as ads.
• Do not let legal/PR rewrite quotes into corporate speak - offer to cut a quote rather than lobotomize it.

Quality bar

• The headline contains the key result.
• At least one quantified outcome (exact, %, or range) with a timeframe in the results section.
• At least two verbatim quotes that sound like a human, including one about the problem or the objection.
• The product appears in a supporting role; the customer drives every turn of the story.
• One page; the key metric is pull-quoted; the CTA is soft and situation-matched.
• Customer has approved quotes and numbers in writing.

Upstream: gather short standalone quotes via testimonial capture before running this skill. Downstream: package the finished study into battlecards and one-pagers with sales-enablement-kit.