Back to Details

sales-account-intelligence

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sales Account Intelligence

销售账户情报

Workflow

工作流

Use search and extract to produce fast, useful sales account context with cited sources; use map or crawl only when a known company site needs scoped navigation. Keep this skill focused on research planning, query construction, source selection, and sales-ready synthesis; execution mechanics should come from companion endpoint skills.
Treat the guidance below as base guidance; adapt it to the user's request when appropriate.
  • Define the account, audience, sales motion, geography, and meeting or outreach goal.
  • Split research into short subqueries under 400 characters: company overview, recent news, products, customers, leadership, funding/financials, hiring, partnerships, pain points, and relevant initiatives.
  • Use search for discovery, then filter by source quality before extracting.
  • Extract the strongest sources: official website, newsroom, product pages, customer stories, investor/press pages, credible news, job postings, and relevant executive profiles.
  • Use site navigation when the company site is large and useful pages are hard to find.
  • Collect scoped site sections only when the user needs broad coverage of customers, case studies, news, products, solutions, or careers.
使用 search 和 extract 快速生成实用且有来源引用的销售账户背景；只有在需要对一个已知公司的网站进行限定范围导航时，才使用 map 或 crawl。确保此 skill 专注于研究规划、查询构建、来源选择和面向销售的综合整理；执行机制应由配套的 endpoint skills 提供。
以下指导作为基础建议；应根据用户请求进行调整。
  • 明确账户、受众、销售方式、地理区域以及会议或外联目标。
  • 将研究拆分为少于 400 个字符的简短子查询：公司概况、最新新闻、产品、客户、领导层、融资/财务、招聘、合作伙伴、痛点和相关计划。
  • 使用 search 进行发现，然后在 extract 前按来源质量筛选。
  • 提取最强来源：官方网站、新闻中心、产品页面、客户案例、投资者/新闻页面、可信新闻、职位发布和相关高管简介。
  • 当公司网站规模较大且难以找到有用页面时，使用站点导航。
  • 仅当用户需要广泛覆盖客户、案例研究、新闻、产品、解决方案或招聘时，才收集限定范围的网站板块。

Research Budget

研究预算

  • Start with a small focused search set: account overview, recent triggers, product/initiative context, and buyer/pain-point evidence.
  • Extract only the strongest sources before drafting the brief.
  • Add more searches only for named gaps that block the brief, such as missing trigger events or missing official product context.
  • Do not use map until search finds the company domain and there is a specific buried page type to locate.
  • Do not use crawl for first-pass account prep unless the user explicitly asks for a site scan.
  • 从一组小而聚焦的搜索开始：账户概况、最新触发因素、产品/计划背景，以及买家/痛点证据。
  • 在起草简报前，仅提取最强来源。
  • 只有在出现阻碍简报的明确缺口时，才增加搜索，例如缺少触发事件或官方产品背景。
  • 在 search 找到公司域名且有明确的埋藏页面类型需要定位之前，不要使用 map。
  • 除非用户明确要求扫描站点，否则不要在账户准备的第一轮使用 crawl。

Capability Guidance

能力使用指南

  • Use search for most account briefs, meeting prep, outreach research, and trigger-event checks.
  • Use extract on selected official pages, newsroom posts, customer stories, credible news, job postings, and executive profiles.
  • Use map when the company domain is known but important pages are buried.
  • Use crawl for account site scans only after narrowing to sections that support the sales goal.
  • Use research only when the user asks for a deep strategic account report.
  • 对大多数账户简报、会议准备、外联研究和触发事件检查，使用 search。
  • 对选定的官方网站、新闻中心帖子、客户案例、可信新闻、职位发布和高管简介，使用 extract。
  • 当公司域名已知但重要页面埋藏较深时，使用 map。
  • 仅在将范围缩小到支持销售目标的板块后，才对账户网站扫描使用 crawl。
  • 仅当用户要求深度战略账户报告时，才使用 research。

Query And Source Guidance

查询与来源指南

  • Include company name, aliases, product names, executive names, industry terms, geography, and the sales motion in separate subqueries.
  • For trigger events, use explicit recency language and search for funding, hiring, partnerships, launches, expansion, regulation, incidents, and leadership changes.
  • Prioritize official company pages, newsroom posts, customer stories, product pages, investor or press pages, credible news, job postings, and relevant executive profiles.
  • Treat LinkedIn-style profile snippets, unsourced lists, and old syndicated pages as lower confidence.
  • Report failed or inaccessible sources when they affect trigger events, official pages, customer evidence, or buyer context.
  • 在单独的子查询中包含公司名称、别名、产品名称、高管姓名、行业术语、地理区域和销售方式。
  • 对于触发事件，使用明确的时效性语言，并搜索融资、招聘、合作伙伴关系、产品发布、扩张、监管、事故和领导层变动。
  • 优先使用公司官方页面、新闻中心帖子、客户案例、产品页面、投资者或新闻页面、可信新闻、职位发布和相关高管简介。
  • 将 LinkedIn 风格的个人资料摘要、无来源列表和过时的转载页面视为较低置信度。
  • 当失败或无法访问的来源影响触发事件、官方页面、客户证据或买家背景时，予以报告。

Output Template

输出模板

Use this markdown structure and keep it practical:
markdown
undefined
使用此 Markdown 结构并确保实用：
markdown
undefined

Account Brief: <company>

账户简报：<company>

Account Snapshot

账户概览

  • What they do:
  • Size/market/geography:
  • Relevant products or business lines:
  • 业务内容：
  • 规模/市场/地理区域：
  • 相关产品或业务线：

Trigger Events

触发事件

  • <event>: <why it matters> (source)
  • <事件>：<为何重要> (来源)

Business Priorities And Likely Pain Points

业务重点与潜在痛点

  • Priority:
  • Evidence:
  • Sales relevance:
  • 优先级：
  • 证据：
  • 销售关联性：

Buyer And Executive Context

买家与高管背景

  • Person/team:
  • Relevant context:
  • Confidence:
  • 人员/团队：
  • 相关背景：
  • 置信度：

Outreach Angles

外联切入点

  • Angle:
  • Supporting evidence:
  • Discovery question:
  • 切入点：
  • 支持证据：
  • 探索问题：

Source Gaps

来源缺口

  • <missing or uncertain item> 

Keep claims practical. Do not invent budget, intent, internal priorities, or buyer names when sources do not support them.
  • <缺失或不确定项>

保持论断实用。来源不支持时，不要虚构预算、意图、内部优先事项或买家姓名。