Case study one-pager template (a layout that actually gets read)
Last updated July 20, 2026
A case study one-pager compresses one customer story onto a single printed page: a context line establishing who the customer is, a before/after showing what changed, three proof points, one quote, and one call to action. What follows is a structure template — the lines describe each zone of the layout, and every example is an illustrative placeholder to replace with a real, approved customer story of your own.
The one-page limit enforces the right discipline: one customer, one arc. The most common case-study failure is cramming every win onto the page until no single result is legible. Pick the story whose problem most resembles your reader's, and let the other stories wait for other readers.
Key takeaways
- This is a structure template — the lines describe layout zones, and all example content is placeholder to swap for a real customer story you have permission to tell.
- One customer, one arc: a before/after built around a single headline change outperforms a page crammed with every metric you've got.
- The context line does the targeting — your prospect should recognize themselves in the first line, or the rest of the page never gets read.
- Proof points carry what happened; the quote carries how it felt — don't spend the quote restating a number.
- A case study matched to the recipient's situation, mailed by name in a FedEx envelope, is one of the highest-response sends in physical outbound.
The template
Six zones, top to bottom. Everything in brackets — including the sample phrasings — is illustrative placeholder text: the structure is the template, and the content comes from a real story your customer has approved.
The layout — zone by zone
[ZONE 1 — CONTEXT LINE · top of page, above the headline] One line telling the reader this story is about someone like them: [customer descriptor, e.g. 'A ~400-person logistics company running legacy dispatch software']. Use real, approved details — or the anonymized variant below.
[ZONE 2 — HEADLINE] The result as a sentence: [what changed, e.g. 'From (before state) to (after state) in (timeframe)']. Drawn from the real story; specific enough to be believable.
[ZONE 3 — BEFORE / AFTER · two parallel columns] Before: two or three lines on the old state and what it cost. After: the same lines, transformed. Keep the structure parallel — the reader's eye does the comparison for you.
[ZONE 4 — THREE PROOF POINTS · row of three] [Approved metric or fact 1] · [Approved metric or fact 2] · [Approved metric or fact 3], each with a short label. Three is the ceiling — past that it reads like marketing.
[ZONE 5 — QUOTE · visually set apart] One or two sentences in the customer's own words, attributed as [Name, Title, Company] with their sign-off. The quote's job is voice, not statistics.
[ZONE 6 — CTA] One line connecting the story to the reader: ['Facing the same problem? 20 minutes: yourco.com/meet'].
Why this layout works
The context line is the whole targeting mechanism: buyers believe stories about companies shaped like theirs and discount everything else, so the first line has to close that distance before the headline spends any attention. The before/after band works because readers process change faster than states — two parallel columns tell a story at a glance that a paragraph would bury.
The three-point ceiling on proof is a credibility rule: one strong number is memorable, three build a case, six start canceling each other out. The quote earns its space only by doing what numbers can't — conveying what the change felt like from inside the team. And every element on the page must be real and approved: a case study is only as strong as your permission to tell it, and nothing here should ever be invented.
Variant: the metric-led layout
When one approved number is genuinely strong, build the page around it instead of the narrative.
Variant — metric-led layout
[HERO NUMBER · top half of the page] The single approved metric, set very large: [the number]. One line of plain context beneath it — what it measures and over what period.
[HOW IT HAPPENED · three short steps] The path from before to after in three moves: [what they changed first], [what that unlocked], [where it landed]. Keep each to a line and a sentence.
[QUOTE + CTA · bottom band] A short attributed quote beside the single ask. The number opened the page; the human voice closes it.
Variant: the no-numbers layout
Enterprise, security, and healthcare customers often can't approve metrics for publication. Anonymized is not invented: the story stays real and approved — the identifying details are disguised, with the customer's agreement on how they're described.
Variant — anonymized, narrative-led layout
[CONTEXT LINE] An approved anonymized descriptor: ['A Fortune-500 financial services firm', 'A multi-state hospital network'].
[THE SITUATION · one short paragraph] The problem in narrative form — what was breaking, who felt it, what it was costing in operational terms.
[WHAT CHANGED · three qualitative proof points] Concrete operational facts in place of metrics: [what the team stopped doing by hand], [what became possible that wasn't], [how far the rollout spread].
[QUOTE · attributed by role only] ['Title, industry'] — with the customer's sign-off on both the wording and the attribution level.
[CTA] Same rule as always: one line, one ask.
How to send it
Selection is most of the outcome: match the story to the recipient — same problem first, similar size second, same industry third — and say in a short cover letter why you chose this story for them (the letter craft is at /blog/b2b-direct-mail-letter-template). Upload your design to B2BMail or have it AI-generated, and the page is printed and shipped in a FedEx envelope via FedEx Priority to the named contact, with the address verified as deliverable before anything prints. A case study that answers a specific objection is also a classic stalled-deal send — per-piece tracking shows the day it lands, so the rep can call while the story is still on the desk.
Frequently asked questions
What if my customer won't let me use their name?
Use the anonymized variant: keep the story real and the approval explicit, and disguise the identifying details with the customer's agreement on exactly how they're described. What you can't do is fabricate — a composite or invented story presented as a customer result will eventually be asked about in a live deal, and the cost of that moment far exceeds the value of the page.
How many case studies do I need before mailing them?
One good one, well matched, beats five shallow ones. If you have a single approved story, build this page around it and send it only to prospects whose situation genuinely resembles it. Depth and match quality drive response; volume of stories doesn't.
Does the case study need to match the prospect's industry exactly?
Match the problem first, company size second, industry third. A reader facing a messy systems migration cares more that your customer faced the same migration than that both companies share an industry code. When you do have an exact industry match, lead with it in the context line — it's the strongest opening a case study page can have.
Land on every prospect's desk
B2BMail puts your message in a FedEx envelope on the desk of every decision-maker at your target accounts — with per-piece tracking and every address verified before it ships.