A testimonial that reads "This tool saved our team ten hours a week" is good. The same testimonial sitting next to a logo a visitor instantly recognizes is far better — because the logo does the one thing the words cannot: it proves a real, credible company stood behind the claim. This is why a wall of customer logos is often the single most persuasive element on a B2B homepage.
But a logo is a trademark, and displaying one implies an endorsement. Using a customer's mark without clear permission can strain a relationship you worked hard to earn, trip a clause in their brand guidelines, or — with larger enterprises — pull in their legal team. The good news is that getting permission is usually simple. It just has to be asked for explicitly and captured in writing.
Why the quote and the logo are two separate permissions
The most common mistake is assuming that a customer who agreed to a testimonial has also agreed to have their logo displayed. They have not. These are two distinct asks:
- The words. Permission to publish what they said, attributed to their name and title.
- The mark. Permission to display their company's trademarked logo alongside it.
A customer can be perfectly happy to praise you in words while their company policy forbids the logo appearing on a vendor's site — or requires it to be reviewed first. Treating the logo as automatically included is how a friendly testimonial turns into an awkward takedown request. Ask for both, and ask for them separately if you sense any hesitation.
For a broader look at where these logo walls actually earn their keep, see our guide on where to display testimonials on your website.
Who actually has the authority to say yes
The person who gave you the quote is often not the person who can approve logo use. A team lead or an individual champion can speak to their own experience, but brand and legal permissions usually sit with marketing, communications, or legal.
This does not mean you need to escalate every request to a customer's legal department — that is overkill for most small and mid-sized companies, and it slows everything down. But it does mean you should:
- Ask your contact whether logo use needs sign-off from anyone else. A one-line question ("Is it okay to show your logo, or is that something your brand team likes to review first?") surfaces the constraint without creating friction.
- Respect a "let me check" as a real answer. If they need to confirm internally, that is a good sign they take their brand seriously — and that the permission you get will actually hold.
- Never guess. Pulling a logo from the customer's website and posting it because "they clearly like us" is exactly the shortcut that causes problems later.
How to ask — a template that gets a clean yes
Keep the request short, specific, and easy to approve. The goal is to make saying yes a two-second decision:
Hi [Name] — thank you again for the kind words about [product]. We'd love to feature your quote on our site. Two quick things I want to confirm so we do it right:
- Are you comfortable with us publishing the quote attributed to you by name and title?
- Is it okay to display [Company]'s logo alongside it? If your team prefers to review placement first, I'm happy to share a mock-up.
No rush at all — just let me know what works on your end.
This does three things well: it separates the two permissions, it offers a review step before they have to ask for one, and it signals that you care about doing it correctly. Customers are far more willing to say yes to a vendor who obviously respects their brand than to one who treats the logo as free real estate.
What to capture in writing
Verbal permission is better than nothing, but it evaporates the moment the person who gave it leaves the company. Capture the essentials in a short written record — an email thread is usually enough for small and mid-market customers:
- What was approved: the exact quote text and the logo.
- Who approved it: name, title, and date.
- Any conditions: "logo only on the homepage," "review before any paid ad use," "remove within 30 days of a written request," and so on.
- How to revoke: a simple line noting they can ask you to remove it at any time.
Storing this alongside the testimonial itself — rather than in a random inbox — means that a year from now, when someone asks "are we allowed to use this?", the answer is one lookup away instead of a nervous guess. This is also what makes it painless to comply quickly if a customer ever asks you to take the logo down, which protects the relationship far more than clinging to a logo you were only loosely permitted to use.
Handling the customer who says yes to the quote but not the logo
This happens often, especially with enterprises and regulated industries, and it is not a rejection. Have a graceful fallback ready:
- Attribute by name and title without the logo. "Head of Operations, a Fortune 500 logistics company" still carries real weight when the full mark is off the table.
- Offer a text-only company name if the logo specifically is the issue but the name is fine.
- Use an industry descriptor when even the name is sensitive: "a national retail chain," "a mid-market SaaS company."
The credibility of a testimonial comes from specificity and a real human voice, not from the logo alone. A vivid, concrete quote attributed to a named person will almost always outperform a generic quote sitting next to a famous mark. If you have to choose, choose the better words.
For more on turning existing praise into words that land, see how to turn a positive Google review into a website testimonial.
The short version
- Treat the quote and the logo as two separate permissions, and ask for each explicitly.
- Confirm whether your contact can approve logo use, or whether a brand or legal team needs to.
- Make the ask short, offer a review step, and capture the yes in writing — including any conditions and how to revoke.
- If they decline the logo, fall back to name, title, or an industry descriptor. The credibility was never only in the mark.
Getting logo permission right costs you one careful email and a saved record. Getting it wrong costs you a relationship. The math is not close.