Most Quarterly Business Reviews are a PowerPoint deck of metrics that the customer already knows, followed by a politely disguised ask for more money or more commitment. The customer endures them. The vendor hopes something sticks.
After running hundreds of QBRs with enterprise customers across AWS and Fidelity, I've found a format that actually changes the relationship rather than just maintaining it. The difference comes down to three structural choices most vendors get wrong.
Lead With Their Business Outcomes, Not Your Metrics
The standard QBR opens with the vendor's metrics: consumption up 18%, tickets resolved in 2.1 days, NPS score of 52. These numbers tell the customer how you performed against your targets. They tell the customer almost nothing about whether your product is actually moving their business.
The better opening: what business outcomes did we achieve together since we last met? Not "your API call volume grew 40%" but "the integration you built with our platform reduced your customer onboarding time from 5 days to 18 hours, which your product team told us was a prerequisite for the EMEA expansion." Not "you consumed 300TB of storage" but "your compliance team met its regulatory archiving deadline for the first time in three years."
This requires homework before the meeting. It requires talking to people outside your primary champion — to the business units who use what you built, to the executives who sponsored the initiative, to the end users who live with the product daily. That homework is the most valuable preparation you can do for a QBR. It also almost nobody does it.
Make the Roadmap a Collaboration, Not a Reveal
The typical QBR roadmap slide is a vendor talking at a customer: here are the features we're building, here's when they'll be ready, here's how they map to what you told us you needed six months ago.
The better version is a facilitated discussion: here are the problems we think you're facing in the next two quarters, based on what we're hearing from your team — do these resonate? Here are the capabilities we're building that address those problems — which ones are most urgent for you? Where does this roadmap fall short of what you actually need?
This shift from presentation to conversation changes who owns the roadmap. When the customer has shaped it, they advocate for it internally. When it's handed to them, they nod and wait to see what actually ships.
Surface the Risks They Haven't Named
The most valuable thing a QBR can do is give an executive visibility into risks in their environment that they don't know exist yet. This is where the vendor's external perspective creates real value — you see patterns across dozens of similar customers that your counterpart doesn't have access to.
At AWS, I made a practice of including a "what we're seeing across your industry" section in every executive QBR. Not vendor content — actual patterns from the work: security misconfigurations that were causing breaches for companies at similar scale, cost optimization opportunities that were consistently missed during migrations, architectural choices that were creating technical debt three years down the road.
This section was consistently rated as the most valuable part of the QBR. It positioned the relationship as advisory rather than transactional. It gave executives something to bring back to their own leadership — "our vendor flagged a risk pattern we should look at." And it created natural leads for conversations about additional work without feeling like a sales pitch.
End With a Commitment, Not a Close
The typical QBR ends with a vendor ask: renew at this level, expand into this new product, approve this professional services engagement. The close is often awkward because it signals that everything leading up to it was really preamble to the ask.
The better close is a mutual commitment: we've agreed that the top priority for next quarter is X. On our side, we're committing to Y. On your side, you're committing to Z. Let's put those in writing and track them at our next meeting.
The commitments are small and specific. Getting the customer to commit to including two additional stakeholders in the next session, or to completing a security assessment by a specific date, is worth more than an aspirational conversation about a seven-figure expansion. Small commitments build the pattern of follow-through that makes large commitments possible.
The best QBR I ever ran ended with the customer saying "this is the first vendor meeting I've had in years where I walked away feeling like I learned something." That's the bar. Not a bigger renewal — a better relationship. The bigger renewal follows.
