Evidence in Plain Wrappers: Credible Case Studies When Clients Withhold Their Names
Photo: anonymised case study documents no logos on office desk, via img0.reactor.cc
UK clients are often willing to describe outcomes but unwilling to be named. The reasons are familiar: commercial sensitivity, group communications policy, data protection, procurement rules, or a simple preference for discretion. For consultants and project businesses, the temptation is to treat this as a marketing problem. It is better treated as an evidence problem. A case study without a logo can still be credible, provided the proof is structured, specific, and approved. Anonymity should not become vagueness.
Confidentiality is normal, not a rejection
A refusal to be named is rarely a judgement on the quality of the work. In larger UK organisations, case study approval may sit with communications, legal, or procurement functions that have no operational knowledge of the project. The consultant who hears 'no' should ask a more useful question: what can be said, to whom, and in what form? That shifts the conversation from permission to parameters. It also protects the relationship. A client who feels pressured for a logo may become more cautious about sharing evidence later.
Anonymised evidence that carries weight
Useful anonymisation preserves the shape of the problem and the rigour of the outcome while removing identifying details. Describe the client by sector, scale, operating model, and constraint: for example, a UK-based logistics group with a multi-site operation and a legacy planning system. Use ranges where precision would identify the client. State the period, the baseline, and the measure. Separate the intervention from the outcome. Include the limitations. A case study that says what did not change is often more persuasive than one that claims uniform success.
Metrics that survive procurement
Procurement teams are trained to test claims. A logo does not answer their questions; a method does. Present metrics with a baseline, a measurement period, and an attribution caveat. Distinguish outputs from outcomes. An output might be a new process or a completed migration. An outcome might be a reduction in cycle time, a fall in error rates, or a faster approval route. Where possible, identify the evidence source: client-verified figures, system reports, or third-party assurance. If numerical evidence is unavailable, use observable decisions: an audit passed, a backlog cleared, a business case approved. These are weaker than hard metrics but stronger than adjectives.
Consent language that is specific
Consent should be narrow and documented. Ask for permission to publish an anonymised description, agreed metrics, and, if appropriate, an unattributed quotation. Specify where the material will appear, how long it will remain, and who will approve the final text. Avoid blanket marketing consent. A short consent note, signed by an authorised person, is usually more acceptable than a wide waiver. Under UK data protection rules, avoid personal data and unnecessary identifiers. If individuals could be recognised, remove the detail or seek specific approval. This is not legal advice; it is risk management.
Formatting for procurement and panels
A credible no-logo case study should be easy to assess. Use a consistent one-page summary followed by a two-page narrative. Headings might include context, challenge, approach, outcome, and assurance. Put the evidence in an annex. Avoid design that depends on a client brand to create authority. Use plain typography, footnotes, and version control. If the case is used in a bid, make sure the claims match the approved text exactly. Procurement-friendly proof is proof that can be checked, not proof that looks impressive.
The no-logo portfolio
A portfolio of three or four anonymised cases can demonstrate range without breaching confidence. Mix sectors, project types, and outcome measures. Label each case as a representative example, not a client endorsement. Do not combine separate clients into a composite story without saying so. Keep an internal audit trail linking each published case to its consent record and evidence source. That trail protects the business if a claim is challenged and makes future approvals easier.
When consent is refused entirely
Sometimes the answer is no. In that situation, do not bend the rules. Offer aggregate evidence, a methodology note, or a reference conversation under confidentiality. A named referee who will speak privately can be more valuable than a public logo. Over time, a client may agree to a more detailed case once the relationship has matured. Discretion is itself a form of proof: it shows that the consultant can be trusted with sensitive information.
Credibility is constructed, not borrowed. A logo is a shortcut to recognition, but it is not the substance of proof. UK buyers increasingly need evidence they can defend internally. A rigorous anonymised case study, supported by clear consent and honest metrics, gives them that evidence. For a portfolio-led practice, the no-logo case study is not a compromise; it is a discipline. No logo does not have to mean no proof. It means the proof has been designed for the world in which the client actually operates.
