sales-content

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sales Content Management

销售内容管理

Help the user organize, distribute, measure, and govern sales collateral — from building a content library and creating battle cards through auditing content effectiveness and aligning marketing with sales on content needs. This skill is tool-agnostic and applies to any enablement platform (Seismic, Highspot, Showpad, Guru) or general-purpose tool (Google Drive, SharePoint, Notion).
帮助用户对销售素材进行组织、分发、衡量和治理——从构建内容库、创建battle cards,到审计内容有效性、协调营销与销售团队的内容需求。本Skill不绑定特定工具,适用于任何赋能平台(Seismic、Highspot、Showpad、Guru)或通用工具(Google Drive、SharePoint、Notion)。

Step 1 — Gather context

步骤1 — 收集背景信息

Ask the user:
  1. What do you need to do?
    • A) Build a content library from scratch
    • B) Organize/restructure existing content
    • C) Create specific content (battle card, one-pager, case study, playbook)
    • D) Audit content usage and effectiveness
    • E) Set up content governance/workflows
    • F) Improve content findability for reps
    • G) Other
  2. What types of content?
    • A) Battle cards
    • B) One-pagers/datasheets
    • C) Case studies
    • D) Sales decks/presentations
    • E) Playbooks/guides
    • F) ROI calculators/tools
    • G) Email templates
    • H) All of the above
  3. Team size?
    • A) Under 10 reps
    • B) 10-50
    • C) 50-200
    • D) 200+
  4. Current content tool?
    • A) Seismic
    • B) Highspot
    • C) Showpad
    • D) Guru
    • E) Google Drive/SharePoint/Notion
    • F) No dedicated tool
    • G) Other
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
询问用户:
  1. 你需要完成什么任务?
    • A) 从零开始构建内容库
    • B) 组织/重构现有内容
    • C) 创建特定类型内容(battle card、one-pager、案例研究、操作手册)
    • D) 审计内容使用情况与有效性
    • E) 搭建内容治理/工作流
    • F) 提升销售代表的内容查找效率
    • G) 其他
  2. 涉及哪些类型的内容?
    • A) Battle cards
    • B) One-pagers/数据手册
    • C) 案例研究
    • D) 销售演示文稿
    • E) 操作手册/指南
    • F) ROI计算器/工具
    • G) 邮件模板
    • H) 以上所有
  3. 团队规模?
    • A) 少于10名销售代表
    • B) 10-50名
    • C) 50-200名
    • D) 200名以上
  4. 当前使用的内容工具?
    • A) Seismic
    • B) Highspot
    • C) Showpad
    • D) Guru
    • E) Google Drive/SharePoint/Notion
    • F) 无专用工具
    • G) 其他
如果用户的请求已提供大部分此类背景信息,可直接跳至相关步骤。先基于合理假设(需明确说明)给出最佳答案,最后仅询问最关键的1-2个澄清问题——不要要求收集完整背景信息后才给出回复。

Step 2 — Content strategy

步骤2 — 内容策略

Content taxonomy

内容分类体系

Organize content along these dimensions:
  • By buyer journey stage: Awareness → Consideration → Decision → Expansion
  • By persona: C-suite, VP/Director, Manager, Individual contributor, Technical evaluator
  • By use case: Prospecting, Discovery, Demo follow-up, Proposal, Objection handling, Competitive displacement, Renewal
  • By content type: Battle card, One-pager, Case study, Deck, Playbook, Calculator, Template
从以下维度组织内容:
  • 按买家旅程阶段:认知 → 考虑 → 决策 → 拓展
  • 按用户角色:高管层、副总裁/总监、经理、个人贡献者、技术评估者
  • 按使用场景:潜在客户开发、需求探索、演示跟进、提案、异议处理、竞品替代、续约
  • 按内容类型:Battle card、One-pager、案例研究、演示文稿、操作手册、计算器、模板

Content audit framework

内容审计框架

