🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.

Quarterly Business Review (QBR) Framework

Plan a customer-focused QBR that proves value, surfaces priorities, and creates a clear path to renewal or expansion.

Sales - Account Management - Quarterly Business Review (QBR) Framework

Who it's for

Account managers, customer success managers, sales leaders, client success teams, revenue teams

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a senior account management advisor. Your task is to create a complete Quarterly Business Review framework for one customer account.

### Required Input
- Account Name: [Customer name, e.g. “Acme Health Group”]
- Review Period: [Quarter or date range, e.g. “Q2 2026”]
- Customer Goals: [Business outcomes expected, e.g. “reduce onboarding time and improve reporting”]
- Products or Services Used: [What the customer currently uses]
- Performance Data: [Usage, adoption, ROI, project progress, support trends, or outcome metrics]
- Key Stakeholders Attending: [Names, roles, priorities, and influence level]
- Account Health: [Current sentiment, renewal status, risks, or relationship context]
- Desired Commercial Outcome: [e.g. “secure renewal confidence” or “open expansion discussion”]
- Next Quarter Priorities: [Known or assumed customer initiatives]

### Input Validation
Review every required input before creating the output. If the account context, objective, stakeholders, commercial situation, risks, or available evidence are missing, unclear, or too vague, ask specific clarification questions. Pause and wait for clarification before producing the final result.

### Instructions
Design the QBR around customer value, not vendor activity. Begin by framing the meeting purpose in a way that feels useful to the customer: what changed, what value was delivered, what needs attention, and what decisions or priorities should come next.

Translate performance data into business meaning. Do not simply restate metrics. Explain what the data suggests, where outcomes are strong, where adoption or impact may be weak, and what should be discussed openly.

Create a meeting flow that balances proof of value, strategic discussion, risk management, and next-step alignment. Include talking points that help the account team avoid a slide-by-slide status update.

Identify stakeholder-specific interests. For each attendee type, clarify what they are likely to care about and what evidence or question should be prepared for them.

Include renewal or expansion positioning only if it fits the account context. The recommendation should feel earned from business outcomes, not forced.

Create follow-up actions that turn the QBR into account momentum, including owner, timing, and intended result.

### Output
Provide:
1. QBR Objective
2. Executive-Level Meeting Narrative
3. Recommended Agenda
4. Value Delivered Summary
5. Performance Insights and Interpretation
6. Stakeholder Talking Points
7. Risks, Gaps, and Discussion Areas
8. Next Quarter Priority Plan
9. Renewal or Expansion Conversation Angle
10. Follow-Up Action Tracker
11. Customer Questions to Ask During the QBR

Make the output specific, commercially realistic, and ready to use in an account review, customer meeting, or internal planning session.

Optional advanced instructions

				
					Create a more executive-level version for senior decision makers with less operational detail.

Example output

1. QBR Objective

The primary objective of this QBR is to shift the vendor-customer dynamic from an operational tool provider to an enterprise infrastructure partner. The meeting will validate the substantial time-savings ROI achieved over the last quarter, proactively address hidden engineering gatekeeper objections regarding processing speeds, and position our platform as a foundational layer to support their upcoming international scale-up, effectively securing renewal confidence and opening a natural expansion runway.

2. Executive-Level Meeting Narrative

The Framing Narrative: “Over the past quarter, our shared focus was to decentralize your data tracking infrastructure so your operations team could move faster without pulling developers away from core projects. The data shows we achieved exactly that—slashing reporting assembly times from 12 hours to under 30 minutes, giving your team back valuable hours every single week. As you prepare to launch into the UK and EU markets next quarter, today’s conversation is about taking those proven efficiencies and scaling them globally. We will review your regional data-routing architecture, ensure your systems maintain ultra-low latency, and discuss how to keep your expanding teams integrated under one secure framework.”

3. Recommended Agenda

