# Quarterly Business Review ## {Account Name — Not Provided} — {Quarter Not Specified, Year 1 of 3-Year Contract} --- ### CARD 1 — EXECUTIVE SUMMARY Overall status: **STABLE — MONITOR**. Usage and support metrics this quarter are strong and fully documented — 40% QoQ usage growth, all onboarding milestones hit on schedule, zero critical incidents. But two of the five health dimensions (Sentiment, Stakeholder Engagement) rest on thin or missing evidence, and both gaps sit directly under next quarter's expansion plans. **The single most important thing to raise in the meeting:** the Finance Director — the stakeholder next quarter's 15-seat expansion depends on — is aware of the product but not yet using it, and there is no documented sentiment data from anyone on the account beyond the champion relationship. Neither is a red flag on its own, but both should be surfaced and addressed before treating the expansion goal as on-track. --- ### CARD 2 — VALUE DELIVERED SUMMARY - **Usage grew 40% quarter-over-quarter** (DOCUMENTED — Usage Data). No decline in any module was reported this quarter, so this stands as a clean win within its documented scope. - **All 3 onboarding milestones completed on schedule** (DOCUMENTED — Milestone Tracking). - **2 support tickets filed, both resolved within SLA; no critical incidents** (DOCUMENTED — Support Ticket Log). Scope note: all of the above reflects usage within the VP of Operations' organization. No usage data exists yet for the Finance team — that's not a decline, it's simply outside the current footprint, and should not be implied as already-in-progress adoption. No documented data supports any sentiment-based "win" (e.g., customer satisfaction, perceived value) this quarter — none is claimed, since none was supplied. --- ### CARD 3 — HEALTH SNAPSHOT DIAGNOSTIC | Dimension | Score | Status | Rationale | |---|---|---|---| | Usage Health | 5 | HEALTHY | 40% QoQ growth, all onboarding milestones on schedule (DOCUMENTED — Usage Data, Milestone Tracking) | | Support Health | 5 | HEALTHY | 2 tickets, both resolved within SLA, no critical incidents (DOCUMENTED — Support Ticket Log) | | Sentiment Health | UNKNOWN | UNKNOWN | No survey, NPS, or verbatim sentiment data supplied. Strong usage and on-time milestones are behavioral proxies, not sentiment evidence — not scored as healthy on that basis | | Commercial Health | 3 | STABLE — MONITOR | Year 1 of a 3-year contract with renewal in 8 months (DOCUMENTED — Relationship Context); no billing/expansion data yet, only planned expansion goals — a plan is not evidence of realized commercial health | | Stakeholder Engagement Health | 3 | STABLE — MONITOR | Champion (VP of Operations) highly engaged; Finance Director aware but not using; IT Security approved rollout but low ongoing engagement (DOCUMENTED — Stakeholder Map) | | Renewal Risk Amplifier (OPERATIONAL EXTENSION — NOT PART OF THE HEALTH SCORE) | MODERATE | — | Renewal is 8 months out and two open engagement gaps (Finance Director, IT Security) map directly onto stakeholders required for next quarter's planned expansion and automation pilot | **Core Health Reading:** The account is performing well on the dimensions with hard data (Usage, Support) but has no evidence base for Sentiment, and a mixed picture on Stakeholder Engagement and Commercial Health. Nothing here indicates active risk, but nothing yet documents readiness for the two next-quarter goals either. --- ### CARD 4 — OPEN ISSUES & RISKS | Issue | Impact | Owner | Target Resolution | |---|---|---|---| | No documented sentiment data on the account | Cannot confirm customer satisfaction ahead of the renewal conversation; team beliefs about satisfaction would be TO BE CONFIRMED WITH CUSTOMER, not fact | CSM | Before next QBR | | Finance Director aware of product but not yet using it | Directly blocks or slows the planned 15-seat finance team expansion | Account team + VP of Operations (champion) | Next quarter, ahead of expansion push | | IT Security has low ongoing engagement since initial rollout approval | Could slow or block security review needed for the automation feature pilot | Account team | Before automation pilot kickoff | | Commercial Health scored STABLE rather than HEALTHY due to lack of realized expansion/usage-value evidence | Renewal conversation in 8 months would rely on planned (not yet documented) expansion as its main growth story | Account executive | Before renewal date | --- ### CARD 5 — STAKEHOLDER ENGAGEMENT MAP | Stakeholder | Role | Engaged This Quarter? | Note | |---|---|---|---| | VP of Operations | Champion | Yes — highly engaged | Primary driver behind usage growth and on-schedule onboarding | | Finance Director | Aware, not yet using product | No | Known decision-relevant contact for next quarter's finance-team expansion goal — flagged here per engagement gap, not buried in prose | | IT Security | Approved initial rollout | Low ongoing engagement | Approved rollout but has not been actively engaged since; relevant to the upcoming automation feature pilot, which may require a security review | --- ### CARD 6 — NEXT-QUARTER PLAN | Goal | Success Metric | Owner | |---|---|---| | Expand usage to the Finance team (+15 seats) | Seats activated and active usage recorded among Finance users | Account team + VP of Operations (champion) | | Pilot the new automation feature | Pilot completed with defined adoption criteria (e.g., % of target workflows automated) | Account team + customer technical lead | | Re-engage Finance Director and IT Security ahead of the above two goals | At least one direct touchpoint logged with each this quarter | Account team | --- ### CARD 7 — TALKING-POINT SCRIPT - Open with the documented win: 40% QoQ usage growth and all 3 onboarding milestones hit on schedule — no caveats needed here. - Note support health is clean: 2 tickets, both resolved within SLA, zero critical incidents. - Name the Finance team expansion goal, then directly ask the VP of Operations to help bring the Finance Director into a working session before the 15-seat rollout begins. - Ask, rather than assume, how the Finance Director and broader team feel about the product — there's no sentiment data on file, so this should be treated as an open question, not confirmed. - Raise the automation feature pilot and check whether IT Security will need to re-engage for a security review before piloting. - Acknowledge the renewal is 8 months out and frame the next two quarters as the window to convert planned expansion into documented usage before that conversation. - Close by confirming ownership and timing on the three next-quarter goals. --- ### CARD 8 — RENEWAL RISK FLAG Renewal is 8 months away. Two open issues from Card 4 — the Finance Director's lack of engagement and IT Security's low ongoing engagement — directly overlap with the renewal window, because both stakeholders are needed for the very growth story (finance expansion, automation pilot) that would support a strong renewal case. Per the Renewal Risk Amplifier (OPERATIONAL EXTENSION — NOT PART OF THE HEALTH SCORE), this is rated **MODERATE**: not urgent enough to signal renewal jeopardy today, but the runway is finite — if these engagement gaps aren't closed in the next one to two quarters, the account team would be heading into the renewal conversation with only Year 1's usage numbers and no documented expansion evidence. --- ### CARD 9 — METHOD NOTE This document is a preparation aid for the account team ahead of a live QBR conversation — it is not a certified account status report. Scoring follows the five-dimension Account Health Framework (Usage, Support, Sentiment, Commercial, Stakeholder Engagement), extended with the Renewal Risk Amplifier, which is explicitly a non-scoring operational lens used only to set urgency framing in Card 8, not to adjust any dimension's score. The supplied stakeholder map was used directly in Card 5 and to identify the engagement gaps in Cards 4 and 8; the supplied next-quarter goals were used as the basis for Card 6 and to identify which open stakeholder gaps are most load-bearing for those goals. No claim in this document is marked TO BE CONFIRMED WITH CUSTOMER because no unverified "win" was supplied in the account data — but any belief the account team holds about customer sentiment, satisfaction, or intent that isn't backed by usage, billing, or ticket data should be treated the same way if raised live: validated in the meeting, not presented as settled fact. --- **VERDICT: STABLE — MONITOR — driven by Stakeholder Engagement Health and the absence of any documented Sentiment Health data, both of which sit under the next-quarter expansion goals rather than reflecting any current negative signal.**