QBR Execution Manager

Qbr planning

by LeadMagic · MIT license · ★ 62 on GitHub

Plan and execute Quarterly Business Reviews — value documentation, ROI presentation, executive alignment, and expansion roadmap. Use when preparing for QBRs, business reviews with customers, or executive stakeholder meetings.

---
name: qbr-planning
description: >-
  Plan and execute Quarterly Business Reviews — value documentation, ROI
  presentation, executive alignment, and expansion roadmap. Use when preparing
  for QBRs, business reviews with customers, or executive stakeholder meetings.
  Triggers on: "QBR", "quarterly business review", "executive business review",
  "customer review", "value review", or any request about strategic customer
  meetings.
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: customer-success
  tags: [qbr, customer-success, executive-review, value]
  frameworks:
    - "Gainsight QBR Methodology"

Overview

Before delivering, verify: - [ ] All required sections are complete - [ ] Output matches the user's stated need - [ ] Named frameworks are cited for key recommendations - [ ] No vague claims — every recommendation has a specific action - [ ] Deliverable is ready for operational use, not just conceptual

Manual install (npx, ZIP)

Claude Codenpx skills add LeadMagic/gtm-skills --skill qbr-planning -g -a claude-code

Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/customer-success/qbr-planning#main ~/.claude/skills/qbr-planning

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md5.8 KB

Read SKILL.md here

LeadMagic/main1 file shown

SKILL.md5.8 KB

Browse every file on GitHub↗

SKILL.md

Show the full text136 lines

qbr-planning/SKILL.md136 lines · 5.8 KB

QBR Planning

Overview

A QBR is not a status update — it is a strategic alignment meeting that demonstrates value delivered, aligns on future priorities, and sets the stage for expansion. This skill builds QBR templates that executives want to attend because they see clear ROI from the relationship.

When to Use

"Plan a QBR"
"Prepare for an executive business review"
"Build a QBR deck"
"Document value for a customer"
"Structure a quarterly review"

Authoritative Foundations

Gainsight QBR methodology: QBRs should cover value realized, value roadmap, and strategic alignment — not product updates. Winning by Design Bowtie metrics: frame expansion within the customer's lifecycle, not your quota.

Step-by-Step Process

Phase 1: Pre-QBR Preparation

Gather: usage metrics, support history, NPS/CSAT trends, expansion signals, stakeholder map, competitor activity. Document value delivered in their language — not your feature names.

Phase 2: QBR Structure

Executive Summary — value delivered this quarter, in their words
Metrics Review — adoption, usage, outcomes achieved vs. goals
Success Stories — wins since last QBR
Strategic Alignment — how this maps to their company priorities
Roadmap Preview — what's coming, how it benefits them
Expansion Opportunity — logical next steps, not a sales pitch
Action Items — mutual commitments for next quarter

Phase 3: Delivery

60 minutes: 40 min presentation, 20 min discussion. Send deck 24 hours in advance. Include their logo, their metrics, their language. This is about them — not you.

Output Format

QBR deck template, value documentation template, stakeholder map, and pre-QBR checklist.

Quality Check

Before delivering, verify:

All required sections are complete
Output matches the user's stated need
Named frameworks are cited for key recommendations
No vague claims — every recommendation has a specific action
Deliverable is ready for operational use, not just conceptual

Common Pitfalls

Product update disguised as QBR — executives don't care about feature releases. They care about business outcomes.
Surprise expansion ask — if expansion is first mentioned at the QBR, it's too late. Plant the seed months before.
Your metrics, not theirs — "you logged in 50 times" means nothing. "Your team reduced time-to-close by 40%" means everything.
No action items — a QBR without mutual commitments is a meeting, not a milestone.

Execution Artifacts

references/framework-notes.md — named frameworks, citation anchors, and operating assumptions
templates/output-template.md — copy-paste deliverable structure for the user
scripts/check-output.py — local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand: Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions

What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?

Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

Gainsight QBR Methodology: apply only the part that directly improves the requested deliverable.
Winning by Design Bowtie Metrics: apply only the part that directly improves the requested deliverable.
Gainsight — Customer Success Maturity Model: apply only the part that directly improves the requested deliverable.

Deliverable Standard

A strong output from this skill includes:

A crisp diagnosis of the current situation
A recommended path with tradeoffs, not a generic list
A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
A measurement plan with leading and lagging indicators
Risks and edge cases called out before execution

Adaptation Rules

For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.

cs-playbooks: Full CS operating system
customer-marketing: Case studies and advocacy from QBRs
expansion-selling: Turn QBR insights into expansion

