How To Write a Case Study for a Company: 10 Sections to Include
If you're interning at a startup or small company and someone just handed you a finished project and asked you to "write it up as a case study," you've probably realized nobody actually explained what that means. A case study isn't a report, and it isn't a testimonial. It's a structured story about a real problem, a real solution, and a measurable result, and it follows a fairly predictable shape once you know what to look for.
This guide walks through the ten sections a strong business case study includes, in the order they usually appear, and what each one is actually doing for the reader.
A case study is a great way to understand businesses, and the skills used there are also useful for business internships, if you’re curious as to what you can learn, check out this blog here!
This guide walks through the ten sections a strong business case study includes, in the order they usually appear: title, summary, client background, challenge, goal, approach, solution, results, testimonial, and call to action. A case study works because it proves a claim with a specific story, not because it summarizes a project. Get the real numbers from whoever ran the project before you write a single section; a case study without a genuine results section falls apart. It's useful for any intern or new hire asked to turn a completed project into marketing or portfolio material, and most run 500 to 800 words covering all ten sections without padding any of them.
Why do companies write case studies in the first place?
Companies write case studies to do one job: prove that a product, service, or approach actually worked, using one specific, real example instead of a general claim about the company. Anyone can say their marketing agency 'drives results.' A case study is what a company publishes instead of saying that
This is also why case studies show up so often during internships. Interns at a program like Ladder Internships are frequently the ones asked to write the first draft, since the person closest to the project's daily details (the timeline, the specific decisions, the exact numbers) is often the intern who worked on it, not the manager who oversaw it from a distance. More on that below.
What's the default shape a strong case study follows?
The default shape follows ten sections, in the order most case studies actually use them, rather than a handful of loosely patched-together paragraphs that read like an internal memo instead of something a prospective client would want to read. The ten sections below cover the version companies actually publish, in the order most case studies use them.
Not every case study needs every section in every situation, and a short one might compress two of these into a single paragraph. But this is the default shape to start building from before you cut anything.
Section 1: The title
The title of a case study needs to do more work than a blog title does. It should name the client, the industry, or the specific result, not just the general topic. "How We Helped a Local Bakery Increase Online Orders by 40%" tells a reader in five seconds whether this case study is even relevant to what they're looking for, and "A Marketing Case Study" never will.
If a real number is available, put it in the title. A specific result-driven title, a percentage, a dollar figure, a timeframe, pulls in exactly the reader a company wants: someone deciding whether to work with them on a similar problem.
Section 2: The summary or snapshot
Right under the title, most case studies include a short snapshot: the client's name and industry, the core problem in one line, and the headline result in one line. Think of it as the version someone reads if they never make it past the first paragraph, since plenty of readers won't.
This section is often formatted as three or four short lines rather than a paragraph (Client, Challenge, Result), which is one of the few places outside the numbered body where that kind of formatting is expected. It exists purely so a skimming reader gets the shape of the story before committing to reading the rest.
Section 3: The client background
Before the reader can understand why a problem mattered, they need to understand who had it. This section gives a short, factual introduction to the client: what the company does, roughly how big it is, and anything about its situation that makes the coming challenge make sense.
Keep this section tight. Its only job is giving the reader enough context to care about the problem, not telling the client's full story. A paragraph is usually enough, two at most.
Section 4: The challenge
This is where the actual problem gets named, specifically. Not "the client wanted to grow," but the real, concrete obstacle they were facing: a stalled metric, a broken process, a deadline they were about to miss. Vague challenges make everything that follows feel less earned.
The stronger case studies also explain why the problem was hard, not just that it existed. Why hadn't the client already solved it themselves? What had they already tried that didn't work? That's usually the detail that makes a reader trust the solution that comes next.
Section 5: The goal
The goal section states, in plain terms, what success would have looked like before the project started. This is easy to skip past because it feels obvious, but it's what lets the results section later actually land as a result instead of just a number floating on its own.
A useful goal is specific and, where possible, measurable before the work even begins: increase sign-ups by a target percentage, cut a process from five days to two, and reach a defined audience size. A vague goal like "improve visibility" makes it much harder to prove anything happened later.
Section 6: The approach
Here's where the case study explains the thinking behind the solution, before describing the solution itself. What options did the team consider? Why did they choose this direction over another one? This section is about judgment, not just activity, and it's often the part that impresses a reader most, since it shows the company thinks strategically rather than just executing tasks.
Keep this section honest. If the approach involved trade-offs, a smaller budget than ideal, a shorter timeline than requested, say so. A real constraint handled well reads as more credible than a project that sounds like it had no obstacles at all.
Section 7: The solution or implementation
This is the part most people picture when they think of a case study: what was actually built, run, or changed. Walk through it clearly enough that a reader unfamiliar with the client's industry could still follow what happened, without drowning the section in internal jargon.
Specificity is what separates a strong solution section from a generic one. Naming the actual tactic, tool, or process used, not just the category it belongs to, is what makes a reader believe this is a real project and not a marketing summary written after the fact.
Section 8: The results
The results section is the section the rest of the case study exists to set up, and it needs real numbers. A percentage increase, a dollar figure, a time saved, whatever metric was defined back in the goal section. If the actual data isn't available yet, that's a sign the case study isn't ready to write, not a reason to estimate one.
Where possible, show the before-and-after, not just the after. "Orders increased by 40%" means far more next to "from 50 orders a month to 70" than it does floating alone. Specific, verified numbers are what turn this section from a claim into proof.
Section 9: The testimonial
A short quote from the client, ideally naming a person and their title, adds a kind of credibility a company can't generate about itself. It doesn't need to be long. One or two sentences that capture what the experience was actually like, or what the result meant to them, does more work than a paragraph of praise.
This section only works with a real quote the client has actually approved, never one written on their behalf and assumed to be fine. If a quote isn't available yet, it's worth asking for one directly rather than skipping the section or inventing something close enough.
Section 10: The call to action
Every case study ends by telling the reader what to do with what they just read. That might be scheduling a call, requesting a similar service, or simply reading another case study. Without this section, a genuinely convincing story just ends, with nowhere for an interested reader to go next.
Keep it short and specific rather than generic. A single clear next step, one link, one action, does more than a paragraph restating how great the results were. The results section already made that case.
How do you actually gather the material before you start writing?
The order above is the order you write about, not necessarily the order you gather information in. In practice, start by tracking down the real numbers, the actual goal, the actual result, before writing a single sentence, since the whole piece is built around proving that gap between the two.
Interns are often the ones asked to draft a case study precisely because they were closest to the work, and a structured program like Ladder Internships builds that skill in directly: working alongside a company manager on a real project, then having a dedicated Ladder Coach to review the draft before it goes anywhere near a client, catches the vague claims and missing numbers before they become a problem.
Common questions about writing a case study
1. Do I need the client's permission before publishing a case study?
Yes, always. Get sign-off on any quote, number, or specific detail before it goes public, even if the client seems enthusiastic about the project. Skipping this step is the most common way a case study gets pulled after the fact.
2. How long should a case study actually be?
Most run 500 to 800 words, enough to cover all ten sections without padding any of them. A case study with a dramatic result can sometimes run shorter, since the numbers do most of the persuading on their own.
3. What if the results weren't especially dramatic?
Be honest rather than inflating the number. A modest but real result, framed clearly against the original goal, is more convincing than a vague claim that sounds bigger than it actually was.
4. Can I write a case study for a project I only partly worked on?
Yes, but get the missing pieces, especially the exact numbers and the client quote, directly from whoever else was involved rather than guessing. A case study is only as strong as its least verified detail.