It is the last week of the quarter. Priya has 58 accounts. Four of them have QBRs this week. She opened her laptop at 7am and it is now 11am and she has not spoken to a single customer. She has been pulling usage data from Amplitude, copying it into a slide template, writing context sentences she will revise three times, and chasing a number from the data team that was supposed to arrive yesterday.
The QBR itself takes 45 minutes. The prep took nine hours across three days. And this week she has four of them.
Nobody told Priya that pulling data from four different tools and reformatting it into slides was her job description. But here she is. And across every CS team we work with, the story is the same.
Where the 11 hours actually go
We tracked QBR prep time across accounts on our platform in Q1 2026. The average came out to 11.2 hours per CSM per week during peak QBR periods. The breakdown across a four-account QBR week looks like this: 4.5 hours pulling data from CRM, product analytics, billing, and support tools; 2.5 hours formatting slides; 2 hours writing narrative context; 1.2 hours chasing missing numbers; 0.8 hours in internal review loops.
The largest single category is data gathering — not because the data does not exist, but because it exists in four different places and nobody automated the assembly. The second largest is slide formatting: moving numbers into a template that looks the same every quarter. Both are entirely automatable. The only genuinely irreplaceable part is the 2 hours of narrative writing — the CSM's judgment about what the numbers mean for this specific customer.
"Preparing MBRs used to take up the entire last week of the month, but now it is down to just 2 minutes per customer. The AI gives us everything we need."
Sridhar Kowtal, Head of Customer Success · LimeChat
The cost nobody is calculating
Eleven hours of prep per CSM per week does not sound catastrophic until you do the math at team scale.
Those 572 hours are distributed invisibly across evenings and early mornings. The other cost is quality: when prep takes nine hours, the tenth hour is the call itself, and by then the CSM is running on fumes. The strategic conversation gets compressed into whatever time is left after the slides are finished.
What should never have been manual
The data gathering problem
A CSM running a QBR for a mid-market SaaS account pulls data from at least four tools: CRM for relationship history, product analytics for usage, billing for MRR trajectory, and support for open tickets. None of these talk to each other. The CSM is the integration layer. That is 4.5 hours of work that is entirely automatable and that CSMs do every single week.
The formatting problem
The slide template exists. The numbers change every quarter. The work is copying the numbers into the right cells, adjusting the charts, making sure nothing is stale. This is clerical work. It takes 2.5 hours because it is done manually, account by account, every time.
The narrative problem
Writing the context for each slide takes time because the CSM has to remember what happened on the last three calls, check their notes, and synthesize. If a system already had that synthesis ready, the CSM's job becomes editing rather than building from scratch. That collapses two hours to twenty minutes.
RetainSure generates the full QBR draft in two minutes.
Data pulled, slides structured, narrative written. The CSM edits, adds judgment, and walks in ready for the conversation.
What happens to the time you get back
When prep drops from 11 hours to under one hour, the freed time does not automatically flow into better customer conversations. That shift requires intent. The highest-return use of recovered QBR prep time is proactive account engagement: reaching out to accounts before a signal fires rather than after. A CSM with nine extra hours per week can read every account once, identify the three or four that need attention before the health score moves, and start the conversation while there is still time to change the outcome.
The second highest-return use is the strategic conversation inside the QBR itself. When a CSM walks in having spent twenty minutes reviewing a pre-built brief rather than nine hours building the deck, they walk in thinking about the customer. They know what to say when the VP mentions the vendor consolidation review. The meeting becomes what it was supposed to be.