Using client data in a case study without a difficult conversation

This is general practice for retention agencies, not legal advice — check your own contracts and, where it matters, an actual lawyer. What follows is the operational version most agencies need day to day.

What is usually in your contract already

Most agency service agreements already have a confidentiality clause and, separately, a reference-rights clause — and the two are often not the same scope. Confidentiality typically covers strategy, pricing and internal communications; reference rights, when they exist at all, are what actually govern whether you can name the client publicly. Before publishing anything with a client's name attached, check which clause your contract actually has, not which one you assume it has.

Three levels of disclosure

• Anonymous by sector and size — "a mid-size apparel retailer." No name, no identifying detail beyond a category.
• Anonymous with detail — sector, approximate size, and specific enough operational detail (e.g. "a subscription-based skincare brand") that someone in the industry might guess, but nothing confirms it.
• Identified — name and, usually, logo. Requires explicit permission, ideally in writing, every time — not a one-time blanket approval from a year-old contract.

Anonymous can be more credible than you think

An anonymous case study loses nothing that actually establishes credibility, provided the parts that matter stay visible: sector, rough size, the specific metric, the period, and the source. What makes a case study feel thin isn't the missing name — it's a missing method. A reader forgives "a mid-size ecommerce brand" far more easily than they forgive an unsourced percentage.

How to ask

The best time to ask for permission to use a client's name is right after a genuinely good result, not at contract renewal when the ask can feel transactional. A short, direct request works better than a long one:

"We'd like to share the results from your [flow name] as a case study — we'd credit [Client Name] by name and link to your site. Happy to share a draft before anything goes live, and just as happy to keep it anonymous if you'd rather. Let us know either way."

Giving the anonymous option in the same message, rather than only as a fallback if they say no, tends to get a faster and more comfortable answer.

Where agencies get it wrong

The recurring mistakes aren't about whether to name a client — they're about accidental identification in an "anonymous" piece: a dashboard screenshot with the client's domain visible in a browser tab, a revenue figure specific enough that anyone in the client's own supply chain could work out who it is, or a flow name that's unique enough to be searchable. Anonymous mode should mean actually unidentifiable, not "we didn't say the name out loud."

Defaulting to anonymous

The safer default is anonymous unless a client has explicitly opted in to being named — reversing that (named by default, anonymous only on request) puts the burden on the client to notice and object, which is backwards. Whatever you publish this way, decide upfront what stays fixed once it's live: a page whose numbers can quietly change after a client agreed to it undermines the trust the whole exercise depends on.