If you sell B2B software, the quarterly business review is the most underused testimonial opportunity you have. By the time a QBR happens, your customer has lived with the product for a full quarter, someone on their side has pulled the numbers, and the whole meeting is structured around one question: did this deliver value? When the answer is yes, you are sitting in the exact emotional and factual moment that makes a testimonial credible. Most teams walk out of that room without asking. This is how to change that — without turning a strategic review into a sales pitch.
Why the QBR beats every other testimonial moment
A testimonial is only as strong as the evidence behind it, and the QBR manufactures evidence as a matter of routine. Three things line up at once:
- The value is quantified. A QBR deck almost always contains real usage data, outcomes, or ROI. That is the raw material of a specific, non-generic testimonial. "It saved us time" is weak; "we cut our onboarding cycle from 11 days to 4" comes straight off the slide.
- The right person is in the room. QBRs are attended by the champion and often their manager or an executive sponsor — exactly the named, senior voices that make a testimonial persuasive on a landing page.
- The relationship is at its peak. A QBR is a deliberate investment of your customer's time. If they showed up, they are engaged. Asking a disengaged customer for a testimonial is awkward; asking an engaged one is natural.
Miss the QBR and you are back to asking cold weeks later, when the numbers have faded and the meeting warmth is gone.
The timing rule: ask when the value is on screen
The mistake is asking at the wrong minute. Do not open the meeting with the request, and do not tack it onto the calendar invite. Ask in the moment the customer themselves acknowledges a result — when they look at the outcomes slide and say some version of "yeah, this has been working."
That acknowledgment is your cue. It means the customer has stated the value in their own words, unprompted. You are not asking them to invent praise; you are asking them to repeat something they just said, on the record.
The exact language
Keep it short and specific. A version that works:
"This is great to hear. That number on the onboarding slide is exactly the kind of result other teams evaluating us want to see. Would you be open to us capturing a short quote about it — one or two sentences, and I'll draft it for you to edit so it's zero work on your end?"
Three things make this land:
- You reference the specific metric they just validated. The testimonial is anchored to a real number, not a vague feeling.
- You lower the effort to near zero. "I'll draft it for you to edit" removes the blank-page burden that kills most testimonial requests. Busy champions do not want to write; they want to approve.
- You frame it as helping their peers, not you. "Other teams evaluating us want to see this" is a softer ask than "we need testimonials."
Draft it before they forget
The single highest-leverage move is drafting the quote from the QBR itself. You have the deck. Pull the exact metric, write two sentences in the customer's register, and send it within 24 hours while the meeting is fresh:
"Draft for your review — edit anything: 'ProofShow cut our onboarding cycle from 11 days to 4 in a single quarter. The QBR made the impact impossible to ignore.' — [Name], [Title], [Company]."
An editable draft converts far better than an open-ended "would you write us a testimonial?" because you have done the work and handed them a one-click yes. This is the same principle behind drafting the testimonial for the customer to approve — remove the writing, keep the approval.
Handle the "let me check with legal" reflex
In larger accounts, the champion may want internal sign-off before their name and company appear publicly. Do not treat this as a no. Make it easy:
- Offer to anonymize to title and industry if the company name is the blocker ("a VP of Operations at a mid-market logistics firm").
- Offer the quote for internal use first — sales decks, case studies shared under NDA — which is a lower bar than a public website.
- Give them a clear, revocable arrangement so nothing feels permanent.
If it still stalls, the path forward is the same as what to do when a customer agrees to a testimonial but goes quiet: follow up once with the finished draft attached, not with a reminder that they owe you writing.
Build it into the QBR process, not the person
The reason most teams miss this moment is that it depends on a rep remembering in real time. Systematize it instead:
- Add a "testimonial-worthy result?" checkbox to your QBR template so the CSM flags strong quarters as they present.
- Make "send editable draft within 24h" a standard post-QBR task, the same way sending the recap deck is.
- Route flagged quotes into a single collection and approval flow so nothing gets lost between the meeting and the website.
When capturing proof is a step in the QBR workflow rather than an act of initiative, your testimonial pipeline fills itself every quarter — from your most engaged, best-documented, most senior customers. That is exactly the segment whose voice moves deals, and the QBR hands it to you four times a year. The only real cost is remembering to ask in the right minute — so stop leaving it to memory, and put it in the process.