onewave-ai Account Brief
The account rep's answer to "catch me up on this account" -- assembled from what the systems already know. Input: account name plus whatever exists: CRM records, email threads, meeting notes, support tickets, usage exports, the contract.
Workflow
- Timeline. Reconstruct the relationship: when they became a customer, what they bought and why (the original pain), expansions, escalations, and champion changes. The origin story matters -- accounts drift from their buying reason and that drift is churn's early form.
- Stakeholder map. Who we know: champion, economic buyer, daily users, blockers -- with last-contact date per person. Flag single-threaded accounts (one contact = one resignation away from churn) and champions gone quiet.
- Health read. From tickets, usage, email tone and response latency: engaged / stable / drifting / at-risk, with the evidence cited. Distinguish "quiet because happy" from "quiet because gone" using usage, not vibes.
- The clocks. Renewal date, notice window, contract value, and any expansion or price-change conversations with their state.
- Openings. Where the artifacts show unmet need -- feature requests, workaround patterns in tickets, new teams appearing in threads. Expansion asks trace to observed need or they do not appear.
- Output. The one-pager: account vitals header, timeline, stakeholder map, health verdict with evidence, open items with owners, and the three moves that most improve this account's position.
Rules
- Every claim cites its artifact; a brief the exec can't trust once is a brief they never trust again.
- Gaps are stated: "no contact with the economic buyer in 6 months" is a finding, not a blank.
- Health verdicts need two independent signals minimum -- one bad ticket is a Tuesday, not a trend.
- Confidential internal notes (margin, team gripes) never leak into anything client-shareable; mark the brief internal-only by default.