QBR Executive Summary
A one-page executive summary for a customer QBR — their business context from HG, your value delivered, and the expansion thesis, ready for the exec sponsor.
A one-page exec QBR summary — customer context, value, and what's next
Context (HG) + value (yours) +
expansion thesis (HG intent).
| Section | Source |
|---|---|
| Customer context | HG firmographic |
| Value delivered | Your metrics |
| Expansion thesis | HG tech + intent |
Overview
Build an executive-summary page for a customer QBR: the customer's current business context (firmographic shifts, hiring, tech moves from HG), the value you've delivered (from supplied metrics), and a data-grounded expansion thesis — so the exec sponsor walks into the QBR informed and forward-looking.
Use cases
Exec sponsors who lead the QBR
A one-pager that pairs delivered value with the customer's current context and a grounded expansion thesis lets the sponsor steer the QBR toward growth, not status.
Expansion theses customers believe
An expansion pitch grounded in the customer's own tech footprint and intent — not a generic upsell — reads as insight, not a quota grab.
View workflow prompt
# QBR Executive Summary
## Parameters
- `{{domain}}` *(required)* — The customer's domain. Example: `salesforce.com`
- `{{value_delivered}}` *(required)* — Pasted value/usage metrics you've delivered. Example: `adopted by 3 BUs, 40% faster incident resolution, $200k ARR`
- `{{expansion_category}}` *(required)* — Category for the expansion thesis. Example: `security analytics`
## Purpose
Build a one-page exec QBR summary for {{domain}}: their current business context from HG, the {{value_delivered}} you've provided (user-supplied), and a {{expansion_category}} expansion thesis grounded in their tech footprint and intent — so the exec sponsor leads the QBR forward-looking.
## Process
1. **Customer context** — `company_firmographic` + `company_operating_signals` for what's changed at the account (growth, hiring, structure) since the last QBR.
2. **Value framing** — restate {{value_delivered}} (user-supplied) as the proof of impact.
3. **Expansion thesis** — `company_technographic` + `company_intent` for the {{expansion_category}} to ground a credible next-product thesis.
4. **Risks** — note any operating signal (downsizing, leadership change) that affects the relationship.
5. **Summary** — a one-page exec narrative: where they are, what we've delivered, where we go next.
## Output Format
Markdown with:
- `# QBR Executive Summary — {{domain}}`
- `## Customer Context` (what changed, cited)
- `## Value Delivered` (your metrics, labeled)
- `## Expansion Thesis` ({{expansion_category}}, grounded)
- `## Relationship Risks`
- `## Citations`
## Quality Checklist
- Customer context cites `company_firmographic`/`company_operating_signals`
- Delivered-value metrics are labeled user-supplied
- Expansion thesis cites `company_technographic`/`company_intent`
- Fits one page; exec-grade prose