The Case Study Structure That Sales Teams Actually Use

Image URL

Do not index

AI summary

A case‑study framework that sales reps can instantly use by filling six slots—headline with a metric, who, the number or proxy, a brief “before” description, the current “Tuesday” outcome, and a quote—then extracting three artifacts: a four‑line email block, a one‑page sales sheet, and a longer detailed page; the guide stresses focusing on concise, quotable content, obtaining permission, and avoiding traditional Situation‑Solution‑Result structures that don’t serve quick sales needs.

Title

The Case Study Structure That Sales Teams Actually Use

Date

Apr 18, 2026

Description

Case study format examples built from how a rep uses the asset: skimmed on a phone, pasted into an email, one metric quoted on a call — not PSR.

Status

Done

Current Column

Published ✨

Person

Writer

You published a 2,000-word case study on /customers.

The rep opened it on a phone, skipped the company history, and pasted one sentence into an email.

That sentence is the structure that got used. The rest of the page did not.

Most case study format examples teach Situation / Solution / Result. That produces a page. It does not produce the three things a deal actually needs: something a stranger can skim on a phone, something a rep can paste without hunting a PDF, and one metric they can quote on a call without looking down.

This page works backwards from those three uses. Fill six slots in scan order. Ship three artifacts from the same slots. The long page is what is left, not the deliverable.

If you still need the interview itself — pick, invite, collect without a calendar link — that is our guide to customer case studies. If you want a quote next to a pricing button rather than a sales asset, start with the whole testimonial pipeline. This page is the layout the answers go into.

The three uses, before you write a word

Do not pick a format from a catalog. Video, hybrid, vertical, PSR — those are production choices. They are not the job.

The job is a live deal. Three moments, in the order they actually happen.

One metric, quoted on a call

The rep is sharing a screen. They have eight seconds before the prospect asks a different question.

They need one line they can say without looking down. A number with a before attached, or a named change if the number is not shareable.

"They cut the Friday report to a Tuesday morning" is quotable.

"They saw significant efficiency gains across their workflow" is not. Nobody says that out loud. It is brochure copy wearing a result's clothes.

If you cannot say it in one breath, it is not the call asset. It is a page.

Four lines, pasted into an email

This is the one that decides whether the case study exists.

If the rep has to find a PDF, download it, and attach it, they will send the pricing deck instead. The case study sits in a Drive folder named "customer stories" and the email goes out with a feature list.

Here is the block. Copy it. The [blanks] are yours.

[Name], [role] at [Company] — they were [before, one clause].
Now [named change or number], in [timeframe].
"[One sentence in their words.]"
[Link]

Four lines. Who, before, number, link. The quote is optional if it does not fit; the number is not.

If it does not fit in a reply without scrolling, cut it. I would rather send four honest lines than a "full story" nobody opens.

First screen, on a phone

A prospect is not reading. They are checking two things: does this person look like me, and is the number real.

First screen: headline with the outcome, who they are, the number. That is the whole screen.

Company founded in 2014. Forty-seven employees. "A culture of innovation." None of that is the first screen. It is the about-us page leaking into the sales asset.

If the number is below the fold, it might as well not be on the page.

Why Situation / Solution / Result fails these three

I would still use a before, a change, and a result. Those are the pieces. I would not ship them as three equal chapters.

PSR is easy to brief. Marketing likes it because every story uses the same headings. Sales does not open a page looking for the Situation heading. They look for a line they can steal.

PSR buries that line under "About [Company]" and a 400-word Solution that is a feature tour. The result arrives after the prospect has already bounced.

As of August 2026, Zapier's roundup of case study examples is still a gallery of challenge / solution / results — sixteen named companies, three templates. Useful if you want to see how other people package a page. It is not a layout a rep can paste. (The previous version of this URL cited Zapier for a "70% of top-performing examples follow PSR" figure. That number is not on their page. I am not repeating it.)

Result first. Before in one paragraph. Tuesday, not a product walkthrough. That is the whole argument.

The six slots, in the order a stranger hits them

This is not the order you collect in. Collect with the six questions on the pillar page. This is the order a stranger hits once the answers exist.

1. Headline a rep can say on a call

A number, or a named change, in one line. Same test as the call quote: if you cannot say it in one breath, rewrite it.

"How [Company] moved [task] from Friday afternoons to Tuesday morning."

Do not invent a percentage to make it punchier. The named change is a legitimate headline.

