How to Write a Case Study

When I finally got the CFO to sign off on the draft, I realized the narrative had to be tighter than a courtroom brief. The first paragraph I sent back was a single sentence: “Our new pricing model lifted monthly recurring revenue by 12 % in Q2.” That line forced every later section to prove the claim, not merely describe it.

The hardest part isn’t finding data; it’s deciding which data to foreground. In my last project, I tossed out three charts that looked impressive but added nothing to the client’s decision point. The remaining chart—customer churn before and after the intervention—became the visual anchor for the whole story. Keep the reader’s question in mind: “What did we change and why does it matter to me?” Every paragraph should answer that question directly.

A case study lives between a press release and a research paper. It must be credible enough for a skeptical board member, yet readable enough for a junior analyst. That balance comes from a disciplined outline, a clear voice, and ruthless editing. Below is a workflow that has produced more than a dozen publishable studies for B2B services, SaaS platforms, and nonprofit programs.

Step by Step

1. Pick the focal outcome and lock it down – Choose one metric that tells the story. In a recent health‑tech case, I selected “patient adherence rose from 68 % to 84 % within six weeks.” I discarded secondary metrics like “average session length” because they diluted the headline.
2. Identify the decision‑maker who will read it – Tailor the narrative to the person who will act on it. For a logistics client, the primary audience was the VP of Operations; I therefore emphasized route‑optimization savings rather than software uptime.
3. Gather raw data and verify it – Pull the original source files, not the summary slides. I requested the raw CSV from the finance team, ran a sanity check (no negative values, correct date formats), and saved a copy with a timestamp. This step prevented a later audit discrepancy.
4. Craft a “problem → solution → result” hook – Write a one‑sentence hook that juxtaposes the pain point with the quantified outcome. Example: “When delivery delays cost the company $250 k per month, our routing algorithm cut late shipments by 37 % in the first quarter.” The hook appears at the top of the executive summary.
5. Select two supporting quotes that add human perspective – Interview a frontline employee and a senior manager. I quoted the warehouse supervisor: “Before the new system, we were guessing; now we know exactly where each pallet is.” The senior manager’s line reinforced the business impact.
6. Design a single visual that encapsulates the result – Choose the chart that most clearly shows the change. I used a side‑by‑side bar chart comparing “Monthly Revenue” before and after the rollout, annotated with the 12 % lift. Simpler visuals reduce cognitive load.
7. Edit for brevity and consistency – Run a word‑count check; each section should stay under 250 words. Replace passive verbs with active ones, and ensure tense consistency. The final draft for the SaaS case ended up at 1,842 words, well within the client’s 2,000‑word limit.

A Simple Structure to Follow

Title: [Client Name] – [Brief Outcome]

1. Executive Summary (150‑200 words)
 - Hook sentence
 - Core metric
 - One‑line recommendation

2. Background (200‑250 words)
 - Industry context
 - Client’s initial challenge
 - Stakeholder quote

3. Approach (250‑300 words)
 - Solution description
 - Implementation timeline
 - Key decision points

4. Results (300‑350 words)
 - Before/after metrics
 - Visual (chart or table)
 - Two supporting quotes

5. Takeaways (100‑150 words)
 - What readers can apply
 - Potential next steps

Copy the table into your document and replace the placeholders. The sections are deliberately sized to keep the whole piece under 2,000 words, a common limit for B2B publications.

The Length Question

Readers rarely finish a piece that feels endless. In my experience, a case study that exceeds 2,500 words sees a 30 % drop‑off in completion rates, according to internal analytics. Aim for 1,800–2,000 words for a full‑funnel audience; trim aggressively if you hit 2,200. A good rule of thumb: if a paragraph can be expressed in fewer than 45 words without losing meaning, cut it. When you reach the word‑count ceiling, revisit step 6 and see whether a visual can replace a paragraph of explanation.

Tone for Skeptical Stakeholders

A CFO will scan for ROI, a technical lead will hunt for architecture details, and a marketing director will look for brand impact. Use a neutral, data‑first tone for the first two, then sprinkle in narrative flair only where it serves the decision. In a recent case for a nonprofit, I wrote the results section in plain language (“We reduced the time to process applications from 12 days to 4 days”) and saved the technical deep‑dive for an appendix. This approach kept the main body under 1,600 words while still providing the depth a technical reviewer expects.

A Worked Excerpt

> Executive Summary

> When the retailer’s checkout abandonment rate hovered at 28 %, our personalization engine lowered it to 19 % within eight weeks—a 9‑percentage‑point improvement that translated to $1.2 M in additional annual revenue. The recommendation: roll out the engine to all online channels by Q4.

> Results

> Before: Average cart value $84, abandonment 28 % (Jan–Mar).

> After: Average cart value $89, abandonment 19 % (Apr–Jun).

> The bar chart below shows the month‑over‑month decline. “Customers now see offers that actually match their browsing history,” said the senior merchandiser, confirming the qualitative shift.

This excerpt demonstrates how the hook, metric, and quote sit together without extra fluff. Replicate the pattern in each section of your own study.