Cc Qbr Deck Builder

QBR Deck Builder

Generates data-populated QBR decks by assembling usage metrics, health trends, support data, value evidence, and adoption analytics into a structured presentation. Part of the Communication & Content Production pillar.

This is a content assembly and generation skill. It produces a data-rich deck that the CSM customises with narrative, strategic recommendations, and relationship-aware framing. The agent builds the evidence; the human tells the story.

When to Run

• Triggered: By lo-qbr-orchestrator at T-7 before a scheduled QBR
• On-demand: When a CSM requests a QBR deck for a specific account

Core Execution Logic

Step 1: Pull Data from All Sources

Gather the complete data picture for the account:

Data freshness check: All data must be within 7 days of the QBR date. Flag any data source that is stale. A QBR deck with outdated data undermines credibility.

Step 2: Select Deck Template by Segment

Step 3: Populate Slides by Template

Enterprise QBR deck:

Mid-Market QBR deck follows the same logic with slides 3 and 8 consolidated and lighter data depth.

SMB QBR compresses to: usage snapshot, value highlights, 2-3 tips/recommendations, and action items.

Step 4: Generate Comparison Views

For every data slide, produce comparison context:

Step 5: Apply Quality Gates

Before delivering the deck:

Output Format

{
  "account_id": "string",
  "qbr_date": "2026-04-15",
  "deck_format": "enterprise",
  "slides_generated": 11,
  "slides_requiring_csm_input": 3,
  "data_freshness": {
    "all_current": true,
    "stale_sources": [],
    "oldest_data_point": "2026-04-09"
  },
  "content_summary": {
    "health": { "score": 74, "trend": "improving", "vs_last_qbr": "+6" },
    "usage": { "dau_mau": 0.42, "feature_breadth": 0.65, "trend": "growing" },
    "value": { "headline": "340 hours saved this quarter", "vs_prior_quarter": "+22%" },
    "support": { "tickets": 12, "avg_resolution_hours": 4.2, "csat": 4.6 },
    "benchmark_position": "Above average across key metrics. Top quartile in workflow completions"
  },
  "csm_action_required": [
    "Write strategic recommendations (slide 9)",
    "Review and customise executive summary framing (slide 2)",
    "Prepare discussion questions based on relationship context (slide 10)"
  ],
  "delivery_status": "draft_ready_for_csm_review"
}

Handoff to Human

Confidence and Limitations

• High confidence for data population -- pulling metrics and formatting into slides is deterministic
• High confidence for period-over-period computation -- mathematical comparison with defined windows
• Medium confidence for chart selection and emphasis -- the skill highlights statistically significant changes, but the CSM may want different emphasis based on conversation strategy
• Medium confidence for benchmark context -- peer comparison is factual, but whether a specific benchmark motivates or discourages this customer depends on their competitive mindset
• Low confidence for narrative framing -- the skill generates factual summaries, not persuasive narratives. The CSM adds the story. A QBR deck without narrative is a data dump, not a business review
• Cannot generate the strategic recommendation slides. These require judgment about the account's future direction, relationship dynamics, and what the customer is ready to hear. This is the CSM's highest-value contribution to the QBR
• Cannot determine which slides the customer will care about most. An executive may want to skip straight to the financial summary; a technical lead may want to deep-dive into usage. The CSM adjusts the presentation flow based on the room

Dependencies

Required:

• bi-health-score (health data for trajectory slides)
• bi-usage-monitor (usage data for adoption slides)
• pa-value-reporter (value evidence for ROI slides)
• CRM API (contract data, account context)

Strongly recommended:

• pa-adoption-tracker (feature-level adoption for depth)
• pa-benchmark-engine (peer comparison data)
• lo-milestone-tracker (success plan progress)
• Support platform (support summary data)
• ic-feature-request-tracker (roadmap update status)
• ra-engagement-tracker (engagement context for relationship slides)

Downstream consumers:

• CSM (deck review and customisation -- the most important consumer. The deck is a tool for the CSM, not the final product)
• lo-qbr-orchestrator (deck delivery as part of the QBR lifecycle workflow)
• CRM (QBR activity record with deck link)
• pa-value-reporter (QBR is a validation point for value metrics -- customer reaction feeds back)

References

• references/deck-guidelines.md -- Slide design principles, data visualisation standards, and customer-safe content rules