MetricWhat to measureAction threshold
Usage rate% of content used by reps in last 90 days<20% → archive or refresh
Win correlationContent shared in won vs lost dealsLow correlation → rework messaging
Time to findHow long reps spend searching>2 min → improve taxonomy/search
FreshnessDays since last update>180 days → review and refresh
Coverage gapsPersonas/stages with no contentAny gap → prioritize creation
指标衡量内容行动阈值
使用率过去90天内被销售代表使用的内容占比<20% → 归档或更新
赢单相关性赢单与丢单中分享的内容对比相关性低 → 重写信息传递逻辑
查找耗时销售代表搜索内容的时长>2分钟 → 优化分类体系/搜索功能
新鲜度上次更新至今的天数>180天 → 审核并更新
覆盖缺口无对应内容的用户角色/旅程阶段任何缺口 → 优先创建

Content types deep dive

各内容类型深度解析

Battle cards — competitive intelligence one-pagers for reps:
  • Structure: Overview → Strengths/Weaknesses → Landmines (questions to plant) → Objection responses → Win stories
  • Update frequency: Monthly or on competitor changes
  • Length: 1-2 pages max — reps won't read more
One-pagers/datasheets — product/feature summaries for buyers:
  • Structure: Problem → Solution → Key features → Social proof → CTA
  • One per product/use case/persona combination
  • Include a clear "why us" differentiation section
Case studies — customer success stories:
  • Structure: Challenge → Solution → Results (with metrics) → Quote
  • Tag by industry, company size, use case, product
  • Minimum 3 quantified results per case study
Sales playbooks — step-by-step guides for specific scenarios:
  • Structure: When to use → Target persona → Discovery questions → Demo flow → Content to share → Objection handling → Next steps
  • One per major use case or sales motion
  • Include actual talk tracks, not just bullet points
ROI calculators — interactive tools for justifying purchase:
  • Structure: Input fields (current metrics) → Calculations → Output (projected savings/gains)
  • Must be defensible — use conservative assumptions
  • Include methodology explanation for skeptical buyers
Battle cards — 供销售代表使用的竞品情报单页:
  • 结构:概述 → 优势/劣势 → 埋点问题(可抛出的问题) → 异议回复 → 赢单案例
  • 更新频率:每月更新或竞品变动时更新
  • 篇幅:最多1-2页——销售代表不会阅读更长的内容
One-pagers/数据手册 — 供买家参考的产品/功能摘要:
  • 结构:问题 → 解决方案 → 核心功能 → 社交证明 → 行动号召(CTA)
  • 每个产品/使用场景/用户角色组合对应一份
  • 需包含清晰的“为何选择我们”差异化板块
案例研究 — 客户成功故事:
  • 结构:挑战 → 解决方案 → 成果(含指标) → 客户引用
  • 按行业、公司规模、使用场景、产品打标签
  • 每份案例研究至少包含3项量化成果
销售操作手册 — 特定场景的分步指南:
  • 结构:适用场景 → 目标用户角色 → 需求探索问题 → 演示流程 → 需分享的内容 → 异议处理 → 后续步骤
  • 每个主要使用场景或销售流程对应一份
  • 需包含实际话术,而非仅要点列表
ROI计算器 — 用于证明采购合理性的交互式工具:
  • 结构:输入字段(当前指标) → 计算逻辑 → 输出(预计节省/收益)
  • 必须具备说服力——使用保守假设
  • 需为持怀疑态度的买家提供方法论说明

Content governance

内容治理

  • Ownership: Every piece of content needs an owner (person responsible for updates)
  • Review cadence: Quarterly for battle cards, semi-annual for case studies, annual for playbooks
  • Approval workflow: Draft → Review (SME) → Approve (marketing) → Publish
  • Retirement policy: Archive content unused for 6+ months; delete after 12 months archived
  • Version control: Always publish the latest version; prevent reps from sharing outdated content
  • 所有权:每一份内容都需要指定负责人(负责更新的人员)
  • 审核周期:Battle cards每季度审核,案例研究每半年审核,操作手册每年审核
  • 审批流程:草稿 → 审核(领域专家) → 批准(营销团队) → 发布
  • 淘汰政策:未使用6个月以上的内容归档;归档12个月后删除
  • 版本控制:始终发布最新版本;阻止销售代表分享过时内容

