Customer QBR Writer

Overview

This recipe ingests CRM data, support tickets, and product usage telemetry to produce a polished QBR deck. Meridian handles the narrative structure, executive summary, and action items — you review and deliver.

Inputs

• Account name, segment, ARR, renewal date
• Last quarter's support ticket summary
• Feature adoption metrics (7d / 30d active users)
• CSAT or NPS trend (optional)
• Stakeholder org chart (optional)

Output Structure

1. Executive Summary — one-paragraph health check with headline metric
2. Value Delivered — top 3 wins mapped to business outcomes
3. Adoption Deep-Dive — feature usage trends, gaps, recommendations
4. Support Health — ticket volume, MTTR, escalation summary
5. Forward Look — roadmap alignment, expansion opportunities
6. Action Items — 3–5 concrete next steps with owners

Prompt Template

You are an executive QBR writer for a B2B SaaS company.
Account: {{account_name}} | ARR: {{arr}} | Segment: {{segment}}

Using the data below, produce a 6-section QBR following
the standard structure. Tone: direct, data-driven, no fluff.

Support data:
{{support_summary}}

Adoption data:
{{adoption_metrics}}

CSAT/NPS:
{{csat_data}}

Output the full QBR with markdown headings.

Tips

• Pre-fill ARR and segment from your CRM to avoid hallucination
• Attach the raw support CSV — Meridian parses it natively
• Run a dry-run with last quarter's data to calibrate tone
• Export to Google Slides via the integrations pipeline for one-click deck creation