Plan Qbr

Generates an executive-ready QBR/EBR agenda with data narratives, proof points, and follow-up actions.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Command: plan-qbr

Inputs

  • account – required account name or ID.
  • tier – customer tier (strategic, growth, scale).
  • date – meeting date to anchor timeline.
  • theme – optional focus area (value, roadmap, expansion, executive alignment).
  • attendees – optional list of customer/internal roles.

Workflow

  1. Signal Compilation – pull KPIs, adoption, sentiment, roadmap updates, commitments.
  2. Narrative Structuring – outline wins, impact, and upcoming milestones.
  3. Agenda Draft – sequence intro, metrics, customer speakers, roadmap, decisions.
  4. Materials Prep – assemble decks, dashboards, demo assets, FAQs.
  5. Follow-up Plan – pre-fill action tracker, owners, and deadlines.

Outputs

  • QBR/EBR agenda with timing, speakers, objectives.
  • Narrative brief (wins, KPIs, roadmap, asks).
  • Action tracker template pre-populated with expected decisions.

Agent/Skill Invocations

  • relationship-director – curates executive messaging.
  • success-planner – aligns agenda to success plan milestones.
  • account-health-analyst – supplies data + insights.
  • exec-briefing skill – ensures narrative structure + proof points.
  • expansion-playbook skill – tags upsell motions for discussion.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0