The case study structure that wins agency clients: section order, proof and metrics that turn portfolio visitors into enquiries — from a senior Framer developer.
Written by
Pavlo Zhydkykh
Most agency case studies read like project diaries — long on process, short on proof. The right case study structure flips that: it walks a prospective client from their problem to your result in the order they actually make decisions. Here is the structure I use on real portfolio builds, section by section, plus the mistakes that quietly cost agencies enquiries.
Key takeaways
A case study is a sales asset, not a project diary — structure it around the client’s decision, not your timeline
The order that converts: client context, problem, approach, solution, results, proof
Put the headline result near the top — one hard number beats ten screenshots
Three to five deep case studies outperform twenty thin project pages
Every case study should end with a next step — a clear route to contact you
Why structure decides whether a case study sells
Prospective clients do not read case studies — they scan them for evidence. On every portfolio project I have worked on, buyers are looking for three things: have you solved a problem like theirs, what you were like to work with, and what happened after launch. A structure that answers those three questions, in that order, does most of the selling before the first call.
I have written before about what clients actually look at in a design studio portfolio — and case studies are where that attention concentrates. The work grid earns the click; the case study wins or loses the enquiry. That is why its structure matters more than anywhere else on your site.
The six-part case study structure that wins work
Every effective case study I have built follows the same six-part sequence:
Client context — one or two sentences on who the client is and what was at stake, enough for the reader to recognise themselves
The problem — the situation the client could not fix alone, framed in their words, before any mention of your services
The approach — why you chose the direction you did: the decisions and trade-offs, not a list of tools
The solution — the work itself, shown with real screens and specifics rather than adjectives
Results — the numbers that changed: enquiries, conversion rate, load time, revenue — dated and concrete
Proof and next step — a short client quote, then a clear route to start a conversation
Lead with the result, not the process
The single biggest structural fix is moving the outcome to the top. Put your strongest result in the first screen — in the subtitle, or as a stat strip directly under the hero image. A buyer who sees “enquiries doubled in three months” keeps reading; a buyer who sees “we began with a discovery workshop” leaves.
A case study is judged in ten seconds and read in three minutes — structure for the ten seconds first.
No shareable numbers? Use qualitative outcomes: time from brief to launch, a before-and-after pairing, or what changed for the client’s team. An honest “shipped in five weeks, replacing a site that had not converted in two years” is stronger than a vague claim — and it survives any NDA.
How deep should each case study go?
Depth is not word count — it is the density of decisions and evidence. What to keep:
The decisions that changed the outcome, and what they cost or saved in dollars or days
Five to eight real screens that show the thinking, not every artboard you produced
One honest constraint — budget, deadline, a legacy brand — because constraints make wins believable
A two-line client quote in the client’s actual voice
What to cut:
Process narration — “then we moved to wireframes” tells a buyer nothing
Tool lists and tech stacks, unless the client hired you for them
Generic mood boards and style tiles
Any paragraph that could appear in a competitor’s case study unchanged.
In practice that lands most case studies at 600–900 words — readable between two meetings, deep enough to be believed.
Building case studies that scale
The agencies that keep their portfolios sharp treat the case study as a repeatable template, not a one-off page. Set it up as a CMS collection — fields for context, problem, approach, results and quote — so every new project ships in the same proven shape, written by whoever ran it. I walk through exactly that setup in my complete Framer CMS guide.
You can see the structure working in 044Grid, the high-contrast studio template I designed: its case study layout leads with the outcome and one strong image, then walks context, problem, work and result in order. Remix it free and drop your own projects into the same skeleton: https://framer.link/nlREUB6
Prefer to watch the argument made on screen? Michael Janda — a designer who built and ran his own agency — breaks down what makes portfolio case studies convert in this walkthrough:
The mistakes that quietly kill agency case studies
Burying the result in the final paragraph, where only competitors ever read it
Writing for other designers — jargon impresses peers and loses buyers
Padding with every screen produced instead of the five that carry the story
No client voice anywhere — a two-line quote does more than a page of self-praise
Ending with nothing to do next — every case study needs a route to contact
Want case studies that win better clients?
Pavlo Zhydkykh designs and builds portfolio and case study sites for agencies and studios in Framer — structure, motion and CMS in one pair of hands, with pricing agreed upfront. If your work is better than your website tells it, get in touch.
Related reading
How long should an agency case study be?
Between 600 and 900 words with five to eight images. That is long enough to show real decisions and results, and short enough to be read between meetings. Depth beats length: one honest constraint and one hard number do more than another thousand words.
How many case studies does an agency portfolio need?
Three to five deep ones. Buyers never read twenty; choose projects that represent the work you want more of, cover different industries or problem types, and retire the rest to a simple archive grid.
What if we cannot share client names or numbers?
Anonymise rather than skip. "A B2B logistics SaaS" with real numbers is more convincing than a named client with none. If numbers are off-limits, use qualitative outcomes — time to launch, a before-and-after, what changed for the client's team. That structure survives any NDA.
Should a case study show our design process?
Only the decisions that changed the outcome. Buyers do not want wireframe narration; they want to know why you chose a direction, what it traded off, and what it produced. Cut anything that could sit in a competitor's case study unchanged.
Where should case studies live in the site structure?
One click from the homepage, linked from the work grid, and each on its own URL so it can be shared in proposals and rank in search. A CMS collection with a repeatable template keeps every new study consistent without developer time.
