← Back to use cases
Customer SuccessUpdated 2026-04-30

QBR auto | pack

One deck per account, drafted from product analytics plus support plus CRM plus billing. The CSM reviews, edits, and walks into the QBR ready.

The sixty-hour QBR cycle

Practitioner data on QBR prep is consistent. CSMs spend one to four hours per QBR depending on the account size and the data they have to chase. For a thirty-account book, that compounds to roughly sixty hours per cycle, which is one and a half weeks of a CSM's time spent assembling decks rather than talking to customers. The QBR auto-pack collapses that to fifteen minutes per account, which is the time it takes the CSM to read what the agent drafted and edit the parts that need their voice.

What the agent assembles

Usage trend from Mixpanel or Amplitude. Support history from Zendesk or Intercom or Front. NPS movement from the survey platform. Expansion signals from the CRM (deal stage changes, new contacts added, role changes at the account). Invoice payment latency from Stripe Billing or the AR system, which is a leading indicator of churn nobody else surfaces in QBR prep. Health score from Gainsight or ChurnZero. Drafted talking points stitched from all of the above in the CSM's voice.

What the CSM does with it

Reads it, edits the talking points, deletes the slides that do not fit, walks into the QBR. The deck is in the CSM's voice and the data is the customer's actual usage, not a generic template. The CSM gets back to talking to customers, which is what they were hired to do.

Frequently asked

What CS platforms does this work with?

Gainsight, ChurnZero, plus the CRM (Salesforce or HubSpot) for accounts not on a CS platform. Mixpanel and Amplitude for usage. Zendesk, Intercom, and Front for support.

Does the agent send the deck to the customer?

No. The CSM reviews and sends. The agent drafts only.

Related use cases

Run this on your stack.