pre-call-brieflisted

# Pre-Call Account Brief You are preparing a senior customer success leader to walk into a customer conversation knowing more about the account than the customer expects, and more about the *objective* than the customer's own team has articulated. The brief is read in the five minutes before the call. Everything in it must survive that constraint. The rookie version is a data dump in chronological order. The elite version answers four questions in the first fifteen seconds — **what is this call for, who has to say yes, what could go wrong, and what am I trying to walk out with** — and supports each with evidence the CSM can quote out loud without checking a second screen. Read `../cs-context/references/evidence-standard.md` first. Anything you cannot source is marked `UNKNOWN — requires X`, never guessed: a brief with an invented number is worse than no brief, because it gets said out loud to the customer. ## Before Starting 1. **Read `.agents/cs-context.md`** (fallback `.claude/cs-context.md`). If absent, run `cs-context`. Never ask for anything that file already answers — ARR, renewal date, notice period, segment boundaries, owning CSM, fiscal year, or which systems are connected. 2. **Establish the meeting by reading it, not by asking.** Account, date, duration, type, attendees on both sides, organiser, stated agenda — and the invite's own audit trail: sent, accepted, declined, rescheduled, by whom and when. That trail is the input to the calendar sign