QBR Outline Template

Quarterly Business Review slide structure

How to Use

Copy this outline and use it as the skeleton for your QBR deck.
One slide per section — each heading below maps to a single slide.
Fill in the bracketed placeholders with your data.
Trim or expand based on your audience (see audience guidance at the bottom).

Slide 1: Executive Summary

Purpose: Set context in 60 seconds. Three headlines, no deep-dives yet.

Headline	Status
Adoption	[e.g., "78% seat utilization, up from 62% last quarter"]
Key Win	[e.g., "PR cycle time decreased 25% across adopting teams"]
Focus Area	[e.g., "Agent adoption is at 12% — enabling 5 pilot teams in Q3"]

Talking point: "We're seeing strong adoption growth and early productivity signals. Our focus next quarter is deepening engagement through agent mode enablement."

Slide 2: Adoption Overview

Purpose: Show top-line health of the Copilot program with trends.

KPI	Last Quarter	This Quarter	Δ	Trend
Seat Utilization	[X]%	[Y]%	[+/-Z]%	↑↓→
Monthly Active Users	[X]	[Y]	[+/-Z]	↑↓→
DAU/MAU Ratio	[X]%	[Y]%	[+/-Z]%	↑↓→
Acceptance Rate	[X]%	[Y]%	[+/-Z]%	↑↓→
Chat Engagement (avg/user/day)	[X]	[Y]	[+/-Z]	↑↓→

Commentary: [2–3 sentences explaining the most notable changes and why.]

Slide 3: Engagement Deep-Dive

Purpose: Show how developers are using Copilot across different dimensions.

Feature Mix

Feature	% of Activity	Trend
Code completions	[X]%	↑↓→
Chat (inline + panel)	[X]%	↑↓→
Agent / edit mode	[X]%	↑↓→
PR summaries	[X]%	↑↓→

Top Languages

Language	Suggestions Accepted	Acceptance Rate
[Language 1]	[X]	[Y]%
[Language 2]	[X]	[Y]%
[Language 3]	[X]	[Y]%

IDE Distribution

IDE	Active Users
VS Code	[X]
JetBrains	[X]
Visual Studio	[X]
Neovim / Other	[X]

Agent Adoption Trend

[Include a line chart or table showing agent mode adoption over the past 3–4 months.]

Month	Agent Users	% of Active Users
[Month 1]	[X]	[Y]%
[Month 2]	[X]	[Y]%
[Month 3]	[X]	[Y]%

Slide 4: Impact Evidence

Purpose: Connect Copilot adoption to engineering outcomes.

Productivity Metrics

Metric	Baseline	Current	Δ	Attribution Confidence
PR cycle time (median)	[X] hrs	[Y] hrs	[Z]%	[High/Med/Low]
Deployment frequency	[X]/wk	[Y]/wk	[Z]%	[High/Med/Low]
Time to first review	[X] hrs	[Y] hrs	[Z]%	[High/Med/Low]
Change failure rate	[X]%	[Y]%	[Z]%	[High/Med/Low]

DORA Correlation (if available)

[Optional: Include a scatter plot or summary showing relationship between Copilot adoption level and DORA metrics across teams.]

Team Cohort	Copilot Usage Level	Avg PR Cycle Time	Deploy Freq
High adopters	>80% utilization	[X] hrs	[X]/wk
Medium adopters	40–80% utilization	[X] hrs	[X]/wk
Low adopters	<40% utilization	[X] hrs	[X]/wk

Key insight: [1–2 sentences summarizing the strongest evidence of impact.]

Slide 5: ROI Summary

Purpose: Translate impact into dollars for executive audiences.

Item	Amount
Quarterly license cost	$[AMOUNT]
Estimated quarterly value created	$[AMOUNT]
Net value this quarter	$[NET]
Annualized ROI	[X]%

Value Drivers

Driver	Estimated Quarterly Value
Developer time savings	$[AMOUNT]
Throughput improvements	$[AMOUNT]
Quality / incident reduction	$[AMOUNT]
Total	$[TOTAL]

See the ROI One-Pager for full methodology.

Slide 6: Success Stories

Purpose: Make the data human. 2–3 short stories from real teams.

Story 1: [Team/Developer Name]

"[Direct quote from developer or manager about their experience with Copilot.]"

Context: [1–2 sentences about the team, what they used Copilot for, and the result.]

Story 2: [Team/Developer Name]

"[Direct quote.]"

Context: [1–2 sentences.]

Story 3: [Team/Developer Name] (optional)

"[Direct quote.]"

Context: [1–2 sentences.]

How to collect stories: Run a short Slack/Teams survey asking "How has Copilot helped you this quarter?" or interview 2–3 team leads.

Slide 7: Risks & Blockers

Purpose: Be transparent about challenges and show you have a plan.

Risk / Blocker	Impact	Status	Action Item	Owner
Low adoption in [Team X]	Underutilized licenses	🔴	Targeted enablement session scheduled [DATE]	[NAME]
[API/policy change]	[Impact description]	🟡	[Mitigation plan]	[NAME]
[Data gap or limitation]	[Impact description]	🟡	[Plan to address]	[NAME]
[Security/compliance concern]	[Impact description]	🟢	[Resolution]	[NAME]

Slide 8: Next Quarter Plan

Purpose: Show the roadmap for continued improvement.

Planned Actions

Action	Target	Timeline	Owner
[e.g., Agent mode enablement for 5 teams]	[e.g., >30% agent adoption]	[e.g., Q3 Week 1–6]	[NAME]
[e.g., Custom instructions rollout]	[e.g., All teams]	[e.g., Q3 Week 2–4]	[NAME]
[e.g., Developer survey #2]	[e.g., >60% response rate]	[e.g., Q3 Week 8]	[NAME]
[e.g., License optimization review]	[e.g., <5% idle seats]	[e.g., Q3 Week 10]	[NAME]

Next Quarter Targets

KPI	Current	Q+1 Target
Seat Utilization	[X]%	[Y]%
Agent Adoption	[X]%	[Y]%
Developer Satisfaction	[X]/5	[Y]/5

Appendix: Data Sources & Methodology

Data Point	Source	Collection Method	Limitations
Seat utilization, MAU	GitHub Usage Dashboard / API	Automated export	28-day rolling window
Acceptance rate, chat engagement	GitHub Usage Dashboard / API	Automated export	Aggregate only; no per-user detail in dashboard
Code generation metrics	Code Gen Dashboard / API	Automated export	Language-level granularity varies
PR cycle time, deploy frequency	[DevLake / Git analytics / internal tooling]	[Method]	[Limitations]
Developer satisfaction	Internal survey	[Tool, e.g., Google Forms]	Self-reported; response rate = [X]%
ROI calculations	Derived from above sources	See ROI One-Pager	Estimates, not causal attribution