Quarterly Business Review (QBR)

The most effective QBR structure is outcome-centric, not feature-centric. A 60-minute QBR agenda: (1) Their World (10 min) — open by asking about the customer's business priorities, changes in their market, and goals for the next quarter. This signals genuine partnership orientation, not a vendor pitch. (2) Value Delivered (15 min) — present data on the measurable business outcomes delivered in the past quarter. Not feature adoption statistics — business metrics the customer cares about: "Your team resolved 3,200 tickets last quarter, 22% faster than Q1 — that's approximately 180 agent-hours recaptured." Connect product usage to business value. (3) Product Roadmap Preview (10 min) — share 2–3 upcoming roadmap items relevant to this specific customer's use case. Frame as "here's what we're building that's relevant to your goals." Not a marketing slide deck. (4) Action Items and Success Plan (10 min) — review the mutual success plan: what was committed, what was achieved, what is the plan for next quarter? (5) Open Discussion (15 min) — unstructured time for their questions and concerns. This is where real relationship intelligence is gathered.

QBR preparation is one of the most time-intensive CSM activities — and the one most at risk of being deprioritized when CSMs are managing large books of business. CS Ops reduces preparation time by automating the data assembly portion. A QBR preparation dashboard in Gainsight or a BI tool automatically populates: product usage metrics for the past 90 days (feature adoption, DAU/MAU, core action frequency) compared to the previous quarter; support ticket volume and response time metrics; open issues and milestones from the success plan; ARR history and upcoming renewal date. This pre-populated dashboard reduces CSM QBR preparation from 3–4 hours to 30–45 minutes of customization and narrative development. CS Ops maintains a QBR template library — slides and talking points organized by customer lifecycle stage and account size — that CSMs customize rather than create from scratch. Critically, CS Ops tracks QBR completion rate monthly: every enterprise account should have a QBR every 90 days, and accounts where QBRs are missed represent unknown renewal risk.

The post-QBR follow-up determines whether the QBR created momentum or was simply a pleasant conversation. Within 24 hours of the QBR: the CSM sends a structured recap email to all attendees, documenting: (1) "What we discussed" — a 3-sentence summary of the meeting themes; (2) "What we committed to" — a bulleted list of vendor commitments with owners and target dates (escalating a bug to Engineering, scheduling a training session for the new team, coordinating a roadmap preview with the PM); (3) "What we need from you" — the customer commitments (introduction to the new VP, submitting their use case for a case study, adding the Q3 renewal to their budget cycle). All commitments are entered into the CS platform as success plan tasks, so progress is visible to the CSM manager and leadership. The following QBR opens by reviewing progress against every commitment from the previous QBR — accountability creates the trust that justifies another 90-day commitment cycle.