All posts
L3 Maturitymeeting-intelligence 6 min read

Playbook: AI-Generated QBR Decks for Scale

Stop wasting 6 hours on QBR prep. Learn how to use LLMs and CRM data to automate 80% of your deck creation, shifting CSMs from authors to editors.

Run the playbook

AI-generated QBR decks (L3)

Pull product usage + support + CSM notes → LLM generates a draft QBR deck. CSM edits, does not author.

Why this matters

The average Customer Success Manager (CSM) spends 4 to 6 hours preparing for a single Quarterly Business Review (QBR). They spend 80% of that time "data mining"—digging through Mixpanel for usage stats, Zendesk for ticket trends, and Salesforce for account notes—and only 20% of the time actually strategizing on how to grow the account.

When QBR prep is this manual, CSMs naturally avoid them. They prioritize "squeaky wheel" fire-fighting over proactive business reviews, resulting in low QBR coverage across the book of business. For a company at $50M ARR, a 10% drop in QBR completion often correlates directly with a 2-3% increase in gross churn.

By moving to an AI-generated QBR workflow (Level 3 Maturity), you flip the script. You shift the CSM from "Author" to "Editor." The goal is to reduce prep time by 75%—down to 45 minutes—allowing your team to double their QBR volume without adding headcount.

How it works

Step 1: Map data sources and create schema

The AI is only as good as the context you feed it. Your CS Ops lead needs to define the "Source of Truth" for four specific pillars: Adoption, Support, Value, and Risk.

  • Product Analytics: Pull DAU/MAU or feature-specific "stickiness" from Mixpanel, Pendo, or directly from Snowflake.
  • Support Health: Pull ticket volume and CSAT from Zendesk or Salesforce Service Cloud.
  • Qualitative Context: Use a tool like Momentum.io or Granola to sync meeting notes directly into Salesforce "Account Notes" fields.
  • The Output: Develop a clean SQL query or CSV export that aggregates this into a single row per customer.

Pro Tip: Don't dump 50 metrics. Pick the "Vital 5" (e.g., license utilization, open bugs, last login, ROI metric, and renewal date). Noise leads to hallucination.

Step 2: Build the LLM generation prompt

You are moving from a blank PowerPoint to a fixed schema. Use an LLM like Claude 3.5 Sonnet (widely regarded for better data reasoning) via API.

Your prompt must act as a "Strategic CS Executive." Use "Few-Shot" prompting—provide the LLM with two examples of a "Perfect" slide.

  • Example Prompt Fragment: "Based on the {{usage_data}} showing a 20% drop in seat utilization, write a 'Value Realization' slide. Focus on the cost-per-active-user and suggest three re-engagement tactics. Tone: Consultative, not accusatory."

Step 3: Automate the draft assembly pipeline

Connect your data to the LLM using Zapier or Make.com.

  1. Trigger: A CSM checks a box in Salesforce labeled "Request AI QBR."
  2. Action: Zapier pulls the data from Step 1 and sends it to the Claude/OpenAI API.
  3. Assembly: Use the Google Slides API or a tool like Plus AI to inject the text into a branded template.

Production Note: If you are processing a high volume of accounts, build in a 30-second "Sleep" step in Zapier to avoid API rate limits.

Step 4: Human review and narrative layer

This is where the CSM earns their commission. The AI provides the "what," but the CSM provides the "why."

  • Verification: The CSM checks if a usage drop was actually a seasonal holiday or a migration.
  • Personalization: Add 2-3 bullets regarding the customer’s specific Q1 goals that weren't in the CRM.
  • The Narrative: Record a 2-minute Loom video embedded in the deck to send to the customer's executive sponsor. This increases executive attendance because they can consume the "highlights" before the meeting starts.

Step 5: Measure outcomes and iterate

Tag every QBR in your CRM as "AI-Generated" vs. "Manual."

  • Compare Time to Prep and Executive Attendance Rate.
  • Benchmark: Aim for a 50% reduction in prep time by the end of Month 2.
  • SQL Audit: Run a monthly query: SELECT drafting_method, avg(retention_rate) FROM qbr_table GROUP BY 1. If AI-drafted accounts have lower retention, your "Vital 5" metrics in Step 1 are likely the wrong ones.

Tools you need

  • Data Warehouse/Analytics: Snowflake, Mixpanel, or Pendo.
  • Meeting Intelligence: Granola or Fathom (to get high-quality qualitative notes into the CRM).
  • LLM API: Claude 3.5 Sonnet (Anthropic) or GPT-4o (OpenAI).
  • Orchestration: Zapier, Make.com, or Lindy.ai for more complex agents.
  • Presentation: Google Slides API, Plus AI, or Gamma.

KPIs to track

  • QBR Prep Time: Target < 60 minutes.
  • QBR Volume: Target 100% coverage of Tier 1 and Tier 2 accounts.
  • Exec Attendance: Percentage of meetings where a Director+ level stakeholder is present.
  • CSM Sentiment: Qualitative feedback on whether the tool reduces "grunt work."

Common pitfalls

  • The "Wall of Text": AI loves to be wordy. Force your prompt to use "Max 15 words per bullet point."
  • Hallucinating Metrics: If the LLM doesn't have a specific data point (like "ROI Dollars"), it might make one up. Use system instructions that say: "If data is missing, leave the field as [NEEDS INPUT]."
  • Ignoring Seasonality: AI sees a 10% drop in usage in December as a risk; a human knows it's a holiday. Always keep the human "Editor" in the loop.

When to graduate to the next level

You are ready for Level 4 (Autonomous Insights) when:

  1. Your AI doesn't just draft the deck; it proactively prompts the CSM to schedule a QBR because it detected a specific data anomaly.
  2. You integrate Clay to pull external news about the customer (e.g., a recent acquisition) to automatically add a "Market Context" slide.
  3. The AI suggests specific "Expansion Plays" based on which features the customer is not using compared to your most successful clients.
qbrdeckscsm

Ready to ship it? Open the playbook

AI-generated QBR decks (L3)

Step-by-step instructions, the tools to use, and the KPIs to watch — already wired into the Revenue AI Strategy workspace.

Open playbook