Ask while they are still delighted

A customer replied to a support thread this morning and, somewhere in the third line, wrote: "honestly this saved me about a day a week, I stopped dreading Mondays." You read it, felt good for four seconds, typed "so glad to hear it!" and archived the thread. That sentence is now gone. It was better than anything on your homepage, it was free, it was offered without being asked for, and it will never be seen by another human being.

This happens constantly and it is not a discipline problem. Praise arrives in the wrong place — inside a support reply, a renewal email, a passing remark on a call — at a moment when you are doing something else, and there is no obvious place to put it. Meanwhile the actual asking gets scheduled: a batch of twenty polite requests sent out one afternoon when someone finally notices the site has no proof on it. Those two things never meet. The praise you already received goes unrecorded, and the requests you send go out to people who are no longer feeling anything in particular about you.

Notice what the batch request is really asking. You are writing to a person having an ordinary Tuesday, who used your product six weeks ago, felt something then, and has since moved on. To answer you they must reconstruct an emotion they no longer have, translate it into a sentence they would be comfortable seeing in public, and do it as a favor with no deadline. Most people will genuinely intend to and never get to it. The ones who do reply write the thing you would write in that position, which is a compliment with no information in it: great product, easy to use, highly recommend. You now have proof that says nothing, and you will put it on the site anyway because you asked twenty people and got four answers.

praise has a shelf life, and it is shorter than your reporting cycle.

The alternative is not asking more people. It is asking at a different time. There are three or four moments in any customer relationship when the feeling is present, specific and unprompted, and they are easy to spot because the customer initiates them: they thank you unprompted; they tell you they got a result; they ask a question that reveals they have gone deeper than you expected; they renew or upgrade without being chased. In each of those moments, the sentence you want already exists in their head, fully formed, in their own words. You are not asking them to produce something. You are asking permission to keep something they already said.

Run it as arithmetic, with invented numbers meant only to show the shape. Batch approach: twenty requests, six weeks cold, four replies, one of which is usable and specific. Cost, an afternoon. In-the-moment approach: over the same quarter you notice eleven of these openings, and you reply to each one within the hour with a single line asking if you can quote what they just said. Eight say yes, because agreeing to a quote you already wrote is nearly free, and all eight are specific because they came out of a real situation. Same quarter, eight times the usable proof, and no afternoon spent. The whole difference is timing.

What to actually ask for

Do not ask for a testimonial. The word triggers marketing brain in the reader, and marketing brain writes superlatives. Ask for the thing you want to be able to say. "Can I quote that line about Mondays on the site, with your first name and company?" is a yes or no question with the work already done, and it takes them nine seconds. If you want something you do not have yet, ask one narrow question instead of an open one: what were you doing before this, or what would you go back to if we vanished tomorrow. Both invite a concrete answer. "How do you like the product" invites a compliment, which is the thing you do not need.

Then handle it like a real asset rather than a nice email. Keep one plain file with the quote, the name and role, the date, and one line about the situation it came out of, because in four months you will not remember whether the Mondays line came from a solo consultant or a fifteen-person team, and that context is what makes it persuasive to the next reader. Get permission in writing, ask specifically whether their company name can appear, and honor it exactly. A quote used more broadly than the person expected is a small betrayal that costs more than the quote was worth.

Where it goes matters as much as having it. Proof works next to the moment of doubt, not gathered on a page of its own that nobody visits. The line about saving a day a week belongs beside the price, in the same eyeline as the number the reader is hesitating over. The line about switching from a spreadsheet belongs next to the part of your site that explains what this replaces. This is the same idea as making your ad and your landing page tell one continuous story, which we wrote about a while back: the reader has a specific worry in a specific place, and proof answers a worry or it decorates a page.

We build tools that draft copy and pull your numbers into one place, and it is worth being plain that none of that produces this. AI can draft the ask, remind you the moment looked like one, and keep the file tidy. It cannot manufacture the sentence, and a generated testimonial is not a shortcut, it is a lie with your customer's name attached. This is the rare part of marketing where the raw material has to be given to you by another person, which is exactly why the only thing that matters is being awake when they hand it over.

So the practical version is one habit, not a project. The next time somebody says something good about your product, before you archive the thread, reply and ask if you can quote it. That is the whole thing. You will not get an afternoon back, but by the end of the quarter you will have a handful of real sentences from real people, and every one of them will be better than the paragraph you would have written about yourself.