Back to blog Pillar 1 · Cluster 1.13

Vendor performance reviews that actually drive improvement.

Most reviews are theatre — the vendor presents, the buyer accepts. Here's how to run one that produces decisions instead of slide decks.

JR

Julian Robida

Research Lead · Aventario · 8 min read · 8 May 2026

A vendor performance review (often a Quarterly Business Review or QBR) is the structured forum where buyer and vendor jointly assess delivery against the contract. Most reviews fail because the vendor sets the agenda, the buyer accepts vendor-reported performance, and no decisions emerge. A review that drives improvement follows a buyer-set agenda, opens with independently-verified performance data, surfaces structural patterns rather than incident reports, and ends with named decisions, not next-steps.

The pattern that doesn't work.

The default vendor performance review runs like this. Calendar invitation lands two weeks in advance. The vendor prepares a 30–50 slide deck covering the last quarter's delivery. The buyer attends. The vendor presents. The deck closes with a list of upcoming initiatives and a request for feedback. Buyer thanks the vendor. Meeting ends. Nothing changes.

The fundamental problem: the vendor controlled the agenda, the data, and the framing. The buyer's role was reactive. The forum produced a report, not a decision.

This pattern accounts for the majority of vendor performance reviews we observe. It is not because the people involved are doing a bad job. It is because the structural setup of the forum makes any other outcome difficult.

The pattern that does work.

Five structural changes:

1. Buyer-set agenda.

The agenda is set by the buyer, not the vendor. It opens with the buyer's view of vendor performance — independently verified — not the vendor's. The vendor's slides supplement the buyer's view; they do not lead it.

2. Independently-verified data.

The performance data driving the discussion comes from the buyer's own systems — ticket-level data, telemetry, finance reconciliation. The vendor sees the data the buyer is using before the meeting and has the chance to reconcile their view. When the views diverge, the discussion focuses on the divergence, not on which version is correct.

3. Patterns over incidents.

The review focuses on structural patterns — trend over six months, repeat incident categories, cumulative change-request impact, scorecard trajectory — not on individual incidents. Individual incidents belong at operational governance (weekly). The performance review is for the patterns that operational governance is too close to detect.

4. Named decisions.

Every issue surfaced ends in a named decision: continue as-is, mitigation action with owner and timeline, structural change to scope or terms, or escalation. "Take an action" is not a decision. "Tim agrees to deliver a remediation plan by 2026-06-30, reviewed at the next QBR" is.

5. Structured documentation.

The meeting produces a documented record of (a) performance against scorecard, (b) decisions taken, (c) actions assigned with owners and dates, (d) open items rolling forward. This documentation is the source of truth for the next review and the basis for any commercial or governance escalation.

The standard agenda.

For a strategic-vendor quarterly review:

  1. Performance scorecard review (20 min). Buyer presents independently-verified scorecard. Vendor responds with their view. Discussion focuses on variance and trajectory.
  2. Run-rate and commercial review (15 min). Run-rate against baseline; cumulative CR impact; renewal pipeline status; benchmark variance if recent data exists.
  3. Risk register review (15 min). All seven categories. Active mitigations. Any escalations to be promoted to strategic governance.
  4. Open actions and decisions from last review (10 min). Status of every action; closure or rollforward; escalation if needed.
  5. Forward-looking discussion (20 min). Upcoming changes on either side. Roadmap alignment. New scope discussions. Structural commercial items.
  6. Decisions and actions (10 min). Explicit close: what was decided, who owns each action, when it's due, when it will be reviewed.

The roles in the room.

For a tier-1 strategic vendor, the room contains:

Both sides should have decision authority in the room. Reviews where the vendor's account team can commit to actions but the buyer's representatives cannot — or vice versa — degenerate quickly into "we'll need to check with [absent senior person]."

The failure modes.

Vendor pitch.

The vendor uses the forum to demonstrate new capabilities and propose new services. Common when the buyer doesn't set the agenda actively. The forum becomes sales-led; performance discussion is squeezed.

Status report.

The forum becomes a one-way information flow with no decisions. Status reports without decisions are not reviews — they are emails that take an hour to send.

Performance theatre.

Vendor presents green; buyer accepts; both parties agree the relationship is healthy; neither acknowledges the issues that operational teams know about. Often the result of vendor-reported data not being verified.

Escalation funnel.

The forum becomes the dumping ground for every unresolved operational issue, with no time for structural discussion. Symptom of operational governance not functioning at Tier 1 — issues that should have closed there are escalating to Tier 2 by default.

How often.

Performance reviews — at the formal, structured level described here — quarterly for tier-1 strategic vendors. Lighter monthly reviews at Tier 2 of the three-tier governance model handle the running performance discussion. The quarterly review is for the patterns the monthly cadence is too close to detect.

For tier-2 (preferred) vendors, semi-annual formal review. For tactical vendors, annual review or as triggered by performance issues.

The Aventario perspective.

"The single biggest change we make to client review forums is moving the data ownership. The buyer brings the scorecard; the vendor responds to it. That one structural change transforms the forum from a vendor pitch into a working session. Everything else follows from there."

— Markus Jaksch, COO, Aventario

FAQ.

What is a vendor QBR?

Quarterly Business Review — the structured forum where buyer and vendor jointly assess delivery against the contract. The most common formal performance-review cadence for tier-1 strategic vendors.

Who should chair the vendor review?

The buyer's service owner, with vendor management presenting the performance data and finance/risk providing their respective views. The vendor's account director is the senior vendor-side participant but does not chair.

How long should a vendor performance review run?

90 minutes is the typical structure: 20 minutes scorecard, 15 commercial, 15 risk, 10 open actions, 20 forward-looking, 10 decisions. Longer than 90 minutes usually indicates the forum is doing work that should sit elsewhere.

Let’s talk.