Communitygithub.com

cbrock84/sales-enablement

构建销售团队所需的所有销售资料——推销演示文稿、一页纸简介、异议处理方案、竞争对战卡、演示脚本和案例研究。用于创建或修复销售材料、为竞争交易做准备、构建演示流程、记录异议应答,或诊断推销转化率低的原因。

sales-enablement 是什么?

该技能旨在解决销售过程中的一个核心问题:销售资料只有在解决销售人员的实时对话痛点时才会被真正使用,否则会被遗忘。它引导用户首先精准定位交易在哪个环节停滞(首次通话、演示后、定价环节、安全审查或是决策者审批),并针对不同环节提供差异化的补救策略,避免盲目创建精美的无用材料。技能涵盖了销售团队所需的核心资料集,包括结构化的推销演示文稿、可在无背景说明下独立传播的一页纸、尊重客户真实异议的应答方案、客观描述竞品优劣的对战卡、以及包含可验证数据案例的研究报告。此外,技能还强调了演示应聚焦于客户可见的价值结果而非产品界面,并为每个资料资产设定负责人和定期审查日期,以防止信息过时,最终确保销售赋能落到实处——即销售人员在真实交易中实际使用这些材料。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

销售赋能

只有当销售材料能解决销售人员在实际对话中遇到的问题时,才会被真正使用。除此之外,一切都会被归档并遗忘。

了解交易实际停滞的环节

在制作任何材料之前,先找出交易在哪个环节停滞:首次通话、演示之后、定价环节、安全审查、还是决策者审批。每个停滞环节都有不同的应对方法,而针对错误的环节构建材料,只会产生设计精美却无人问津的资料。

核心资料集

推销演示文稿 —— 一个结构,而非脚本。结构应包括:买家能识别的问题、当前方法为何失败、你的差异化方案、证据、商业条款以及下一步行动。十到十五页,每页都有一个核心观点标题。

一页纸简介 —— 供支持者转发给那些你永远不会见到的内部人员。它必须能在没有背景说明和主讲人的情况下独立传达信息。这通常是最具杠杆价值的资产,却也是最容易被忽视的。

异议处理方案 —— 用客户实际使用的语言表达的真实异议,回应需先承认异议的合理部分。否认异议的回应会被视为回避,并终止信任。

对战卡 —— 针对每个竞争对手:他们真正擅长的领域、你的优势所在、需要避免的陷阱,以及当客户提及对手时应如何回应。宣称你在所有方面都获胜的对战卡会被销售人员忽视,因为他们更了解实际情况。

案例研究 —— 情境、变化、可衡量的结果,采用买家的语言表述。一个可验证的数据胜过一页形容词。

演示

演示的是结果,而非界面。从价值可见的地方开始,而不是从登录和设置开始。

根据客户告诉你的问题定制演示内容——展示所有功能的特性演示恰恰证明你没有认真倾听。为总是会出错的三个方面做好准备,并知道当时间被压缩时如何在五分钟内触及价值时刻。

维护

销售材料会过时。每个资产都需要一个负责人和审查日期,任何涉及定价、竞争对手或产品能力的内容都需要每季度检查一次。描述竞争对手旧产品的对战卡会导致丢单。

禁忌

  • 在了解交易实际停滞环节之前,不要构建销售材料。先询问销售代表并阅读失败案例。
  • 不要发布没有负责人和审查日期的演示文稿或一页纸。未维护的销售材料比没有更糟糕。
  • 不要围绕产品的功能列表来组织演示顺序,而应按照买家问题展开的顺序进行。
  • 不要把交付当作销售赋能的终点。只有当销售人员在真实交易中实际使用这些材料时,赋能才算完成。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

相关技能