20%
of page words the average reader actually reads
3 hrs
realistic build time with this framework
7
client interview questions that do the heavy lifting
1
hero metric per page -- no exceptions
The Outcome: A Case Study That Sells While You Sleep
By the end of this guide you will have a published, client-approved case study page built around one headline metric, one client quote, and one clear next step -- plus a reusable template you can fill in for every future project in roughly 90 minutes instead of three weeks.
Start with the number that explains why most portfolios fail. Nielsen Norman Group's eye-tracking research found that visitors read roughly 20% of the words on an average page, and that they scan in an F-shaped pattern -- first two lines, then the left edge, then almost nothing (NN/g, F-Shaped Pattern). If your case study is a 1,500-word chronological retelling, four-fifths of your proof is invisible.
The fix is not writing less. It is writing structurally. Every case study that converts follows the same skeleton: an outcome the reader wants, a problem they recognize, a decision they are curious about, and evidence that it worked. Build those four blocks and everything else is formatting.
Time budget: 45 minutes gathering, 60 minutes drafting, 45 minutes design, 30 minutes client review. You can stretch it, but do not skip a step -- missing evidence is the number one reason a case study reads as thin.
Prerequisites: Five Things to Gather Before Step 1
Do not open a blank document until you have all five. Each one maps to a step below.
- A finished project with at least one measurable outcome. Not "they were happy" -- a number. Revenue, hours saved, conversion rate, support tickets, load time, churn, signups. Whatever the client actually tracks.
- Written permission. An email saying "yes, you can publish this with our name and logo" is enough. A one-page release is better. Step 4 covers the exact wording.
- Raw artifacts. Screenshots, old versions, Figma files, analytics dashboards, Slack threads, decks, drafts, and before/after photos.
- Baseline data. Your before-state. If you never captured it, ask the client retroactively -- most can pull it from their analytics or CRM within a day.
- A primary publishing surface. Your own site, a Notion page, Behance, or a PDF. Pick one as the canonical version; everything else is a copy of it.
Step 1: Pick the Project That Can Carry a Number
Why this step matters: Not every project deserves a case study. Each one costs a few hours plus a favor from a client, so spend that budget on the project most likely to attract the next client you actually want. The common trap is choosing the project with the most impressive logo. The better filter is simpler: which project produced a result a prospect would recognize as their own problem?
How to execute it: List your last ten projects and score each from 1 to 5 on three axes:
- Measurability. 5 = a hard metric with a documented baseline. 1 = "they seemed pleased."
- Relatability. Is this client the same size, industry, and stage as your ideal next client? A beautiful project for a Fortune 500 does very little for a solo founder if founders are who you want to serve.
- Tension. Was there a real constraint -- a brutal deadline, a broken integration, a skeptical stakeholder, a compliance wall? Tension is what makes the middle of a story readable instead of a list of deliverables.
Pick the highest total. If two projects tie, pick the one where you can get the client on a 25-minute call this week.
PRO TIP: Keep a "case study shortlist" inside the project tool you already open daily (Notion, Trello, Linear, whatever it is). The moment a project hits a measurable win, tag it. If you wait until you need new work, you will have forgotten the baseline numbers -- and the client will have moved on.
Common mistakes: Choosing a project you cannot legally discuss. Choosing a project where someone else produced the result. Choosing a project you personally disliked -- the flatness shows up in the writing, and readers feel it.
Step 2: Build the Before Snapshot Before You Forget It
Why this step matters: A case study is a story about change, and change needs two data points. Without a before, your after is just a claim -- and claims are cheap. This is the step most freelancers skip, which is exactly why so many case studies read like brochures rather than arguments.
How to execute it: Create one folder and fill it with five things:
- Baseline metrics. Pull them from the client's analytics (Google Analytics, Mixpanel, Amplitude), CRM (HubSpot, Salesforce), billing system (Stripe, QuickBooks), or a manual spreadsheet.
- Visual before/after. Screenshot the old design, the old workflow, the old deck. If the work was invisible (strategy, ops, research), draw a simple diagram of the old process instead.
- Scope facts. Timeline in weeks, team size, budget band if shareable, and the tools you used.
- The constraint, in one sentence. "The real problem was X." That sentence becomes your subheadline.
- The exact deliverables. Specificity signals seniority. "A 12-page design system with 40 components" beats "design support" every time.
If the client cannot produce a baseline number, use a proxy they will confirm in writing: "weekly support tickets dropped from about 40 to about 12." An attributed estimate is fine. An invented number is not -- and you will get caught.
Common mistakes: Saving only final files. Taking screenshots after launch. Reporting metrics with no denominator -- "we got 4,000 views" means nothing without knowing where it started.
Step 3: Interview the Client With a 25-Minute Script
Why this step matters: The client's own words are the most persuasive asset in the entire piece. Readers discount anything you say about yourself and trust a third party almost instantly. A recorded 25-minute call also solves your blank-page problem: you are transcribing, not inventing.
How to execute it: Send the questions 24 hours ahead, get permission to record (Zoom, Riverside, or Otter.ai), and ask these seven:
- What was happening in the business that made you start looking for help?
- What had you already tried that did not work?
- What made you decide to work with me specifically?
- What worried you at the start?
- Walk me through the moment things started to click.
- What changed in the numbers after we finished?
- What would you say to someone in the same position you were in six months ago?
PRO TIP: Question 7 is your testimonial. It is almost always the most quotable line on the recording, because it is the client selling on your behalf to a peer. Pull it verbatim and place it directly under your hero metric.
Common mistakes: Asking "were you happy with the work?" -- leading and useless. Talking more than the client. Skipping the recording and then trying to reconstruct quotes from memory.
Step 4: Get Written Permission and Set Up the Review Loop
Why this step matters: Publishing a client name and a revenue figure without sign-off is both a contract risk and a reputation risk. Done properly, this step takes days, gives you legal cover, and creates a built-in amplifier -- clients reshare case studies they helped shape.
How to execute it: Send one short email containing all four of these:
- What will be published. A live link to a Google Doc draft or a password-protected staging page -- never a request to approve something they cannot see.
- What will be named. Their company name, their title, their headshot, their logo, and the specific figures you plan to include.
- A redaction option. If they cannot share hard numbers, offer a relative version: "revenue tripled within one quarter" instead of an absolute figure.
- A response deadline. "If I do not hear back by Friday, I will treat the draft as approved." A soft deadline is normal in agency work and keeps momentum. Publishing without consent is not.
Once approved, save the email thread as a PDF and file it next to the project assets. Ten seconds of filing saves an hour of panic later.
Common mistakes: Sending the draft and the publish request in the same message. Using logos without explicit permission. Assuming a verbal yes covers publication.
If case studies are part of a plan to move from hourly work into retainers or productized services, run the numbers before you rewrite your site. Our free Income Architect maps your rates, utilization, and service mix into a single plan -- which tells you what a case study actually needs to sell.
Step 5: Build the Story With the Four-Block Skeleton
Why this step matters: Structure is what makes a case study skimmable. A reader should be able to extract 80% of your argument from the subheads alone. The four-block skeleton guarantees that.
How to execute it: Write these four blocks in order, then move the result to the top when you format the page:
- Challenge (100-150 words). The situation, the constraint, and the stakes. What was at risk if nothing changed?
- Approach (200-300 words). What you decided to do -- and, critically, what you chose not to do. Decisions demonstrate judgment. Deliverables only demonstrate output.
- Execution (200-300 words). Milestones, tools, and artifacts. A short timeline or numbered list works better than prose here.
- Result (100-150 words). The numbers, the client quote, and what happened next. If they hired you again or referred someone, say so.
Then restructure for the web: lift the strongest sentence from the Result block into a hero banner at the very top, right next to the headline metric. Readers who bounce after 15 seconds should still leave knowing the outcome.
Common mistakes: Writing chronologically ("first we had a kickoff call"). Skipping the decision-making middle, which is the part that makes you look senior. Ending without giving the reader a next step.
What This Looks Like in Practice
"I had fourteen thumbnails on my site and not one story. I rewrote my three best projects with this structure, added the hero metrics, and did the client interview thing -- which felt awkward, by the way. Two months later an inbound lead quoted a specific paragraph back to me before we ever got on a call. I priced that project 40% above my old rate and nobody blinked."
Step 6: Write the Headline and the Hero Metric Block
Why this step matters: The headline is doing most of the work. It sets the reader's expectation for the number, the timeframe, and whether this story is about someone like them. Vague headlines -- "A Brand Refresh for a SaaS Company" -- give the reader no reason to scroll, and search results truncate anything past roughly 60 characters.
How to execute it: Pick one of three formulas and fill in the blanks:
- Outcome headline: "[Client] cut [metric] by [X]% in [timeframe]." Example: "Bramble & Co cut onboarding time 62% in six weeks."
- Transformation headline: "How [client] went from [bad state] to [good state] without [common tradeoff]."
- Mechanism headline: "[Deliverable] that [specific outcome]." Example: "A 12-page design system that killed 40 hours of design debt per quarter."
Three rules hold across all of them: lead with a numeral rather than a spelled-out word, cut every adjective that is not doing measurable work, and name the client's category so both search engines and human scanners know who the story is for. Then build the hero block beneath the headline with four stacked elements -- the headline metric in large type, a one-line context sentence, the client logo, and a single-sentence pull quote.
PRO TIP: Test two headline versions against each other with Hotjar heatmaps, or simply watch which one earns more clicks from your LinkedIn Featured section. Two weeks of real data beats a week of agonizing over adjectives.
Common mistakes: Using the client's internal project codename. Writing "Case Study:" as a prefix -- it burns characters and adds nothing. Burying the number in paragraph two.
Step 7: Design the Page for Skimmers, Not Readers
Why this step matters: You are designing for someone who is on their phone, in a hurry, and quietly deciding whether to trust you. Everything above the fold has to survive a 15-second glance from a distracted person.
How to execute it: Apply these seven layout rules:
- A subhead every 150-200 words. If a section runs longer than a phone screen and a half, break it.
- One visual per 300 words maximum. Real screenshots beat stock photography every single time.
- A three-stat metric row. Three numbers in a row, each with a two-to-four word label beneath it.
- The client quote in a tinted block. Give it a colored left border and a light background so it reads as a third-party voice, not yours.
- One CTA, repeated. Not four options -- one offer, linked at the top, the middle, and the bottom.
- 16px minimum body text on mobile. Baymard Institute's usability testing consistently shows that small type and low contrast drive abandonment.
- An obvious next step. "Book a 20-minute call" or "See availability." Not "get in touch."
If you are not a designer, use a template-driven builder -- Webflow, Framer, Carrd, or a well-built WordPress theme. A clean template executed properly beats a custom layout that is half-finished.
Common mistakes: Publishing as a PDF only -- search engines cannot read it, phones render it badly, and nobody downloads it. Full-width paragraphs that stretch past 90 characters. Stock photos of people shaking hands.
Step 8: Distribute It, Then Measure the One Metric That Matters
Why this step matters: Writing the case study is maybe 20% of the work. Case studies do not sell from your portfolio archive -- they sell when they land in front of a specific person at the exact moment they are deciding.
How to execute it: Put the finished piece in six places this week:
- Your proposal template. Attach the two most relevant case studies to every quote you send. This is the highest-leverage placement that exists.
- Your LinkedIn Featured section and profile summary.
- An email to past clients. "Here is what we built together, in case it is useful to share internally." Warm referrals follow almost automatically.
- A repurposed carousel or short video. Three slides and one 60-second clip, posted natively rather than linked out.
- Your marketplace profile -- the Project Catalog description on Upwork or wherever you list services.
- Your email signature. One line, one link, zero explanation needed.
Then measure exactly one number: how many qualified conversations started because of it. Track link clicks with a UTM parameter in Google Analytics, but treat pageviews as trivia. Replies, calls booked, and proposal win rate are the metrics that pay rent.
Common mistakes: Burying the piece three levels deep under Portfolio > 2024 > Project X. Publishing once and never touching it again. Never asking the client to share it with their own network.
When You Do Not Have Big Results Yet
This is the objection that stops most people from starting, so here is the workaround.
Use process-level outcomes. You may not have moved revenue, but you almost certainly reduced something: feedback rounds, revision cycles, handoff errors, build time, or the number of tools in a stack. Those are real numbers, and they are honest.
Use the constraint as the story. "How I shipped a full brand system solo in nine days" works even without a client metric, because the constraint itself is the achievement.
Label borrowed or self-initiated work honestly. A volunteer project or a self-directed concept piece is perfectly fine as long as you say so. "Self-initiated concept project" costs you nothing. Passing it off as client work costs you everything.
Ship two small ones instead of one perfect one. Two case studies at 600 words each, published this month, will outperform one flawless page you are still "gathering material" for in March.
PRO TIP: If your work is genuinely confidential, write a composite case study. Combine the shape of two or three real projects into one anonymized narrative labeled "Healthcare client, name withheld at their request." State the composite openly in the first line. Readers respect the honesty and still learn exactly how you think.
The Quick-Start Checklist
Print this, or paste it into your task manager. Work top to bottom.
- Score ten past projects on measurability, relatability, and tension. Pick one.
- Recover baseline numbers from the client's analytics, CRM, or billing system.
- Collect before/after visuals and a diagram of the old process.
- Book a 25-minute recorded client call and send the seven questions 24 hours ahead.
- Transcribe and pull three verbatim quotes -- one for the hero, one for the middle, one for the close.
- Send a permission email with the draft link, the naming list, a redaction option, and a soft deadline.
- Write the four blocks: Challenge, Approach, Execution, Result.
- Lift one result sentence into a hero banner at the top of the page.
- Write the headline using a numeral and the client's category.
- Add a three-stat metric row and a tinted quote block.
- Check mobile at 16px and confirm one CTA repeated three times.
- Add the case study to your proposal template and your LinkedIn Featured section.
- Email it to three past clients with a one-line personal note.
- Add a UTM tag and check the qualified-conversation count in 30 days.
Three Mistakes That Quietly Kill Case Studies
No number in the first 50 words. Case studies are evidence, and evidence has units. If the reader cannot find a figure before they start scrolling, they will assume there is not one.
No decision in the middle. Anyone can list deliverables. The reason a client hires a specific person is judgment -- what you chose to do when the obvious path was wrong. Give the reader at least one paragraph of that.
No next step at the end. A case study that ends on a neat summary is a brochure. A case study that ends on "book a 20-minute call" is a sales asset.
The Bottom Line
A case study is not a report on what you did. It is an argument that the reader's problem is solvable, delivered by someone who has already solved it for someone just like them. One page, one number, one quote, one next step -- built with the eight steps above, refreshed once a quarter, and attached to every proposal you send. Do that consistently and your portfolio stops being a gallery and starts being a sales channel.