Decision Process Mapper

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

Map a prospect's buying process as voiced on recent calls — their stated decision criteria, timeline, steps, and approvers. Uses conversation_intelligence over an account's recent engagements, with account_research for stakeholder context. Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup). Use when someone asks "what's their buying process", "who actually signs off", "what's the timeline and what do they need to decide", or wants to qualify a deal against MEDDIC-style criteria. Captures only what was actually stated; gaps are marked as unknown rather than inferred.

AI 產生的概覽

根據近期銷售對話,梳理客戶明確表達的採購流程——決策標準、步驟、時程與簽核人。

功能
根據客戶在近期通話與郵件中實際說過的内容,還原其採購方式,涵蓋決策標準、評估步驟、時程、預算或採購流程,以及決策參與者。它透過 ZoomInfo 公司 ID 或名稱/網域查詢來定位客戶,再借助對話智慧與客戶研究填入決策流程表。每個欄位都對應到來源片段,未提及的內容會標示為未說明,而非推論得出。它也會列出最大的資訊缺口,以及下次通話應提出的問題。
適用情境
當有人詢問客戶的採購流程、誰真正簽核,或時程與決策需求是什麼時使用。它也適合依 MEDDIC 類標準評估商機。它適用於已有對話紀錄連結的客戶;若沒有,只能產出有限的利害關係人檢視。
執行需求
需要 conversation_intelligence 與 account_research 工具、至少一個已連接的會議或郵件來源,以及用於客戶查詢的 ZoomInfo 公司 ID 或名稱/網域。這些工具會消耗 AI 額度。不附帶指令碼,僅為說明文件。

Decision-Process Mapper

Reconstruct how the prospect actually buys, from what they have told you: criteria, steps, timeline, and the people who decide.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source; conversation_intelligence and account_research consume AI credits. If no conversation data exists, build what you can from account_research and mark the rest unknown, 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.
  • Framework (optional) — e.g. "MEDDIC", "just the approvers and timeline". Shapes which fields to foreground.

Workflow

  1. Resolve the account. Use the ZoomInfo ID directly, or resolve a name/domain via search_companies.
  2. Extract the process. Run conversation_intelligence scoped to the account, asking what the prospect has said about how they will decide: the decision criteria, the evaluation steps, the timeline and any deadlines, the budget or procurement process, and who is involved in or approves the decision. Run account_research for the org/stakeholder picture. Keep CI scoped to one account; it sees only the last few engagements and cannot topic-search, so map what was said, not the whole sales cycle.
  3. Map, and mark gaps honestly. Assemble the process. For anything not actually stated in conversation, label it not stated rather than inferring it. Distinguish a named approver from a guessed one. Tie each filled field to the source moment.

Output Format

Decision process — [Company]

ElementWhat they saidSource / status
Decision criteria
Evaluation steps
Timeline / deadline
Budget / procurement
Decision-makers & approvers
Champion

Use not stated in any cell the conversations did not cover.

Biggest gaps — the two or three unknowns that most need confirming, and a question to surface each on the next call.

When there is no data

If conversation data is unavailable, present the account_research stakeholder view, mark the process fields unknown, and note the read is limited without connected conversation history.

來源與署名

來源:Zoominfo/zoominfo-mcp-plugin位於skills/decision-process-mapper提交d07402f

授權條款: 無授權條款

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

檢舉或申請下架