Business Strategy & ROIField Note

How CS managers use Claude to prepare for QBRs and renewals

In brief

QBR prep used to take half a day per account. Here is the workflow that gets it to 45 minutes — without cutting corners on the things that actually matter.

6 min read·Projects

Contents

♡Sign in to save

A quarterly business review is one of the highest-leverage moments in the CS calendar. Done well, it deepens the relationship, surfaces expansion signals, and shores up renewals before they become conversations about churn. Done poorly — or done hastily because you had eight QBRs to prep in two days — it is worse than not doing it at all.

The CS teams that have redesigned their QBR and renewal workflow around Claude are not cutting corners. They are moving the time investment from gathering and formatting to thinking and relationship building.

What the old workflow looks like

Before the QBR: pull usage data from the product, pull health score from Gainsight or your CS platform, find the account notes from the last four check-ins, pull the contract details, build the deck. Two to four hours per account, half of it formatting.

The actual insight — what is this customer getting from the product, what are they not using, what is their risk profile, what should the renewal conversation focus on — gets ten minutes, if that.

Claude inverts this.

The Claude-assisted QBR prep workflow

Step 1: Data dump into Claude

Paste everything into a Project conversation: usage stats, health score summary, account notes, previous QBR notes if you have them, the contract renewal date and value. Do not format it — just paste it raw.

Prompt: "Here is everything I have on this account ahead of a QBR. Give me: (1) a one-paragraph account narrative — what is working, what is not, and where they are relative to their stated goals; (2) three specific things to highlight; (3) two risks or gaps I should be prepared to address; (4) one expansion angle if appropriate."

This takes five minutes. What you get back is a structured read on the account that would have taken an hour of mental assembly to produce otherwise.

Step 2: Slide structure

Give Claude your QBR template (upload it to the Project once, and it is always there). Ask it to fill in the framework using the account narrative.

Prompt: "Using the account narrative above and our standard QBR template, draft the key slides: goals recap, progress summary, value delivered, roadmap for next quarter, and renewal/expansion proposal."

The drafts will not be final — you will edit them. But you are editing a structured draft, not building from scratch. The difference is 20 minutes of editing versus 90 minutes of writing.

Step 3: Anticipate objections

This is the step most CS managers skip under time pressure.

Prompt: "Based on this account's profile — the gaps I identified, their usage patterns, their renewal date — what are the three most likely objections or concerns they will raise in the QBR? For each, give me a one-sentence response and a clarifying question I could ask."

Walking into a QBR with three prepared objection responses is a different experience from winging it.

Step 4: Pre-meeting email

Prompt: "Draft a pre-meeting email to the economic buyer and the day-to-day contact. It should set context for the QBR, confirm the agenda, and make them feel like we have done our homework."

Done. Ten minutes of editing, not thirty minutes of writing.

The renewal conversation specifically

Renewal conversations are a different mode from QBRs — they are often shorter, more commercial, and riskier if the relationship is shaky. Claude helps here in two specific ways.

Risk profiling. Paste the account's engagement history, support ticket volume, NPS scores if you have them, and usage trends. Ask Claude to rate the renewal risk and give you the three factors driving it. You already knew these intuitively — Claude makes them explicit and forces you to have a plan for each.

Renewal email drafts. The first renewal outreach email is one of the hardest emails to write well — it has to be confident without being presumptuous, commercial without feeling transactional. Claude drafts these well when you give it the account context and specify the tone.

Prompt: "Draft an initial renewal outreach email for this account. The renewal is in 90 days. The relationship is strong but they have under-used the [feature] we sold them on. Tone: warm, partnership-focused, not pushy. Include a natural ask for a call."

Setting up your CS Project properly

One Project for the whole CS team, shared, with:

In the system prompt:

Your company name, product name, and what it does
Your standard QBR structure and what each section covers
The renewal stages you use (60-day outreach, 30-day conversation, etc.)
What a healthy vs. at-risk account looks like at your company

Documents to upload:

Your QBR slide template (text description or outline)
Example of a strong QBR deck (redacted)
Renewal email examples that have worked
Churn risk criteria for your product
Common objections and standard responses

Once this is set up, every CS rep on the team operates from the same baseline. A new hire in their first week can run a QBR prep workflow that previously required six months of experience to do well.

What changes when you do this at scale

The teams that have implemented this workflow consistently report the same shift: they go from spending 70% of QBR prep time on production and 30% on thinking, to the inverse. The actual relationship work — knowing this customer's situation cold, anticipating what matters to them, walking in prepared for the hard question — gets the time it deserves.

That is what the QBR is supposed to be for.