Prepping a QBR With AI: The 6 Slides Clients Actually Care About

When a CSM at a 70-person SaaS told me she spent 8-12 hours prepping a single QBR, I asked her how many of those slides the client opened twice. She paused and said "maybe four." Eight hours of CSM time per QBR, four slides of payoff. That ratio is what AI fixes — not the slide design, the prep loop.

Why are QBR decks so bloated?

Because CSMs are anxious about looking unprepared. The 28-slide deck is defensive: agenda, logo, "our journey together" timeline, every feature shipped, every ticket closed, NPS chart, ROI calculator, roadmap teaser, ask slide, thank-you. Each individual slide makes sense to someone. The aggregate makes the meeting fight against itself.

Definition: QBR — Quarterly Business Review, a recurring meeting between vendor and customer to review outcomes against commitments, surface risk and expansion topics, and align on the next quarter's plan.

The client sits through the deck politely, asks two questions about slide 11, makes a decision about slide 19 that the CSM didn't realize was the point, and leaves. Half the deck never gets revisited. The other half could have been an email.

What do clients actually care about?

Six things. I've watched 50+ QBRs across B2B SMB and Enterprise; the same six topics drive 90% of the actual decisions. Every other slide is supporting evidence at best, filler at worst.

The six are: outcomes against commitments, usage and adoption reality, risk surface, expansion opportunities, ask of the client, next-quarter plan.

That's the deck. Six slides. The CSM brings supporting data in a backup section, opens it only if the client asks. The meeting becomes a conversation instead of a presentation.

The 6-slide QBR template

Each slide has a single owner question and a default AI prompt for the first draft. The CSM rewrites for tone and adds context the AI can't see.

Slide 1 — Outcomes vs commitments

What we agreed at last QBR, what actually happened. Honest accounting, including misses. Owner question: "Did we do what we said we'd do?"

Definition: Outcome commitment — a specific, time-bounded result the vendor and customer agreed to track between QBRs; serves as the contract for the next QBR's accountability slide.

AI prompt: "Pull the commitments documented at the [DATE] QBR. For each, summarize the actual outcome in 1 sentence with a status flag (delivered / partial / missed). For misses, note the documented reason if one exists."

Slide 2 — Usage and adoption reality

Not a token chart. The number of users actively using the workflows you sold them, broken down by department or team. Owner question: "Is the product actually doing work for them?"

AI prompt: "From product telemetry over the last 90 days, summarize: active users by team, % of seats used at least weekly, top 3 features by frequency, any team that started or stopped using the product. Highlight changes vs prior quarter."

Slide 3 — Risk surface

The honest list of what could go wrong in the next quarter. Champion changes, integration concerns, competitive pressure, internal re-orgs the customer mentioned. Owner question: "What should we be worried about together?"

AI prompt: "Read the last 90 days of support tickets, CSM notes, and NPS comments for [ACCOUNT]. Identify and rank by severity the top 3-5 risks that could affect renewal. For each, suggest one mitigation the CSM and customer could agree on."

Slide 4 — Expansion opportunities

Not a sales pitch. Specific opportunities surfaced from the customer's own usage and conversations. Owner question: "Where could we do more?"

AI prompt: "Based on usage patterns, support ticket topics, and meeting notes from [ACCOUNT] over 90 days, identify 2-3 expansion opportunities (new team, adjacent use case, higher tier). For each, frame as the customer's problem first, not our product feature."

Slide 5 — Ask of the client

What we need them to do or decide. Reference call, case study, executive sponsor introduction, integration sign-off, decision on a tier change. Owner question: "What do we need from you?"

This is the slide most QBRs skip — and skipping it is why customers feel QBRs are vendor-driven. The ask makes it a peer meeting.

Slide 6 — Next-quarter plan

3-5 commitments back. What we'll deliver, by when, measurable. This becomes Slide 1 of the next QBR. The deck closes the loop on itself.

AI prompt: "Draft 3-5 commitments for the next quarter based on: (a) unresolved items from this QBR, (b) the expansion opportunities surfaced, (c) the risk mitigations agreed. Each commitment must be specific, time-bounded, and measurable."

How the AI workflow actually runs

Three phases, one hour total. The CSM owns the output; the AI does the heavy data pulling.

Phase 1 — data pull (15 minutes). AI agent or scripted pull from product telemetry, CRM, support system, and NPS responses for the account. Output: a structured JSON or markdown summary the LLM can reason over.

Phase 2 — first-draft slides (20 minutes). AI runs the 6 slide prompts against the data pull. Output: bullet-point first drafts for each of the 6 slides plus suggested commitments.

Phase 3 — CSM rewrite (25 minutes). The CSM adds relationship context, edits tone, removes anything that misreads the account, and writes Slide 5 (the ask) entirely by hand. The CSM is doing what only the CSM can do; the AI handled what shouldn't have been a human task.

Total: under an hour for a deck that used to take 8.

Copy/paste deck-prep template

Run this checklist before every QBR.

Account: [NAME]
QBR date: [DATE]
Prior QBR: [DATE]
CSM: [NAME]

AI data pull complete (Phase 1): [Y/N]
- Telemetry export: [LINK]
- Support tickets pulled (90d): [N]
- NPS responses pulled: [N]
- Meeting notes pulled: [Y/N]

