A web designer in Seattle has built 30 websites over the past two years. Her portfolio page has screenshots of the twelve best ones, arranged in a grid. Each one links to the live site. No context. No story. No results. When a prospect asks "what happened after you built this?" she has no answer, because she never followed up.
A different designer in the same city has built 15 websites. Her site features three case studies. Each one opens with the client's problem, walks through the specific decisions she made, and closes with real metrics: a 340% increase in organic traffic, a 4.2-second improvement in load time, a 22% boost in phone calls within 60 days.
The second designer charges twice as much and closes faster. Not because she is a better designer. Because she proves her work produces outcomes, not just deliverables.
Portfolios show skill. Case studies show value.
A portfolio answers the question "can this person design?" A case study answers the question "will this person make me money?" Business owners care about the second question.
The difference is structural:
- A portfolio is a gallery. A case study is a story.
- A portfolio shows what you built. A case study shows what changed.
- A portfolio requires the viewer to imagine the value. A case study hands them the evidence.
You need both. But if you are using your portfolio as your primary sales tool and wondering why prospects are shopping on price, the case study is the piece you are missing.
The Problem-Solution-Result framework
Every effective case study follows the same three-part structure. You do not need to be a writer. You need to fill in three sections with specifics.
Problem: What was wrong before you got involved? Be concrete. "The site was outdated" is vague. "The site loaded in 7.3 seconds on mobile, had no click-to-call button, and was converting paid traffic at 1.2% against an industry average of 5.8%" is a case study.
Solution: What did you build and why did you make the choices you made? This is where you demonstrate expertise. Not "I built a modern responsive website" but "I restructured the site from twelve pages to five, added a sticky click-to-call header, moved the service area map above the fold, and reduced image payloads by 80% using WebP with lazy loading."
Result: What happened after launch? This is the section that sells. Traffic numbers, conversion rates, phone call volume, search rankings, load time improvements. If you have them, use them. If you do not have them, this is why you need to start collecting them.
How to collect the numbers you need
Most designers do not have post-launch data because they never asked for it. Fix this going forward with three steps:
1. Benchmark before you start. On every new project, run a quick baseline before you touch anything. Google PageSpeed score, current monthly traffic (ask the client for Google Analytics access), current conversion rate if they track it, and current search ranking for their primary keyword. Write these numbers down. They become the "before" in your case study.
2. Check in at 30 and 90 days. Set a calendar reminder. Run PageSpeed again. Ask the client how calls or form submissions have changed. Pull the search ranking. You need two data points to tell a story: before and after.
3. Ask the client directly. "Since we launched the new site, have you noticed any change in the number of calls or leads you are getting?" Most business owners can answer this even without analytics. "We used to get maybe 5 calls a week, now it is 10 to 12." That is a case study data point.
The key is that you do not need perfect data. You need specific data. "Traffic increased" is weak. "Organic traffic went from 180 to 620 monthly visitors in 90 days" is a case study. The precision makes it credible.
Where to use case studies (not just your portfolio page)
Most designers create a case study and bury it on a portfolio subpage. That is one use case out of five.
In cold outreach emails. When you reach out to a plumber in Phoenix, link to your case study about the plumber in Denver. Same industry, same problems, proven results. This is infinitely more compelling than "check out my portfolio."
In proposals. Dedicate a half-page to a relevant case study in every proposal. "We did this for a similar business. Here is what happened." This anchors your price to an outcome rather than a deliverable.
On sales calls. Walk through one case study during the discovery call. Screen-share the before and after. Let the numbers do the talking while the prospect imagines the same results for their business.
On LinkedIn and social media. A case study post with a before/after screenshot and three data points outperforms every "tips for small businesses" post you will ever write. It is proof, not advice.
In follow-up sequences. When a prospect goes dark after a proposal, send a relevant case study as a re-engagement touchpoint. "I was looking at your site again and it reminded me of a project we did last year. Here is what happened with their traffic after we rebuilt their site."
Writing the case study: keep it under 500 words
Longer is not better. A case study is a sales tool, not a blog post. Business owners are busy. Give them the story in under 500 words.
Here is a template:
Headline: "[Business Type] in [City]: [Key Result]" Example: "HVAC Company in Tampa: 340% More Organic Traffic in 90 Days"
The Problem (100 words): Who is the client, what was wrong, and what was the business impact? Include at least two specific numbers.
The Solution (150 words): What did you build? Focus on the decisions that drove the results, not every feature. Three to four bullet points work well here.
The Results (100 words): Before and after numbers. Load time, traffic, calls, conversions, search rankings. Use a simple table or bold numbers for scannability.
Client quote (1-2 sentences, optional): If you have one, include it. If you do not, skip it. A fabricated testimonial is worse than none.
You only need three
You do not need a case study for every project. You need three strong ones, ideally in different niches. A plumber, a dentist, and a landscaper covers most of the local service businesses you will pitch.
Three case studies with real numbers will outsell a portfolio of thirty screenshots. They prove that your work produces measurable business results. That is the gap between a designer who competes on price and one who competes on value.
Start with your most recent project. Run the numbers. Write it up. That single case study will change how every future prospect evaluates your pitch.
Related reading