2. Who

Name, role, company, size if they gave it. Two seconds.

"[Name], the person who owns outbound at a 12-person agency" is enough. "[Name], marketing" is not. "A SaaS company in the Midwest" is an anecdote. I would not publish an anecdote as a case study.

The reader is trying to self-identify. What makes a testimonial good is the same test in a smaller space: a stranger has to be able to step into it.

3. The number, or the named proxy — on the first screen

Not in chapter three. Not after the implementation timeline.

If they gave you a figure, attribute it and date it. "According to [Name], [metric] went from [X] to [Y] in [timeframe]." If you measured it on your side, say that separately. Do not blend the two into one number.

If they cannot share a figure — board rules, a pending fundraise, a customer who is also a competitor — do not write "approximately 3x" because it felt like 3x. Use the proxy they actually offered:

A task that stopped (the Friday report, the weekly fire-drill)

A hire they did not make

A step that disappeared

A time of day something now happens

We do not have a figure for how often completed case studies contain a quantified result. I am not going to guess one. The rule is still: a named proxy beats a round percentage you cannot source.

4. Before — one paragraph, their words

The email's second line. The thing a prospect uses to check "did this person have my problem."

Clean the throat-clearing. Do not punch it up. "We had challenges with our previous process" is a Situation heading. "I spent Monday mornings exporting a CSV and emailing it to three people" is a before.

This is a teaching example, not a real quote. If the sentence could sit on any site in the category, it is not a before. It is praise with a frown.

5. What Tuesday looks like now

Not "the platform." Not a feature list.

A workflow, a number of tabs, a meeting that disappeared. The same level of grain as the before, or the after does not land.

If this slot is thin, one follow-up: "You said it saved time — can you say what that looks like on a Tuesday?" If they still shrug, cut the slot. Five honest pieces beat six with one you guessed.

6. One quote, in their words

Usually a sentence from slot 5 or 4. Not a third "highly recommend."

If you have tightened it, it goes back for approval. The moment a case study reads better than the person who signed it, it stops working.

A star rating next to the quote does none of the work. The name, the role, and the before already did it.

The slot PSR skips. "Who should skip this?" is not on the six-slot scan, and it is the sentence I would rather publish than another recommend. Put it on the long page. Leave it off the email block. A four-line paste cannot carry a limitation and a number; the number wins.

Build three artifacts from the same slots

You are not writing a page and then "repurposing" it. You are filling six slots, then cutting three objects from them. Do them in this order or the long page will eat the week.

Step 1 — Confirm you have answers, not a vibe

You need the six answers from the pillar, or a draft they can redline, or sentences they already said in a thread. If you have none of those, stop. How to ask for a testimonial is the social half of the ask; the case-study vehicle is the six questions with no calendar link. Do not open a blank doc and "find the narrative."

Step 2 — Write the email block first

Fill the four-line template above. Read it out loud.

If you cannot fill it, you do not have a case study yet. You have a long testimonial, or you have a hole. Go back to the thin slot. Do not proceed to Figma.

This is the quality gate. Everything else is optional.

Step 3 — The one-pager, same slots, one screen

Headline. Who. Number. Before. Tuesday. Quote. Link or CTA.

That is the page a counsel can clear in a day, and the PDF a rep can attach when someone actually asks for it. It is also the thing you send before the twelve-page version, because the twelve-page version will sit in someone else's legal queue until the win is no longer recent.

Do not add "About [Company]." Do not add a feature tour. Do not add three more quotes to make it look finished.

Step 4 — The long page last

For the person who clicked. Extra implementation detail, the "who should skip this" line, a second stakeholder if you have one. Still the same six slots at the top. If a phone-skimmer has to scroll to find the number, you built the brochure again.

/customers is fine as the archive. It is a bad only-home. If the story lives nowhere a deal is happening, you built a footer link.

Step 5 — Get permission on the short version

Ask in writing. Be specific about where it will appear — site, email, paid, sales deck are different yeses. Ask separately for the name, the job title, the company, and the face.

Send the one-pager first, not the long page. A counsel who can say yes to six slots will stall on twelve pages.

If they will not let you name the company, you do not have a case study. You have an anecdote. I would not publish it as one.

If anything changed hands — a discount, a free month, a gift card — the connection has to be disclosed. That is a requirement in several jurisdictions, not a nicety. The legal side of testimonials is the primer. Check your own jurisdiction rather than treating that page as advice.

