On this page
A case study doesn’t need a dramatic percentage to be useful. It needs to explain the problem, what you contributed and why the work mattered.
The hard part is often deciding what you’re allowed to show. Client approvals, agency relationships and confidential information should be settled before a polished draft becomes a public page.
Start with the permissions you have
Check the relevant agreement and the client’s instructions. A public website doesn’t automatically give you permission to share private discussions, internal screenshots or results.
Ask for approval of specific material: the client name, screenshots, your stated role, quotations and any metrics. If private sales presentations are also intended, include that use in the request rather than assuming it’s covered.
Keep the response with the project record. If permission is unclear, don’t try to solve the uncertainty with vague wording in the article.
I’m describing an editorial process, not interpreting any particular NDA. If the contract wording is in dispute, that’s a separate conversation, and it comes first.
Describe your contribution precisely
If an agency supplied the design and you handled Webflow development, say so. If you joined an existing site to improve forms and performance, don’t present it as a complete original build.
A focused contribution reads better than a big claim. Clear attribution makes the case study more credible, and it tells a potential client what they’d actually be hiring you for.
Use a role statement early: who owned strategy, design, development and content, and which parts you delivered. Name collaborators where that’s appropriate and approved.
Write around a concrete problem
“The client needed a modern website” explains very little. A more useful problem might be that marketers couldn’t publish a case study without asking a developer, or that one form had to send different submissions to different destinations.
Then describe the decisions. Why use a reference collection? Why simplify one interaction on mobile? What did the editor need to do after handover? The handover checklist is a good source of those details.
You don’t need to expose confidential architecture to explain a trade-off. Choose enough detail for the reader to see your judgement.
Separate delivery from measured results
| Statement | Evidence it needs |
|---|---|
| Built reusable campaign sections | The implemented sections and their intended use |
| Reduced image transfer | Comparable before-and-after measurements |
| Improved conversion rate | Defined events, date ranges and a meaningful comparison |
| Saved the marketing team time | A supported estimate or client confirmation |
Deliverables can be described without presenting them as measured commercial outcomes. “Editors can create pages from approved components” is a different claim from “The client publishes ten times faster.”
For metrics, record the baseline, the final value, the source and the period. Explain important limitations such as changed traffic or concurrent campaigns. Don’t credit all of an improvement to your work just because it came after launch.
Anonymity isn’t a shortcut around confidentiality
Removing a name may still leave a project identifiable through screenshots, industry, dates or distinctive details. Ask whether an anonymised account is permitted before you prepare one.
If you can’t share the work, write a separate educational example with invented inputs, clearly labelled as an example. Don’t present that exercise as a client case study.
Give the client a reviewable draft
Send the complete proposed copy and images, not a broad request to “mention the project”. Ask them to confirm sensitive facts and approve the intended use.
After revisions, keep the approved version. If you later add a metric, a testimonial or a new screenshot, check whether that addition needs separate approval.
The finished story should let a reader see your role and your decisions. Accurate, specific work is persuasive on its own, and invented results make a portfolio harder to trust. For portfolio structure, see the CMS collections guide.