Step 3 — Platform-specific guidance

步骤3 — 平台专属指南

In Seismic

Seismic平台

  • Content Library: Organize with Content Profiles (metadata schemas) and Content Classes (taxonomy). Use Predictive Content to surface relevant content to reps based on deal context.
  • LiveDocs: Auto-generate personalized one-pagers, proposals, and datasheets by pulling CRM data into templates. Use LiveDocs Express for quick generation, Process for approval workflows.
  • Analytics: Track content usage, engagement (via LiveSend), and win correlation. Seismic's reporting shows which content is used in won deals.
  • Governance: Use workspaces for content authoring with review/approval workflows before publishing to the library.
  • 内容库:使用Content Profiles(元数据架构)和Content Classes(分类体系)组织内容。利用Predictive Content根据销售机会背景为销售代表推送相关内容。
  • LiveDocs:通过将CRM数据导入模板,自动生成个性化one-pagers、提案和数据手册。使用LiveDocs Express快速生成内容,使用Process管理审批流程。
  • 分析功能:跟踪内容使用情况、互动数据(通过LiveSend)和赢单相关性。Seismic的报告可展示哪些内容在赢单中被使用。
  • 治理:使用工作区进行内容创作,发布到库前需经过审核/审批流程。

In Highspot

Highspot平台

  • SmartPages: Create curated content collections organized by sales play, persona, or deal stage.
  • Spots: Organize content into browsable categories with role-based access.
  • Analytics: Track pitch activity, content engagement, and scorecard metrics.
  • AI recommendations: Highspot's AI surfaces relevant content based on CRM context.
  • SmartPages:创建按销售流程、用户角色或交易阶段分类的精选内容集合。
  • Spots:将内容组织为可浏览的分类,支持基于角色的访问权限。
  • 分析功能:跟踪推介活动、内容互动和评分卡指标。
  • AI推荐:Highspot的AI会根据CRM背景推送相关内容。

In Showpad

Showpad平台

  • Content Management: Organize with channels and collections. Tag content by buyer stage and persona.
  • Shared Spaces: Create buyer-facing content rooms similar to Seismic DSRs.
  • Analytics: Track content usage and engagement across the buyer journey.
  • 内容管理:通过频道和集合组织内容。按买家旅程阶段和用户角色为内容打标签。
  • 共享空间:创建面向买家的内容房间,类似Seismic DSRs。
  • 分析功能:跟踪整个买家旅程中的内容使用情况和互动数据。

In Guru

Guru平台

  • Knowledge Cards: Create bite-sized content cards for battle cards, objection handling, and product info.
  • Verification: Built-in content verification workflow ensures cards stay current.
  • Browser extension: Reps access content in-context without leaving their workflow.
  • 知识卡片:创建用于battle cards、异议处理和产品信息的短内容卡片。
  • 验证机制:内置内容验证流程,确保卡片内容始终最新。
  • 浏览器扩展:销售代表无需离开工作流即可在上下文环境中访问内容。

In Google Drive / SharePoint / Notion

Google Drive / SharePoint / Notion

  • Folder structure: Mirror your taxonomy (by stage → by persona → by type). Use naming conventions religiously.
  • Limitations: No engagement tracking, no content recommendations, no governance workflows. Workable for <20 reps but breaks down at scale.
  • Upgrade path: When reps can't find content or you can't measure usage, it's time for a dedicated enablement platform.
  • 文件夹结构:镜像你的分类体系(按阶段 → 按用户角色 → 按类型)。严格遵循命名规范。
  • 局限性:无互动跟踪、无内容推荐、无治理工作流。适用于少于20名销售代表的团队,但规模扩大后会失效。
  • 升级路径:当销售代表无法找到内容或无法衡量使用情况时,就该切换到专用赋能平台了。

