The QBR Nobody Prepared For — And Why Viktor Fixes That
———
The Quarterly Business Review has a specific failure mode, and it is nearly universal.
The CSM responsible for it has spent the quarter doing everything except preparing for it. The data sits in five tools. The success metrics agreed at kickoff live in a Notion page nobody has opened in three months. The customer’s executive sponsor has expectations that haven’t been checked against reality since the contract was signed. So the deck gets built on Sunday night. Numbers are estimated. Talking points are guessed. The title gets changed on the old template, and it goes out.
The meeting is fine. The conversation is shallow. The renewal happens or doesn’t on momentum that has nothing to do with what was said in the room.
This is not a laziness problem. It is a coordination problem. The inputs for a serious QBR are scattered across product databases, CRM records, call transcripts, email threads, and a kickoff document written eight months ago by people who have since moved on. Assembling them by hand takes hours no CSM has to spare two days before the meeting.
Viktor assembles the pack. The CSM reviews it and has the conversation.
———
What the QBR Is Actually For
There are three honest reasons a Quarterly Business Review exists. First, to re-anchor the customer’s executive sponsor on value delivered. The sponsor was present at signing and then did not think about the platform again for six months. The QBR is the meeting that shows them the data.
Second, to surface what is not working before it shows up in churn. A customer who is unhappy in October will not renew in January. They will not say so in October. They will sit through the QBR, nod politely, and quietly stop responding by November. The QBR forces a conversation that catches the problem in time to fix it.
Third, to open the expansion conversation. Usage approaching plan limits, a power-user pattern in a new department, feature requests that have already been shipped — these are expansion signals. The QBR is the right context to surface them as evidence, not as a sales pitch.
A QBR that does not do those three things is a status update. Status updates do not need 60 minutes.
The Week Before Every QBR
Consider a CSM and AE pair managing 30 enterprise customers on a quarterly review cadence. That is two or three QBRs every week. Here is what the week before each one typically looks like.
Monday: realize the QBR is next Wednesday. Promise to start tomorrow. Tuesday: escalation pulls the CSM off track. Promise to start tomorrow. Wednesday: check the analytics tool, find there is no access to the customer’s tenant, file a request. Thursday: get the access, pull basic usage numbers, note they are “down a bit” without being precise. Friday: ask the AE for commercial context. Saturday: receive a one-paragraph summary. Sunday 9 PM: open the deck template, copy from last quarter, change the title, populate three slides, send to the AE.
Monday morning: the AE has not reviewed. The deck goes out anyway.
Wednesday 2 PM: the meeting. The exec sponsor asks one question 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 exactly where it was before the meeting.
This is the dominant pattern.
What Viktor Does Instead
Viktor is set up once against the QBR workflow. Fourteen days before any meeting in the CSM’s calendar with a title matching “QBR” or “Quarterly,” it fires automatically.
What it does in that run:
Resolves the customer from the calendar attendee domain to a HubSpot or Salesforce record.
Retrieves the original kickoff document from Notion. Pulls the agreed success metrics and the executive sponsor’s stated goals verbatim.
For each metric, pulls the current value from the relevant source — product database, PostHog, HubSpot, Salesforce — and calculates the change versus last quarter and versus the original baseline.
Pulls the last 90 days of call transcripts, email threads, support tickets, and shared Slack or Teams channel messages for this customer.
Extracts the five strongest verbatim customer quotes, each with source attribution.
Identifies the executive sponsor’s likely top question based on patterns in their recent communications.
If usage data supports an expansion, drafts a specific evidence-based proposal — not a generic pitch.
Outputs a 10-slide draft deck and speaker notes, posted to the CSM’s DM and the customer’s deal channel.
From the CSM’s perspective: fourteen days before any QBR, a complete deck and talking-point pack arrives. Review it. Edit the parts that need judgment. Align with the AE on the expansion slide. Send the deck to the customer forty-eight hours before the meeting.
The Same Week, With Viktor
Monday two weeks out: the draft arrives. Spend 30 minutes reading it. Tuesday: send the AE the draft, ask for the commercial slide refinement. Wednesday: twenty-minute alignment meeting with the AE. Friday: small edits. Deck sent to the exec sponsor with a three-paragraph framing email.
Wednesday meeting: walk in already aligned with the customer. The conversation is strategic because both sides have the same data.
The hours saved are real. The win that matters is upstream of hours: the deck is correct.
What the Deck Actually Looks Like
Viktor produces a ten-slide draft. Each slide has a purpose.
Slide 1 is the title slide. Customer name, quarter, attendees. Required.
Slide 2 is the one that earns the meeting. The goals the customer stated at kickoff, pulled verbatim from the kickoff document. The exec sponsor said something specific eight months ago. Showing them you remember it is the difference between a generic update and a personalized conversation.
Slide 3 is the performance table: goal, baseline, last quarter, this quarter, change. Color-coded. The exec sponsor reads this slide and knows within thirty seconds whether the answer is yes or no.
Slide 4 is three wins with the actual data behind each. Not “we improved efficiency.” Specifically: in March, support ticket triage dropped from 3.2 minutes to 1.1 minutes after enabling the auto-context workflow. That is a 65 percent reduction. Numbers, not adjectives.
Slide 5 is the slide most CSMs leave out, which is exactly why most QBRs fail to surface unhappiness. Two friction points or risks, with verbatim customer quotes. Acknowledging problems in the room, with a plan, builds more trust than pretending they do not exist.
Slides 6, 7, and 8 cover customer voice (three direct attributed quotes from the last 90 days), roadmap items relevant to this customer, and the expansion proposal anchored to usage evidence. Not a price slide. A value slide.
Slide 9 is three real questions for the customer. “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 is the recap and asks. What we are doing. What we need from them. Dates.
Ten slides. Specific. Honest. The customer leaves having had a real conversation.
What Viktor Does Not Do
This is worth being precise about, because the value is often misunderstood.
Viktor does not auto-send the deck to the customer. Drafts only. The CSM reviews and sends.
Viktor does not make the renewal commitment. The data informs; the human commits.
Viktor does not replace the AE on the commercial slides. The AE owns that conversation.
Viktor does not replace customer interviews. It reads what was already collected.
Viktor does not decide which customers get a QBR. That is a leadership decision.
It assembles the input pack and the draft deliverable. The conversation is human, the proposal is human, the relationship is human. Viktor handles the mechanical part so the humans can do the part only they can do.
How This Scales
A five-customer enterprise team running this workflow finds expansion opportunities in the first quarter that would have been missed without the data assembly. Not because the data did not exist before — it did — but because nobody had time to look.
A fifty-customer mid-market team finds that the QBR cron is the difference between QBRs happening on time and QBRs being quietly skipped. Renewal predictability improves within one quarter.
A 500-customer commercial team running thirty-minute QBRs at scale uses Viktor to generate a condensed five-slide deck. At that volume, automated assembly is not an option — it is the only path.
One Dependency Worth Naming
A QBR automation is only as good as the kickoff document it reads from. “Make the team more productive” cannot be measured against. “Reduce support ticket volume by 30 percent by end of Q2 and increase active users from 12 to 30 by end of Q3” can.
Teams that adopt this workflow find their kickoff documents need to be tightened. That is a feature, not a problem. The kickoff document is the foundation for the entire customer relationship; better kickoffs produce better QBRs, and better QBRs produce better renewals.
A sixty-minute kickoff meeting with specific, measurable success criteria is worth more than a four-hour kickoff that produces goals nobody can track.
A Note on Security and Data
QBR preparation involves customer data — usage patterns, contract terms, commercial context, call transcripts. The governance question is real.
Viktor’s workspace is architecturally isolated. No data is shared with any other Viktor client. Your conversations, files, and connected integration data are walled off entirely — cross-tenant access is architecturally impossible.
Your data is never used to train any AI model. That is a contractual and architectural commitment, not a policy that can be quietly amended.
Viktor is SOC 2 Type 1 certified (Type 2 in progress), GDPR aligned, CCPA compliant, and CASA Tier 3 certified — the highest tier required for Google API access. Full documentation at viktor.com/security.
Viktor runs on Claude (Anthropic), GPT-4 (OpenAI), and Gemini (Google). All three are included in one credit balance. Viktor selects the right model for each task automatically. There are no separate API subscriptions to manage.
———
Getting Started
You get $100 of free credits to begin — no credit card, no time limit, no commitment. Explore Viktor properly. Do real work. When you are ready to go further, $50 comes straight off your first bill.
Via the link below:
———
Disclosure: Some links in this article are affiliate links. If you choose to get started with Viktor using the links provided, I may receive a commission — at no additional cost to you. I only recommend tools I use and believe in.