Written by Marijn Overvest | Reviewed by Sjoerd Goedhart | Fact Checked by Ruud Emonds | Our editorial policy

How Claude Prepares Your Supplier QBR in 15 Minutes

What a Good QBR Brief Actually Contains, and Why Most Teams Don't Produce One

A QBR (Quarterly Business Review) with a strategic supplier should be the most useful 60 minutes the procurement team has with that supplier in the quarter. In practice, most QBRs are a status update where the supplier presents how well they are doing and the procurement team listens. There is a gap, and the gap is in the preparation.

Most procurement teams find that isolated experiments with Claude only become a durable team capability when tool practice is paired with structured training. The AI Fundamentals for Procurement Teams program is built for exactly that transition, from individual curiosity to a procurement function that works differently.

A good QBR brief, the document the procurement lead walks in with, has five sections. Spend snapshot: where the supplier sits in the procurement team's total spend, growth or contraction trajectory, payment-term variance, currency or rate exposures. Performance scorecard: SLA attainment, delivery reliability, quality data, support responsiveness, against the agreed targets. Risk register: open risks, supplier financial signals, concentration risk, geopolitical or sustainability flags. Contract status: time-to-renewal, open commercial issues, scope changes pending, change-control requests outstanding. Strategic agenda: the three to five items the procurement team specifically wants to drive in this conversation, not the supplier's agenda.

Most procurement teams produce one or two of these sections, usually the spend snapshot and a light scorecard. The other three live in different systems, take an hour each to assemble manually, and never make it into the brief in time. The result is QBRs where the supplier drives the agenda because the procurement team didn't have one ready.

Claude collapses the preparation work to the point where all five sections are in the brief, every quarter, without it being a heroic effort by a senior category manager.

The 15-Minute Claude QBR Prep Workflow

The end-to-end workflow that procurement teams have settled into for Claude-prepped QBRs. Total time once the Project is set up: 15-20 minutes. Setup is a one-off afternoon.

Setup. Create a Claude Project per strategic supplier (or one Project per category if your portfolio is small). Upload: the master agreement, the most recent scorecard data, the previous QBR brief, the renewal calendar entry, and a short "about this supplier" note covering their role in your category strategy. Add a standing instruction: "This Project prepares QBR briefs for [Supplier X]. Always produce the five-section brief structure. Surface uncertainty rather than fabricate."

Step 1, current-quarter data drop. Drop in the quarter's spend transactions, the latest scorecard, any open risk items from the risk register, and any contract-related correspondence since the last QBR. Two minutes.

Step 2, generate the brief. Invoke: "Produce the Q[X] QBR brief for [Supplier X]. Use the five-section structure. Pull spend trajectory from the new transactions, performance from the scorecard, risks from the register, contract status from the agreement and correspondence, and propose three strategic agenda items based on what's emerged this quarter. Mark uncertainty." Five minutes for Claude to produce; three minutes for the procurement lead to review.

Step 3, refine the agenda items. The strategic agenda is the part that needs human judgement. Review Claude's three proposed items; usually two are obvious from the data and one is original. Refine, swap one if needed, decide which order to raise them in the meeting. Five minutes.

Step 4, finalise and share. Export the brief, share with the supplier-facing team members 24 hours before the QBR so everyone walks in aligned. The brief is the procurement team's agenda, not the supplier's. Two minutes.

The Five Sections of a Claude-Prepped QBR Brief

What each section actually contains, in the level of detail that makes the brief usable.

1. Spend snapshot

Quarterly spend with this supplier, comparison to same quarter last year, year-to-date vs. budget, currency split if relevant, payment-term realisation (are they being paid on agreed terms?), top three PO categories. The objective is to walk into the meeting with the same number the supplier will quote, plus one or two numbers the supplier will not have ready.

2. Performance scorecard

SLA attainment per service line, on-time delivery rate, quality rejection rate, ticket resolution time, NPS or satisfaction metric if measured. Show the trend, not just the current value, three quarters of data on each metric. Highlight any metric that breached the agreed threshold; this is where the QBR's accountability conversation happens.

3. Risk register

Open supplier risks from the procurement risk register, with the current mitigation status. New external signals: news flow on the supplier's financial health, leadership changes, M&A activity, regulatory issues. Concentration risk if this supplier has grown into a strategic dependency. Sustainability or ESG flags if relevant.

4. Contract status

Months to renewal, any auto-renewal clause and notice period. Open contractual items: change orders, scope expansions, pricing reviews scheduled, indexation triggers. Items the procurement team intends to raise this quarter that need contract negotiation. The renewal clock starts ticking 12 months out for strategic suppliers; the QBR is the place to keep both sides aligned on it.

5. Strategic agenda

Three items the procurement team wants to leave the meeting having addressed. Not five, not two, three. Examples: "Lock in the volume rebate for FY27 by end-of-quarter," "Resolve the open SLA gap on incident response or trigger the credit clause," "Get supplier commitment on the sustainability roadmap they presented six months ago." These are written as commitments to seek, not topics to discuss; the framing matters for what the meeting produces.

Worked Example: Building a QBR Brief for a Tier-1 IT Services Supplier

Walk-through for a real-feeling scenario. A procurement team prepping a QBR with a Tier-1 IT services supplier providing managed services, EUR 4M annual spend, three years into a five-year MSA, two service lines (managed infrastructure, application support).

Spend section, Claude pulls the quarter's transactions: EUR 1.05M, 7% above same quarter last year, 4% above plan, driven entirely by the application-support line. Payment terms 45 days; realisation 38 days (paying faster than agreed, finance flag for the team's working-capital conversation).

