How to write design case studies that win clients
Most case studies are written for other designers. Here is how to write ones that show founders why they should hire you.

Most design portfolios show finished screens. Most clients hire for something else: proof that you understand a business problem and can solve it without drama. A case study is where you show that proof. Done well, it does more selling than any discovery call.
The problem is that many case studies are written for other designers. They focus on process diagrams, tool choices and pixel details, while the founder reading it wants to know one thing: will this person help my business? Here is how to write case studies that answer that question.
Write for the client you want next
Before writing, decide who should read this case study. A seed-stage founder needs a launch-ready website fast. A product lead at a larger company cares about collaboration with engineers and design systems. The same project can be told for either reader, but not both at once.
Pick the reader, then choose what to emphasise. If you want more founder clients, show speed, clarity and business results. If you want product teams, show how you worked with their constraints.
Lead with the problem and the result
Busy readers decide in seconds whether to keep reading. Put the essentials at the top, before any images:
- Client and context: who they are and what stage they were at.
- Problem: what was not working, in their words if possible.
- What you did: one sentence, such as "new brand and Framer website in five weeks".
- Result: the outcome that mattered to them.
If a reader stops after this block, they should still understand why the project mattered.
Use real numbers carefully
Numbers are persuasive, but only if they are true and specific. "Conversion increased" means little. "Demo requests went from 12 to 31 a month in the first two months after launch" is useful, as long as the client agrees you can share it.
If you do not have hard numbers, use other honest evidence:
- Time saved, such as "the team can now publish a landing page in a day instead of a week".
- A business milestone the work supported, such as a funding round or a product launch.
- A short quote from the client about what changed.
Never invent or round up results. A single exaggerated claim can undo the trust the rest of the case study builds.
Show decisions, not just deliverables
The most convincing part of a case study is not the final screen. It is the moment you made a choice and explained why. Pick two or three key decisions and show them:
- The options you considered.
- Why you chose one, linked to the client's goal.
- What happened as a result.
For example: "We cut the homepage from nine sections to five because users were dropping off before reaching pricing." This shows judgement, which is exactly what clients pay for.
Keep the process short and specific
Generic process steps such as "Discover, Define, Design, Deliver" appear in almost every portfolio and tell the reader nothing. Replace them with what actually happened on this project: the workshop where the positioning clicked, the test that changed the navigation, the constraint that forced a simpler solution.
A short timeline also helps. Founders want to know how long things take. "Week 1: positioning and wireframes. Week 2–3: visual design. Week 4–5: Framer build and launch" is reassuring and concrete.
Make it easy to scan
Most people skim. Structure the page so skimming still works:
- Clear headings that tell the story on their own.
- Short paragraphs, two to four sentences each.
- Captions under every image that explain what the reader is looking at and why it matters.
- A few strong images rather than every screen you designed.
If you built the site in Framer, link to the live site. A working site is more convincing than any mockup.
Write a proper page title and meta description for every case study too. Founders often search for a designer's name plus a client's name after a referral, and a clear, specific title such as "Brand and Framer website for a fintech launch" helps the right page show up and tells them what they will find before they click.
End with a clear next step
A case study that ends with the last image wastes the reader's attention. Close with a short summary and a direct invitation: "Working on a launch like this? Book a call." Link to your contact page or calendar. Readers who reach the end of a case study are your warmest leads.
A good case study answers the client's real question: what will it be like to work with you, and what will I get?
Get the client's approval
Always ask before publishing details, numbers or quotes. Send the draft to the client, mark what you would like to share and let them edit. Many clients are happy to be featured, and some will share the case study themselves, which brings you more readers than your own site ever would. Check your contract for confidentiality terms before you start writing.
Conclusion
A case study that wins work is short, honest and written for the next client. Lead with the problem and result, use real evidence, show the decisions you made and end with a clear next step. Two or three case studies written this way will do more for your business than a grid of twenty beautiful screens.


