Key Takeaways
- Most QBRs are stitched together the night before. The CSM pulls usage from the analytics tool at 9 PM, asks the AE for talk-track at 10 PM, copies last quarter's deck and edits the title. The customer can tell. The QBR becomes a status update instead of a strategy meeting.
- A QBR is supposed to be a renewal conversation in disguise. It exists to align the customer's executive sponsor with the value being delivered, surface what's working, surface what's broken, and set the expansion path. None of that survives a 90-minute Sunday-night scramble.
- An AI coworker can assemble the entire QBR pack two weeks before the meeting. Pull the success metrics from the kickoff document. Populate them with real numbers from the product database, Stripe, and HubSpot. Pull customer quotes from the last 90 days of calls and emails. Identify the expansion opportunity from usage patterns. Output a draft deck the CSM and AE review with two weeks to spare.
- The conversation in the room becomes different. Both sides walk in with the same data. The exec sponsor doesn't have to ask "what about X" because X is already on slide 4. The expansion proposal is anchored to evidence. The renewal conversation has already started two weeks ago, and the meeting is where it lands.
- This is not "automate the QBR." This is "give the QBR back to the humans." The deck assembly is mechanical. The conversation is human. The AI does the mechanical part so the humans do the part only they can do.
The short version
A Quarterly Business Review fails for a predictable reason. The CSM and AE responsible for it have spent the quarter doing other work. The data they need lives in five tools they don't open daily. The success metrics agreed at kickoff live in a Notion page nobody updated. The customer's executive sponsor has expectations the CSM has not seen written down in months. The deck gets built from memory, the meeting gets through it, and the renewal happens or doesn't on momentum that has nothing to do with the meeting.
The fix is to assemble the QBR pack two weeks before the meeting, with real data and a draft of the conversation. That assembly is exactly the kind of cross-tool work an AI coworker does well: pull from the product database, Stripe, HubSpot, Granola, Gmail, Notion, and the original kickoff doc; populate a deck template; flag risks and opportunities. The CSM and AE review with time to react. The meeting becomes a strategy session, not a slide tour.
This is the workflow.
What a QBR is for
There are three honest reasons a QBR exists:
- Re-anchor the customer's executive sponsor on value delivered. The sponsor is busy. They saw the platform get rolled out, then they didn't think about it. The QBR is the meeting that reminds them why they signed and shows the data.
- Surface what's not working before it shows up in churn. A customer who is unhappy in October will not renew in January, but they will not say so in October. They will sit through the QBR with polite questions and quietly stop responding by November. The QBR is a forced conversation that catches the unhappiness in time to fix it.
- Open the expansion conversation. A growing usage curve, a power-user pattern in a new department, a feature limit being hit, all are expansion signals. The QBR is the right context to surface them. Not as a sales pitch. As "you might want this; here's what it would cost."
A QBR that doesn't do those three things is a status update, and status updates do not need to be 60 minutes.
What goes wrong without an AI coworker
Pick a typical CSM-AE pair, owning 30 enterprise customers, with a QBR cadence of one per customer per quarter. That's about 2-3 QBRs per week.
The CSM week before each QBR:
- Monday: realize the QBR is next Wednesday. Promise to start tomorrow.
- Tuesday: get pulled into a customer escalation. Promise to start tomorrow.
- Wednesday: check the analytics tool. Realize you don't have admin access to that customer's tenant. File a request.
- Thursday: get the access. Pull the basic active-user count. Note that it's "down a bit" without being precise.
- Friday: ask the AE for the commercial context. AE says "I'll send something over the weekend."
- Saturday: receive a one-paragraph note from the AE.
- Sunday 9 PM: open the deck template, copy from last quarter, edit the title, populate three slides with the numbers from Thursday, write talking points for two slides, send to the AE for review.
- Monday 8 AM: AE has not reviewed. Send slide deck anyway.
- Wednesday 2 PM: the meeting.
The deck is fine. The conversation is shallow. The customer's exec sponsor asks one question that the CSM cannot answer ("how does our usage compare to similar customers?") and the meeting ends with "we'll get back to you." The renewal is unchanged from where it was before the meeting, which means it is still not won.
This is the failure mode. It is the dominant one.
What the AI-coworker version looks like
The CSM-AE pair set up the QBR cron once. It runs forever. Two weeks before any QBR scheduled in the calendar, this fires:
@Viktor 14 days before any meeting in the assigned CSM's calendar with title
matching "QBR" or "Quarterly":
For the customer associated with the meeting (resolve via the Google Calendar
attendee email domain to a HubSpot company record):
1. Pull the original kickoff document from Notion (search the customer's
project folder for "kickoff" or "success criteria"). Extract the agreed
success metrics and the executive sponsor's stated goals.
2. For each success metric, pull the actual current value from the relevant
source:
- Active users, feature adoption, time-to-value: from the product
database via PostHog or the analytics warehouse
- Revenue impact metrics (deals influenced, cycle time, etc.): from
HubSpot or Salesforce reports filtered to this customer
- Internal efficiency metrics: from Slack or Linear if those were tied
to the kickoff goals
3. For each metric, calculate the change vs. the prior quarter and vs.
the original baseline (when they signed).
4. Pull the last 90 days of:
- Granola call transcripts tagged with this customer
- Gmail threads with anyone at the customer's domain
- Pylon tickets opened by anyone at the customer's domain
- Slack messages in any shared channel with this customer
5. Extract the 5 strongest verbatim quotes from those sources that capture
the customer's experience. Attribute each (role, channel, date).
6. Identify the executive sponsor's likely top question based on the
patterns in their last 5 emails or calls. (Common patterns: "are we
getting the ROI we expected", "is the team using it", "what's next
for us", "how does this compare to what we were doing before").
7. Identify the expansion opportunity if the data supports one:
- Usage approaching plan limits (>70%)
- Power-user pattern in a new department
- Feature requests that exist in our roadmap or are already shipped
- Cross-sell to a sister product if applicable
8. Output a draft deck (Google Slides) in the customer's QBR folder with
this structure (10 slides max):
1. Title slide (customer name, quarter, date, attendees)
2. The kickoff goals we agreed (verbatim from kickoff doc)
3. How we tracked against each goal (4 metrics, prior quarter vs. now
vs. baseline)
4. What worked (3 wins, with the actual data behind each)
5. What's noisy (1-2 risks or friction points, with verbatim customer
quotes)
6. Customer voice (3 quotes from the last 90 days)
7. What's next on our roadmap they should know about (2-3 items)
8. Where we see the next growth (the expansion proposal, if data supports
one; otherwise replace with "areas to invest in for next quarter")
9. Open questions for them
10. Recap and asks
9. Add speaker notes per slide with the talking points the CSM should hit.
10. Post a link in the assigned CSM's DM and in the deal's Slack channel
(#cs-{{ customer_slug }}) with a checklist of 5 things to verify and a
"request feedback" button to ping the AE.That is the cron. From the rep's perspective: 14 days before any QBR, a complete deck and talking-point pack lands in their channel. They review for 30-45 minutes, edit the parts that matter, ping the AE for the commercial slides, finalize, share with the customer 48 hours before the meeting.
The CSM week before the QBR now looks like:
- Monday two weeks out: receive the auto-draft. Spend 30 minutes reading.
- Tuesday: send the AE the draft and ask for the commercial slide refinement.
- Wednesday: meet with the AE for 20 minutes to align on the expansion pitch.
- Friday: small edits. Send the deck to the customer's exec sponsor with a 3-paragraph framing email.
- Wednesday meeting: walk in already aligned with the customer. The conversation is strategic.
The hours saved are real. The win that matters is upstream of hours: the deck is correct.
What the deck actually looks like, slide by slide
Here is the structure we recommend, generated from the cron above:
Slide 1: Title. Customer name, "Quarterly Business Review," quarter and year, names of attendees on both sides. Boring. Required.
Slide 2: The goals we agreed at kickoff. Verbatim from the kickoff doc. The exec sponsor said something specific eight months ago. Show them you remember. This single slide is the difference between a generic meeting and a personalized one.
Slide 3: How we tracked against each goal. A 4-row table. Goal, baseline (when we started), last quarter, this quarter, change. Color the changes (green up, red down, yellow flat). The exec sponsor reads this and knows whether the answer is "yes we delivered" or "no, here's what happened."
Slide 4: What worked. Three wins with the actual data behind each. Not "we improved efficiency." Specifically: "in March, the support team went from 3.2 minute average ticket triage to 1.1 minutes after enabling the auto-context workflow. That's a 65% drop." Numbers, not adjectives.
Slide 5: What's noisy. This is the slide most CSMs leave out, which is exactly why most QBRs fail to surface unhappiness. Two risks or friction points with verbatim customer quotes from the last quarter. Examples: "in the April support ticket, your team wrote: 'we still cannot get the integration to handle our European entity, this has been three months.' Here's the status." Honest. Painful. Builds trust.
Slide 6: Customer voice. Three direct quotes from the last 90 days, attributed to specific people (with their consent). Not survey averages. Real sentences. This is the slide the exec sponsor remembers.
Slide 7: What's next on our roadmap. Two or three items we're shipping next quarter that this customer cares about. Anchored to the customer's stated needs, not to our marketing-page features.
Slide 8: Where we see the next growth. The expansion slide. Specific. "Your sales team has 18 of the 25 seats active. The seven inactive ones are people who joined in the last 60 days but didn't get onboarded. We propose: re-onboard those seven and discuss adding 10 more seats next quarter to cover the new hires the VP of Sales mentioned in the March call." Evidence, proposal, what changes for them. Not a price slide; a value slide.
Slide 9: Open questions for them. Three questions you actually want answered. "Has the new VP of Customer Success started? When can we meet them? Is there a board update coming we should be aware of?" Real questions move the relationship forward.
Slide 10: Recap and asks. What we're doing, what we're asking them to do, dates. The CSM owns the close.
10 slides. Specific. Honest. The customer leaves the meeting having had a real conversation.
What the cron does NOT do
This is critical. The cron does not:
- Auto-send the deck to the customer. Drafts only. The CSM and AE review and send.
- Make the renewal commitment. The data informs; the human commits.
- Replace the AE on the commercial slides. The AE owns slide 8.
- Replace customer interviewing. The cron uses what was already collected. New customer questions still happen between QBRs.
- Decide which customers get a QBR. The cadence is a CS leadership decision; the cron just runs against the calendar.
It does not turn a QBR into an automated process. It assembles the input pack and the draft deliverable. The conversation is human, the proposal is human, the relationship is human.
What this changes for the AE
The AE side of the QBR usually shows up at slide 8 (expansion) and slide 10 (close). With the cron, the AE walks in with:
- The actual usage data that supports the expansion proposal
- The verbatim quotes that show the customer's appetite
- A draft expansion proposal anchored to the data
- The CSM's review notes
The AE used to have a 20-minute pre-call to figure out "what should I pitch them?" Now they have a 5-minute review to check the proposal makes sense and adjust if needed. The pitch is sharper because it's built from evidence, not from a default expansion playbook.
Some AEs are skeptical of this at first. The framing that lands: "the data isn't pitching for you. It's letting you pitch the right thing instead of the obvious thing."
What this looks like at three scales
A 5-customer enterprise team. One CSM, a head of CS, and an AE per customer. The QBR cron runs with high attention from each rep. The deck quality matches what an enterprise customer expects. The first quarter, the team finds two expansion paths they would have missed.
A 50-customer mid-market team. Three CSMs and three AEs. The QBR cron is the difference between QBRs happening on time and QBRs being skipped. Renewal predictability improves within one quarter because every customer gets the same deck rigor.
A 500-customer commercial team. Five CSMs, supplementary digital touch points. QBRs at this scale are usually 30 minutes, not 60, and the cron runs a smaller deck (5-6 slides). The payoff is enormous because the only path to QBRs at this scale is automated assembly.
The kickoff document as the foundation
A QBR cron is only as good as the kickoff document it reads from. If your kickoff Notion page says "make the team more productive," the QBR cannot measure against that. If it says "reduce monthly support ticket volume by 30% by end of Q2 and increase active users from 12 to 30 by end of Q3," the QBR can measure exactly.
Implication: the cron forces a discipline. Teams that adopt it find their kickoff documents need to be tightened. That's a feature, not a bug. The kickoff doc is the foundation for the entire CS relationship; better kickoffs mean better QBRs mean better renewals.
We recommend a kickoff template with these mandatory fields:
- Executive sponsor name, role, what they care about (one paragraph)
- 3-5 success metrics, each with: name, baseline, target, source-of-truth
- Top 3 use cases the customer signed for, in priority order
- Risks the customer's team raised
- Decision criteria for renewal (what would success look like at month 12?)
A 60-minute kickoff with these fields filled honestly is worth more than a 4-hour kickoff that produces vague goals. The cron reads from this doc forever.
Safety and approval
QBR is customer-facing work. Every artifact is reviewed by a human before it touches the customer.
Hard rules:
- No deck shared with the customer auto-magically. The cron drafts. The CSM finalizes and shares.
- No commitments made in the deck that haven't been reviewed by the AE. The expansion slide especially is reviewed before any customer sees it.
- No customer quote shared without provenance. Every quote in the deck has a source link (call timestamp, ticket ID, email date) so the CSM can verify before sharing.
- Internal-only by default. The deck and all the supporting analysis live in the team's "Drafts" folder until the CSM moves the final version to "Customer-shared." This separation prevents the Air Canada bereavement-refund class of failure where AI output reaches a customer surface unchecked.
- The cron is reviewed quarterly. As the customer relationship evolves, the prompt should evolve. Add or drop metrics, update the executive-sponsor pattern, refine the expansion logic.
Frequently Asked Questions
Will the customer notice the deck is AI-assembled?
Only if it's bad. A deck that opens with verbatim quotes from their own team, real numbers from their actual usage, and a specific expansion proposal anchored to the data, is a better deck than 80% of human-built QBR decks. The AI assembled it; the human reviewed and shaped it. The customer sees the result.
What if our customers don't agree to share their data?
The cron only reads data that already exists in our systems (product database for usage of our product, our CRM, our ticketing tool, our call transcripts of meetings we already had). There's no separate data ask. If a customer has restricted certain integrations, the cron skips those.
Does this work for SMB at lower contract values?
Yes, with a smaller deck (5-6 slides) and a shorter cadence (semi-annual or annual). The cron pattern is the same; the depth is calibrated to the customer's value.
Can multiple stakeholders on our side review the deck?
Yes. The cron posts in the customer's deal channel and DMs the CSM. The AE, the manager, anyone in the channel can leave comments. The CSM owns the final.
What if the data shows the customer is unhappy and the meeting will go badly?
The cron surfaces it 14 days early. That's the value. A QBR where the unhappiness is acknowledged on slide 5 with a credible plan is far better than a QBR where the unhappiness comes out as a surprise question. The cron creates time to fix the underlying issue or at least to walk in with a plan.
How long until we see the renewal-rate improvement?
The first cohort of QBRs run with the cron will show measurably better customer feedback (post-meeting NPS or pulse) within one quarter. Renewal-rate impact is visible within 2-3 quarters once the cohort cycles through. The earlier indicator is the meeting quality itself; ask the customer "how was that compared to last QBR?" after the first one.
Does this work for non-CSM customer-facing roles (account managers, partner managers)?
Yes. The cron pattern adapts to any quarterly business review. Partner reviews, channel reviews, internal stakeholder reviews. The data sources change; the structure is the same.
