Most case study pages bury the result.
The structure goes: client logo, then "About the client" (three paragraphs about the company nobody asked for), then "The challenge" (more paragraphs), then "Our approach," then "The solution," then finally — at the bottom of the page where nobody scrolled to — the number that justified the whole thing. "Conversion increased 47%."
The visitor who would have been sold on that number left at "About the client."
This post is the structure that actually sells: result-first, with the supporting evidence stacked behind it for the visitor who wants more. Most case studies need to be rewritten, not redesigned. The rewrite is the same shape every time.
Why case studies underperform
Three reasons we see consistently:
The narrative is biographical, not commercial. The page tells the story of the project (we did A, then B, then C, then we shipped). Visitors don't care about the chronology. They care about whether the result is something they could replicate.
The numbers are decorative, not central. "47% increase in conversion" appears as a callout in a colored box halfway down. It should be the largest text on the page.
The "Why we picked this studio" angle is missing. A good case study tells the visitor why this team was the right choice for this work. Without that, the visitor reads it as "this client got results, sure," and doesn't connect the dots to themselves.
The result-first structure
A case study that converts has the same five sections, in this order:
Section 1: The headline result
The largest text on the page. One sentence that captures the win.
Bad: "How Acme Corp transformed their digital presence."
Good: "Acme Corp's conversion rate doubled in six weeks after we rebuilt their landing page."
The headline needs three components: the client (or generic descriptor), the metric, the timeframe. If you can't write a headline that has all three, the case study isn't done yet — go back and get the data.
Section 2: The result in one paragraph
Two to four sentences immediately under the headline. The numbers, with context.
"Acme Corp's primary landing page was converting at 2.1%. We rebuilt the page over four weeks with new positioning, structure, and visual design. Six weeks after launch, the conversion rate had risen to 4.2%, with no change in traffic mix. The improvement has held for the four months since."
That's the entire case study, condensed. A visitor who reads only the first 100 words should know the result and the cause. Everything below is for the visitor who needs more evidence.
Section 3: What was wrong before
Now you can describe the problem. Specifically. With numbers if possible.
"The original page was a 47-section scroll built on Webflow. Lighthouse Performance was 42 on mobile. The conversion path was visible only after scrolling past three above-the-fold sections. Forms had eight fields. The page hadn't been touched in 18 months."
This section serves two purposes:
- It establishes the starting point so the result feels earned.
- It lets the visitor recognise their own situation. If you describe the symptoms they have, they'll trust the cure you prescribe.
Section 4: What we did, in narrative
A focused account of the work. Not a full chronology. The 5-8 decisions that mattered.
The shape that works: each decision gets a paragraph, named explicitly. "We moved pricing from below the fold to the third section." "We rewrote the headline to lead with the outcome, not the product." "We cut the form from eight fields to three."
What to avoid: long descriptions of process. Visitors don't read "We held a discovery workshop, then conducted user research..." They read "We changed the headline."
This is also where the case study can talk about why this team. Specific decisions are specific to the team that made them. A generic "we improved the design" doesn't differentiate. "We rewrote the value proposition to remove industry jargon" does.
Section 5: The result in detail
Now you can show the numbers in full. The headline metric expanded. The secondary metrics. The qualitative quote from the client.
A pattern that works: a table or a small set of cards, each showing one metric, with "before" and "after" values.
- Conversion rate: 2.1% → 4.2%
- Lighthouse Performance: 42 → 96
- Form completion rate: 31% → 64%
- Time on page: 1m 12s → 2m 48s
Then one paragraph putting the numbers in context (revenue impact, customer feedback, what's next).
The client quote belongs at the end of this section. Not the top of the page (where it reads like marketing copy from the client's POV) and not buried (where it loses weight). At the bottom of the results section, it punctuates the story.
A worked example: rewriting one
Here's a case study we rewrote for a client recently. The original opening:
About SomeCo
>
SomeCo is a B2B SaaS company specialising in workflow automation for mid-market firms. Founded in 2019 and based in [city], they serve over 200 customers globally...
Three paragraphs of "About SomeCo." The reader has no reason to keep going.
The rewrite:
SomeCo's free-trial signup rate went from 2.4% to 5.1% after we rebuilt their landing page over four weeks.
>
The original page treated the visitor as already-convinced. The hero was a product screenshot with no headline. Pricing was on a separate page. The signup form had nine fields. We replaced all three. The new page leads with the use case, makes pricing visible in the third section, and asks for two fields to start a trial.
Same content. Same client. The first version led with "About SomeCo." The second version led with the result. The visitor who would have left at the first paragraph stays for the second.
Supporting elements worth including
A few things that earn their place if you have them:
A screenshot pair. Before and after, side by side. Annotate what changed. Visitors believe images more than they believe paragraphs.
A direct client quote. Not "We had a great experience working with [studio]." Something specific: "We were spending $400 per signup. Now it's $190. The page paid for itself in the first month."
A breakdown of the work. If you did discovery → design → build → launch, name them, but in a one-paragraph summary, not a five-section walkthrough.
A "what we learned" section. One paragraph at the end, optional, where the studio reflects on what was unusual or hard about the project. This humanises the page in a way the case-study format usually flattens.
What to drop
Things we see in most case studies that don't earn their place:
- "About the client" sections longer than two sentences.
- "The challenge" sections that describe the problem in vague terms ("they wanted to improve their conversion") instead of specific terms.
- "Our process" sections that explain how every project goes ("we start with discovery..."). Visitors didn't come for your process; they came for this project's result.
- Stock photos of the team. Either use real photos from the project (whiteboards, sketches, screens) or none at all.
- A long testimonial without a name. If you can't name the source, the testimonial is doing the opposite of building trust.
When not to write a case study
Sometimes a case study isn't the right format. Skip it when:
- The result is real but tiny. A 3% lift isn't a case study; it's a footnote.
- The client won't let you name them or share specifics. An anonymous case study with no concrete data has the credibility of an unattributed quote.
- The project was a partial success. Half-wins don't make compelling case studies. Use it internally as a learning, not externally as marketing.
- The client churned. Self-explanatory.
Better to ship fewer case studies that are real than many that are vague. Two strong case studies outweigh ten weak ones.
A checklist
- The largest text on the page is the result, not the client's name.
- The first 100 words contain the metric, the client, and the timeframe.
- "About the client" is two sentences max, or omitted.
- Specific numbers, not vague claims.
- Before/after comparison is visible without scrolling far.
- The client is named (or, if anonymous, the reason for anonymity is explained).
- One named, specific testimonial.
- The narrative tells the visitor why this team, not just what was done.
Hit eight of eight, and the case study earns the visitor's read. Most case studies hit two or three. Rewriting them in the result-first structure is one of the highest-leverage marketing changes most B2B sites can make.
If you want case study pages built (or rebuilt) with this structure, see how we work on websites.