The quarterly business review is the most under-used testimonial source in B2B. It is the one recurring meeting where the customer has already done the work of proving to themselves that your product is worth keeping — they have pulled the numbers, reviewed the outcomes, and come prepared to discuss whether the relationship is paying off. If the answer is yes, the raw material for a strong testimonial is already sitting on the screen. The problem is that most teams treat the QBR as a renewal-protection ritual and walk out without capturing any of it.
This guide covers how to collect a testimonial inside a QBR without turning the meeting into a favor request, and how to convert the specific, number-backed language that surfaces in these reviews into proof you can publish.
Why the QBR beats a cold testimonial ask
A cold testimonial request asks the customer to stop what they are doing, recall why they like you, and compose praise from memory. It fails not because customers dislike you but because recall is hard and unprompted praise is vague. The QBR removes both problems.
- The evidence is already on the table. A QBR is built around outcomes: usage growth, time saved, tickets deflected, revenue influenced. These are the exact specifics that make a testimonial credible rather than generic.
- The customer is already in an evaluative frame. They came to judge whether the relationship is working. When they say out loud that it is, they are not doing you a favor — they are stating a conclusion they arrived at independently.
- The relationship is warm and the context is business, not personal. You are not asking a friend for a nice quote. You are asking a stakeholder to stand behind a result they just presented.
Set up the capture before the meeting
The testimonial is only usable if you can quote it, which means you need permission and a record. Do two things in advance.
First, if the QBR is recorded (many are, for internal notes), confirm the recording consent covers your use of quotes, or plan to ask for a specific quote in writing afterward. Never publish a line lifted from a recording the customer did not know you would use externally.
Second, decide which outcome you most want proof of before you walk in. If you are building a case around onboarding speed, listen for the moment the customer describes their ramp. If you are building proof around ROI, listen for the number they cite. Knowing your target keeps you from leaving with a warm feeling and no quotable sentence.
The in-meeting move
The best testimonials from a QBR are captured at the moment the customer volunteers a positive conclusion, not bolted on at the end. When the customer says something specific and favorable — "we cut our review cycle from two weeks to three days" — you do two things.
- Reflect it back to confirm the specifics. "So the review cycle went from two weeks to three days — is that across the whole team or just the pilot group?" This does two jobs: it sharpens the number, and it signals that the statement mattered.
- Flag it lightly as quotable. "That's a great way to put it. Would you be comfortable if we quoted that — with your name and title — as a customer result?" Asking in the moment, about a specific sentence they just said, is far easier to say yes to than a blank request for "a testimonial."
If they hesitate, do not push. Note the sentence and follow up in writing after the meeting with the exact quote drafted, so all they have to do is approve it.
Turn the review into a publishable quote
The language that surfaces in a QBR is often better than anything a customer would write in a testimonial form, because it is grounded in the numbers they just presented. Your job afterward is to preserve the specificity, not to polish it into marketing language.
- Keep the number. "Cut our review cycle from two weeks to three days" is proof. "Saved us a ton of time" is not. If the customer gave you a figure, the quote must keep it.
- Keep the mechanism. A testimonial that says what changed and how outperforms one that only says the product is great. The QBR gives you the mechanism for free because the customer explained it.
- Attribute it fully. Name, title, and company turn a floating quote into a claim someone is standing behind. A QBR participant is a real stakeholder, which is exactly the kind of attribution that reads as credible.
Once you have the approved quote, place it where it answers a buyer's actual doubt rather than in a generic wall of praise. A QBR quote about onboarding speed belongs next to your onboarding claims; a QBR quote about ROI belongs next to your pricing or results section. For more on turning a vague endorsement into something specific enough to publish, see our guide on turning a glowing but vague testimonial into specific proof. And if the outcome the customer described is one you want to feature prominently, our guide on deciding which testimonial to feature on your homepage covers how to choose.
What to do when the QBR is not glowing
Not every QBR ends in praise, and you should not force a testimonial out of a lukewarm review. If the customer is neutral or working through problems, the right move is to fix the problems, not to extract a quote. A testimonial collected under strain reads as strained, and a customer who felt pressured to praise a product they are unsure about is a customer who will not renew. Capture testimonials only from QBRs where the customer volunteered a genuine positive conclusion — those are the ones that hold up when a prospect reads them.
The takeaway
The QBR is a testimonial engine hiding inside a renewal meeting. The customer arrives having already assembled the proof, states their conclusion in specific and number-backed language, and does so in a business context where attribution is easy. Capture the quote in the moment it is volunteered, confirm the specifics, ask lightly for permission, and follow up in writing with the exact line drafted. Done consistently, a single recurring meeting becomes a steady source of the most credible proof you can publish — testimonials grounded in numbers the customer chose to present themselves.