Step 4 — Actionable guidance

步骤4 — 可落地指南

Building a content library from scratch

从零开始构建内容库

  1. Audit: Inventory all existing content across all locations (shared drives, email attachments, rep desktops, Slack messages). Expect to find 2-3x more content than anyone thinks exists.
  2. Score: Rate each piece on usage (is it being shared?), freshness (when was it last updated?), and quality (is it on-message?). Archive anything that fails 2 of 3.
  3. Taxonomy: Define your organizing structure — by buyer journey stage, then persona, then content type. Keep it to 3 levels max or reps won't navigate it.
  4. Migrate: Move surviving content into your taxonomy. Re-tag and rename everything consistently. This is the hardest step — budget 2-4 weeks for a team of 50+ reps.
  5. Governance: Assign owners, set review cadences, define the approval workflow. Without this, you'll be back to chaos in 6 months.
  6. Launch: Train reps on the new library. Show them how to find content in <30 seconds. Get feedback in the first 2 weeks and adjust taxonomy based on search patterns.
  1. 审计:盘点所有位置的现有内容(共享驱动器、邮件附件、销售代表桌面、Slack消息)。预计会发现比预期多2-3倍的内容。
  2. 评分:从使用率(是否被分享)、新鲜度(上次更新时间)、质量(是否符合品牌信息)三个维度为每份内容评分。两项不达标则归档。
  3. 分类体系:定义组织架构——按买家旅程阶段,再按用户角色,最后按内容类型。最多保留3个层级,否则销售代表不会使用。
  4. 迁移:将筛选后的内容移入分类体系。统一重新打标签和重命名。这是最困难的步骤——50名以上销售代表的团队需预留2-4周时间。
  5. 治理:分配负责人,设置审核周期,定义审批流程。没有这些,6个月后会重回混乱。
  6. 上线:培训销售代表使用新库。向他们展示如何在30秒内找到内容。上线前2周收集反馈,根据搜索模式调整分类体系。

Content creation prioritization

内容创建优先级

