Should You Draft a Testimonial for a Customer, or Let Them Write Their Own?

A customer says yes. They love your product, they're happy to help, and they mean it. Then you send the request — "Would you mind writing a few sentences?" — and nothing comes back. Not because they changed their mind, but because a blank text box is intimidating, and "a few sentences about your experience" is a small writing assignment nobody signed up for.

This is the single most common reason testimonials die between "yes" and "published." The fix is a decision most people never make on purpose: do you draft the testimonial for them, or do you let them write their own? Both are legitimate. The wrong one for the situation costs you the testimonial — or your credibility.

The case for drafting it yourself

When you write a first draft and send it over for approval, you remove the hardest part of the ask. The customer's job shrinks from "compose something" to "does this sound right?" — a five-second task instead of a five-paragraph one. Response rates on "approve or edit this draft" are dramatically higher than on "please write something," for a simple reason: editing is easier than creating.

Drafting also lets you shape a testimonial that actually does marketing work. Left to their own devices, most happy customers write something warm but useless — "Great product, highly recommend!" A draft you propose can name the specific outcome, the before-and-after, the objection it overcame. You know which of those matters; the customer often doesn't.

Drafting is the right call when:

• The customer is busy or senior. An executive will happily approve a paragraph they'd never take twenty minutes to write.
• You already know the story. You've seen their results, read their support tickets, or heard them rave on a call. You're transcribing, not inventing.
• You need a specific angle. You want a testimonial that speaks to a particular objection — price, onboarding time, a competitor — and a blank box won't reliably produce it.

The hard line: drafting is not fabricating

Here's where drafting goes wrong, and why some teams are right to be nervous about it. A draft you send for approval must be built from things the customer actually said or actually experienced. You are putting their thoughts into cleaner words — you are not manufacturing a quote and hoping they rubber-stamp it.

Three rules keep you on the right side of the line:

1. Source every claim. Every sentence in your draft should trace back to a real statement — a call, an email, a survey answer, a support thread. If you can't point to where a claim came from, don't write it.
2. Never invent metrics. "Cut our onboarding time by 40%" is a fact the customer owns, not a number you get to guess. If you don't have the figure, ask for it or leave it out.
3. Give real permission to change it. The approval step only means something if the customer can actually rewrite it. Frame it as "edit anything that doesn't sound like you" — and mean it. A draft they feel pressured to accept isn't their words; it's yours in their mouth.

Done this way, drafting is transcription with better grammar. Done carelessly, it's fabrication with a signature — and that's a legal and reputational risk, not a shortcut. If a customer later says "I never said that," a fabricated testimonial becomes a liability far more expensive than the conversion it bought.

The case for letting them write their own

Sometimes the customer's own words are the entire point. A testimonial in the customer's unpolished voice — with their idioms, their specific frustration, their oddly specific praise — reads as unmistakably real. Over-editing sands off exactly the texture that makes social proof believable. This is the same instinct behind why over-polished testimonials read as fake: the closer you get to marketing copy, the less it persuades.

Letting them write is the right call when:

• The customer is a strong writer or communicator. Founders, marketers, and consultants often produce better copy than you would, and they enjoy doing it.
• Authenticity is the whole value. For a video testimonial, a public review, or a quote where voice matters more than precision, their words win.
• You want quotes you couldn't have predicted. The best testimonials often praise something you didn't know was a selling point. A draft can't surface what you don't already know.

The hybrid that beats both

For most B2B situations, the highest-yield approach is neither pure drafting nor a blank box. It's a guided prompt: instead of asking them to write freely or approving your paragraph, you send three or four specific questions.

• What problem were you trying to solve before you found us?
• What almost stopped you from signing up?
• What's the concrete result you've seen?
• What would you tell someone considering us?

This does the work of a draft — it structures the response and pulls out specifics — while keeping the words entirely theirs. You get answers you can lightly assemble into a testimonial, and every phrase is genuinely the customer's. It sidesteps the fabrication risk of drafting and the blank-box paralysis of free writing at the same time. For more on getting these questions right, see the questions that produce specific testimonials instead of generic praise.

A simple decision rule

• Busy customer, story you already know, specific angle needed → draft it, source every line, and give real edit permission.
• Strong writer, authenticity is the point, video or public review → let them write it.
• Everyone else (most cases) → send guided questions and assemble from their answers.

Whichever path you choose, the failure mode to avoid is the same on both ends: never publish words the customer didn't actually mean, and never let a blank text box quietly kill a testimonial the customer was genuinely willing to give. The goal isn't to make the writing easier for you — it's to make saying "yes, that's exactly right" easy for them.