1	---
2	name: qbr-planning
3	description: >-
4	Plan and execute Quarterly Business Reviews — value documentation, ROI
5	presentation, executive alignment, and expansion roadmap. Use when preparing
6	for QBRs, business reviews with customers, or executive stakeholder meetings.
7	Triggers on: "QBR", "quarterly business review", "executive business review",
8	"customer review", "value review", or any request about strategic customer
9	meetings.
10	license: MIT
11	compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
12	metadata:
13	version: "1.0.0"
14	author: LeadMagic
15	category: customer-success
16	tags: [qbr, customer-success, executive-review, value]
17	frameworks:
18	- "Gainsight QBR Methodology"
19	- "Winning by Design Bowtie Metrics"
20	- "Gainsight — Customer Success Maturity Model"
21	---
22
23	# QBR Planning
24
25	## Overview
26	A QBR is not a status update — it is a strategic alignment meeting that
27	demonstrates value delivered, aligns on future priorities, and sets the
28	stage for expansion. This skill builds QBR templates that executives want
29	to attend because they see clear ROI from the relationship.
30
31	## When to Use
32	- "Plan a QBR"
33	- "Prepare for an executive business review"
34	- "Build a QBR deck"
35	- "Document value for a customer"
36	- "Structure a quarterly review"
37
38	## Authoritative Foundations
39	Gainsight QBR methodology: QBRs should cover value realized, value roadmap,
40	and strategic alignment — not product updates. Winning by Design Bowtie
41	metrics: frame expansion within the customer's lifecycle, not your quota.
42
43	## Step-by-Step Process
44	### Phase 1: Pre-QBR Preparation
45	Gather: usage metrics, support history, NPS/CSAT trends, expansion signals,
46	stakeholder map, competitor activity. Document value delivered in their
47	language — not your feature names.
48
49	### Phase 2: QBR Structure
50	1. Executive Summary — value delivered this quarter, in their words
51	2. Metrics Review — adoption, usage, outcomes achieved vs. goals
52	3. Success Stories — wins since last QBR
53	4. Strategic Alignment — how this maps to their company priorities
54	5. Roadmap Preview — what's coming, how it benefits them
55	6. Expansion Opportunity — logical next steps, not a sales pitch
56	7. Action Items — mutual commitments for next quarter
57
58	### Phase 3: Delivery
59	60 minutes: 40 min presentation, 20 min discussion. Send deck 24 hours
60	in advance. Include their logo, their metrics, their language. This is
61	about them — not you.
62
63	## Output Format
64	QBR deck template, value documentation template, stakeholder map, and
65	pre-QBR checklist.
66
67
68	## Quality Check
69
70	Before delivering, verify:
71	- [ ] All required sections are complete
72	- [ ] Output matches the user's stated need
73	- [ ] Named frameworks are cited for key recommendations
74	- [ ] No vague claims — every recommendation has a specific action
75	- [ ] Deliverable is ready for operational use, not just conceptual
76
77	## Common Pitfalls
78	1. Product update disguised as QBR — executives don't care about
79	feature releases. They care about business outcomes.
80	2. Surprise expansion ask — if expansion is first mentioned at the
81	QBR, it's too late. Plant the seed months before.
82	3. Your metrics, not theirs — "you logged in 50 times" means nothing.
83	"Your team reduced time-to-close by 40%" means everything.
84	4. No action items — a QBR without mutual commitments is a meeting,
85	not a milestone.
86
87	## Execution Artifacts
88
89	- `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions
90	- `templates/output-template.md` — copy-paste deliverable structure for the user
91	- `scripts/check-output.py` — local checklist validator for required sections
92	This skill includes lightweight artifacts the agent can load on demand:
93	Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
94
95	## Implementation Depth
96
97	Use this section when the user asks for a finished asset, not a high-level explanation.
98
99	### Diagnostic Questions
100
101	1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
102	2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
103	3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
104	4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
105	5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
106
107	### Framework Application
108
109	Map the recommendation explicitly to the named frameworks in this skill:
110
111	- Gainsight QBR Methodology: apply only the part that directly improves the requested deliverable.
112	- Winning by Design Bowtie Metrics: apply only the part that directly improves the requested deliverable.
113	- Gainsight — Customer Success Maturity Model: apply only the part that directly improves the requested deliverable.
114
115	### Deliverable Standard
116
117	A strong output from this skill includes:
118
119	- A crisp diagnosis of the current situation
120	- A recommended path with tradeoffs, not a generic list
121	- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
122	- A measurement plan with leading and lagging indicators
123	- Risks and edge cases called out before execution
124
125	### Adaptation Rules
126
127	- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
128	- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
129	- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
130
131
132	## Related Skills
133	- cs-playbooks: Full CS operating system
134	- customer-marketing: Case studies and advocacy from QBRs
135	- expansion-selling: Turn QBR insights into expansion
136