Quarterly Business Review (QBR) Writer

A structured QBR document that gives executives a clear, honest view of the quarter and a confident path forward.

Best For

•A department head preparing for an executive review uses it to turn raw metrics and a list of missed targets into a data-first QBR document leadership can act on
•A startup CEO reporting to the board uses the 'asks' section to be explicit about what resources or decisions are needed, instead of burying the request in narrative
•A team lead who missed two targets last quarter uses the root-cause and corrective-action structure to present the miss honestly without it reading as an excuse

Prompt Template

Create a Quarterly Business Review (QBR) document for [COMPANY_OR_TEAM_NAME] covering [QUARTER] [YEAR]. Use the following data inputs: revenue or key metrics: [METRICS_DATA], top initiatives completed: [INITIATIVES], missed targets: [MISSED_TARGETS], and strategic priorities for next quarter: [NEXT_QUARTER_PRIORITIES]. Structure the QBR with these sections: (1) Executive snapshot, a 4-bullet dashboard of the quarter's most critical numbers, (2) Wins, 3–4 accomplishments with specific results and business impact, (3) Misses, 2–3 targets not hit, root cause for each, and corrective actions already taken or planned, (4) Key learnings, 2 insights the business is taking forward, (5) Q[NEXT_QUARTER] priorities, 3–5 strategic priorities each with an owner and success metric, (6) Asks, any resources, decisions, or support needed from leadership. Write for an executive audience: direct, data-first, no fluff. Total: 500–800 words.

Pro Tip

Paste in actual numbers for the metrics data field rather than describing them qualitatively, since the executive snapshot dashboard is only credible if it leads with real figures instead of adjectives like 'strong growth'.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Executive snapshot: Revenue up 14% quarter over quarter; churn held flat at 2.1%; two of three roadmap initiatives shipped on time. Misses: the enterprise pricing tier launch slipped by 6 weeks, root cause was underestimated legal review time; corrective action is now building a 2-week legal buffer into all pricing changes. Ask: need one additional engineer allocated to the billing team to hit next quarter's priorities.