Time Block	Segment Topic	Core Objective & Content Focus
00:00 – 00:05	Executive Welcome & Alignment	Frame the meeting around corporate goals: operational autonomy and regional market expansion.
00:05 – 00:15	Value Realization Review	Present the quantitative efficiency gains (hours saved, false-positive drops) realized over the review period.
00:15 – 00:30	Technical Performance & Infrastructure Optimization	Openly review network latency trends and address engineering architecture needs for the upcoming global launch.
00:30 – 00:45	Future Roadmap & Regional Workspace Alignment	Collaborative strategy session mapping out user permissions, regional data isolation, and predictive forecasting requirements.
00:45 – 00:50	Commercial Next Steps & Action Items	Lock down owners, timelines, and commercial parameters for the upcoming expansion proposal.

4. Value Delivered Summary

Reporting Overhead Drastically Reduced: Successfully condensed multi-channel data assembly time from a manual 12-hour bottleneck down to an automated, sub-30-minute processing loop.
Reclaimed Operational Capacity: Returned roughly 11 hours of productive time back to individual data analysts every single week, allowing the existing team to absorb a 20% increase in baseline transaction volumes without hiring additional staff.
Improved Pipeline Stability: Maintained a 72% Daily Active User to Monthly Active User (DAU/MAU) ratio among managers, proving deep, consistent platform adoption across daily operations.

5. Performance Insights and Interpretation

While operational adoption remains flawless across the core marketing and analyst teams, our platform telemetry indicates a sharp drop-off in activity immediately following complex API configuration changes. This indicates that while the user interface is intuitive for daily reporting, the operational team is running into technical friction whenever they attempt to modify underlying data routing paths.

Furthermore, our regional network diagnostic logs indicate that while standard US data pipelines are running smoothly, current cross-border test calls are hovering near the 35ms mark. To prevent this from triggering an infrastructure veto by their engineering leadership at the upcoming renewal, we must use this QBR to map out a transition to our dedicated low-latency webhook endpoints, which will pull execution speeds safely back below the critical 15ms threshold.

6. Stakeholder Talking Points

For the VP of Commerce (Economic Gatekeeper)

What They Care About: Risk mitigation, fast time-to-market for international launches, and protecting operating margins.
Talking Point: “We’ve proven this infrastructure can handle your US data velocity while freeing up your analysts. Let’s look at how replicating this framework in the UK and EU protects your margins against cross-border operational errors from day one.”

For the Marketing Operations Director (Operational Champion)

What They Care About: Cross-functional team efficiency, eliminating manual tracking errors, and system flexibility.
Talking Point: “The team is saving 11 hours a week on reporting. As you spin up your new European teams, we want to ensure they inherit these exact same automated workflows without creating messy, fragmented data silos.”

For the Core Infrastructure Lead (Technical Gatekeeper)

What They Care About: API execution speeds, processing latency, data isolation compliance, and minimizing code maintenance.
Talking Point: “We know that every millisecond counts during an international checkout process. Let’s look at how our dedicated webhook architecture ensures sub-15ms processing speeds across your new regional endpoints.”

7. Risks, Gaps, and Discussion Areas

The Single-Threaded Relationship: Our relationship equity is concentrated almost entirely within the marketing operations tier. If this team experiences turnover, our upcoming contract renewal is exposed to significant risk. We must use this review to formally embed engineering and commercial leadership into our platform governance model.
The Silent Latency Objection: Engineering stakeholders rarely complain before ….

When to reuse this workflow

Forecast Risk Assessment

Assess forecast risk across pipeline quality, deal confidence, timing, rep judgement, and data reliability.

Sales, Revenue Operations

Revenue Growth Constraint Analysis

Identify the main operational constraints preventing sales growth and create a focused action plan.

Sales, Revenue Operations

Sales Activity Effectiveness Analysis

Assess which sales activities create pipeline progress, meetings, opportunities, and closed revenue.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.