abx-strategy
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseABX Strategy Framework
ABX策略框架
A comprehensive Account-Based Everything (ABX) strategy framework for B2B companies with complex sales cycles, lots of personnas, high-value deals, and limited addressable markets.
这是一套面向销售周期复杂、角色众多、高价值交易且目标市场有限的B2B企业的全域客户（ABX）综合策略框架。
When to Use This Skill
何时使用该策略
Use this skill when:
- Building GTM strategy for companies with <500 addressable accounts
- Deal sizes exceed $100K+ with 6+ month sales cycles
- Buying committees involve 5+ stakeholders
- Products require technical translation for business buyers
- You need to prioritize segments with limited resources
- Marketing must directly influence pipeline, not just generate awareness
This framework is designed for complex B2B sales where traditional demand generation fails and account-based approaches are structurally required.
在以下场景中使用本策略：
- 为目标客户数量少于500家的企业制定GTM策略
- 单笔交易额超10万美元且销售周期达6个月以上
- 采购委员会涉及5名及以上利益相关者
- 产品需要为业务买家进行技术语言转化
- 需要在资源有限的情况下优先选择细分市场
- 营销需直接影响销售管道，而非仅提升品牌知名度
本框架专为复杂B2B销售设计，这类场景中传统需求生成方法失效，必须采用基于客户的结构化方法。
Core Philosophy: Marketing as Product
核心理念：营销即产品
Treat every campaign, message, and channel as a hypothesis to validate, not a plan to execute.
| Traditional Marketing | Marketing as Product |
|---|---|
| Annual messaging framework | Messaging backlog with sprint-based testing |
| Launch plan executed once | Launch as v1.0, iterated based on field data |
| Competitive analysis updated quarterly | Competitive intel as live feed from sales calls |
| Sales enablement = collateral dump | Enablement = tested talk tracks with win-rate data |
| Success = assets shipped | Success = pipeline influenced and deal velocity changed |
将每个营销活动、信息和渠道视为需要验证的假设，而非执行计划。
| 传统营销 | 营销即产品 |
|---|---|
| 年度信息框架 | 基于迭代测试的信息待办清单 |
| 一次性执行的发布计划 | 以v1.0版本发布，根据一线数据迭代 |
| 每季度更新的竞品分析 | 来自销售通话的实时竞品情报 |
| 销售赋能=资料堆砌 | 销售赋能=经过验证且有胜率数据的沟通脚本 |
| 成功=产出营销资产 | 成功=影响销售管道并提升交易速度 |
The Bet Board Methodology
投注板方法论
Every initiative is a bet with four components:
┌─────────────────────────────────────────────────────────────┐
│ BET: [Name of initiative] │
├─────────────────────────────────────────────────────────────┤
│ HYPOTHESIS: [What you believe will happen] │
│ │
│ TEST: [How you will validate] │
│ │
│ SUCCESS CRITERIA: [Measurable outcome that confirms bet] │
│ │
│ KILL CONDITION: [When to abandon and pivot] │
│ │
│ LEARNING OUTPUT: [What you'll know regardless of outcome] │
└─────────────────────────────────────────────────────────────┘Example Bet Categories:
- Messaging bets (which narrative resonates)
- Channel bets (where to invest)
- ABM motion bets (what triggers engagement)
- Product launch bets (what drives conversion)
每个举措都是一个包含四个部分的投注：
┌─────────────────────────────────────────────────────────────┐
│ BET: [举措名称] │
├─────────────────────────────────────────────────────────────┤
│ HYPOTHESIS: [你预期会发生的结果] │
│ │
│ TEST: [验证方法] │
│ │
│ SUCCESS CRITERIA: [确认投注有效的可衡量结果] │
│ │
│ KILL CONDITION: [何时放弃并转向] │
│ │
│ LEARNING OUTPUT: [无论结果如何都能获得的认知] │
└─────────────────────────────────────────────────────────────┘投注类别示例：
- 信息投注（哪种叙事更能引起共鸣）
- 渠道投注（资源投向何处）
- ABM动作投注（触发客户参与的方式）
- 产品发布投注（推动转化的因素）
Framework 1: Segment-Specific vs. Synergy Analysis
框架1：细分市场专属vs协同分析
Not everything needs to be rebuilt for each segment. This framework identifies what MUST differ vs. what can be REUSED.
无需为每个细分市场重建所有内容。本框架明确哪些内容必须差异化，哪些可以复用。
Segment-Specific (Must Differ)
细分市场专属（必须差异化）
| Dimension | Why It Must Differ |
|---|---|
| ICPs & Personas | Different buyers, different motivations, different language |
| Pain Points | Each segment has unique problems driving urgency |
| Pricing Strategy | Value perception varies; commercial vs. government procurement differs |
| Channels | Where buyers gather and consume information varies |
| Messaging & Positioning | Same product, different value narrative per audience |
| Budget Allocation | ROI per segment differs; invest proportionally |
| 维度 | 必须差异化的原因 |
|---|---|
| ICP与角色 | 不同买家有不同动机和语言习惯 |
| 痛点 | 每个细分市场有独特的核心问题驱动购买 urgency |
| 定价策略 | 价值感知存在差异；商业与政府采购逻辑不同 |
| 渠道 | 买家聚集和获取信息的渠道各不相同 |
| 信息与定位 | 同一产品针对不同受众需传递不同价值叙事 |
| 预算分配 | 各细分市场ROI不同；需按比例分配资源 |
Synergies (Reusable Across Segments)
协同复用（跨细分市场通用）
| Dimension | Why It's Reusable |
|---|---|
| Education Topics | Core technology/market education applies broadly |
| Technical Collateral | Specs, datasheets, architecture diagrams are universal |
| Product Roadmap | Features serve multiple segments |
| Strategic Partners | Integrators, channel partners often span segments |
| Success Stories | On-orbit/in-production proof points validate for all |
| Core Narrative | Category-level story transcends segments |
| 维度 | 可复用的原因 |
|---|---|
| 教育主题 | 核心技术/市场教育内容具有普适性 |
| 技术资料 | 规格、数据表、架构图是通用的 |
| 产品路线图 | 功能可服务多个细分市场 |
| 战略合作伙伴 | 集成商、渠道合作伙伴通常覆盖多个细分市场 |
| 成功案例 | 已落地/已投产的验证案例对所有受众都有效 |
| 核心叙事 | 品类层面的故事超越细分市场 |
Template: Segment Analysis Matrix
模板：细分市场分析矩阵
markdown
undefinedmarkdown
undefinedSegment: [Name]
细分市场：[名称]
Segment-Specific Elements
细分市场专属要素
- ICP: [Description]
- Primary Personas: [List with titles]
- Top 3 Pain Points:
- [Pain point]
- [Pain point]
- [Pain point]
- Pricing Model: [Approach]
- Primary Channels: [List]
- Key Message: "[One sentence value prop for this segment]"
- ICP：[描述]
- 核心角色：[职位列表]
- Top 3痛点：
- [痛点]
- [痛点]
- [痛点]
- 定价模型：[方案]
- 核心渠道：[列表]
- 关键信息："[面向该细分市场的一句话价值主张]"
Synergies from Other Segments
可复用的协同要素
- Reusable Collateral: [List]
- Shared Success Stories: [List]
- Common Education Topics: [List]
---- 可复用资料：[列表]
- 共享成功案例：[列表]
- 通用教育主题：[列表]
---Framework 2: ABX Account Motions
框架2：ABX客户动作模型
Replace the linear funnel with signal-driven account motions. Each motion is triggered by observed signals, not assumptions about where accounts "sit" in a journey.
用信号驱动的客户动作替代线性漏斗。每个动作由观测到的信号触发，而非假设客户处于旅程的某个阶段。
The Five Motions
五大动作
DETECT ──→ DECODE ──→ ENGAGE ──→ ACCELERATE ──→ EXPAND
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Signal Map the Multi- Close Grow the
appears buying thread the deal account
committee engagementDETECT ──→ DECODE ──→ ENGAGE ──→ ACCELERATE ──→ EXPAND
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
信号出现 绘制采购 多线程 完成交易 客户增长
委员会地图 客户互动Motion Details
动作详情
| Motion | Trigger Signals | Marketing Actions | Success Metrics |
|---|---|---|---|
| DETECT | Policy announcement, RFI published, leadership change, contract expiring, funding round, strategic initiative announced | Account research sprint, buying committee mapping, PURE score assessment, tier assignment | Signal-to-first-touch latency (<72 hrs) |
| DECODE | First meeting booked, stakeholder org emerging, champion identified | Deep committee mapping, personality profiling, custom value narrative per stakeholder | # stakeholders mapped, personas engaged (target: 3+) |
| ENGAGE | Active evaluation confirmed, multiple touchpoints, content consumption increasing | Multi-channel surround: exec events, site visits, technical deep-dives, personalized content, ABM ads | Multi-thread penetration, content engagement depth |
| ACCELERATE | Proposal stage, competitive evaluation, procurement initiated | Competitive battle support, reference activation, custom ROI analysis, executive alignment | Pipeline velocity (days), competitive win rate |
| EXPAND | First product delivered, performance validated, satisfaction confirmed | Performance reporting, expansion narrative, peer referral program, fleet/portfolio growth pitch | Expansion rate (% entering 2nd deal discussion) |
| 动作 | 触发信号 | 营销行动 | 成功指标 |
|---|---|---|---|
| DETECT（发现） | 政策公告、RFI发布、领导层变动、合同到期、融资、战略举措公布 | 客户研究冲刺、采购委员会绘制、PURE分数评估、客户分层 | 信号到首次触达延迟（<72小时） |
| DECODE（解码） | 首次会议预约、利益相关者架构浮现、内部支持者确定 | 深度委员会绘制、人格分析、为每个利益相关者定制价值叙事 | 已绘制的利益相关者数量、触达的角色数（目标：3+） |
| ENGAGE（互动） | 确认客户处于主动评估阶段、多触点互动、内容消费增加 | 多渠道包围：高管活动、实地拜访、技术深度交流、个性化内容、ABM广告 | 多线程渗透度、内容互动深度 |
| ACCELERATE（加速） | 提案阶段、竞品评估、采购启动 | 竞品对抗支持、客户参考激活、定制ROI分析、高管对齐 | 销售管道速度（天数）、竞品胜率 |
| EXPAND（拓展） | 首个产品交付、性能验证、满意度确认 | 绩效报告、拓展叙事、同行推荐计划、批量/组合增长提案 | 拓展率（进入二次交易讨论的客户占比） |
Signal Detection Categories
信号检测类别
| Signal Type | Examples | Sources | Response Protocol |
|---|---|---|---|
| Policy/Regulatory | New legislation, budget allocation, mandate announced | Government portals, industry news, regulatory filings | Research sprint: map decision-makers, assess timing |
| Procurement | RFI/RFP published, contract expiration, vendor review | Procurement portals, industry contacts, news | Immediate: assemble capture team, prepare response |
| Leadership Change | New CEO/CTO, new program manager, reorg announced | LinkedIn, press releases, job change alerts | Welcome outreach with executive briefing offer |
| Competitive | Competitor failure, delay, price increase, service issue | Industry news, sales intelligence, customer network | Targeted outreach to affected customers |
| Strategic | M&A activity, funding round, expansion announced | News, SEC filings, press releases | Assess fit, prepare relevant value narrative |
| 信号类型 | 示例 | 来源 | 响应流程 |
|---|---|---|---|
| 政策/监管 | 新法规、预算分配、强制要求公布 | 政府门户、行业新闻、监管文件 | 研究冲刺：绘制决策者、评估时间节点 |
| 采购 | RFI/RFP发布、合同到期、供应商评审 | 采购门户、行业联系人、新闻 | 立即行动：组建攻坚团队、准备响应 |
| 领导层变动 | 新CEO/CTO、新项目经理、重组公告 | LinkedIn、新闻稿、职位变动提醒 | 欢迎 outreach，提供高管简报 |
| 竞品动态 | 竞品故障、延迟、涨价、服务问题 | 行业新闻、销售情报、客户网络 | 定向触达受影响客户 |
| 战略动作 | 并购活动、融资、扩张公告 | 新闻、SEC文件、新闻稿 | 评估适配性、准备相关价值叙事 |
Framework 3: PURE Problem Scoring
框架3：PURE问题打分法
Score ICP tiers using the PURE framework to identify "hair-on-fire" accounts.
使用PURE框架为ICP分层打分，识别“紧急需求”客户。
The PURE Criteria
PURE评估标准
| Criterion | Question | Score 0-3 |
|---|---|---|
| Painful | How acute is the problem? Is it causing real damage today? | 0=mild, 3=severe |
| Urgent | Is there a forcing function (deadline, mandate, event)? | 0=no timeline, 3=imminent |
| Recognized | Does the buyer know they have this problem? | 0=unaware, 3=actively seeking solution |
| Expensive | What's the cost of inaction (financial, strategic, competitive)? | 0=low, 3=existential |
| 标准 | 问题 | 得分0-3 |
|---|---|---|
| Painful（痛点强烈） | 问题的严重程度？是否已造成实际损失？ | 0=轻微，3=严重 |
| Urgent（紧急） | 是否有强制时间节点（截止日期、要求、事件）？ | 0=无时间限制，3=迫在眉睫 |
| Recognized（已认知） | 买家是否意识到自身存在该问题？ | 0=未察觉，3=主动寻求解决方案 |
| Expensive（代价高昂） | 不采取行动的成本（财务、战略、竞争层面）？ | 0=低成本，3=关乎生存 |
Tier Assignment
客户分层
| Total Score | Tier | Priority | Resource Allocation |
|---|---|---|---|
| 10-12 | Tier 1: Hair-on-Fire | Highest | Dedicated account team, custom everything |
| 7-9 | Tier 2: Burning Platform | High | Proactive outreach, personalized content |
| 4-6 | Tier 3: Active Pain | Medium | Targeted campaigns, scaled personalization |
| 1-3 | Tier 4: Emerging Need | Lower | Nurture programs, educational content |
| 0 | Tier 5: Future Potential | Lowest | Light touch, brand awareness only |
| 总分 | 层级 | 优先级 | 资源分配 |
|---|---|---|---|
| 10-12 | 层级1：紧急需求 | 最高 | 专属客户团队、全定制化服务 |
| 7-9 | 层级2：迫切需求 | 高 | 主动触达、个性化内容 |
| 4-6 | 层级3：主动需求 | 中 | 定向营销活动、规模化个性化 |
| 1-3 | 层级4：潜在需求 | 较低 | 培育计划、教育内容 |
| 0 | 层级5：未来潜力 | 最低 | 轻触式、品牌认知 |
Template: Account PURE Scorecard
模板：客户PURE打分卡
markdown
undefinedmarkdown
undefinedAccount: [Company Name]
客户：[公司名称]
PURE Assessment
PURE评估
| Criterion | Score (0-3) | Evidence |
|---|---|---|
| Painful | [X] | [Why this score] |
| Urgent | [X] | [Why this score] |
| Recognized | [X] | [Why this score] |
| Expensive | [X] | [Why this score] |
| TOTAL | [X/12] | Tier: [X] |
| 标准 | 得分(0-3) | 依据 |
|---|---|---|
| Painful | [X] | [得分理由] |
| Urgent | [X] | [得分理由] |
| Recognized | [X] | [得分理由] |
| Expensive | [X] | [得分理由] |
| 总分 | [X/12] | 层级：[X] |
Buying Committee (Known)
采购委员会（已知）
| Name | Title | Role in Decision | Engagement Status |
|---|---|---|---|
| Champion / Influencer / Blocker / Decision-maker | Cold / Warm / Engaged |
| 姓名 | 职位 | 决策角色 | 互动状态 |
|---|---|---|---|
| 支持者/影响者/反对者/决策者 | 未触达/已触达/已互动 |
Next Actions
下一步行动
- [Action]
- [Action]
---- [行动]
- [行动]
---Framework 4: Message Resonance System
框架4：信息共鸣系统
Creating content is not enough. This system ensures messages actually land.
仅产出内容是不够的。本系统确保信息真正被客户接受。
The Five Components
五大组成部分
┌─────────────────────────────────────────────────────────────┐
│ MESSAGE RESONANCE SYSTEM │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │PERSONALI- │ │STORYTELLING │ │ ENGAGEMENT │ │
│ │ZATION │ │ │ │ METRICS │ │
│ │ │ │ │ │ │ │
│ │Tailored │ │Real examples│ │Track what │ │
│ │content per │ │and case │ │lands via │ │
│ │persona and │ │studies that │ │analytics, │ │
│ │segment │ │make abstract│ │Gong, email │ │
│ │ │ │tangible │ │engagement │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ FEEDBACK │ │ CONSISTENT │ │
│ │ LOOPS │ │ VOICE │ │
│ │ │ │ │ │
│ │Sales input, │ │Professional │ │
│ │win/loss │ │yet human. │ │
│ │analysis, │ │Innovative │ │
│ │customer │ │but proven. │ │
│ │interviews │ │ │ │
│ └─────────────┘ └─────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────┐
│ 信息共鸣系统 │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │个性化 │ │故事化 │ │ 互动指标 │ │
│ │ │ │ │ │ │ │
│ │针对不同角色和│ │真实案例和 │ │通过分析工具、│ │
│ │细分市场定制内容│ │研究让抽象概念│ │Gong、邮件互动│ │
│ │ │ │变得具象 │ │追踪有效信息│ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ 反馈循环 │ │ 统一语调 │ │
│ │ │ │ │ │
│ │销售输入、胜败│ │专业且人性化。│ │
│ │分析、客户访谈│ │创新且经过验证。│ │
│ │ │ │ │ │
│ └─────────────┘ └─────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘Message Resonance Rate (MRR)
信息共鸣率（MRR）
The key leading indicator: % of sales conversations where the prospect uses your language back.
Track via conversation intelligence (Gong, Chorus) by monitoring:
- Keyword adoption (do they say "dedicated capacity" or "shared bandwidth"?)
- Objection patterns (are we addressing the right concerns?)
- Competitive mentions (how are we being compared?)
Target: 40%+ of qualified meetings show message adoption.
关键领先指标：客户在销售对话中使用我方语言的比例。
通过对话智能工具（Gong、Chorus）追踪：
- 关键词采用率（客户是否使用“专属容量”而非“共享带宽”？）
- 异议模式（我们是否解决了正确的顾虑？）
- 竞品提及（客户如何对比我们与竞品？）
目标：40%+的合格会议中出现信息复用。
Framework 5: Capability-to-Benefit Translation
框架5：能力到价值的转化
Technical products require systematic translation from what it does to why it matters.
技术产品需要系统化转化，从“功能是什么”到“对客户有什么意义”。
The Translation Hierarchy
转化层级
Layer 1: CATEGORY NARRATIVE
"Why this matters to the world"
│
▼
Layer 2: CAPABILITY → BENEFIT TRANSLATION
"What it does → So what? → Why you care"
│
▼
Layer 3: PERSONA-SPECIFIC MESSAGES
"Tailored value prop per buyer type"Layer 1: 品类叙事
“这对整个行业的意义”
│
▼
Layer 2: 能力→价值转化
“功能是什么 → 有什么用 → 与你何干”
│
▼
Layer 3: 角色专属信息
“针对不同买家定制的价值主张”Template: Capability Translation Matrix
模板：能力转化矩阵
| Technical Capability | So What? (Translation) | Benefit: Segment A | Benefit: Segment B |
|---|---|---|---|
| [Technical feature] | [Plain language explanation] | [Value for segment A buyer] | [Value for segment B buyer] |
| [Technical feature] | [Plain language explanation] | [Value for segment A buyer] | [Value for segment B buyer] |
| 技术能力 | 价值转化（有什么用？） | 细分市场A价值 | 细分市场B价值 |
|---|---|---|---|
| [技术功能] | [通俗易懂的解释] | [对细分市场A买家的价值] | [对细分市场B买家的价值] |
| [技术功能] | [通俗易懂的解释] | [对细分市场A买家的价值] | [对细分市场B买家的价值] |
Template: Persona Message Map
模板：角色信息地图
| Persona | What They Care About | Message Frame | Proof Points |
|---|---|---|---|
| CEO/Board | Strategic positioning, competitive advantage, ROI | "[Strategic value prop]" | [Evidence] |
| CTO/Technical | Specs, integration, performance, reliability | "[Technical value prop]" | [Evidence] |
| CFO/Finance | TCO, payback period, risk mitigation | "[Financial value prop]" | [Evidence] |
| Ops/User | Ease of use, support, day-to-day experience | "[Operational value prop]" | [Evidence] |
| Procurement | Compliance, risk, vendor stability | "[Risk mitigation prop]" | [Evidence] |
| 角色 | 核心关注点 | 信息框架 | 验证依据 |
|---|---|---|---|
| CEO/董事会 | 战略定位、竞争优势、ROI | “[战略价值主张]” | [证据] |
| CTO/技术岗 | 规格、集成、性能、可靠性 | “[技术价值主张]” | [证据] |
| CFO/财务岗 | 总拥有成本、投资回报周期、风险缓解 | “[财务价值主张]” | [证据] |
| 运营/用户 | 易用性、支持、日常体验 | “[运营价值主张]” | [证据] |
| 采购岗 | 合规、风险、供应商稳定性 | “[风险缓解主张]” | [证据] |
Framework 6: Constant Discovery Mindset
框架6：持续探索思维
Every engagement generates learnings. This framework captures and applies them.
每次互动都能产生认知。本框架用于捕捉并应用这些认知。
The Four Discovery Questions
四大探索问题
Before, during, and after every deal:
┌─────────────────────────────────────────────────────────────┐
│ 1. Do we know and understand the PLAYERS? │
│ Who are the real decision-makers vs. influencers? │
│ Who can kill the deal? Who's the hidden blocker? │
├─────────────────────────────────────────────────────────────┤
│ 2. Do we understand the RELATIONSHIPS? │
│ Internal dynamics? External advisors? Political factors? │
│ Who trusts whom? Who competes internally? │
├─────────────────────────────────────────────────────────────┤
│ 3. Do we understand the INFLUENCING FACTORS? │
│ Budget cycles? Regulatory timelines? Competitive moves? │
│ Internal mandates? Strategic priorities? │
├─────────────────────────────────────────────────────────────┤
│ 4. Do we know the DECISION FACTORS? │
│ Technical requirements? Commercial terms? Risk tolerance?│
│ Timeline constraints? Evaluation criteria? │
└─────────────────────────────────────────────────────────────┘在交易的前、中、后阶段都要问：
┌─────────────────────────────────────────────────────────────┐
│ 1. 我们是否了解所有**参与者**？ │
│ 谁是真正的决策者 vs 影响者？ │
│ 谁能否决交易？谁是隐藏的反对者？ │
├─────────────────────────────────────────────────────────────┤
│ 2. 我们是否了解**关系网络**？ │
│ 内部动态？外部顾问？政治因素？ │
│ 谁信任谁？内部存在哪些竞争？ │
├─────────────────────────────────────────────────────────────┤
│ 3. 我们是否了解**影响因素**？ │
│ 预算周期？监管时间？竞品动作？ │
│ 内部要求？战略优先级？ │
├─────────────────────────────────────────────────────────────┤
│ 4. 我们是否了解**决策因素**？ │
│ 技术要求？商业条款？风险容忍度？│
│ 时间限制？评估标准？ │
└─────────────────────────────────────────────────────────────┘Win/Loss Analysis Framework
胜败分析框架
| Dimension | Questions to Answer | How to Capture |
|---|---|---|
| Decision Criteria | What were the top 3 factors? Were these what we expected? | Post-decision debrief |
| Buying Process | Who was the real decision-maker? Who influenced most? | Sales team debrief, call analysis |
| Messaging Effectiveness | Which messages resonated? Which fell flat? | Keyword analysis, champion feedback |
| Competitive Dynamics | Who else considered? What did they say about us? | Direct inquiry, third-party research |
| Timeline & Process | Faster or slower than expected? What caused delays? | CRM tracking, sales input |
| 维度 | 需回答的问题 | 收集方式 |
|---|---|---|
| 决策标准 | 前3位决策因素是什么？是否符合预期？ | 交易后复盘 |
| 采购流程 | 谁是真正的决策者？谁的影响最大？ | 销售团队复盘、通话分析 |
| 信息有效性 | 哪些信息引起共鸣？哪些无效？ | 关键词分析、支持者反馈 |
| 竞品动态 | 客户还考虑了哪些竞品？他们如何评价我们？ | 直接询问、第三方研究 |
| 时间与流程 | 比预期快还是慢？延迟原因是什么？ | CRM追踪、销售输入 |
Framework 7: Learning Loop Architecture
框架7：学习循环架构
Structured cadence for turning field data into strategy improvements.
| Cadence | Inputs | Decisions | Outputs |
|---|---|---|---|
| Weekly | Call summaries, signal alerts, content engagement | Adjust messaging, reprioritize accounts | Updated talk tracks, account priority shifts |
| Bi-weekly | Win/loss patterns, objection frequency | Test new value props, update battle cards | New messaging variants for testing |
| Monthly | Full pipeline analysis, content performance, ABM metrics | Kill underperforming bets, double down on winners | Bet board update, resource reallocation |
| Quarterly | Market shifts, competitive landscape, customer feedback | Strategy pivots, new bet proposals | Updated GTM strategy, new hypothesis slate |
将一线数据转化为策略改进的结构化节奏。
| 节奏 | 输入 | 决策 | 输出 |
|---|---|---|---|
| 每周 | 通话总结、信号提醒、内容互动数据 | 调整信息、重新排序客户优先级 | 更新沟通脚本、客户优先级调整 |
| 每两周 | 胜败模式、异议频率 | 测试新价值主张、更新竞品应对卡 | 用于测试的新信息变体 |
| 每月 | 完整销售管道分析、内容表现、ABM指标 | 终止表现不佳的投注、加大成功投注的资源 | 投注板更新、资源重新分配 |
| 每季度 | 市场变化、竞品格局、客户反馈 | 战略转向、新投注提案 | 更新GTM策略、新假设清单 |
Framework 8: Budget Allocation by Stage
框架8：分阶段预算分配
Marketing investment mix should shift as market position evolves.
| Stage | Primary Investment | Secondary | Rationale |
|---|---|---|---|
| Early Market (0→1) | Branding & Positioning (40%) | Sales Enablement (35%) | Category creation, message testing, foundational collateral |
| Scaling (1→10) | Demand Generation (40%) | Sales Enablement (30%) | ABM campaigns, event presence, thought leadership at scale |
| Market Leader | Demand Generation (45%) | Customer Marketing (25%) | Expansion, reference program, ecosystem development |
营销投资组合应随市场地位演变而调整。
| 阶段 | 核心投资 | 次要投资 | 理由 |
|---|---|---|---|
| 早期市场（0→1） | 品牌与定位（40%） | 销售赋能（35%） | 品类创建、信息测试、基础资料搭建 |
| 增长期（1→10） | 需求生成（40%） | 销售赋能（30%） | ABM活动、展会参与、规模化思想领导力 |
| 市场领导者 | 需求生成（45%） | 客户营销（25%） | 客户拓展、参考计划、生态系统开发 |
Framework 9: Customer Journey Mapping
框架9：客户旅程地图
Map both internal (your team) and external (customer) activities across the journey.
绘制内部（团队）和外部（客户）在整个旅程中的活动。
Template: Journey Map
模板：旅程地图
| Stage | Customer Activities | Your Internal Activities | Key Stakeholders | Marketing Deliverables |
|---|---|---|---|---|
| Identification | Evaluating options, initial research, internal alignment | Signal detection, account research, tier assignment | Innovation leads, technical scouts | Account brief, persona mapping |
| Consideration | Technical evaluation, stakeholder education, vendor comparison | Multi-threading, technical deep-dives, exec engagement | CTO, architects, finance | Technical collateral, ROI calculator, battle cards |
| Validation | POC/demo, reference checks, contract negotiation | Reference activation, proposal support, legal/contract | CEO, legal, board, implementation | Custom business case, exec presentation |
| Implementation | Deployment, integration, go-live | Onboarding support, success planning | Ops team, project manager | Implementation guides, training |
| Expansion | Performance review, additional use cases, renewal | Performance reporting, expansion pitch, reference program | Exec sponsor, ops | Performance report, expansion narrative, case study |
| 阶段 | 客户活动 | 内部团队活动 | 关键利益相关者 | 营销交付物 |
|---|---|---|---|---|
| 识别 | 评估选项、初步研究、内部对齐 | 信号检测、客户研究、分层 | 创新负责人、技术侦察员 | 客户简报、角色地图 |
| 考虑 | 技术评估、利益相关者教育、竞品对比 | 多线程互动、技术深度交流、高管对接 | CTO、架构师、财务 | 技术资料、ROI计算器、竞品应对卡 |
| 验证 | POC/演示、参考核查、合同谈判 | 客户参考激活、提案支持、法务/合同对接 | CEO、法务、董事会、实施团队 | 定制商业案例、高管演示稿 |
| 实施 | 部署、集成、上线 | 上线支持、成功规划 | 运营团队、项目经理 | 实施指南、培训材料 |
| 拓展 | 绩效回顾、额外使用场景、续约 | 绩效报告、拓展提案、参考计划 | 高管支持者、运营 | 绩效报告、拓展叙事、案例研究 |
Framework 10: Collaterals with Success Metrics
框架10：带成功指标的营销资产
Every asset should have defined success metrics. Track not just creation, but effectiveness.
| Asset Type | Purpose | Success Metrics | Review Cadence |
|---|---|---|---|
| ROI/TCO Calculator | Self-service economic comparison | % of meetings where used, conversion rate | Monthly |
| Technical Datasheets | Spec validation for technical buyers | Time-on-page, download rate, sales feedback | Quarterly |
| Case Studies | Social proof and use case validation | Cited in sales calls, shared by prospects | Monthly |
| Battle Cards | Arm sales for competitive encounters | Win rate in competitive deals, objection handle rate | Monthly |
| Executive Presentation | C-level storytelling | Meeting-to-proposal conversion, exec feedback | Quarterly |
每个资产都应有明确的成功指标。不仅追踪产出，更要追踪有效性。
| 资产类型 | 目的 | 成功指标 | 回顾节奏 |
|---|---|---|---|
| ROI/TCO计算器 | 自助式经济对比 | 销售通话中使用的比例、转化率 | 每月 |
| 技术数据表 | 为技术买家验证规格 | 页面停留时间、下载率、销售反馈 | 每季度 |
| 案例研究 | 社交证明和使用场景验证 | 销售通话中被引用、被客户分享 | 每月 |
| 竞品应对卡 | 为销售提供竞品对抗支持 | 竞品交易中的胜率、异议处理率 | 每月 |
| 高管演示稿 | 面向C层的故事讲述 | 会议到提案的转化率、高管反馈 | 每季度 |
KPI Architecture
KPI架构
Tier 1: Leading Indicators (Weekly)
层级1：领先指标（每周）
| Metric | Definition | Target |
|---|---|---|
| Message Resonance Rate | % of conversations where prospect uses your language | 40%+ |
| Content Engagement Depth | Time-on-page for key content by target accounts | 3+ minutes |
| Multi-thread Penetration | Unique stakeholders engaged per target account | 3+ before proposal |
| Signal-to-Engagement Latency | Time from signal to first personalized touch | <72 hours |
| 指标 | 定义 | 目标 |
|---|---|---|
| 信息共鸣率 | 客户使用我方语言的对话比例 | 40%+ |
| 内容互动深度 | 目标客户对核心内容的页面停留时间 | 3+分钟 |
| 多线程渗透度 | 每个目标客户触达的独特利益相关者数量 | 提案前触达3+ |
| 信号到互动延迟 | 从信号出现到首次个性化触达的时间 | <72小时 |
Tier 2: Core Pipeline Metrics (Monthly)
层级2：核心销售管道指标（每月）
| Metric | Definition | Target |
|---|---|---|
| Marketing-Sourced Meetings | Meetings from marketing-initiated engagement | 2-3/month from target list |
| Pipeline Velocity | Days from first touch to proposal | Reduce 15% in 6 months |
| Deal Influence Rate | % of active pipeline with marketing touchpoints | 80%+ |
| Competitive Win Rate | % won when competitor present | Track QoQ improvement |
| 指标 | 定义 | 目标 |
|---|---|---|
| 营销发起的会议 | 由营销触达产生的会议 | 目标客户群每月2-3个 |
| 销售管道速度 | 从首次触达到提案的天数 | 6个月内缩短15% |
| 营销影响交易率 | 有营销触点的活跃销售管道占比 | 80%+ |
| 竞品胜率 | 存在竞品时的交易胜率 | 追踪季度环比提升 |
Tier 3: Lagging Confirmation (Quarterly)
层级3：滞后验证指标（每季度）
| Metric | Definition | Target |
|---|---|---|
| Revenue Influenced | $-value where marketing contributed | 50%+ of bookings |
| Customer Expansion Rate | % entering expansion conversations | 60%+ within 18 months |
| Brand Authority Index | Unsolicited inbound citing content/thought leadership | Track growth |
| 指标 | 定义 | 目标 |
|---|---|---|
| 营销影响收入 | 营销贡献的收入金额 | 占签约额的50%+ |
| 客户拓展率 | 进入二次交易讨论的客户占比 | 18个月内60%+ |
| 品牌权威指数 | 主动提及我方内容/思想领导力的 inbound 数量 | 追踪增长 |
Composable ABX Tech Stack
可组合ABX技术栈
Best-of-breed tools, orchestrated through CRM as single source of truth.
| Function | Recommended Tools | Purpose | Est. Annual Cost |
|---|---|---|---|
| CRM / Source of Truth | Salesforce, HubSpot | Central account and deal record | Varies |
| Conversation Intelligence | Gong, Chorus, Clari | Capture calls, surface patterns, track competitors | $30-50K |
| Data Enrichment | Clay, Apollo, ZoomInfo | Account research, signal monitoring, contact data | $10-30K |
| Website Personalization | Mutiny, Demandbase | Account-specific landing pages, dynamic content | $25-40K |
| ABM Advertising | Influ2, ZenABM, LinkedIn | Contact-level targeting, persona-specific creative | $20-30K |
| Workflow Automation | Zapier, n8n, Make | Connect tools, trigger motions automatically | $5-10K |
| Buyer Intelligence | Humantic AI, Crystal | Personality profiling, communication preferences | $10-15K |
Phase 1 Investment: $100-165K for composable stack vs. $150-250K+ for enterprise ABM platforms with less flexibility.
精选工具，以CRM为单一数据源进行编排。
| 功能 | 推荐工具 | 用途 | 年度预估成本 |
|---|---|---|---|
| CRM / 单一数据源 | Salesforce, HubSpot | 集中存储客户和交易记录 | 按需而定 |
| 对话智能 | Gong, Chorus, Clari | 记录通话、发现模式、追踪竞品 | $30-50K |
| 数据 enrichment | Clay, Apollo, ZoomInfo | 客户研究、信号监控、联系人数据 | $10-30K |
| 网站个性化 | Mutiny, Demandbase | 客户专属落地页、动态内容 | $25-40K |
| ABM广告 | Influ2, ZenABM, LinkedIn | 联系人级定向、角色专属创意 | $20-30K |
| 工作流自动化 | Zapier, n8n, Make | 连接工具、自动触发动作 | $5-10K |
| 买家智能 | Humantic AI, Crystal | 人格分析、沟通偏好 | $10-15K |
第一阶段投资：可组合栈需$100-165K，相比企业级ABM平台的$150-250K+更具灵活性。
90-Day Implementation Plan
90天实施计划
Days 1-30: Listen, Map, Foundation
第1-30天：倾听、映射、基础搭建
Listen:
- Sit in on 10+ sales calls. Document buyer language, objections, competitive mentions.
- Interview 5+ customers: Why did they choose you? What almost stopped them?
- Interview 5+ sales reps: What messaging works? What falls flat?
Map:
- Build target account list with PURE scores
- Map buying committees for top 10 accounts
- Audit existing content: What exists? Missing? Stale?
- Competitive audit: How do competitors position? Where vulnerable?
Foundation:
- Draft v1 messaging hierarchy
- Set up conversation intelligence dashboards
- Establish weekly learning loop cadence
倾听：
- 参与10+销售通话。记录买家语言、异议、竞品提及。
- 访谈5+客户：为什么选择我们？什么差点阻止他们？
- 访谈5+销售代表：哪些信息有效？哪些无效？
映射：
- 建立带PURE分数的目标客户列表
- 为Top10客户绘制采购委员会
- 审计现有内容：有哪些？缺失哪些？过时哪些？
- 竞品审计：竞品如何定位？存在哪些弱点？
基础搭建：
- 起草v1信息层级
- 搭建对话智能仪表盘
- 建立每周学习循环节奏
Days 31-60: Build, Test, Launch First Bets
第31-60天：构建、测试、启动首批投注
Build:
- Finalize messaging hierarchy; test with sales + friendly customers
- ROI/TCO calculator v1
- First persona-specific content pieces
- Set up account enrichment for top 30 accounts
Test:
- Launch 2-3 messaging bets
- Launch channel bet (e.g., executive LinkedIn content)
- First warm outbound sequences to signal-showing accounts
Align:
- Present initial findings to leadership
- Align with sales on account prioritization
构建：
- 最终确定信息层级；与销售+友好客户测试
- ROI/TCO计算器v1
- 首批角色专属内容
- 为Top30客户搭建数据enrichment
测试：
- 启动2-3个信息投注
- 启动渠道投注（如高管LinkedIn内容）
- 向有信号的客户发送首批暖启动 outbound 序列
对齐：
- 向领导层汇报初步发现
- 与销售对齐客户优先级
Days 61-90: Iterate, Expand, Prepare
第61-90天：迭代、拓展、准备
Iterate:
- First bet review: What's working? Kill or amplify.
- Update messaging based on call data
- Refine account tiers based on signals
Expand:
- Launch additional bets
- Set up website personalization for top accounts
- Begin product launch planning if applicable
Prepare:
- Present 90-day results and updated Bet Board
- Propose next phase investments
迭代：
- 首次投注复盘：哪些有效？终止或加大资源。
- 根据通话数据更新信息
- 根据信号优化客户分层
拓展：
- 启动更多投注
- 为Top客户搭建网站个性化
- 如有需要，开始产品发布规划
准备：
- 汇报90天成果和更新后的投注板
- 提出下一阶段投资提案
Quick Reference: Power Phrases
快速参考：常用话术
Use these frames in strategy discussions:
- "Hypothesis → Test → Learn → Iterate" — not plan and execute
- "Learning velocity over planning perfection" — especially at 0→1
- "The market tells us, we don't tell the market" — ground strategy in signals
- "Multi-threading is mandatory" — complex deals require parallel engagement
- "Take the complex and make it simple" — the core PMM challenge
- "Proven, not promised" — flight heritage / production deployment matters
- "Every campaign is a bet with a kill condition" — no sacred cows
在策略讨论中使用以下框架：
- "假设→测试→学习→迭代" — 而非计划并执行
- "学习速度优先于计划完美" — 尤其在0→1阶段
- "市场告诉我们答案，而非我们教育市场" — 策略基于信号
- "多线程互动是必须的" — 复杂交易需要并行触达
- "化繁为简" — 产品营销的核心挑战
- "用结果证明，而非承诺" — 落地/投产案例至关重要
- "每个营销活动都是带终止条件的投注" — 没有不可放弃的项目
Using This Skill with Claude
与Claude配合使用本策略
When working on ABX strategy, you can ask Claude to:
- Score accounts: "Apply the PURE framework to [company] based on [context]"
- Build messaging: "Create a capability-to-benefit translation matrix for [product]"
- Design bets: "Propose 5 testable messaging bets for [segment]"
- Map journeys: "Build a customer journey map for [persona] buying [product]"
- Analyze segments: "Apply the segment-specific vs. synergy framework to [segments]"
- Create collaterals: "Draft a battle card for competing against [competitor]"
- Build scorecards: "Create a PURE scorecard template for [industry]"
- Plan launches: "Design a bet board for launching [product] to [segment]"
在制定ABX策略时，你可以让Claude：
- 为客户打分："根据[背景]，用PURE框架为[公司]打分"
- 构建信息："为[产品]创建能力到价值的转化矩阵"
- 设计投注："为[细分市场]提出5个可测试的信息投注"
- 绘制旅程："为[角色]采购[产品]构建客户旅程地图"
- 分析细分市场："用细分市场专属vs协同框架分析[细分市场]"
- 生成资产："起草针对[竞品]的竞品应对卡"
- 创建打分卡："为[行业]创建PURE打分卡模板"
- 规划发布："为[产品]向[细分市场]发布设计投注板"
License
许可证
MIT License. Use freely, adapt to your context, share improvements.
MIT许可证。可自由使用、适配场景、分享改进。