First-draft slides generated (Phase 2): [Y/N]
- Slide 1 (Outcomes vs commitments): [draft ready]
- Slide 2 (Usage & adoption): [draft ready]
- Slide 3 (Risk surface): [draft ready]
- Slide 4 (Expansion opportunities): [draft ready]
- Slide 5 (Ask of client) — CSM WRITES THIS BY HAND: [done]
- Slide 6 (Next-quarter plan): [draft ready]

CSM review complete (Phase 3): [Y/N]
- Relationship context added: [Y]
- Anything misread by AI removed: [Y]
- Tone matches account voice: [Y]
- Backup slides (only opened if asked): [LIST]

Pre-send check:
- Commitments in Slide 6 are measurable: [Y/N]
- Slide 5 ask is specific and reasonable: [Y/N]
- Slide 3 includes at least one honest risk we own: [Y/N]

The Slide 3 honesty check is the one most CSMs fudge — and the one that builds the most trust when it's real.

Tool tip (Course for Business): The reason most CS teams don't run an AI-prepped QBR isn't the prompts — it's that nobody on the CS team has shipped any AI workflow yet, so the QBR draft feels like a leap. Our 6-week program installs the Augment, don't replace mindset by having every CSM ship their first AI automation in week 1; the QBR draft is a typical week-2 or week-3 build because the data is structured and the output is high-leverage. We've seen CSMs cut QBR prep from 8 hours to 50 minutes by the end of week 3. Walk through the program at https://course.aiadvisoryboard.me/business.

Team scan (what AI champions report after week 1)

• 1 AI champion per ~17 CSMs is enough; the QBR prompt set propagates fast once one CSM ships
• Adoption: CSM team converges on the 6-slide template by end of week 2
• Use case: QBR prep time drops from 6-10 hours to 45-90 minutes per account
• Saved time: a CSM with 12 quarterly QBRs gets back roughly 70-100 hours/quarter
• Quality lift: clients comment that the deck is "tighter" and meetings end with clearer commitments
• Common stumble: CSMs auto-accept the AI draft of Slide 5 (the ask); week-2 calibration forces hand-writing
• Champion role: 30-min weekly clinic where CSMs swap edge cases and improve prompts
• Failure mode caught: AI initially over-claimed on outcomes (Slide 1); reason-code field added to the prompt
• New behavior: backup slides get used less because the main 6 cover what clients actually ask
• Next-quarter unlock: same prompts adapt to mid-cycle check-ins and renewal prep

Micro-case (what changes after 7-14 days)

A 220-person B2B SaaS with 40 enterprise accounts ran QBRs that took 8 hours per account to prepare — roughly 320 CSM-hours per quarter across the team. They installed the 6-slide template plus the AI prep workflow in week 1 of an AI program. By week 3, the team's first batch of QBRs ran on the new format; prep time averaged 55 minutes per account. Two clients mentioned unprompted that the deck "felt sharper." More importantly, three QBRs surfaced expansion conversations from Slide 4 that the previous template structure had buried at slide 22 — two converted in the following 30 days. Annual recovered CSM time: roughly 800 hours. Cost to install: one week of prompt engineering and one champion's time. The token bill ran under €100/month for the entire team.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30-500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

Tool tip (Course for Business): The leap from "I should automate QBR prep" to "I actually ship the workflow" is where most CS teams stall — they read the article, agree it makes sense, and never write the first prompt. Shoulder-to-Shoulder hot seats in our 6-week program close that gap: week 2 or week 3 is the QBR-prep installation session, with a champion sitting next to the CSM live-building the data pull and the first slide draft on a real account. The next QBR uses the new workflow by default. Book a 30-min mapping call at https://course.aiadvisoryboard.me/business.

FAQ

What if the client expects the 28-slide deck and would feel short-changed by 6? Send the 6-slide deck for the meeting and a 1-page "supporting data" PDF as a follow-up — most clients prefer this structure once they experience it. If the client truly wants 28 slides, that's a signal about meeting culture, not a constraint on your QBR design.

Can we trust AI to draft Slide 3 (risk surface) accurately? For draft, yes — for sending, no. The CSM owns Slide 3 because the framing of risk requires relationship judgment the AI doesn't have. Use AI to surface the risk candidates from the data; rewrite each one in human language before sending.

Does this work for SMB accounts under €30k ARR or only enterprise? Especially well for SMB. Lower-ARR accounts don't get QBRs at all in many CS teams because the prep cost is uneconomic — the 50-minute version makes QBRs viable for the long tail, often turning silent SMB accounts into expansion conversations.

Should clients see the AI-generated drafts directly? No — always CSM-rewritten before client. Sending raw AI output to a customer in 2026 reads as a tell that you don't care enough to review. The CSM rewrite is what keeps the relationship intact.

What's the right cadence for changing the 6-slide template? Review the slide selection annually, not quarterly. Stability matters — if clients know what to expect, they prepare differently and the meetings get sharper. Change the prompts more often than the slides.

Conclusion

QBRs that took CSMs a workday now take an hour. The 6-slide template doesn't reduce the meeting — it sharpens it. Outcomes against commitments. Usage reality. Risk. Expansion. Ask. Plan. Everything else is backup material.

Pick your 6 slides. Wire the data pull this week. Run the first AI-prepped QBR next week.

If you want every employee to ship their first AI automation in five days — including QBR prep that recovers 6+ hours per account per quarter — book a 30-min call and we'll map your team's first week at https://course.aiadvisoryboard.me/business.