Why we publish anonymized
An editorial choice about case files, and what it signals.
Most agencies brag with client logos. We do not. The choice to publish our case files anonymized, with /Insurance-Carrier/ where another shop would put the actual brand name, is editorial. It is not a legal requirement. It is a deliberate signal.
§01The convention
Walk into most agency portfolios and the case studies look the same: a wall of client logos, headline metrics in 96-point type, percentage gains arranged in a victorious grid. The format is so standardized that the brain stops reading individual entries. It reads “agency portfolio” and moves on.
§02What anonymization signals
Discretion is operational maturity. When a procurement officer at a regulated enterprise reads our case register, the absence of named logos tells them something specific: this firm understands that some clients do not want their problems advertised. If we are willing to redact those clients, we will redact this one.
The legal version of this argument is NDAs. The operational version is harder. NDAs are paper. The willingness to keep names off the marketing surface even when permission exists is a posture. Operational posture is what enterprise procurement is actually buying.
§03The trade-off
Anonymization costs us. A first-time visitor cannot recognize anyone in our case files, which means the case files have to do their own heavy lifting. We compensate with depth: every case has stakes, approach, architecture, technical challenges, the actual outcome, and the audit trail. The case file is the proof, not the logo wall.
“Visitors who read our case files end the read with a more accurate picture of how we work than a logo wall could give them. Clients who chose us partly because of the discretion send the next contract back.”
§04What gets named
The exception is the Imprints register. There, named partner clients (HouseCoin, ACM HVAC, LynkedUp Technologies) appear with explicit publishing permission. They wanted the attribution. We honor that. Two registers, two conventions, one underlying principle: the client picks the surface area of the relationship, not us.
§05Why this matters now
Enterprise budgets for AI and engineering services are getting reviewed harder than they were two years ago. Procurement officers have learned to look past the logo wall. They ask: how do you handle our data, our IP, our reputation? An anonymized public surface is a clean answer to that question that does not require a second meeting.
If we are willing to redact you, that is a feature.