# Sample output — fictional account

> A worked example the qbr-prep skill anchors against for tone and
> structure. The account name, metrics, and quotes here are fabricated.
> Replace this file with three to five real (anonymized) prior QBRs from
> your CSM team to give the tone-match pass real material to mimic.

# QBR draft — Northwind Logistics — Q1-2026

> Generated 2026-04-30 14:22. Status: complete.
> Missing streams: none.

## Slot: `cover_account_name`

```text
Northwind Logistics
```

## Slot: `cover_quarter`

```text
Q1-2026
```

## Slot: `exec_summary`

```text
- ARR held flat at $480k through Q1; renewal scheduled for Q3-2026.
- Active seats grew from 84 to 112 (33%); WAU grew from 61 to 89 (46%).
- Two of three success-plan goals on-track; one (rep onboarding time) at-risk.
- One open red risk: champion transition in RevOps; AE owns replacement intro.
- Proposed agenda: usage trends, success-plan review, expansion conversation around the warehouse-management module.
```

## Slot: `usage_trend`

```text
Active seats grew 33% quarter-over-quarter (84 to 112) while weekly active usage grew 46% (61 WAU to 89 WAU), indicating per-seat engagement is rising rather than diluting. The growth concentrated in the dispatch and routing feature areas, which together accounted for 71% of key-action volume in March. The reporting feature area remains under-used relative to onboarded seats — a likely topic for the live QBR.
```

## Slot: `top_wins`

```text
- Cut average dispatch latency from 9 minutes to 4 minutes after enabling automated route assignment in February ("This freed an entire shift's worth of dispatcher time" — Ops Manager, Gong call 2026-03-12).
- Closed integration backlog with the warehouse system; 12 of 12 facilities now reporting through the unified dashboard.
- Onboarded the second business unit (Eastern region) ahead of plan; 28 new seats activated in March vs Q2 target of 20.
```

## Slot: `risk_summary`

```text
| Risk | Severity | Mitigation owner | Mitigation |
|---|---|---|---|
| RevOps champion took new role; replacement not yet identified | red | ae | CFO intro scheduled for week of May 6 |
| Rep onboarding time-to-first-deal trending 41 days vs 28-day target | yellow | csm | Targeted enablement session booked for new-rep cohort May 14 |
| Reporting feature adoption flat at 22% of seats | yellow | csm | Office-hours session scheduled June; track adoption pre/post |
```

## Slot: `success_plan_progress`

```text
| Goal | Target | Actual | Status |
|---|---|---|---|
| Reduce rep time-to-first-deal | 28 days | 41 days | at-risk |
| Cut dispatch latency | 5 min | 4 min | achieved |
| Unify reporting across 12 facilities | 12/12 | 12/12 | achieved |
```

## Slot: `expansion_paths`

```text
1. **Warehouse-management module.** Signal: usage. Confidence: high. Three Gong calls in March surfaced unprompted asks for the WMS add-on; Eastern region rollout creates natural anchor. Next step: AE to scope WMS pilot with VP Operations during the live QBR.
2. **Premium support tier.** Signal: persona. Confidence: medium. Champion transition makes premium tier (named CSM, 4-hour SLA) a continuity story. Next step: surface tier comparison in the wrap-up if champion replacement question stays open.
3. **Multi-year renewal at Q3.** Signal: contract. Confidence: medium. Two-year commit unlocks 12% pricing concession; usage growth supports the math. Next step: position with CFO during champion-replacement intro, not in the QBR itself.
```

## Slot: `next_quarter_commitments`

```text
- Drive rep onboarding goal back to on-track via May 14 enablement session
- Confirm replacement RevOps champion by end of May
- Run reporting-feature office hours and track adoption delta through June
- Scope WMS pilot with VP Operations and surface a written proposal by July 1
```

## Slot: `appendix_call_themes`

```text
- "We are getting more out of dispatch than we expected" (Ops Manager, 2026-03-12)
- Three calls surfaced WMS interest unprompted (2026-02-08, 2026-03-19, 2026-03-27)
- One call mentioned competitor evaluation in passing (2026-02-22) — context was board pressure, not active eval; AE to confirm
```