Writing case studies when your clients want to stay anonymous

A client can be happy with your work and still not want their name on your website. Confidentiality, internal policy and commercial sensitivity can all make public attribution difficult. I would not treat that as permission to publish a lightly disguised version of their project.

An anonymous case study needs two things: enough approved detail to be useful, and enough restraint to protect the client. Removing a logo is only the beginning. The writing still needs to show what you did without inviting readers to identify who bought it.

Agree what can be published before writing

I would start with the contract and any confidentiality terms, then ask the appropriate client contact about publication. A friendly message from someone involved in the project may not be the approval your agreement requires.

Ask separately about the description of the business, the problem, the work, any results and any quotation. Permission for one of these does not automatically cover the others. Make the intended use clear, including publication on a public website.

Keep a written record of what was approved and by whom. If the client cannot approve even a general description, do not publish the story. You can explain your process elsewhere without presenting confidential work as public evidence.

Check whether the remaining details identify them

I read an anonymous draft as someone who knows the sector might read it. An unusual combination of industry, company size, project date and specialist requirement could identify a business even when the name has gone.

Remove unnecessary clues rather than replacing them with invented details. You can broaden a description from a precise niche to a service category if the client approves it. Do not change the industry or create a fictional location to conceal the real one.

Screenshots need the same care. Check filenames, browser tabs, account names, customer records and small text inside images. If redaction would leave a confusing or risky image, I would leave the image out and describe the approved work instead.

Build the story around a decision

A useful case study explains a problem, a constraint, a decision and the work that followed. I would choose one thread rather than describing every task completed during an engagement.

Start with what the client needed to change and why the existing approach was not suitable. Then explain the constraint that shaped your response. This could be an approval requirement or a limitation in the existing setup, but only if that detail is true and cleared for publication.

Describe your reasoning in plain language. Readers can learn something from seeing why you chose one approach over another. That gives the case study substance even when the client name and commercially sensitive figures cannot appear.

Separate delivered work from measured outcomes

I keep three categories apart: what we delivered, what we observed and what the client reported. They are different kinds of evidence and should not be merged into one confident claim.

A published page or a completed handover can demonstrate delivery. An improvement in enquiries needs reliable measurement and an agreed comparison. A client's impression should be attributed as their impression, not rewritten as a verified business result.

If no suitable outcome data exists, say what the work produced and stop there. You can explain the intended purpose without claiming it happened. An honest account of the deliverable is better than a result you cannot support.

Use quotations only with explicit approval

An anonymous quotation still belongs to a real person. I would ask permission for the exact wording and the description attached to it. A job title can also be identifying, especially in a small organisation.

Do not turn a private email into a public testimonial without agreement. If you edit a quotation for length or clarity, send the edited version back for approval. Avoid changes that make the original statement sound more enthusiastic or more certain.

If permission is not available, leave out the quotation. The case study can stand on its explanation of the work. A generic sentence of praise adds little if the reader cannot tell what it refers to anyway.

Make anonymity clear to the reader

I would add a short note explaining that the client's name and identifying details are withheld with permission, but only when that accurately describes the agreement. Do not imply client approval that you have not obtained.

Keep the note brief, then focus on the useful information. Readers do not need a dramatic account of the confidentiality restriction. They need to understand what the example can and cannot establish.

Place the case study where it answers a buying question. A service page can link to an example showing how a particular kind of work is approached. My guide to writing a services page explains how to connect evidence to those questions.

What to do this week

• Choose one project with a clear, explainable piece of work.
• Review confidentiality terms before drafting anything public.
• Ask what details and evidence the client can approve.
• Remove combinations of details that could reveal their identity.
• Label outputs, observations and reported outcomes accurately.
• Send the complete final version for written approval.

I would save the approved version alongside the permission record. If you later add an image, a result or a more specific client description, check permission again. An anonymous case study stays useful when its limits are respected, not when those limits slowly disappear during future edits.