How to use a customer example without naming the customer

Purpose

Decide what the example must prove before hiding the identity

Read the evidence instruction literally. A buyer may ask for a description of comparable experience, a list of contracts, a completed case-study template, proof of technical capacity or a referee who can verify performance. These are not interchangeable. EU public procurement rules, for example, allow experience to be demonstrated through suitable references when technical and professional ability is assessed. If the tender prescribes names, values, dates or contacts, an anonymous narrative may add context but may not satisfy the condition. Raise a timely clarification where the rules and confidentiality obligations collide.

Turn the criterion into a short proof statement. The evaluator may need evidence that the bidder has migrated a similar volume without service interruption, operated in a regulated setting, coordinated multiple sites or achieved a measurable adoption outcome. Keep the fields that let the evaluator test that proposition. Remove decorative detail. “A financial-services organization in Western Europe” may be enough for regulatory context; its exact country, employee count and launch month may add identification risk without improving the score.

Separate a customer example from an endorsement. The example is the bidder’s factual account, supported by its records and approved for disclosure. A testimonial represents the customer’s experience or opinion. Do not place invented quotation marks around reconstructed feedback, call the customer “delighted,” or say the organization recommends the service without permission. Truth-in-advertising guidance also treats implied claims and omitted context as part of the overall message, so accurate fragments can still create a misleading impression.

Evidence

Build the full case privately before producing the safe version

Create a restricted case record with customer identity, contracting entity, delivery entity, dates, scope, locations, service boundary, partners, measures and source links. Record the bidder’s role and any customer-owned work. Collect the signed contract or statement of work, acceptance records, operational reports, approved performance calculations and the account owner’s confirmation. A previous proposal or marketing case study is a lead, not proof. Its wording may be older, broader or approved for a different audience.

Decompose results into auditable elements. For a claimed reduction in processing time, retain the old and new definitions, population, observation period, exclusions, data owner and calculation. For availability, distinguish contract target from measured performance. For adoption, state whether the count represents invited, registered, active or trained users. If the customer supplied the number, say so internally and determine whether it may be disclosed. If multiple changes influenced the outcome, attribute the supplier contribution instead of asserting sole causation.

Mark every fact with an external disclosure state: approved as written, approved only in aggregate, requires customer consent, restricted to named buyer under confidentiality, or prohibited. Add an owner and expiry. Permission is purpose-specific. Approval to share a case with one evaluator under an NDA does not automatically authorize a public article, a sales deck or use by another legal entity. Preserve the signed decision or accountable approval beside the text it covers.

• Keep customer identity and public narrative in access-separated records.
• Trace each quantitative claim to a reproducible calculation.
• Record the bidder, partner and customer contribution separately.
• Attach disclosure purpose, audience and expiry to the approval.
• Reopen the case when facts, permission or proposed use changes.

Anonymization

Test the whole combination for identification risk

Remove direct identifiers first: organization and product names, personal names, logos, domains, addresses, exact contract numbers and unredacted screenshots. Then inspect indirect identifiers. A single fact may be harmless, but “the only cantonal hospital that replaced a named legacy platform in March 2025” can identify the account. Consider what the buyer, competitors, customer employees and a motivated researcher already know or can find. ICO anonymisation guidance emphasizes singling out and linkability, not only removal of names.

Generalize in a controlled order. Replace an exact date with a period, a city with a region, a precise count with a defensible band, a rare job title with a function and a proprietary technology with its relevant category. Suppress a detail if generalization still leaves a unique combination. Do not perturb material performance numbers or invent a synthetic company. If a precise figure is central to scoring and permitted, keep it while reducing less important contextual identifiers.

Run two reviews. The evidence reviewer checks whether the safe version still matches the private record and preserves relevant differences. The disclosure reviewer attempts to identify the customer from the full text, attachments, file metadata and surrounding proposal. Include adjacent facts elsewhere in the bid. An anonymous example can become identifiable when an organization chart, CV or partner section supplies the missing clue. Record the residual risk and approval rather than claiming anonymity as an absolute property.

Writing

Make the example specific about the work, not the identity

Use a six-part structure: relevant context, buyer problem, awarded scope, supplier method, evidenced result and applicability to the current requirement. State scale and constraints only where they help comparison. Explain what the supplier actually did, who accepted it and how the outcome was measured. Then disclose the material difference from the present bid. An evaluator learns more from a precise boundary than from adjectives such as leading, complex or transformational.

Write numbers with their basis in the sentence or nearby note. “Cut handling time by 32%” needs the compared periods, included cases and measurement source. If the evidence supports only an observed association, write that the measure changed after implementation rather than that the supplier caused it. If the example represents an unusually successful case, do not imply it is the expected result for every customer. FTC guidance on substantiation is jurisdiction-specific, but its practical discipline is widely useful: possess evidence for express and reasonably implied claims before making them.

End with a relevance bridge, not a promise of repetition. Identify which conditions transfer, such as transaction pattern, regulatory control, integration method or governance structure, and which differ. State how the proposed approach accounts for those differences. The past case supports capability and judgement; it does not guarantee the same result under another baseline, buyer organization or dependency set. If verification is available under confidentiality, describe the route without implying that the customer has agreed to be contacted when it has not.

• Name the evaluator decision the example supports.
• Describe the supplier role and service boundary precisely.
• Give every result its baseline, period, population and source type.
• Disclose material differences from the present requirement.
• State verification availability only within the approved permission.