You did everything right. You caught your customer at a happy moment, you drafted the quote for them, and your champion replied "love it, go ahead." Then they added the sentence that kills more enterprise testimonials than anything else: "I just need to run it past legal." Two weeks later the answer comes back — no. Not because anyone is unhappy with you, but because a legal or communications team said so. This is maddening precisely because the customer wants to endorse you; the blocker is a department that has never used your product and never will. The good news is that a legal "no" is almost never a no to the endorsement itself — it is a no to something specific in how it was packaged, and once you find that thing, you can usually get to yes.
Why legal says no (it is rarely about you)
Legal and PR teams are not evaluating whether your product is good. They are managing risk on behalf of their company, and a public quote from a named employee triggers a checklist that has nothing to do with your relationship. The usual objections are predictable: the employee is not authorized to speak for the company publicly; a specific metric ("cut our costs 40%") could be read as a financial disclosure or an unverifiable claim; the company has a blanket policy against endorsing vendors to avoid looking like they play favorites in future procurement; or the quote implies a relationship the company does not want competitors or regulators to see. Notice that none of these are "we don't like the product." They are packaging problems. If you treat the rejection as a verdict on your relationship, you will retreat and lose it. If you treat it as a list of removable objections, you can negotiate.
Find out what was actually rejected
The single most useful move after a legal "no" is to ask your champion one question: what specifically did legal object to? Most people, when a testimonial gets blocked, hear "no" and never learn the reason — so they cannot fix it. Your champion usually knows, or can find out in one message, and the answer tells you exactly which lever to pull. If the objection is "we don't attribute quotes to named individuals," you have an anonymization path. If it is "you can't cite a specific dollar figure," you soften the metric. If it is "we have a blanket no-vendor-endorsement policy," that is a harder wall — but even then there are moves left. You cannot solve an objection you cannot see, and asking is free.
The de-escalation ladder: trade specificity for approval
Legal approval and testimonial power sit on a slider. The most powerful testimonial — named person, named company, hard number — is also the one most likely to get blocked. Instead of fighting for the maximum and losing everything, walk down the ladder until you hit a version legal will sign off on. Each rung keeps most of the credibility while shedding the specific thing legal objected to:
- Named person and company, softened metric. Keep the human and the logo, drop "40% cost reduction" to "a significant reduction in our costs." Often this alone clears the objection, because the unverifiable-claim risk is what legal flagged.
- Named company, unnamed person. "A Director of Operations at [Company]" instead of a named employee. This clears the "not authorized to speak individually" objection while keeping the logo, which is usually the part prospects care about most.
- Named person, unnamed company. "Sarah T., VP of Engineering at a Fortune 500 logistics firm." This clears blanket no-endorsement policies, because the company is not identifiable, while keeping a real human and a credible descriptor.
- Fully anonymized but specific. "The head of RevOps at a mid-market SaaS company" with the substance intact. Weaker, but still real, and legal almost never blocks a quote that does not identify their company at all — see how to use a testimonial when the customer wants to stay anonymous for how to make an anonymized quote still land.
The key mindset: a named-company testimonial with a soft metric beats a perfect quote that never gets published. Do not let the strongest version you cannot have block the strong-enough version you can.
Make it a one-line approval, not a project
Part of why legal says no is that a vague request ("can we use a quote from Sarah?") forces them to imagine every way it could go wrong, and imagining risk is their job. You reduce the risk they perceive by sending the exact, final text and telling them precisely where and how it will appear: "This 22-word quote, attributed as 'Director of Operations, [Company],' on our website testimonials page and nowhere else, with no metrics and no logo unless you approve the logo separately." A bounded, specific request is far easier to approve than an open-ended one, because legal can see the entire surface area and confirm it is small. Offer, up front, that they can request edits and that nothing publishes until they confirm in writing. You are converting an ambiguous risk into a thirty-second review.
Give legal a reason to say yes: the approval artifact
Legal's deepest fear is a claim they cannot stand behind later. You defuse it by making approval and its scope unambiguous and reversible. Tell them in writing that (a) you will publish only the exact approved text, (b) you will change or remove it within a stated window if they ever ask, and (c) you are not implying any endorsement beyond the words on the page. A written approval trail is not just protection for you — it is the thing that lets a cautious reviewer sign off, because it bounds their exposure. This is also why capturing approvals cleanly matters in general: the same discipline that gets you past legal is the discipline that keeps a published testimonial defensible for years. If you are catching the endorsement early, before it has to climb the corporate ladder, you often avoid the legal gauntlet entirely — timing is a lever here too, as covered in when is the best moment to ask a customer for a testimonial.
When the wall is real: banked and future-dated options
Sometimes legal's answer is a genuine, policy-level no with no rung of the ladder that clears it. Do not burn the relationship arguing. Instead, do two things. First, ask whether an anonymized, non-identifying version is acceptable — most blanket policies are about protecting the company's name, not about forbidding the employee from ever describing their experience. Second, ask your champion to keep the raw praise on file with their permission to revisit: policies change, the champion gets promoted, the company's stance on vendor endorsements evolves. A "not now" that you handle graciously becomes a "yes" in eighteen months, while a pushy fight makes it a permanent no. Bank the goodwill even when you cannot bank the quote.
The bottom line
A legal rejection feels like a door slamming, but it is almost always a door that opens with the right key. The customer already wants to endorse you — that battle is won. What is left is a packaging negotiation: find the specific objection, walk down the specificity ladder until you hit an approvable version, make the request bounded and final, and give legal an approval artifact that limits their risk. Handle it this way and you will convert a large share of "legal said no" into a published, defensible testimonial — one that carries an enterprise logo precisely because it survived the scrutiny that makes it believable.