Every business that collects testimonials runs into the same wall: the customer who loves you, says so warmly on a call, agrees enthusiastically to write a testimonial — and then never does. It is not reluctance. It is that writing a testimonial is a small piece of unpaid work, it lands on a to-do list already full, and it requires the customer to compose praise from a blank page, which is harder than it sounds. Weeks pass, the moment cools, and a real endorsement quietly evaporates. The most reliable way to rescue it is counter-intuitive: don't ask the customer to write the testimonial, write it for them and ask them to approve or change it. Done honestly, this converts a large share of the "yes, I'll get to it" customers into published proof, because you have removed the only thing standing in their way — the blank page.
The instinct against this is that a testimonial you wrote is not really the customer's words, and that objection is right if you do it carelessly. But a drafted-for-approval testimonial is not fabrication — it is a starting point the customer reads, corrects, and signs off on, exactly the way a lawyer drafts a letter a client approves or a ghostwriter drafts a byline the author endorses. The words become the customer's the moment they read them and say "yes, that's what I think." The credibility rests entirely on that approval being genuine, so the whole method lives or dies on how you gather and present the draft.
Build the draft from what the customer already said
You cannot write a credible testimonial from nothing — you write it from the specific things the customer has already told you. Comb your record of the relationship: the sentence in a support thread where they said your tool "saved us a full day every week," the line in a call where they mentioned onboarding "took an afternoon, not a month," the email where they described the problem they had before you. These are the raw material. A drafted testimonial assembled from the customer's own concrete statements reads true because it is true — you are organising things they said, not inventing an opinion. This is why customers who have contacted support are such fertile ground; the specific, emotional language of a resolved problem is exactly what a testimonial needs, a source explored in how to turn a support ticket into a testimonial.
Keep the draft specific and short. The single most common failure of a self-written testimonial is vagueness — "Great product, highly recommend" — and if you draft one for the customer, you have the chance to make it concrete instead: name the problem, name the result, use a number if you have one. A draft that says "We were spending six hours a week on manual reconciliation; ProofShow cut it to under one" gives the customer something worth approving and gives your prospects something worth believing. Write the draft you wish they had written, grounded in their own facts.
Present it as a draft to edit, not a form to sign
How you send the draft determines whether the approval is honest. The wrong way is to bury it in legalese or present it as a fait accompli that the customer rubber-stamps without reading. The right way is to send it plainly, in the customer's inbox, framed as a first draft they own: "I took a stab at writing this up based on what you've told me — please change anything that doesn't sound like you, or rewrite it entirely if you'd rather." That framing does three things: it makes clear the words are provisional, it invites correction so the final version is genuinely theirs, and it lowers the effort to a quick read-and-tweak instead of a blank-page compose. Most customers change a word or two and send it back; some rewrite half of it, which is a gift, because now it is unquestionably their voice.
Timing this send matters as much as the wording. A draft-for-approval lands best right after a moment of expressed satisfaction — a renewal, a solved problem, a piece of praise — when the customer is warm and the effort you are asking for is trivially small. Catching that moment is the same timing discipline that governs every testimonial request, developed in how to ask for a testimonial at the right moment.
Keep the attribution and the proof real
A drafted testimonial carries a slightly higher burden of proof, because it did not originate in the customer's own typing, so be scrupulous about everything that makes it verifiable. Use the customer's real full name, role, and company — with their permission — because a specific, checkable attribution is what tells a prospect this is a real person who really approved these words, a point covered in how to write the attribution line under a testimonial. Never publish a drafted testimonial the customer has not explicitly approved, and keep the approval on record. If a customer edits the draft, publish their edited version, not yours. The moment you publish words the customer did not sign off on, you have crossed from drafting into inventing, and a single customer who says publicly "I never wrote that" undoes far more trust than the testimonial ever built.
Place the approved quote where it works
An approved testimonial is only proof if a prospect meets it at the moment of doubt. Drafting one for approval solves the collection problem, but collection is half the job — placement is the other half. A quote about painless setup belongs beside your onboarding or pricing content; a quote about reliability belongs near a plan comparison. Dropping every approved testimonial into a single reviews page buries it where only the already-convinced go looking, a mistake corrected in where to place testimonials on a pricing page. The draft-for-approval method fills your bench of proof; deliberate placement puts that proof to work.
The point worth keeping
Your warmest customers are not refusing to endorse you — they are stuck on the blank page. Writing the testimonial for them, from their own words, and asking them to approve or edit it removes that block and recovers endorsements that would otherwise have evaporated. The method is honest as long as the approval is genuine: draft from what they actually said, present it as theirs to change, publish only what they sign off on, and keep the attribution verifiable. Do it that way and you convert good intentions into published proof — not by putting words in a customer's mouth, but by handing them words they are glad to call their own.