businessreporting

Quarterly Business Review Presentation

Structures a QBR presentation with performance data, insights, learnings, and next-quarter priorities.

Prompt
Act as a VP of Operations preparing a Quarterly Business Review for the [department/business unit] at [company name] in the [industry] sector. The target audience is the executive leadership team. Create a QBR presentation outline for Q[quarter] [year]. Format as structured sections with talking points and suggested chart types: (1) Quarter Highlights: top 3 wins with quantified impact, (2) KPI Performance: a table of 6-8 key metrics with target vs actual vs previous quarter, plus red/green status indicators, (3) Revenue/Pipeline Summary: top-line numbers with trend direction, (4) Challenges & Learnings: 3 challenges faced, root cause for each, and the lesson learned, (5) Customer Feedback: 2-3 themes from feedback with representative quotes such as '"The onboarding was seamless" ([Client Name])', (6) Team & Resource Updates: headcount, key hires, capacity concerns, (7) Next Quarter Priorities: 5 initiatives ranked by impact, each with an owner and success metric, (8) Asks/Support Needed: 2-3 specific requests from leadership. You must ensure each slide has no more than 3-5 bullet points. Avoid vague statements. Only include data-backed claims. Keep the tone concise and executive-friendly.

Why this prompt works

A QBR is one of those documents where structure matters more than rhetoric: leadership has 30 minutes, scans for status, and either approves the next-quarter plan or asks for a redo. Eight numbered sections (highlights, KPI table, revenue, challenges and learnings, customer feedback, team updates, priorities, asks) match how exec teams actually read these. The 'no more than 3 to 5 bullet points per slide' rule stops the document drifting into a wall of text by mid-quarter, and the 'data-backed claims' constraint is the discipline that turns 'we improved customer satisfaction' into 'NPS moved from 32 to 41 quarter-on-quarter'.

When to reach for it

  • You're preparing your first QBR for an exec audience and want a structured template that's hard to get wrong.
  • You're standardising QBRs across departments and want a baseline shape every team starts from.
  • You inherited a QBR template from your predecessor and it's bloated; this gives you a tighter starting point.

How to customise it

The department field shapes the KPIs the model surfaces. A sales QBR centres on pipeline metrics; a customer success QBR centres on retention, NPS, and feature adoption. If you're presenting to a board rather than internal leadership, ask the model to add a 'macro context' section at the top covering the broader market backdrop. For very small teams (under 10 people), the team and resource updates section can collapse into a single paragraph; ask the model to compress it.

What good output looks like

Eight presentation sections with talking points and chart-type suggestions per slide. KPI table has 6 to 8 metrics with target/actual/previous quarter comparisons and traffic-light status. Customer feedback section has placeholder quotes you replace with real ones. Next-quarter priorities are ranked with owners and success metrics. Total length 1,500 to 2,500 words, designed to read in 15 minutes.

Watch out for

Challenges and learnings is the section most teams underwrite, defaulting to either 'no challenges this quarter' (which leadership doesn't believe) or three vague entries. Push the model with 'each challenge should name a root cause and a specific lesson learned, not just a symptom'. Customer feedback quotes should be from real conversations; if you don't have them yet, the model will generate plausible-looking placeholders, and those should never make it into the final deck.

QBRquarterly reviewbusiness reviewpresentationreportingChatGPT / Claude

Build a prompt like this for your task

Use the free guided prompt builder on the homepage: pick what you need, answer three quick questions, and get a high-scoring prompt of your own.

Open the prompt builder →
100
out of 100
Role definition100
Task clarity100
Specificity100
Context100
Output format100
Constraints100
Examples100