--- name: account-brief description: Builds a one-screen account briefing for a company by combining CRM firmographics, deal and engagement history, key contacts, and recent web research into one recommended angle. Use when the user asks for an "account brief", "brief me on this company", "what's the story on Acme", prep for a QBR, or context before ABM outreach on a named account. license: MIT compatibility: Requires a connected CRM and web search. Read-only. metadata: author: Builder.org version: 2.0.0 persona: Strategic Steve, Marketing Meg rave: R4 A4 V4 E3 category: crm --- # Account Brief ## What it does One screen on a company: who they are, where the relationship stands, what changed recently, and the single best reason to engage now. Built for the ten minutes before a QBR, an ABM push, or a re-engagement decision. It reads your CRM and the web; it never writes anything. ## When to use - "Brief me on [company]", "account brief for Acme", "what's the story on [account]". - "Prep me for the QBR with [company]", "context on this account before I reach out". - Not for a specific person before a specific meeting; that job belongs to `pre-meeting-brief`. Not for a person you have no relationship with; that is `prospect-intelligence-deep-dive`. ## Inputs A company name or domain. That is the whole form. Everything else comes from your CRM and web research. Any CRM your assistant can read works (HubSpot, Salesforce, or similar); the skill only needs companies, contacts, deals, and engagements. Optional: what the engagement is for (QBR, expansion, win-back), which sharpens the angle. ## The bar - The brief fits on one screen. If it does not, cut the weakest item, not the formatting. - Every "what's new" item carries a date and a source. An undated signal is a rumor. - The recommended angle is one reason to engage now, tied to a named signal. A list of three angles is a refusal to decide. - Facts and inferences stay visibly separate. If the data is thin, the brief says so instead of widening the adjectives. ## Workflow 1. **Resolve the company.** Find it in the CRM by name or domain. Pull firmographics (industry, size, region) and fill gaps from the web. If two records match, pick the one with engagement history and name the other. 2. **Map the relationship.** Owner, key contacts with roles, open deals with stage and amount, past deals with outcomes, and the last touch (date and channel). Cap contacts at three: the champion, the decision-maker, the most recent voice. More is a directory, not a brief. 3. **Pull what changed.** Web research over the last 90 days: funding, leadership moves, product launches, hiring surges, market pressure. Rank by relevance to the relationship, keep the top three, date each one. 4. **Choose the angle.** Cross the relationship state with the freshest signal and commit to one reason to engage now, stated in two sentences: why now, and the opening move. If the engagement purpose was given, aim the angle at it. 5. **Name the risks.** One or two open questions or watch-outs: an unanswered thread, a stale champion, a signal that cuts both ways. 6. **Assemble the brief** in the output format, tightest version that survives. ## Output ``` ## [Company] account brief **Profile:** [industry · size · region] **Relationship:** [owner] · [open deal + stage + amount, or "no open deal"] · last touch [date, channel] ### Key contacts - [Name, title]: [one-line engagement note] ### What's new - [Dated signal with source] ### The angle [Two sentences: why engage now, and the opening move.] ### Watch-outs - [Open question or risk] ``` ## Worked example ``` Fictional example. Never reuse these names or numbers in real output. ## Meridian Freight account brief **Profile:** regional logistics · ~140 employees · Midwest US **Relationship:** owned by Sam T. · open deal "Meridian TMS rollout" (Proposal, $48k) · last touch Jan 22, email from their ops director ### Key contacts - Elena Vasquez, Director of Operations: champion, replied to 6 of last 7 emails - Rob Kessler, CFO: joined one call in December, asked about payback period, silent since - Marcus Webb, dispatch lead: day-to-day user voice, invited us to shadow a shift ### What's new - Feb 3: Meridian announced a second distribution hub in Columbus (company newsroom) - Jan 28: posted 4 dispatcher openings, up from 0 in December (careers page) - Jan 15: their largest competitor was acquired by a national carrier (Transport Topics) ### The angle The Columbus hub means their current dispatch process has to scale in the next two quarters, which is exactly the pain the open proposal solves. Bring the hub into the QBR as the reason to close now, and put the payback math in front of Rob, whose silence is the real blocker. ### Watch-outs - Rob went quiet after the pricing call. Confirm the CFO question was answered, not dodged. - The proposal predates the hub announcement; the scope may now be undersized. ``` ## Never - Never invent or embellish a signal. No date and source, no inclusion. - Never recommend three angles. Choose one; put the runner-up in watch-outs if it truly matters. - Never pad a thin brief with generic industry prose. Short and honest beats full and hollow. - Never quietly skip the relationship section when the CRM is empty. Say "no history in the CRM" and lead with web research instead. ## Recovery - Obscure company, thin web results: say confidence is low, lean on the CRM history, and make the angle relationship-based (an anniversary, an unanswered thread, a renewal window). - No CRM record: build the outside-in version (profile, news, angle), label it "no CRM history", and suggest which contact to create first. - Signals conflict (growth news and layoff news): show both with dates and let the angle name the tension honestly; that candor is often the best opener. - Nothing happened in 90 days: widen to 12 months once, say you did, and prefer a relationship angle over a stale news angle.