Logos, not quotes
Customer Logo Permission Request Templates
A row of customer logos is the fastest proof on a homepage, and the one most often put up without asking. The person who loves your product usually cannot approve their company’s logo on their own. These requests are written to be forwarded to whoever can, with the exact use spelled out.
- Says exactly where the logo will appear
- Forwardable to their brand or legal team
- Pairs the logo with a quote when they are ready
Request builder
Write the logo request
Pick where the logo will appear. Every version names the placement, offers to follow their brand guidelines and says how to withdraw permission.
- Logo on your website
Subject: May we show the [Northwind] logo on our site?
Hi [Morgan], We would like to add the [Northwind] logo to [the customer logo row on our homepage], alongside other teams that use [Acme]. It would appear on its own, with no quote and no claim about results. A few things so you can decide quickly: - We will use the logo file you send, or the one from your press page. - We will follow any brand guidelines you share. - You can ask us to remove it at any time, and we will. Is that alright with you, or is there someone else at [Northwind] who should approve it? Thanks, [Lee]
Messages are assembled in your browser. Nothing you type is saved or sent.
The problem, solved
Where logo requests stall, and what StoryProof can and cannot do
StoryProof does not store logo files or log brand approvals for you. It helps with the parts around the logo: knowing who to ask, tracking who said yes, and turning a logo into a story.
- Problem 1
We do not know who to ask
Your contact at the customer may have changed roles, and the logo decision sits with someone you have never emailed.
How StoryProof solves it
Keep each customer contact in StoryProof, so the request goes to a named person rather than a guess. Contacts are on every plan.
- Problem 2
Nobody remembers which logos were approved
A year later the logo row has twelve companies and only half of the approvals can be found in anyone’s inbox.
How StoryProof solves it
Tag the customer with logo approved and the month, and save the approval email in your own files. Tags are included on every plan.
- Problem 3
A logo alone says very little
A row of logos shows who buys, not why. The same customer may happily add a sentence if asked at the right moment.
How StoryProof solves it
Once the logo is agreed, send the collection link so the contact can add a written, video or audio testimonial in the browser.
- Problem 4
Their brand team wants to see the words
If a quote will sit next to the logo, the approver will want to read it before anything appears publicly.
How StoryProof solves it
Anything a customer submits stays private until you approve it, so you can share the exact text with their brand team before it goes live.
- Problem 5
They asked us to take it down
A customer withdraws logo permission, and their quote is still in three widgets on other pages.
How StoryProof solves it
You choose which testimonials each widget shows, so take that customer’s testimonial out of every widget when the logo comes off.
What each use usually needs
A practical guide to how much to explain, not legal advice. When in doubt, ask for more than you need and use less.
In StoryProof
Track logo permission alongside testimonials
Step 1 of 4
Add the customer contact
Add each contact to StoryProof so the logo request and any later testimonial request go to the same person.
Step 2 of 4
Send the request from your inbox
Use the template for the placement. The approval is a reply to you, so keep it in your own records; StoryProof requests go by email but this one is yours to send.
Step 3 of 4
Tag the result
Tag the customer logo approved, logo declined or logo pending, with the month. A filter then shows your logo row’s paperwork at a glance.
Step 4 of 4
Ask for a sentence to go with it
For customers who said yes, send the collection link and invite a short testimonial that can sit beside or below the logo.
Before you start
What StoryProof does not do for logos
It does not store logo files
Keep approved logo files in your design or brand folder. StoryProof manages testimonials, not brand assets.
It does not record the approval itself
A tag shows the status, but the email where they said yes lives in your inbox. Save it where your team can find it.
This is not legal advice
Whether you need written permission, and what it should say, depends on your agreements and where you operate. If your contract has a publicity clause, read it before relying on it.
A logo is not a testimonial
Permission to show a logo is not permission to quote someone. Collect the quote separately, through the collection link, with its own approval.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do I need permission to put a customer’s logo on my website?
It is the safe habit, and many customers expect to be asked. Some contracts include logo use, but even then a courtesy note avoids an awkward surprise. For your specific situation, ask a lawyer.
Who at the customer should approve logo use?
Usually marketing or brand, sometimes legal for larger companies. Your day-to-day contact can rarely approve it alone, which is why the forwardable summary exists.
Is a reply email enough as permission?
Many teams treat a clear written yes from someone with authority as enough for a website logo. Larger customers may want their own form or a contract clause. Keep whatever they send.
What if they say yes to the logo but not to a quote?
Show the logo alone. Do not place a quote from someone else at the same company next to it unless that person has approved their words too.
What should I do when a customer churns?
Decide whether to keep showing them. Many teams remove former customers from logo rows. If the customer asks, take it down promptly.
Still have a question? Ask the StoryProof team or book a demo.
Turn a logo into a story
Keep customer contacts and testimonial approvals in one place, and ask the customers behind your logos for the words to go with them. No credit card needed to start.
Last updated 2026-11-11.