Turning a Vendor QBR From a Sales Pitch Into a Real Review
Most quarterly business reviews with vendors are the vendor's account team presenting a deck designed to justify the renewal, with your side mostly listening and nodding along. A QBR worth the calendar time flips that dynamic: you arrive with your own questions and data, and the vendor responds directly to what you actually need to know, not what they'd prefer to present.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
How do you run a vendor QBR on your own agenda?
Before the meeting, send the vendor three or four specific questions you want answered, tied to your own usage and goals, rather than accepting their standard template wholesale. This alone changes the tone of the meeting from a scripted pitch to an actual conversation, since the vendor now has to prepare genuine answers to your specific questions rather than simply running through their default deck.
Sending the agenda ahead of time, rather than raising it live in the meeting, also gives the vendor's team a real chance to bring someone who can actually answer a technical or contractual question, instead of an account manager improvising an answer they'll have to follow up on later anyway.
Bring your own usage data, not just theirs
A vendor's own reported usage numbers are, quite understandably, presented in the best possible light for them. Pull your own data on how the tool is actually being used across your team beforehand, and compare it against what the vendor presents. A meaningful gap between the two is itself useful information, either about adoption problems on your side or about metrics that look better in the vendor's framing than they do in practice.
This comparison is often the single most revealing moment of the whole meeting. A vendor's aggregate usage metric can look healthy while masking that only a small pocket of your team actually uses the tool regularly, and your own data is usually the only way to see that clearly.
For example, a vendor may report that nearly all licensed seats are active. Your own logs might show that most of that activity comes from one department, while the rest logged in once to set a password. That gap changes the conversation: instead of debating the vendor's number, you ask what onboarding support they will provide to the idle teams, or whether you should renew fewer seats. Bring the comparison as a simple table with your figures next to theirs, and ask the vendor to explain any difference. If they cannot, that is a finding for the renewal decision.
Spend on G&A as a check against where all this vendor spend fits
Median G&A spend runs about 24% of revenue at B2B SaaS companies1, which is a reasonable outside reference point when reviewing whether your total vendor and tooling spend, cumulative across every QBR-worthy relationship, is tracking sensibly against your own overhead rather than growing unchecked one renewal at a time.
No single QBR is the right venue for this broader check, but keeping the reference point in mind across a full cycle of vendor reviews helps catch the slower, cumulative creep that no individual renewal decision would ever flag on its own.
How do you get real answers about a vendor roadmap?
A vendor's roadmap slide is almost always vague and aspirational on purpose. Push past the slide itself: ask for a specific committed date on any feature that's genuinely blocking your team, and treat a lack of a real date as useful information about that feature's actual priority for the vendor, whatever the roadmap slide implies.
A vendor that can give a specific quarter, even a soft one, is telling you something meaningfully different from a vendor that can only offer "it's on our radar," and that distinction is worth pressing for directly rather than accepting a vague answer politely and moving on to the next agenda item.
Leave with documented actions, not just a good feeling
End every QBR with a short written summary of what was agreed, on both sides, and a follow-up date if anything is still open. Without this, a QBR that felt productive in the room quietly produces nothing, since neither side has a record to hold the other to once the meeting ends and everyone moves on to the next thing.
MeetMyCOO's AI COO, Olivia, can draft that summary from meeting notes right after the call, while the details are still fresh, so it goes out the same day rather than sitting unwritten until momentum from the conversation has already faded.
Use this sequence for every vendor QBR:
- Send the vendor three or four specific questions tied to your own usage and goals before the meeting.
- Pull your own data on how the tool is actually used across your team.
- Compare your numbers with the vendor's reported metrics and note any gap between them.
- Ask for a committed date on any feature that is blocking your team, and treat the lack of a date as information.
- End with a written summary of what was agreed and a follow-up date for anything still open.
What Good Looks Like
A good QBR process brings your own agenda and usage data to the table rather than accepting the vendor's framing wholesale, pushes vague roadmap answers for real specifics, and ends with a documented, mutually agreed set of actions.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Frequently Asked Questions
How often should we hold a QBR with a given vendor?
Quarterly makes sense for your largest, most business-critical vendor relationships. For smaller vendors, a lighter annual check-in, rather than a full quarterly cadence, is usually a better use of everyone's time.
What if a vendor resists answering our specific questions and sticks to their deck?
That's itself useful information about the relationship. A vendor unwilling to engage with your actual questions is worth weighing seriously at the next renewal decision, regardless of how the rest of the meeting goes.
Should the same person always run QBRs with a given vendor?
Continuity helps, since that person builds context on the relationship over time, but bringing in the actual day-to-day users of the tool periodically surfaces ground-level issues an account owner alone might miss.
Sources
Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.
- Operating expense as % of revenue, medians (B2B SaaS). Benchmarkit 2025 SaaS Performance Metrics Benchmark Report (FY2024 data), 2024.
Related Guides
The Operational Readiness Review: A Pre-Launch Checklist
What an operational readiness review should actually cover before a launch, beyond whether the product itself works, and who should run it.
Governing AI Agents Before They Touch Your Operations
A practical way to decide which operational tasks an AI agent can run unsupervised, which need a human check, and how to document the difference.
A Delegation Framework for Operations Leaders
Why delegation usually fails at the handoff, not the intent, and a four-level framework for deciding exactly how much authority to hand over.
Running a Retrospective That Actually Changes Anything
Why most incident retrospectives produce a document nobody reads and no real change, and a format that turns findings into tracked follow-through.
Operating Cadence: Weekly, Monthly and Quarterly Meeting Agendas
Build a weekly, monthly and quarterly operating cadence with agendas, inputs and outputs for each meeting, and cut the ones that don't earn their time.
Catching a Vendor Missing Its SLA Before It Costs You
How to track whether your B2B vendors are actually meeting the response and uptime commitments in their contracts, without manually checking each one.