Writing case studies people actually finish

Most case studies are a project diary nobody reads to the end. A buyer wants to know whether you can solve their problem, so we write them backwards: the result first, then the decision that got there. The structure we use, and what we cut.

By Ketan Pandey Published October 18, 2026 3 min read Writing

A case study is the page a serious buyer reads just before deciding to contact you. Most are written as a diary of the project: the kickoff, the workshops, the moodboards, the three rounds of revisions, and a gallery at the end. The buyer skims for two things, whether you’ve solved a problem like theirs and what came of it, and leaves when they can’t find them. So we write case studies backwards: what changed first, then the one or two decisions that made it happen.

Who is reading, and what they want

The reader isn’t the client you worked with. It’s the next one, comparing you against two other studios with a dozen tabs open. They are asking three questions, roughly in this order:

Is this company like mine? Same stage, same kind of buyer, same kind of mess.
What changed? A result they can picture: a launch, a raise, a number that moved, a sales team that stopped apologising for the deck.
How did they think? Not every step, just the call that someone less experienced would have got wrong.

A diary answers the third question at length and buries the first two. Flip the order and the page does its job in the first screen.

The structure we use

One sentence of context. Who the client is and what they sell, written so a stranger understands it. “Slice is a new consumer bank in India, and we designed and launched its website in four weeks.” If the reader can’t place the client, nothing after it lands.

The problem, in their words. What was wrong before, stated plainly. A quote from the founder works well here because it sounds like a real person with a real worry, which is what the reader is too.

What changed. The result, as early as possible. Use a number when there is one and the client is happy to share it. When there isn’t, describe the outcome honestly: shipped in six weeks, used in the Series A deck, the sales team now leads with the site. A vague “elevated the brand” is worse than nothing, because the reader can tell you had nothing.

The decision that mattered. One or two, not ten. The positioning call, the thing you left out, the moment you pushed back. This is where expertise shows, so it gets the most care in the writing.

The work. Now the images. By this point the reader knows what they are looking at and why it looks the way it does, so the gallery reads as evidence rather than decoration.

What we cut

The process recap. “We began with a discovery workshop.” Every studio does. If a step was unusual, it belongs under the decision that mattered. If it wasn’t, it goes.
Adjectives about the work. “A bold, modern identity.” Let the images say whether it’s bold.
Every deliverable. A list of 40 assets says you were busy, not that you were good. Show the five that carry the idea.
Results you can’t stand behind. If a number came from the client’s own reporting, say so. If a result is still pending, mark it as pending. Buyers forgive a modest result far more readily than one that turns out to be inflated.

Length

Shorter than you think. The written part of a good case study is usually 400 to 700 words. Long enough to explain one real decision, short enough that someone reads it to the end on a phone. If a project has more to say, split it: a short case study for buyers, and a longer Note for the people who want the detail.

Make it readable by machines too

Buyers increasingly ask an AI assistant to shortlist studios, and the assistant reads your case studies to decide what you’re good at. The same structure helps: a plain first sentence naming the client and the work, the result in text rather than baked into an image, and the client’s name in the page title. It’s the same rule as a homepage headline: say what it is first.