Anonymous case studies when clients won't let you name them
Anonymous case studies: three separate permissions, what to describe instead of the client's name, how to report results without inventing numbers.
How do you write a case study when the client doesn’t want to be named? First, ask for permission on three separate things: the name, a quote and public use of the project description. A client who doesn’t want to be named may agree to the rest. Instead of the name, describe what lets a buyer recognize their own situation: the industry, company size, the problem at the start, the scope of work, the timeline and the role of the person you worked with. Report only results the client has confirmed, together with the starting point. If they won’t agree to a number, describe the change in words or as a range they approved. Ask for permission after the first result, with the finished text. Use a project without permission to publish in proposals for specific clients, if your contract allows it.
In this post I’ll show how to separate the permissions, what to write instead of the name, how to report results and when to ask the client for approval.
A case study without a name still shows what the buyer is looking for
In the Content Marketing Institute’s research for 2025 (980 B2B marketers, mostly from North America), 75% of respondents used case studies and customer stories. 53% of respondents named them among the most effective content types, which put them second, after videos. The year before, they were first.
In my view, a buyer of a service reads a case study mainly to answer one question: has this firm already solved a problem like mine? The client’s name helps because it adds credibility, but a description of the situation, scope and result answers that question without it. That’s why not having permission to use the name is no reason to publish no case studies at all.
Three separate permissions: name, quote, public use
The request “can we write a case study?” bundles three different decisions. That’s why you ask about each one separately:
| Permission | What it allows | Without it |
|---|---|---|
| Client name | using the name and logo | you describe the client without the name (industry, size, situation) |
| Quote | quoting someone from the client’s company in the approved wording | you describe the effect in your own words, without quotation marks |
| Public use | publishing the description on your website, on social media, in material for everyone | the description stays in proposals for specific clients |
One possible combination, for example: permission for public use without the name, with a quote attributed only to a job title. Record what the client agreed to and when, together with the project description, so nobody on the team has to guess a year from now.
Instead of the name, describe what lets a buyer recognize their situation
A buyer compares a case study with their own company. Instead of the name, give them what makes that comparison possible:
- industry: “automotive parts manufacturer”, not “manufacturing company”,
- size: a headcount range or number of locations, not exact figures that make it easy to guess who it is,
- the situation at the start: what wasn’t working and since when,
- scope of work: what you did and what you didn’t,
- timeline: how long the project took and when the first result appeared,
- the role of the person on the client’s side you worked with, for example the finance director.
A buyer from the same industry should recognize their problem in the description, but shouldn’t be able to guess which client it is. You don’t change the industry, size or timeline “to disguise it”: if the description isn’t true, the case study stops being proof. When the true description gives the client away, you make it more general instead of changing it.
Only results the client has confirmed
A result in a case study has a starting point and an end point: “time from shipment to invoice: before and after the project”. You give a number only when the client has confirmed it, ideally in writing, and you record who confirmed it and when.
If the client doesn’t want to share a number, you have two options: a range they approved, or a description of the change in words, for example “invoices go out the same day as the goods”. You don’t round up, you don’t calculate it yourself from data the client hasn’t confirmed, and you don’t write “about 30%” to make the text look better. An invented number in a case study without a name is even worse than in a regular one, because the reader can’t check it.
You ask for permission after the first result, with the finished text
At the start of a project there are no results yet, so there’s nothing to approve. I recommend noting when you sign the contract that you’ll ask about a case study later, and coming back to it after the first result the client has noticed themselves.
You send the request with the finished text without the name, and three questions:
- Can we publish this description on our website and on social media?
- Can we use your company’s name and show its logo?
- Can we use this quote in this wording and with this attribution?
Finished text is easier to approve than a general question: the client sees exactly what will go online. If they agree only to the first question, you publish the version without the name and without the quote.
A project without permission to publish stays in proposals
When the client doesn’t agree to public use, the project description can still go into a proposal for a specific client, in the same form without the name, if the confidentiality terms in your contract with the client allow it; check them before the first use. In my view, this is fair as long as the proposal doesn’t give the client away and doesn’t include numbers they haven’t confirmed. You don’t publish such a description in any form, including as a snippet on LinkedIn.
I covered how to match case studies to the buying stage in the post on content for service firms.
Example: a case study without a name
This is an illustration, not a real project: take a software house that integrated a client’s warehouse system with its accounting. The client agreed to public use and to a quote attributed to a job title, but not to the name.
| Field | Content (illustration) |
|---|---|
| Permissions | public use: yes; quote: yes, attributed to a job title; name: no |
| Industry and size | spare parts wholesaler, several warehouses in Poland |
| Situation at the start | invoices issued by hand, with a delay after the goods shipped |
| Scope of work | integrating the warehouse system with accounting; no changes to the warehouse system itself |
| Timeline | a few months of project work, first result after the integration went live in the first warehouse |
| Role on the client’s side | finance director |
| Result | invoices go out the same day as the goods (described in words, because the client didn’t agree to share numbers) |
| Quote | a sentence from the finance director in the approved wording, attributed to “finance director at a parts wholesaler” |
Frequently asked questions
Can I show the client’s logo if I don’t give the name?
No. A logo gives the client away just like the name. If you show screenshots, blur the logos, names and any data that would identify them.
Can the client withdraw permission?
In my view, it’s worth assuming yes and telling the client so in the request. It’s easier to agree to something you can take back. If they withdraw permission for public use, you take the case study off your website and social media, and the description stays only in proposals, if your contract allows it. If they withdraw permission for the name or the quote, you remove the name or the quote and keep the rest.
How much detail is too much?
It’s too much when someone from the client’s industry can guess who it is. Show the text to someone who knows the client’s market and ask whether they recognize the company. If they do, make the industry or size more general.
Summary
If you don’t publish case studies because clients don’t want to be named, start with one project with a result the client has noticed. Write the description without the name, with a confirmed result, and ask for the three permissions separately. In our open repo (files and instructions for an AI agent such as Claude Code), each piece of project proof has three separate permissions, and a number goes into a case study only when a person has marked it as confirmed (open source).
Every method on this blog also runs as a skill in the open-source B2BForce repo. About the repo