Performance section, Scorecard data shows infrastructure SLA at 99.4% (target 99.5%, marginal miss), application-support resolution time at 6.2 hours (target 4 hours, meaningful miss). Trend on application-support has worsened three quarters in a row. This is the QBR's accountability conversation.

Risk section, External signal flag: the supplier announced a 7% headcount reduction last month, focus on the application-support practice. Likely contributor to the SLA degradation. Concentration risk: this supplier now covers 22% of the team's IT spend, up from 15% three years ago. Worth a review at the category-strategy level.

Contract section, 22 months to renewal; auto-renewal clause with 90-day notice. Open commercial items: change order from Q2 still pending sign-off, EUR 180K scope. Pricing review scheduled for Q4 (indexation trigger, CPI-linked).

Strategic agenda, Three items proposed: (1) Get supplier commitment to remediate application-support SLA within the quarter, with credits if not; (2) Close out the open change order with revised pricing reflecting the volume growth; (3) Open the conversation on the renewal in 22 months, specifically whether to consolidate the two service lines under a unified rate card.

Total prep time start-to-finish: 18 minutes. The brief that previously the team would not have produced is now the meeting's anchor, and the supplier walks out with three commitments rather than three discussion topics. Supplier Relationship Management Course covers the broader QBR discipline this workflow plugs into.

The Data Inputs Claude Needs, and How to Keep Them Current

The workflow works because four data sources are kept current. If they are not, the brief degrades to whatever the procurement lead can remember off the top of their head.

Spend data. Monthly export from the ERP or P2P system, by supplier, with category code, gross amount, payment terms, and PO date. If your organisation already produces a monthly spend cube, drop the relevant supplier slice into the Project. If not, a monthly CSV export is enough; the data hygiene matters more than the tool sophistication.

Scorecard data. If the team runs a supplier scorecard, the quarterly update lives there. If the team does not run a scorecard, the QBR is the wrong place to start one, build the scorecard separately and feed it in. The single biggest failure mode of QBR prep is trying to invent the scorecard in the brief, with no historical baseline.

Contract and correspondence. The current contract should be in the Project from setup. Each QBR cycle, drop in the correspondence with the supplier since the last QBR, formal emails, change-order requests, escalations. Claude reads it and surfaces what's open.

External signals. Web-search-enabled summaries of news flow on the supplier, financial signals, leadership changes, sector signals. Claude pulls these on demand; the team can ask "surface any external signals about Supplier X in the last 90 days that would be relevant to a procurement QBR."

Making QBRs Decision-Driven, Not Just Data-Review

The point of the strategic agenda section is that QBRs produce decisions, not minutes. Three principles that procurement teams use to keep QBRs decision-driven.

Walk in with three things to close, not a list to discuss. The strategic agenda is written as commitments to seek. "Get supplier sign-off on the SLA credit clause this quarter" is a commitment; "discuss SLA performance" is theatre. The brief enforces the discipline.

Document the commitments in the brief itself, not in separate minutes. Add a section at the end of the brief: "Commitments agreed in QBR." Populate it during or immediately after the meeting. The same document that was the prep becomes the record. Next quarter's QBR opens with whether the previous commitments were kept.

Track commitment closure quarter-on-quarter. Strategic suppliers should close >80% of QBR commitments by the following QBR. Suppliers that consistently close less are showing a pattern, either the procurement team is asking for the wrong commitments or the supplier is not delivering. Both signals matter.

Embedding QBR Prep Into the Monthly Procurement Rhythm

QBRs are quarterly; the data they depend on is monthly. The realistic cadence.

• Month 1 of the quarter: data refresh in the Project (spend, scorecard). No QBR prep yet.
• Month 2: data refresh, plus a 30-minute mid-quarter check, run Claude against the data and flag anything emerging that the QBR will need to address.
• Month 3, week 1: finalise data drop, request external signals scan, draft the strategic agenda.
• Month 3, week 2: Claude generates the brief; procurement lead refines; circulate to internal team 24 hours before QBR.
• Month 3, week 3: QBR happens. Document commitments. Reset the cycle.

Teams that follow this rhythm produce briefs that improve quarter over quarter; the prompts get sharper, the data feeds get cleaner, the strategic agenda gets more pointed. This is the compounding return.

Common Mistakes that Make QBRs Feel Like Reporting Theatre

Letting the supplier set the agenda

The supplier shows up with a 30-slide deck and the meeting becomes a presentation. The fix: the procurement team's strategic agenda goes first, before the supplier's deck. The supplier's deck becomes context for the procurement team's three items, not the meeting itself.

Using the same brief template for every supplier tier

A Tier-1 strategic supplier and a Tier-3 operational supplier do not warrant the same prep depth. Reserve the full five-section brief for Tier-1 and Tier-2 strategic suppliers; for the rest, a one-page check-in is appropriate. Trying to apply the full discipline to every supplier exhausts the team and dilutes the value where it matters.

Generating the brief but not reading it

Claude produces a polished brief in fifteen minutes; the procurement lead skims it for five and walks in. Result: the brief is technically present, but the lead is not as prepared as the brief is. The brief is meant to inform the human; the human still needs to internalise it. Block 20 minutes of focused reading time, not just generation time.

Not tying the QBR back to the negotiation cycle

QBR commitments and renewal-cycle commitments should reinforce each other. The team's leverage in the renewal negotiation is partly built from the supplier's QBR commitment track record. Negotiation Course for Procurement Professionals covers how to systematically build that leverage across the supplier relationship cycle.

Frequently asked questions

How long does Claude QBR prep take?

Fifteen to twenty minutes with the scorecard and recent correspondence prepared.

Can Claude anticipate the supplier's arguments?

Based on prior QBR patterns and the performance data, yes, usually accurately.

How often should QBR prep happen?

Before every QBR, plus a monthly light-touch review between.