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.

相關技能