Use Customer Logos Without Confusing Clients, Pilots, and Partners
Use Customer Logos Without Confusing Clients, Pilots, and Partners
A logo page is one sentence spoken on behalf of several organizations at once. The heading supplies the verb — "Customers," "Trusted by," "Our partners" — and the marks supply the subjects. Readers don't audit it mark by mark. They take the page as a single claim, apply it to every name they recognize, and move on.
That is why the fix is rarely a cleverer heading. Before a mark goes up, establish four things about the organization behind it: what kind of relationship it is, whether it is current or historical, how much of that organization the relationship actually covers, and whether this use is authorized. Then put it under a heading that stays true for every member of that group. When a limitation is doing the real work, write a sentence instead of borrowing the recognition of a mark. When something can't be established — the scope, the current state, the permission — leave the mark off. A short page whose collective claim holds is worth more than a full one that quietly overstates.
The four organizations below are invented and labeled A through D. No real company, mark, customer, or permission is involved. They are here because the right answer changes shape for each of them.
Recover the relationship behind each mark
Here is the record as the relationship owners report it.
Organization A is a current customer. One team — network operations — at a larger organization has used the product since 2024, and the renewal is in place. The relationship is with that team's use. Nobody has established that the wider organization has adopted anything. The team's relationship owner confirms that A approved the team-level reference and the use of its mark on this page.
Organization B is a pilot participant. The pilot ran for a fixed term and has ended. Whether it converts is genuinely undecided. The pilot paperwork says nothing about publicity, so name use has not been confirmed.
Organization C is a partner. There is a current technology partnership, no purchase and no deployment recorded anywhere. The partnership owner confirms the arrangement is current, that the partner agreed to be named as a partner, and — separately — that the mark may be reproduced on this page. Naming and mark use are two permissions, and C has given both for this use.
Organization D is an expired engagement. It was a paying customer from 2021 until 2024, when the contract lapsed and was not renewed. The relationship owner confirms that D agreed to be listed. It is a real relationship, and it is a past one.
Now notice what the asset folder tells you about all four: nothing. A row of logo files in a shared drive proves that a designer once had the files. It does not prove a contract, a pilot, a partnership, or permission. Files travel; facts don't.
There is a fifth category that never belongs on the page, and it usually arrives through a person rather than a document. Someone at a recognizable organization tried the product on a personal account. A contact was quoted in a blog post. An engineer you met at a conference said nice things about a feature and was never asked whether their employer could be named. A logo can end up in the folder because a vendor's customer is, in some confused chain of custody, also described as yours. None of these is a relationship with that organization, and none of them becomes one because the name is familiar.
Where the record is silent, leave it silent. If you cannot tell whether a pilot converted, the question "is B a customer?" has no answer yet, and putting B under "Customers" does not supply one. It just launders the uncertainty into a claim.
Write a heading that stays true for every logo under it
Test the heading literally, member by member.
"Customers" cannot cover B, an unconverted pilot. It cannot cover C, a partner with no purchase. It cannot cover D, who stopped being one in 2024. Only A qualifies, and only in a qualified way.
"Trusted by" is softer, and softness is not the same as accuracy. It invites the reader to hear satisfaction, reliance, or endorsement — a degree of confidence the record does not establish for a pilot that ended, a partner that integrates rather than buys, or a departed customer. A vague heading that readers convert into the strong claim has solved nothing; it has only moved the overstatement somewhere less inspectable.
What works is separating the categories and naming them accurately. A "Customers" group containing A. A "Partners" group containing C. A "Past engagements" group containing D with its dates attached. B does not appear anywhere yet — for two independent reasons that happen to point the same way.
That last point matters more than it looks. If B's pilot terms had permitted publicity and the pilot were still running, "Pilot participants" would be an honest heading, and there is nothing shameful about it. Accurate categories are not the timid version of a logo page. They are the version that survives the reader who knows one of these companies.
Write the heading twice if it helps: once before you assemble the group, to decide what belongs, and once after, to check what you've built. Either way, the heading should be a summary of established facts, not a container into which facts are poured.
Make the scope legible, not just disclaimed
A department-level relationship is not organization-wide adoption, and the page has to say so at a size where it can actually be read.
For A, that means naming the team: "Network operations team, since 2024." A mark at full width with a line of nine-point type underneath is not the same statement. The logo reads first and stays in memory; the qualifier reads last, if it is read at all. Worse, slides get cropped, screenshotted, and pasted into other decks. A footnote does not travel with the mark. If the qualification is the part that keeps the page honest, give it comparable weight — or let prose carry it.
That is the third treatment worth comparing. A sentence can hold a limitation that a mark cannot: "Organization A's network operations team has used the product since 2024." For D, a dated line ("2021–2024") does more work than a logo under a heading that implies the present tense. And for a relationship whose whole truth is a limited one — a single team, a short engagement, an evaluation that stopped — a plain description is often clearer than a mark that requires a caption to be accurate.
The decision rule is roughly this: a logo earns its place when the reader learning the name is itself worth something and the surrounding text still tells the truth at a glance. Otherwise you are spending the reader's assumption of a strong relationship to buy attention for a weak one.
A true relationship is not a permission slip
Truth and permission are separate questions, and passing the first does not settle the second.
Permission attaches to a use, not to a company. An agreement that lets you list someone in a partner directory is not automatically an agreement to place their mark on a sales slide. A customer reference clause written for a website testimonial may say nothing about a pitch deck that gets forwarded outside the account. So the question is not "may we name them?" but "may we use this mark, in this document, in this placement, presented this way, for how long?"
C's record above carries both answers, recorded separately: one for the name, one for the mark in this placement. That is why C's mark is on the corrected page, and why neither answer was inferred from the other.
Ask the relationship owner, who knows whether the engagement is still what you think it is, and the people who hold the marks and the rights, who can tell you whether this use is covered. Record the answer somewhere the next person can find it.
For general US context, the Federal Trade Commission's overview of advertising endorsements (https://www.ftc.gov/news-events/topics/truth-advertising/advertisement-endorsements, checked September 8, 2026) is about truthful, non-misleading endorsements and material connections. It is context, not a verdict on your slide, and it does not decide what any particular logo represents or how trademark rights apply here. Real questions about a real mark belong with qualified review.
Omitting is a legitimate outcome, and it is often the right one. Organization B does not appear on the corrected page — not because the pilot didn't happen, but because its status is undecided and its name use is unconfirmed. Neither condition is repaired by wanting a fuller-looking page.
One trap to avoid: replacing the unapproved mark with unapproved copy. Writing a sentence that identifies Organization B by name, without the logo, is the same authorization question wearing different clothes. Naming an organization in prose can still function as a claim that they endorse or use you. If permission is missing, the fix is to leave the organization out, not to describe them more quietly.
Don't let the wall make the outcome claim
A mark beside a heading shows an association. It does not show satisfaction, improved performance, or continued use. Readers supply all three anyway, which is exactly why the page cannot be allowed to supply them implicitly.
If a real, evidenced result exists — something measured, attributable, approved by the customer, and stated with its conditions — it belongs in the account of that engagement, where the reader can see what changed and what didn't. It does not belong as a caption under a group of logos, and it does not become true because four marks appear above it.
Which brings up maintenance. The corrected page is accurate for the quarter in which it was written. When the pilot converts, B can move into the customer group with its new dates. When D signs again, D stops being past. When A's network operations team ends its subscription, the customer group is no longer true. A logo page is not a monument; it is a statement with a shelf life, and someone should own the calendar that refreshes it.
Read the page one mark at a time
The test takes about ninety seconds. Read the heading aloud. Then walk the marks left to right and ask, for each one: is this relationship the kind the heading names, in the state the heading implies, at the scope the page suggests, with permission for this use?
If every mark passes, you have a page you can hand to anyone. If one fails, change the presentation rather than shrinking the fact beneath it — split the group, name the scope, write the sentence, date the engagement, or take the mark off until the record catches up. The point of filling a page with recognizable names is that recognition does something. When it carries a larger implication than the relationship supports, the fix is never a smaller version of the truth. It is a page whose claim you can defend mark by mark.
Frequently asked questions
What four things should be established before a logo goes on a page?
Establish what kind of relationship it is, whether it is current or historical, how much of the organization the relationship covers, and whether this use is authorized. Then put it under a heading that stays true for every member of that group. If scope, current state, or permission cannot be established, leave the mark off.
How should Organizations A, C, and D be grouped?
A is a current customer relationship with one team, so it belongs under Customers with scope such as network operations team, since 2024. C is a current technology partner with no purchase or deployment, so it belongs under Partners if both name use and mark reproduction are confirmed. D is an expired paying customer from 2021 to 2024, so it belongs under Past engagements with dates attached.
Why is Trusted by not automatically a safe fix?
It is softer, but softness is not accuracy. It can invite readers to hear satisfaction, reliance, or endorsement that the record does not establish for an ended pilot, a partner that integrates rather than buys, or a departed customer. A vague heading that readers convert into a strong claim has moved the overstatement somewhere less inspectable.
Is a true relationship enough to use a logo?
No. Truth and permission are separate questions. Permission attaches to a use, not to a company, so an agreement to list someone in a partner directory is not automatically an agreement to place their mark on a sales slide. Ask the relationship owner and the people who hold the marks and rights whether this use is covered, and record the answer.
What should happen with Organization B or with a person who used a personal account?
B is a pilot that ended, its conversion is undecided, and its name use is unconfirmed, so it does not appear yet. A personal account, a quoted contact, or a conference conversation is not a relationship with that organization and never becomes one because the name is familiar. Replacing an unapproved mark with unapproved prose naming the organization is the same authorization question.