A case study is not a scrapbook of a project you enjoyed. It is a sales document with pictures. Clients reading it are asking one question — can this person solve a problem like mine? — and they will answer it in about ninety seconds. Everything you include should pull towards that answer. Everything else should be cut without sentiment.
Most freelance portfolios fail in the same way: beautiful images, no argument. The work looks good, but the reader cannot tell what you were hired to do, what you considered, or whether it worked. Structure fixes that. The four-part spine below — brief, process, decisions, results — works for design, branding, illustration and web work, and you can apply it to finished projects in an afternoon.
Open with the brief, in plain language
Before a single image, tell the reader what the job was. Not “a rebrand for a bakery” but “a two-person bakery with a strong local following wanted to sell celebration cakes online without losing the shop’s handmade character. The site had to launch before the Christmas order window.” Now the images have a job to do.
Keep this to three or four sentences and include the constraints, because constraints separate professionals from hobbyists. A fixed deadline. A brand you could not touch. A client team of five people who all had opinions. A printing process that allowed two colours. Name who the client was — anonymised if you must — and what success looked like from their side.
A useful formula: [Client] needed [outcome] because [reason]. The main constraint was [constraint]. Say it out loud. If it sounds vague, sharpen it before you write anything else.
Show the process as a small number of moves
A process section is not a project timeline. Nobody needs to know that week three was “client feedback”. Group what you did into three or four stages and give each one a purpose.
Discovery
What you needed to learn, and how you found it out. Interviews, a competitor review, a trawl through old customer emails, a day in the shop. Two sentences per method is plenty. The point is to show that decisions came from evidence rather than taste.
Direction
Show the paths you explored, including the ones you abandoned. Two or three early routes, briefly annotated, do more for your credibility than a single polished hero shot. Explain what each route was trying to achieve.
Delivery
What you shipped, in which formats, and how it was handed over. If you built a small design system, a set of templates or a file structure the client could maintain, say so. Clients hire people who leave things in better order than they found them.
Explain the decisions, especially the difficult ones
This is the section most portfolios skip, and it is the one that wins work. Anyone can show a finished logo. Fewer people can explain why the wordmark sits tight to the left, why the palette dropped the brand’s original green, or why the checkout went from four steps to two.
Pick three decisions and write a short paragraph for each: the choice, the alternative, and what tipped it. “We tested a warmer palette against the existing blue. The warmer version performed better in isolation but made the pharmacy packaging look medicinal, so we kept the blue and warmed the photography instead.”
That paragraph shows judgement, not just skill. It also tells a prospective client you will present options with reasons rather than waiting to be told what to do.
Put the results in plain sight
Results do not have to be dramatic to persuade. Use whatever the client actually measures, and be honest about scale.
- Numbers the client already tracked — enquiries, orders, sign-ups, average order value, hours saved each week.
- Before-and-after comparisons on the same measure over the same period.
- Qualitative feedback: a customer who finally understood the menu, a sales team that stopped answering the same question.
- Longevity: an identity still in use four years on, a template the client’s own team still updates.
- Follow-on work: a second project, a retained role, a recommendation to another business.
If you have no numbers, say what you do have and do not dress it up. “The client reported a busier launch week than the previous year” is fine. Invented percentages are not, and experienced buyers can smell them.
Format it so it can be skimmed in ninety seconds
Layout matters as much as the words. Someone scrolling on a phone should get the shape of the project without reading every sentence.
- Lead with one strong image, then the brief — not a full-screen mood shot.
- Use one heading per section, kept short and specific.
- Caption every image with what it shows and why it mattered.
- Keep the body between roughly six hundred and a thousand words; longer only if the project genuinely warrants it.
- State the result near the top as well as at the end, in a sentence or a small panel.
- Finish with a clear next step: the service you want more of, and how to start a conversation.
Write in the first person and use plain words. “I” is warmer than “the studio”, and concrete nouns beat adjectives. Read the draft aloud: anywhere you stumble needs less decoration.
Before you publish: a fifteen-minute edit
- Delete the first paragraph. It is almost always throat-clearing.
- Check the brief section names a client, a problem and a constraint.
- Make sure at least three decisions are explained, not merely shown.
- Confirm every claim in the results section is something you could evidence if asked.
- Read the headings alone, top to bottom. If they do not tell the story, rewrite them.
- Add one closing line naming the work you want next.
Then do it again for your second-best project. Two well-structured case studies will bring you more enquiries than twenty images with no argument behind them.