Step 6 — Put the email block where reps actually type

A shared doc named paste-this.md. A snippet in the CRM. Four lines under the feature they hesitate on.

If the only copy of the block lives in Notion two folders deep, it will not get sent. The artifact that does not reach the deal is decoration.

The questions that fill the slots

Do not invent a second questionnaire.

The short-form four that produce a publishable testimonial live on questions to ask. The long-form six live on the customer case studies pillar. Send one set. Not both.

How those six land on this layout:

Who are you, and what do you actually do day to day? → slot 2

What were you doing about [task] before [Product], and what was broken about it? → slot 4, and the second line of the email

What almost stopped you picking us? → not on the one-pager. Put it next to the pricing button or the feature they hesitated on.

What does [task] look like now, on a normal Tuesday? → slot 5, and usually the quote

What has it got you — and if you can put a number on it, do? → slot 1 and slot 3

Who should skip this? → long page only

The manual path, if you want nothing from us: paste those six into an email, a Google Form, or a Notion page you share. Map the answers onto the six slots in a doc. Cut the email block. You are done enough to use it in a deal this week.

Where the questions break the layout. Fifteen questions. You turned a favour into a survey, and slots 5 and 6 come back as "see above." I would send six and stop. If one answer is thin, send that question back once, rewritten.

Where this breaks

You have praise and no before. Then you have a testimonial. Publish it as one. Do not dress it up with Situation / Solution headings and call it a case study. A prospect will notice.

You have a before and no number, and they offered no proxy. You can still ship an email block with a named change. You cannot ship a "3x ROI" headline. Write the named change. Live with it.

Legal wants a twelve-page PDF with methodology, logos at 2x, and a quote from the CEO. Sometimes that is the actual buyer. Do the one-pager first anyway, and let them ask for the rest. If you start at twelve pages, you will not finish.

You wrote the number in after they did not give you one. That is how you get a case study that reads better than the person who signed it. Delete the number. Send one follow-up. If they still cannot share it, the proxy or the named change is the honest version.

The customer churned, or the title is two jobs old. A dated case study from someone who left is worse than none. Re-ask once a year: still true, still a customer, still the same title? If not, retire it. Do not accumulate.

We do not have a completion rate for async interviews, and we do not have a figure for how many published case studies ever get pasted into an email. I would rather say that than invent one.

Doing this with Testimonial

The six slots above work in a Google Doc. You do not need us for that.

What async case-study interviews change is the gap between "they said yes" and "you have answers to drop into the slots." You build a question set — 5–10 questions, saved as a template — and send each customer their own link. No signup. They type, or they talk; voice is transcribed with ElevenLabs Scribe and dropped into the box as editable text. Original audio is kept for playback. Answers arrive pre-attributed. You can resend, remind, or revoke.

If someone scores 9 or 10 on an NPS survey, they can get the case-study invite automatically. That is a routing rule, not a new ask you have to remember. NPS and Case Study are both on the same plan.

Case Study is on Ultimate +. As of August 2026 that is $95/month/space, or $1,140 a year. Ultimate and Ultimate + are priced per space. The plans and pricing page is the live list.

Where it breaks, including for us. The product collects answers. It does not assemble the email block or the one-pager. You still map slots by hand. That is the whole point of this page, and pretending the tool emits a sales-ready PDF would be a lie.

The builder will let you write ten questions. I have seen people write ten. Completion falls off because you turned a favour into homework. I would put six and stop. The product will not stop you.

Async still needs them to open the link. A reminder helps. It does not create time they do not have. Nothing in the tool clears legal — approval is still a human email.

If you have one customer, they will hop on a Zoom, and you are happy to write from a transcript, do the Zoom. The tool earns its place when the backlog is eight names and you cannot keep booking around them.

A separate free case study generator will draft from testimonials you already have. That is a writing aid, not an interview, and not a layout. Use it after slot 3 has an answer. Do not feed it "write us a case study about Acme" and publish the output. That is how you get a story nobody said.

Wrapping up

Six slots, in scan order. Three artifacts from the same slots. Email block first — if a rep cannot paste it, you do not have a case study.

If you only do one thing this week, take a story you already published and cut the four-line block. Send that. Leave the 2,000-word page where it is.

Stuck on whether your draft is a case study or a long testimonial? Reply with the four lines — I will tell you which slot is empty.

Send the six questions to the next customer who said yes.