Focus on the highest-impact content first:
  1. Decision stage — battle cards, ROI calculators, competitive comparisons (these directly influence close rates)
  2. Proposal stage — case studies, one-pagers, reference materials (buyers need validation before signing)
  3. Discovery stage — playbooks, discovery question guides, demo frameworks (improve qualification)
  4. Awareness stage — educational content, industry reports (lower priority for sales content; this is marketing's domain)
优先创建最高影响力的内容:
  1. 决策阶段 — battle cards、ROI计算器、竞品对比(这些直接影响成交率)
  2. 提案阶段 — 案例研究、one-pagers、参考资料(买家签约前需要验证)
  3. 需求探索阶段 — 操作手册、需求探索问题指南、演示框架(提升资格预审效率)
  4. 认知阶段 — 教育内容、行业报告(销售内容中优先级较低;属于营销团队的范畴)

Measuring content ROI

衡量内容ROI

Tie content usage to pipeline and revenue metrics:
  1. Tag content per opportunity: Track which content pieces are shared in each deal
  2. Win rate by content: Compare win rates for deals where specific content was shared vs not shared
  3. Time-to-close impact: Measure whether certain content accelerates deal velocity
  4. Rep adoption: Track which reps use the content library and correlate with their performance
  5. Content-influenced pipeline: Calculate total pipeline value of deals where content was shared
将内容使用情况与销售管道和收入指标关联:
  1. 按机会标记内容:跟踪每个交易中分享的内容
  2. 按内容统计赢单率:对比分享特定内容与未分享的交易的赢单率
  3. 对成交周期的影响:衡量某些内容是否加速交易推进
  4. 销售代表采用率:跟踪哪些销售代表使用内容库,并与他们的绩效关联
  5. 内容影响的销售管道:计算分享内容的交易的总管道价值

Gotchas

注意事项

  • Don't create content without talking to reps first. Claude tends to suggest content based on marketing strategy. The most valuable content addresses what reps actually need — ask your top 5 performers what they wish they had.
  • Don't organize content by department (marketing, product, sales). Organize by how reps search — by deal stage, persona, or use case. Nobody searches "marketing folder."
  • Don't skip the audit before building. Most teams have 60%+ unused content. Building a new library on top of stale content makes findability worse, not better.
  • Don't create battle cards longer than 2 pages. Reps need quick-reference cards they can scan in 30 seconds before a call. Long documents don't get used.
  • Don't forget to measure content effectiveness, not just usage. A battle card used 100 times that doesn't improve win rates needs reworking. Track content's correlation with deal outcomes, not just downloads.
  • 不要在未咨询销售代表的情况下创建内容。 Claude倾向于基于营销策略建议内容。最有价值的内容是解决销售代表实际需求的——询问你的Top5销售代表他们最需要什么。
  • 不要按部门(营销、产品、销售)组织内容。 按销售代表的搜索方式组织——按交易阶段、用户角色或使用场景。没人会搜索“营销文件夹”。
  • 不要跳过审计就直接构建内容库。 大多数团队有60%以上的内容未被使用。在陈旧内容之上构建新库会降低内容可查找性,而非提升。
  • 不要创建超过2页的battle cards。 销售代表需要的是可在30秒内浏览的快速参考卡片。过长的文档不会被使用。
  • 不要只衡量内容使用率,还要衡量有效性。 被使用100次但对赢单率无提升的battle cards需要重写。跟踪内容与交易结果的相关性,而非仅下载量。

Related skills

相关Skill

  • /sales-seismic
    — Seismic platform help (for Seismic-specific content management setup)
  • /sales-coaching
    — Sales coaching and training (content for onboarding and enablement programs)
  • /sales-compete
    — Competitive displacement campaigns (battle cards and competitive content)
  • /sales-proposal-page
    — Proposal page design (Qwilr proposals)
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
    npx skills add sales-skills/sales --skills sales-do
  • /sales-seismic
    — Seismic平台帮助(适用于Seismic特定的内容管理设置)
  • /sales-coaching
    — 销售辅导与培训(适用于入职和赋能项目的内容)
  • /sales-compete
    — 竞品替代活动(适用于battle cards和竞品内容)
  • /sales-proposal-page
    — 提案页面设计(适用于Qwilr提案)
  • /sales-do
    — 不确定使用哪个Skill?该路由器可将任何销售目标匹配到正确的Skill。安装:
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Organizing a messy content library

示例1:整理混乱的内容库

User says: "I need to organize our sales content — we have 500+ docs scattered across Google Drive and no one can find anything" Skill does:
  1. Audits existing content, proposes taxonomy by stage/persona/type
  2. Recommends scoring each piece on usage, freshness, and quality
  3. Suggests migration plan with timeline based on team size
  4. Sets up governance with owners, review cadences, and retirement policy
  5. Recommends upgrading to a dedicated enablement platform for tracking Result: Full content library build plan with taxonomy, migration steps, governance framework, and platform recommendation
用户提问:“我需要整理我们的销售内容——我们有500多份文档散落在Google Drive上,没人能找到任何内容” Skill操作:
  1. 审计现有内容,提出按阶段/用户角色/类型的分类体系
  2. 建议从使用率、新鲜度、质量三个维度为每份内容评分
  3. 根据团队规模建议迁移计划和时间线
  4. 建立包含负责人、审核周期和淘汰政策的治理机制
  5. 建议升级到专用赋能平台以实现跟踪功能 结果:完整的内容库构建计划,包括分类体系、迁移步骤、治理框架和平台建议

Example 2: Creating battle card templates

示例2:创建battle card模板

User says: "Create a battle card template for our top 3 competitors" Skill does:
  1. Provides battle card structure (Overview → Strengths/Weaknesses → Landmines → Objection responses → Win stories)
  2. Recommends 1-2 page max length for rep usability
  3. Sets monthly update cadence with assigned ownership
  4. Includes competitive research framework for populating the cards
  5. Suggests distribution strategy (enablement platform, Slack alerts on updates) Result: Battle card template with structure, update cadence, ownership model, and distribution plan
用户提问:“为我们的Top3竞品创建battle card模板” Skill操作:
  1. 提供battle card结构(概述 → 优势/劣势 → 埋点问题 → 异议回复 → 赢单案例)
  2. 建议最多1-2页的篇幅以提升销售代表易用性
  3. 设置每月更新周期并分配负责人
  4. 提供用于填充卡片的竞品研究框架
  5. 建议分发策略(赋能平台、更新时的Slack提醒) 结果:包含结构、更新周期、所有权模型和分发计划的battle card模板

Example 3: Measuring content effectiveness

示例3:衡量内容有效性

User says: "How do I measure which content actually helps close deals?" Skill does:
  1. Sets up content-to-deal correlation tracking (tag content shared per opportunity)
  2. Defines key metrics: win rate by content piece, time-to-close impact, rep adoption
  3. Distinguishes usage metrics (downloads, views) from effectiveness metrics (win correlation)
  4. Recommends content-influenced pipeline calculation
  5. Creates a quarterly content review process based on effectiveness data Result: Content measurement framework with specific metrics, tracking approach, and review cadence
用户提问:“我如何衡量哪些内容真正有助于成交?” Skill操作:
  1. 搭建内容与交易的相关性跟踪(按机会标记分享的内容)
  2. 定义关键指标:单内容赢单率、对成交周期的影响、销售代表采用率
  3. 区分使用率指标(下载量、浏览量)与有效性指标(赢单相关性)
  4. 建议计算内容影响的销售管道
  5. 基于有效性数据创建季度内容审核流程 结果:包含具体指标、跟踪方法和审核周期的内容衡量框架

Troubleshooting

故障排除

Reps don't use the content library

销售代表不使用内容库

Cause: Content is hard to find, irrelevant, or outdated. Reps default to their own saved versions or ask colleagues directly. Solution: Audit usage to identify what's being ignored. Simplify taxonomy to 3 levels max. Add search functionality. Involve reps in content creation — they're more likely to use content they helped shape. Survey top performers on what's missing.
原因:内容难以查找、不相关或过时。销售代表会默认使用自己保存的版本或直接询问同事。 解决方案:审计使用率以识别被忽略的内容。将分类体系简化为最多3个层级。添加搜索功能。让销售代表参与内容创建——他们更可能使用自己参与塑造的内容。调查Top销售代表的需求缺口。

Marketing creates content reps don't want

营销团队创建的内容不受销售代表欢迎

Cause: Misalignment between what marketing thinks reps need and what they actually use in deals. Marketing often creates awareness-stage content when reps need decision-stage content. Solution: Run a content needs survey with your top 10 performers. Compare against what marketing is producing. Create a shared content calendar with joint prioritization. Have reps review content before publishing.
原因:营销团队认为销售代表需要的内容与他们实际在交易中使用的内容不一致。营销团队常创建认知阶段的内容,而销售代表需要决策阶段的内容。 解决方案:向Top10销售代表开展内容需求调研。对比调研结果与营销团队的产出。创建共享内容日历并联合确定优先级。让销售代表在内容发布前审核。

Content goes stale quickly

内容很快过时

Cause: No governance process. Content is created and never updated. Competitive battle cards reference features from 2 years ago. Case studies cite customers who churned. Solution: Assign an owner to every piece of content. Set review cadences (monthly for battle cards, quarterly for case studies). Automate expiration alerts — content not reviewed within its cadence gets flagged. Archive anything not updated within 2x its review cadence.
原因:无治理流程。内容创建后从未更新。竞品battle cards引用2年前的功能。案例研究提及已流失的客户。 解决方案:为每份内容分配负责人。设置审核周期(battle cards每月,案例研究每季度)。自动发送过期提醒——未在周期内审核的内容会被标记。归档超过2倍审核周期未更新的内容。