The gap between wanting more testimonials and actually having them is almost always a process problem, not a willingness problem. Your customers are happy; they would say something nice if asked well. What stops the flow is the shape of the ask. Somewhere along the way, "get a testimonial" became "schedule a thirty-minute call, record it, transcribe it, edit the transcript into something readable, and send it back for approval." That process produces good quotes, but it is so heavy that most teams run it two or three times a year and then wonder why their proof wall is thin. The fix is not to try harder at the interview. It is to stop interviewing.
A lengthy interview is the wrong tool for a task that a few well-designed questions can do asynchronously. The interview exists because someone assumed the customer could not write their own testimonial, so you had to extract it verbally and assemble it for them. That assumption is usually wrong. Given the right prompts and almost no time pressure, most customers write something more specific and more honest than they would say on a call, because they can answer between meetings, reread their own words, and send it when it is ready. Your job is to design the prompts, not to conduct the extraction.
Why the interview is the bottleneck
The scheduled call fails on both sides of the exchange. For the customer, it is a calendar commitment for something that is a favor to you, which means it gets deprioritized, rescheduled, and quietly abandoned. For you, it creates a pile of post-call work — the transcript, the edit, the approval loop — that turns a single testimonial into an afternoon. Multiply that by the number of happy customers you have and the reason your pipeline is empty becomes obvious: the unit cost per testimonial is simply too high to run often.
Worse, the interview format tends to produce worse raw material than people expect. On a call, customers reach for the smooth, generic phrases they think you want to hear — "great product, great team, highly recommend" — because talking in real time favors the safe cliché over the specific detail. The vague, interchangeable quote that makes a testimonial sound fake is often a direct product of the live-conversation format, not a failing of the customer. Give the same person a text box and a day to answer, and they will tell you the concrete thing that actually happened.
The asynchronous alternative: three to five sharp questions
Replace the call with a short set of questions the customer can answer in writing on their own schedule. The entire method is in the quality of the questions. Vague questions ("What do you think of us?") produce vague answers; specific questions force specific, usable material. A reliable set looks like this:
- What was the problem you were trying to solve before you found us? This anchors the testimonial in a real situation and gives prospects a "before" they can recognize themselves in.
- What almost stopped you from signing up? This surfaces the objection the quote can defuse — often the most persuasive sentence in the whole testimonial, because it names the exact hesitation a prospect is feeling.
- What is the concrete result you have seen? Push gently for a number, a timeframe, or a specific changed behavior. "Saved us about six hours a week" beats "saved us time" and is barely more effort to write.
- Who would you recommend this to, and who should skip it? The permission to name a non-fit makes the whole testimonial more believable, because praise that admits a limit reads as honest rather than scripted.
Four questions, answerable in ten minutes, in the customer's own words. You are not editing a transcript; you are receiving something close to publishable text. If any answer is thin, one follow-up line — "Could you say a bit more about the six hours?" — does the work that a full call would have, at a fraction of the cost to both of you.
Timing the ask so it barely registers as work
An asynchronous ask lands best at the moment the customer is already feeling the value, so it feels like a natural response rather than an interruption. The strongest triggers are the same ones that make the best moment to ask for a testimonial obvious: right after a customer hits a milestone, praises you unprompted in a support thread, renews, or tells you their result in passing. In each of these moments the specific detail you want is already on their mind, and the short question set simply captures what they were about to say anyway.
This is why the light-touch method compounds where the interview does not. Because each ask costs the customer ten minutes and costs you almost no follow-up work, you can make it a standing habit — a small, repeatable step attached to milestones and support wins rather than a quarterly campaign. A closely related move is to turn a customer support conversation into a testimonial, where the customer has already written the praise and you are simply asking permission to quote it. Both approaches share the same principle: collect proof at the point where the words already exist, instead of manufacturing a formal occasion to extract them.
Keep approval frictionless too
The final place lengthy processes creep back in is approval. If getting sign-off requires another email thread, a legal review, and a name-and-title confirmation spread across three messages, you have quietly rebuilt the friction you just removed. Fold approval into the original ask: tell the customer up front how you plan to use the quote, ask for the name and title you will attach in the same message, and give them a simple "reply 'approved' and we're set" close. Most people will approve in the same breath they answer, and you will have a finished, attributable testimonial from a single short exchange.
What you actually gain
Dropping the interview is not a compromise that trades quality for convenience — it usually improves both. You get more testimonials because each one is cheap enough to ask for often; you get better testimonials because written, unhurried answers are more specific than live ones; and you keep your customers on your side because you asked for ten quiet minutes instead of a place on their calendar. The teams with the deepest, most convincing proof walls are rarely the ones running the most polished interviews. They are the ones who made the ask so small that it happens all the time, and who trusted their customers to say the true, specific thing when given a clear question and a moment to answer it.