Exec Brief

作者 Zoominfod07402feb2b9無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Produce a succinct one-pager for an executive dropping into a call with zero context. Blends account_research (who they are, deal state), conversation_intelligence (what has been discussed and what is open), and contact_research (who is in the room). Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup); name the key attendees if known. Use when someone says "brief the VP for the Acme call", "exec one-pager for tomorrow", "my SVP is joining cold", or needs a tight pre-call brief for a senior stakeholder. Built to be read in two minutes.

AI 產生的概覽

依據調研與對話資料,為高階主管產出一頁式的通話前客戶簡報。

功能
為毫無背景資訊就加入通話的高階主管產出精簡的一頁式簡報。它會以 ZoomInfo 公司 ID 或名稱/網域確認客戶,再整合客戶調研、限定該客戶的對話情報,以及針對已知出席者的聯絡人調研。輸出採用固定格式:核心結論、目前進展、與會人員、高階主管應採取的行動,以及應避開的雷區。
適用情境
適用於高階利害關係人需要一份緊湊的通話前簡報時,例如為某客戶通話向副總裁做簡報,或資深副總臨時加入的情況。設計目標是約兩分鐘讀完。
執行需求
需要 ZoomInfo 能力:account_research、contact_research 與 conversation_intelligence,其中後者需要至少一個已連接的會議或電子郵件來源。這些會消耗 AI 額度。此技能不隨附指令碼,僅為指示文件。

Exec Brief

One page an executive can absorb in the elevator: who, why now, where we stand, and the one thing to do in the room.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source; account_research, contact_research, and conversation_intelligence consume AI credits. If no conversation data exists, build from research and note that the "where we stand" view is research-based only, pointing the user to their ZoomInfo admin.

Input

Provided via $ARGUMENTS:

  • Account (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via search_companies.
  • The exec and the meeting (recommended) — who is being briefed, the meeting's purpose, and the attendees, so the one-pager is framed for their role.

Workflow

  1. Resolve the account (and key attendees, if named). Use ZoomInfo IDs directly, or resolve via search_companies / search_contacts.
  2. Gather, then compress. Run account_research (company + deal context) and account-scoped conversation_intelligence (recent state, open threads, commitments) in parallel. Run contact_research only for attendees the user named or that research surfaces as the key deal contacts; if no attendees are known, ask before spending contact_research credits rather than researching the whole account. Keep CI scoped to the account; it sees only the last few engagements.
  3. Write for an exec. Ruthlessly compress to one page. Lead with why this account matters and why now. Give the exec the single most useful thing to do or say, and the landmines to avoid. Cut firmographic detail that does not change how they show up. Every line earns its place; attribute the relationship claims.

Output Format

Exec brief — [Company]

Bottom line (2-3 sentences) — who they are, why this meeting matters, and where the relationship stands right now.

Where we stand — 2-3 bullets on the deal/relationship state and what is currently open (from CI + research).

In the room — the attendees in one line each: name, role, and what they care about.

Your move — the one thing for the exec to do or say to move this forward.

Landmines — one or two things to avoid (a sore point, a competitor, an unresolved issue), each with a reason.

Keep the whole thing to roughly one page. If a section has nothing high-signal, drop it rather than padding.

When there is no data

If conversation data is unavailable, build the one-pager from research and state that the current-state view is not grounded in recent conversations.

來源與署名

來源:Zoominfo/zoominfo-mcp-plugin位於skills/exec-brief提交d07402f

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架