Verified against ChatGPT · 2026-08-06
Build a quarterly business review agenda that earns the renewal conversation instead of ambushing it
Structures a QBR agenda for an enterprise account around usage evidence and a named risk, so the renewal or expansion discussion at the end lands as an earned conclusion rather than a surprise pivot the account didn't see coming.
The prompt
Ready to copy — highlighted parts are example details you can swap.
I have a quarterly business review coming up with Corville Distribution Partners, renewal date November 15, 2026, and want the agenda structured so the renewal or expansion conversation at the end feels like an earned conclusion, not a surprise pivot after a generic check-in. Usage and outcome data since the last QBR or since signing: onboarded two new regional teams onto the platform, ticket resolution time down 22% quarter over quarter. Who's attending from their side: the VP of Operations who signed originally, and a new Ops Manager who joined last quarter. A specific expansion opportunity worth raising, if there is one: the two new regional teams are still on the base tier, which caps the reporting dashboards they clearly want based on their usage patterns. A known risk or open concern on the account: the new Ops Manager mentioned in passing that leadership questioned the cost at a recent budget review. AGENDA STRUCTURE Build the agenda in this order, each with a time estimate against a total of roughly 45 minutes unless told otherwise: 1. RECAP OF GOALS SET LAST TIME — one or two sentences restating what success was supposed to look like when this account last set goals, so the review has a stated baseline to measure against rather than starting from an ungrounded "how's everything going." 2. RESULTS AGAINST THAT BASELINE — the specific outcomes from onboarded two new regional teams onto the platform, ticket resolution time down 22% quarter over quarter, stated as numbers or concrete results wherever the data allows, mapped directly back to the goals just restated — a QBR that shows usage statistics with no link back to a stated goal is showing activity, not value. 3. THE HONEST PART — address the new Ops Manager mentioned in passing that leadership questioned the cost at a recent budget review directly and specifically, not folded into a vague "any feedback for us?" prompt that lets it go unspoken if the account doesn't volunteer it themselves; naming a known risk first, before the account has to raise it, signals the relationship can handle honesty and builds more trust than pretending it isn't there. 4. FORWARD LOOK — if the two new regional teams are still on the base tier, which caps the reporting dashboards they clearly want based on their usage patterns is filled in, introduce it here as a natural extension of the results just shown, grounded in something specific from onboarded two new regional teams onto the platform, ticket resolution time down 22% quarter over quarter or the account's own stated goals, not a generic upsell pitch dropped into an unrelated slot; if it's empty, skip this section rather than forcing a manufactured expansion angle that isn't actually grounded in anything real about this account. 5. RENEWAL OR NEXT STEPS — close with the specific ask relevant to November 15, 2026's proximity, with a concrete next step and date, not an open-ended "let's regroup soon." MULTI-STAKEHOLDER HANDLING Given the VP of Operations who signed originally, and a new Ops Manager who joined last quarter, flag if any listed attendee is likely to care about a different part of this agenda than the others — a technical stakeholder attending mainly to hear about the risk item, alongside a business stakeholder mainly there for the renewal conversation, changes how much time each section should actually get. HONESTY CHECK If onboarded two new regional teams onto the platform, ticket resolution time down 22% quarter over quarter doesn't clearly connect back to the goals stated in section 1, say so directly in the agenda draft rather than forcing a connection that isn't really there — a QBR that overstates the link between activity and outcome is exactly the kind of review a sophisticated account stakeholder will quietly stop trusting after noticing the gap once.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Structuring the agenda around a restated baseline before showing results is what turns a QBR from a status update into an actual review: usage statistics presented with no reference back to a goal the account itself set are, from the account's perspective, just activity metrics, and activity metrics don't independently make the case for renewal or expansion the way outcomes measured against a stated goal do — the baseline restatement is what gives the later numbers a frame to be evaluated against instead of floating unanchored. Addressing the known risk in its own explicit section, rather than folding it into an open-ended feedback prompt at the end, matters because a vague "anything on your mind?" question relies entirely on the account volunteering a concern that may feel awkward or political to raise unprompted, while naming it directly signals the relationship is secure enough to handle the conversation head-on — accounts that have a known concern sitting unaddressed under the surface of an otherwise upbeat QBR tend to notice the omission, and noticing it erodes trust more than the concern itself would have. Making the expansion pitch, when there is one, an extension of results already shown rather than an unrelated new topic exploits the same narrative-continuation logic that works in renewal conversations generally: an ask that flows out of a result just demonstrated reads as earned, while the identical ask dropped into an agenda with no connection to what came before reads as the real reason for the meeting, undermining the credibility of the review that preceded it. The instruction to skip the expansion section entirely when no real angle exists, rather than manufacturing one, protects the format's core value: a QBR whose closing pitch is grounded in nothing real about this specific account teaches that stakeholder to treat every future QBR as a sales call with extra slides, which defeats the purpose of the format the very first time it's noticed.
Verified against
ChatGPT GPT-5.1 · 2026-08-06
Claude Sonnet 4.5 · 2026-08-07
Changelog
- 2026-08-07 — Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.5).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
