There's a specific way an enterprise testimonial dies, and it isn't a rejection. Your champion is thrilled with your product, they've agreed to say so publicly, and then they add the sentence that quietly kills it: "It just needs to go through legal." Weeks pass. You follow up and get "still waiting on legal." Eventually the momentum drains out and the quote never publishes. What happened isn't that the legal team hated you. It's that the request reached them as an open-ended, undated risk with no defined scope — and an open-ended risk with no deadline is the easiest thing in the world for a busy reviewer to leave at the bottom of the pile. The way to win a legal-gated testimonial is to make the review small, bounded, and fast, so that saying yes costs the reviewer almost nothing.
Why legal review stalls (it's rarely a real objection)
When a testimonial sits in legal for a month, the instinct is to assume there's a substantive problem — a policy against endorsements, a concern about a specific claim. Occasionally that's true. Far more often, nothing is wrong at all: the request simply has no shape. A reviewer who receives "our vendor wants us to say something nice, can you approve it" faces an unbounded question. What exactly will be published? Where? Can it be edited later? Does approving it commit the company to anything? With none of that defined, the safe move for the reviewer is to do nothing, because doing nothing carries no risk and answering carries unknown risk.
The reframe is that your job is to shrink the question until the answer is obvious. Legal teams move fast on requests that are specific, scoped, and clearly low-stakes. They stall on anything that feels like it could come back to bite them. Almost everything below is about converting a vague ask into a bounded one.
Hand legal a finished artifact, not a blank request
The single biggest accelerator is to never ask legal to approve an idea. Ask them to approve an exact, finished quote. The difference is enormous: reviewing "can our customer endorse you" means imagining every possible thing that endorsement could say, while reviewing "does this specific sentence, published in this specific place, create any problem" is a concrete question with a concrete answer.
Give the reviewer a one-page packet containing:
- The exact text. Word for word, the quote as it will appear. No placeholders, no "something like."
- The exact attribution. The name, title, and company as they'll be shown — or the anonymized version if that's what was agreed.
- Where it will appear. "On our website's customer page and in sales presentations." Naming the surfaces bounds the exposure.
- What it does not claim. Explicitly note that the quote makes no performance guarantee, discloses no confidential terms, and doesn't reference pricing. Preempting the three things legal usually worries about removes most of the review.
- A revocation clause. State that the customer can withdraw the testimonial at any time with a simple request. Nothing lowers a reviewer's stakes faster than knowing the decision is reversible.
A packet like this turns a multi-week deliberation into a five-minute read. You've done the reviewer's risk assessment for them.
Strip the claims that trigger scrutiny before legal sees them
Some quotes are slow to approve because of what they say. A testimonial that names a specific dollar figure of savings, guarantees an outcome, or discloses how the customer uses the product internally gives legal real things to weigh. If the quote's power depends on a specific number, keep it — but get ahead of the review by sourcing that number from data the customer already publishes or is comfortable sharing, and say so in the packet. If the number is nice-to-have rather than load-bearing, consider offering the customer a version that conveys the result without the sensitive specifics, so legal has less to object to. The goal isn't to gut the testimonial; it's to make sure every claim that stays in is one you can point to a source for.
Keep your champion engaged through the queue
The person who agreed to the testimonial is your ally inside the company, and a legal review is exactly when you're most likely to lose them to silence. Don't hand the process off and wait. Make it easy for your champion to push it forward: give them the finished packet so they can forward it to legal directly rather than paraphrasing your request, agree on a rough timeframe up front ("would it be reasonable to hear back within two weeks?"), and set a single, gentle check-in rather than a string of anxious follow-ups. A champion who has the artifact in hand and a date to work toward is far more likely to walk it through than one who's been left to relay an open-ended favor.
Know when to stop pushing
If legal comes back with a firm no rooted in company policy — a blanket rule against naming vendors, an industry regulation on endorsements — that's a real answer, and continuing to push damages the relationship you'll want later. When that happens, pivot rather than persist. An anonymized testimonial that describes the role and result without the name often clears a legal bar that a named one can't, and it preserves the proof without asking the customer to fight their own policy. Read the difference between "we're slow" and "we can't," and match your effort to which one you're facing.
The bottom line
A legal-gated testimonial isn't lost the moment legal gets involved — it's lost when the request reaches legal as an unbounded risk. Do the reviewer's job for them: hand over the exact text, the exact attribution, the surfaces, an explicit list of what it doesn't claim, and a revocation clause. Keep your champion armed with the packet and a timeframe. Shrink the question until the answer is easy, and most of the testimonials you'd have written off to "stuck in legal" will publish instead.