The most valuable currency in LinkedIn's consultant economy is the client name. "Helped a Fortune 500 retailer increase conversion 40%" converts ten times worse than "Helped Target increase conversion 40%." So consultants name names — in posts, in carousels, in header images, in "selected clients" grids — and most of them never asked.
The client finds out when a competitor forwards them the post. That conversation rarely goes well.
Why "They Won't Mind" Is a Legal Position, Not a Permission
Your contract governs this. Most consulting, agency, and service agreements include confidentiality clauses — some blanket ("don't disclose the relationship"), some scoped ("results may be shared with approval"). NDA-shaped obligations attach to client work, and "it was a great result" doesn't dissolve a clause. The friendly client who loved your work can still have a legal department with a template letter.
Logos are trademark use. The client logo in your carousel is their intellectual property used commercially to promote your business. "Fair use" arguments here are thin; trademark owners control commercial use of their marks. Agencies get cease-and-desists over client grids regularly — usually quietly, always awkwardly.
Results imply access. Publishing a metric about a client's business ("cut their CAC by 30%") reveals something about their finances and operations to the market. Their competitors read your post. Their investors read your post. The number was theirs before it was your content.
The implied endorsement cuts both ways. Your audience reads the name as a testimonial. The client reads it as an unpaid, unreviewed, unauthorized endorsement — of you, at their expense, with their brand.
The Permission Architecture
Tiered consent, matched to exposure:
- Name + logo + results: written approval from someone authorized to give it — marketing or legal, not just your friendly contact. Include where it will appear and for how long.
- Name only ("client list"): still written approval. A "selected clients" grid is commercial use of every name in it.
- Anonymized results ("a Series B SaaS company"): generally safe when the details genuinely can't identify them — but check: industry + stage + metric + timeframe is often enough for insiders to name the company. Metadata patterns identify the way titles do.
- Internal details (screenshots, dashboards, deliverables): never, without explicit approval — and screenshotted work product carries all the contamination problems of any screenshot, including the surfaces around the deliverable.
Get it in email. "They said yes on the call" evaporates the moment their CMO changes and the new one asks why your header image features their logo.
The Technical Layer Nobody Mentions
Here's where the case-study workflow quietly leaks: the permission-seeking itself is sensitive. "Can I post about our work together?" sent from your LinkedIn DM is a negotiation surface — and negotiations render on screens. The approval email with the legal terms sits in your inbox next to everything else. The client's name in your CRM, your proposals folder, your invoicing app — your business surfaces carry their identity all over.
If you're recording "how I write case studies" or "my client onboarding process" content, every one of those surfaces is in frame unless it's below the capture line. Permission is step one. Surface hygiene is step two. Case-study content needs both.
The Bottom Line
The client name is the strongest word in your content and the least yours to use. Get the yes in writing, anonymize until you have it, and keep the whole permission workflow — DMs, approvals, contracts — out of any frame your audience will ever see. Your portfolio should impress prospects without requiring your past clients to find out from their competitors.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
