Enterprise Account Planning

企业客户规划

Strategic account planning and execution for enterprise deals. Turn complex sales cycles into systematic wins — or at least know when they're dying before you waste months.

面向企业客户的战略客户规划与执行方法。将复杂的销售周期转化为系统化的成功——或者至少在浪费数月时间前就能判断出交易是否即将失败。

When to Use

适用场景

Triggers:

"How do I plan this enterprise deal?"
"This deal has been in motion 3 months, why isn't it closing?"
"Should I create a full account plan or simplified version?"
"How do I know if this deal is actually moving?"
"MEDDICC qualification"
"Building a mutual action plan"

Context:

Strategic deals above your average ACV
Multiple stakeholders involved
Sales cycle exceeds 60 days
Complex buying process (legal, procurement, security)
Enterprise or mid-market accounts

触发场景：

"我该如何规划这个企业客户交易？"
"这笔交易已经推进3个月了，为什么还没成交？"
"我应该制定完整的客户规划还是简化版本？"
"我怎么知道这笔交易是否真的在推进？"
"MEDDICC资质审核"
"制定共同行动计划"

适用背景：

交易金额高于平均ACV的战略级交易
涉及多方利益相关者
销售周期超过60天
复杂的采购流程（涉及法务、采购、安全部门）
企业或中大型客户账户

Core Frameworks

核心框架

1. If Your MAP Hasn't Been Updated in 3 Weeks, That Deal Is Dead

1. 若你的MAP已超过3周未更新，这笔交易已失败

The Pattern I've Seen:

The Mutual Action Plan (MAP) is the single best indicator of deal health. Not pipeline stage. Not verbal commitments. Not "they love the product."

The MAP tells you everything:

Healthy deal:

MAP updated weekly
Customer adding their own action items
Both sides completing tasks on schedule
New stakeholders appearing in MAP
Dates moving up (not pushed out)

Dying deal:

MAP last updated 3+ weeks ago
Only your side has action items
Customer tasks marked "pending" for weeks
No new stakeholders engaged
All dates in the past

Why This Happens:

When a deal is real, the customer wants it to happen. They're doing work. They're involving stakeholders. They're moving through their process.

When a deal is dying, you're doing all the work. They're "too busy." They'll "get back to you next week." The economic buyer is "traveling."

The 3-Week Rule:

If your MAP hasn't been updated in 3 weeks, the deal is dead — you just don't know it yet. I've never seen a deal close with a stale MAP. Not once in 11 years.

What to Do:

Week 1 of silence: Send MAP update: "Here's what we've completed. What's your status on [specific customer action]?"

Week 2 of silence: Escalate to champion: "Haven't heard back on MAP. Are we still on track for [date]? If priorities shifted, let me know."

Week 3 of silence: Qualify out or reset: "It seems like timing might not be right. Should we pause and reconnect in [timeframe], or is there a blocker I can help with?"

Common Mistake:

Keeping deals in pipeline because "they said they want it." Verbal interest ≠ action. If they're not doing work, they're not buying.

我观察到的规律：

共同行动计划（MAP）是判断交易健康度的最佳指标，而非销售漏斗阶段、口头承诺或“他们喜欢我们的产品”这类表述。

MAP能告诉你所有信息：

健康的交易：

MAP每周更新
客户主动添加自己的行动项
双方都按计划完成任务
MAP中出现新的利益相关者
截止日期提前（而非延后）

濒临失败的交易：

MAP最后一次更新是在3周前
只有我方有行动项
客户的任务已标记为“待处理”数周
没有新的利益相关者参与
所有截止日期都已过期

背后的原因：

当交易真实有效时，客户会希望它落地。他们会主动推进工作、引入利益相关者、走完内部流程。

当交易濒临失败时，所有工作都由我方推进。他们“太忙”、“下周再回复你”，或者经济决策人（EB）“在出差”。

3周规则：

若你的MAP已超过3周未更新，这笔交易实际上已经失败——只是你还没意识到。在我11年的职业生涯中，从未见过停滞的MAP对应的交易最终成交。一次都没有。

应对措施：

沉默第1周： 发送MAP更新："这是我们已完成的工作。请问你方在[具体客户行动项]上的进度如何？"

沉默第2周： 联系内部支持者（Champion）升级沟通："尚未收到MAP的更新回复。我们是否仍能按[日期]推进？如果优先级有变化，请告知我。"

沉默第3周： 淘汰该交易或重新规划："看起来当前时机可能不合适。我们是否应该暂停，在[时间段]后再重新对接？或者是否有我可以协助解决的障碍？"

常见误区：

仅因为“他们说过想要”就将交易留在销售漏斗中。口头意向≠实际行动。如果客户没有推进工作，他们就不会购买。

2. The EB Discovery Problem (And Why Deals Die at Week 8)

2. EB对接缺失问题（以及为什么交易常在第8周失败）

The Pattern:

You're 8 weeks into a deal. POC went great. Champion loves you. Technical validation complete. You send the proposal.

Then: radio silence.

What happened? You never met the Economic Buyer.

The Economic Buyer (EB) is the person who:

Controls budget allocation
Makes final purchase decision
Signs the contract

Not:

Your champion (they influence, don't decide)
The technical lead (they validate, don't buy)
The VP who attended one demo (they advise, don't sign)

Why Deals Die Without EB Access:

You built the business case with your champion's assumptions. But the EB has different priorities:

Champion cares about: solving their team's pain
EB cares about: ROI, risk mitigation, strategic alignment

When you send proposal to EB through the champion, EB sees:

Price tag with no context
Solution to a problem they didn't articulate
Risk they haven't evaluated

Result: Deal stalls or dies.

The Framework: EB Validation Checklist

Before sending proposal, validate:

Have you identified the EB? (Name, title, confirmed by champion)
Have you met the EB? (Video call minimum, in-person ideal)
Does EB agree on the problem? (In their words, not yours)
Does EB agree on success metrics? (How they'll measure ROI)
Does EB know the price range? (Ballpark discussed, not surprised)
Does EB understand timeline? (Implementation, go-live, value realization)

If you answered "no" to any, don't send the proposal yet.

How to Get EB Access:

Ask your champion: "Before we finalize pricing, I'd love 15 minutes with [EB name] to make sure we're aligned on outcomes and timeline. Can you intro us?"

If champion blocks: "I can handle that, you don't need to talk to them" → This is a red flag. Either champion doesn't have access (not a real champion) or they're afraid EB will kill the deal (which means deal is weak).

Push back: "I totally understand. At the same time, I want to make sure [EB] sees the full value before seeing the price. In my experience, when economic buyers aren't involved early, deals get delayed in procurement. Can we do a quick alignment call?"

Common Mistake:

Treating EB meeting as "nice to have." It's mandatory for any deal >$50K. No EB access = no deal.

规律：

你已经推进交易8周了，POC（概念验证）效果很好，内部支持者对你青睐有加，技术验证也已完成。你发送了提案。

然后：彻底沉默。

问题出在哪？ 你从未对接过经济决策人（EB）。

经济决策人（EB）是指：

掌控预算分配的人
做出最终采购决策的人
签署合同的人

而非：

你的内部支持者（他们仅能施加影响，无法决策）
技术负责人（他们仅做验证，不负责采购）
参加过一次演示的副总裁（他们仅提供建议，不签署合同）

未对接EB导致交易失败的原因：

你基于内部支持者的假设构建了商业案例，但EB的优先级完全不同：

内部支持者关注：解决其团队的痛点
EB关注：投资回报率（ROI）、风险缓解、战略对齐

当你通过内部支持者向EB发送提案时，EB看到的是：

没有背景说明的价格标签
针对一个他们从未提出过的问题的解决方案
他们未评估过的风险

结果： 交易停滞或失败。

框架：EB验证清单

发送提案前，需验证以下内容：

你是否已确定EB的身份？（姓名、职位，且得到内部支持者确认）
你是否已与EB对接？（至少进行过视频通话，面对面沟通更佳）
EB是否认同存在的问题？（用他们的原话，而非你的表述）
EB是否认同成功指标？（他们如何衡量投资回报率）
EB是否知晓价格范围？（已讨论过大致价位，不会感到意外）
EB是否了解时间规划？（实施、上线、价值实现的时间节点）

如果有任何一项答案为“否”，请不要发送提案。

如何对接EB：

询问内部支持者： "在我们最终确定定价前，我希望能和[EB姓名]进行15分钟的沟通，确保我们在成果和时间规划上对齐。你能否帮我引荐？"

如果内部支持者阻拦："我来处理，你不需要和他们沟通" → 这是危险信号。要么内部支持者无法接触到EB（并非真正的支持者），要么他们担心EB会否决交易（意味着交易本身就很脆弱）。

应对反驳： "我完全理解。但与此同时，我希望[EB]在看到价格前能充分了解产品的全部价值。根据我的经验，如果经济决策人未提前参与，交易在采购阶段很容易被延迟。我们能否进行一次简短的对齐沟通？"

常见误区：

将对接EB视为“锦上添花”的环节。对于任何金额超过5万美元的交易，这都是强制性要求。无法对接EB=无法成交。

3. Personal Win Mapping (People Buy for Themselves)

3. 个人收益映射（人们为自己而购买）

The Pattern:

Enterprise software purchases are made by committees. But committees don't buy. People buy.

And people buy for personal reasons:

Career advancement
Looking good to their boss
Reducing their workload
Covering their ass (CYA)
Proving they were right
Not looking stupid

Framework: Personal Win Identification

For each stakeholder, map:

Professional Win:

What do they get credit for if this succeeds?
What pain goes away for them personally?
How does this make them look good?

Professional Risk:

What happens to them if this fails?
What's their reputation cost if this goes wrong?
Who's skeptical of them internally?

Personal Motivations:

Are they new in role? (Need quick wins)
Facing budget cuts? (Need to justify spend)
Up for promotion? (Need visible success)
Burned by vendors before? (Extra risk-averse)

Example: VP of Engineering

Professional Win:

Reduce on-call burden for team (they'll stop complaining to her)
Faster incident response (looks good in QBRs)
Attract better eng talent (modern tooling)

Professional Risk:

Team rejects new tool (she forced it on them)
Migration goes badly (downtime, incidents)
Vendor fails (she picked them)

Personal Motivations:

New in role (6 months), needs wins
Under pressure to improve uptime metrics
Previous monitoring tool she picked failed

How This Changes Your Pitch:

Generic pitch: "Our platform improves incident response time by 40%."

Personal win pitch: "You mentioned the on-call burden is burning out your team. We've seen teams reduce on-call pages by 40% in the first month, which helps with retention. And since you're focused on uptime metrics for the board, the improved response time shows up immediately in your QBR dashboards."

The Difference:

Generic = business case Personal = career case

Both matter. But personal wins close deals.

Common Mistake:

Selling only to the business problem. "This saves money. This improves efficiency." That's necessary but not sufficient. People need to see what's in it for them personally.

规律：

企业软件采购由委员会决定，但委员会不会购买——是个人在购买。

而个人购买是出于自身原因：

职业晋升
在老板面前表现出色
减轻工作负担
自我保护（CYA）
证明自己是对的
避免出丑

框架：个人收益识别

针对每个利益相关者，梳理以下内容：

职业收益：

如果交易成功，他们会获得什么认可？
哪些个人痛点会被解决？
这会如何提升他们的形象？

职业风险：

如果交易失败，他们会面临什么后果？
如果出现问题，他们的声誉会受到什么损失？
内部谁对他们持怀疑态度？

个人动机：

他们是否刚上任？（需要快速取得成果）
是否面临预算削减？（需要证明支出的合理性）
是否正在争取晋升？（需要可见的成功）
是否曾被供应商坑过？（风险规避程度更高）

示例：工程副总裁

职业收益：

减轻团队的值班负担（团队不会再向她抱怨）
更快的事件响应速度（在季度业务评审（QBR）中表现出色）
吸引更优秀的工程人才（现代化工具）

职业风险：

团队拒绝新工具（是她强制推行的）
迁移过程不顺利（停机、事故）
供应商表现不佳（是她选择的）

个人动机：

刚上任6个月，需要取得成果
面临提升正常运行时间指标的压力
她之前选择的监控工具失败了

这会如何改变你的推销话术：

通用话术： "我们的平台将事件响应时间缩短40%。"

基于个人收益的话术： "你提到值班负担让团队不堪重负。我们看到很多团队在第一个月就将值班告警减少了40%，这有助于留住人才。另外，由于你正专注于向董事会展示正常运行时间指标，提升后的响应速度会立即体现在你的QBR仪表盘中。"

区别： 通用话术=商业案例个人收益话术=职业发展案例

两者都很重要，但个人收益才是促成交易的关键。

常见误区： 仅针对商业问题进行推销。"这能省钱，这能提升效率。" 这是必要条件，但并非充分条件。人们需要看到这对他们个人有什么好处。

4. Enterprise Account Plan Structure (Four Components)

4. 企业客户规划结构（四个组成部分）

A complete account plan has four interconnected pieces. Each feeds the others.

Component 1: Account Summary

Company basics (HQ, size, industry, subsidiaries)
Technical landscape (infrastructure, tools, platforms)
Top corporate initiatives (from press, annual reports, LinkedIn)
Hypothesis: "How can we help?" (write this before engaging)
LinkedIn keyword analysis (quantify their investment in your domain)

Component 2: Org Chart

Map all relevant contacts: name, title, location, LinkedIn, email, phone, notes
Notes capture: domain of responsibility, technical specialties, personal win
Include people across levels: C-suite, directors, architects, leads, specialists
Don't just map buyer — map influencers, users, potential blockers

Component 3: Opportunity Plan (MEDDICC)

M - Metrics: How will the customer measure success? (Validated with EB)
E - Economic Buyer: Who has budget authority? Have you met them?
D - Decision Criteria: What criteria will they use to decide? (Technical, business, political)
D - Decision Process: What's their buying process? (Procurement, legal, security review)
I - Identified Pain: What specific pain have they articulated? (Their words, not yours)
C - Champion: Who inside the account is actively selling on your behalf?
C - Competition: Who else are they evaluating? What's the competitive dynamic?

Plus: Issues/Risks table with mitigation plans, help needed, responsible parties

Component 4: Mutual Action Plan (MAP)

Joint timeline with: Action, Your Owner, Customer Owner, Others Involved, Due Date
Both sides must have actions — if only your team has actions, it's not a deal, it's a demo
Track status (complete/in-progress)
Use MAP as running agenda for check-in calls
If MAP isn't updated in 3 weeks, deal is dead

Decision Criteria:

Full account plans worth investment for top 10-20% of accounts by potential deal size. For rest, use simplified version (summary + MEDDICC + next steps).

Common Mistakes:

Creating account plan after deal is in motion (build before first engagement)
Not maintaining MAP weekly (stale MAP = stale deal)
Filling MEDDICC with assumptions instead of validated info
Mapping only obvious contacts instead of full org chart
Not tracking personal win for each stakeholder

完整的客户规划包含四个相互关联的部分，彼此相辅相成。

部分1：客户摘要

公司基本信息（总部、规模、行业、子公司）
技术架构（基础设施、工具、平台）
企业核心战略（来自新闻稿、年报、LinkedIn）
假设："我们能提供什么帮助？"（在对接前撰写）
LinkedIn关键词分析（量化他们在你的领域的投入）

部分2：组织架构图

梳理所有相关联系人：姓名、职位、所在地、LinkedIn、邮箱、电话、备注
备注内容：负责领域、技术专长、个人收益
涵盖各个层级的人员：高管、总监、架构师、负责人、专员
不要只梳理采购方，还要梳理影响者、使用者、潜在反对者

部分3：机会规划（MEDDICC）

M - 指标（Metrics）：客户将如何衡量成功？（已与EB确认）
E - 经济决策人（Economic Buyer）：谁拥有预算决策权？你是否已与他们对接？
D - 决策标准（Decision Criteria）：他们将依据什么标准做决策？（技术、业务、政治层面）
D - 决策流程（Decision Process）：他们的采购流程是什么？（采购、法务、安全审核）
I - 已明确的痛点（Identified Pain）：他们明确提出了哪些具体痛点？（用他们的原话，而非你的表述）
C - 内部支持者（Champion）：客户内部谁在主动为你推销？
C - 竞争对手（Competition）：他们还在评估哪些竞品？竞争态势如何？

附加内容：问题/风险表格，包含缓解方案、所需支持、负责人

部分4：共同行动计划（MAP）

联合时间规划：行动项、我方负责人、客户方负责人、其他参与人、截止日期
双方都必须有行动项——如果只有我方有行动项，那不是交易，只是演示
跟踪状态（已完成/进行中）
将MAP用作跟进会议的实时议程
如果MAP超过3周未更新，交易已失败

决策标准：

仅针对潜在交易金额排名前10-20%的客户，值得投入时间制定完整的客户规划。对于其他客户，使用简化版本（摘要+MEDDICC+下一步行动）。

常见误区：

在交易推进后才制定客户规划（应在首次对接前就完成）
未每周维护MAP（停滞的MAP=停滞的交易）
MEDDICC内容基于假设而非已验证的信息
仅梳理明显的联系人，而非完整的组织架构图
未跟踪每个利益相关者的个人收益

5. LinkedIn Keyword Analysis for Account Intelligence

5. 用于客户情报的LinkedIn关键词分析

Before engaging strategic account, quantify their investment in your domain via LinkedIn.

How to Execute:

Define 8-10 keywords relevant to your space (e.g., category terms, technical roles, workflow keywords)
Search LinkedIn for "[company name] + [keyword]" and record count
Map concentrations: Which locations? Which departments?
Identify outliers (high keyword concentration in specific departments signals maturity)

Why This Works:

If a company has 50 employees with "SRE" in their profile, they're mature in site reliability. If they have 2, they're not ready for advanced observability tools.

This tells you:

Whether to pursue the account (do they have the team?)
Who to target (where are the concentrations?)
How to personalize outreach (reference their specific context)

Example:

Searching "[Company] + DevOps":

120 results → Mature DevOps org, good fit
5 results → Early, not ready

Searching "[Company] + SRE":

50 results → They care about reliability, pitch uptime/incident reduction
0 results → Don't lead with SRE value prop

Common Mistakes:

Just searching job titles (vary wildly) instead of keywords (consistent)
Not comparing counts to total employee count
Not refreshing analysis (hiring trends change quarterly)

在对接战略客户前，通过LinkedIn量化他们在你的领域的投入。

执行方法：

定义8-10个与你的领域相关的关键词（例如，品类术语、技术职位、工作流程关键词）
在LinkedIn上搜索"[公司名称] + [关键词]"并记录结果数量
梳理分布情况：哪些地区？哪些部门？
识别异常值（特定部门的关键词浓度高意味着该领域成熟度高）

为什么有效：

如果一家公司有50名员工的个人资料中包含“SRE”（站点可靠性工程师），说明他们的站点可靠性领域成熟度高。如果只有2名，则他们还未准备好使用高级可观测性工具。

这能告诉你：

是否应该对接该客户（他们是否有对应的团队？）
应该瞄准谁（哪些部门浓度高？）
如何个性化沟通内容（参考他们的具体情况）

示例：

搜索"[公司名称] + DevOps"：

120条结果 → DevOps组织成熟度高，是优质潜在客户
5条结果 → 处于早期阶段，尚未准备好

搜索"[公司名称] + SRE"：

50条结果 → 他们关注可靠性，推销时重点强调正常运行时间/事件响应优化
0条结果 → 不要以SRE相关价值主张作为切入点

常见误区：

仅搜索职位头衔（差异极大）而非关键词（一致性高）
未将结果数量与员工总数进行对比
未定期更新分析结果（招聘趋势每季度都会变化）

6. The Unified Sales Process (Stage Gates)

6. 统一销售流程（阶段门控）

Enterprise sales follows defined stages with clear exit criteria. Don't advance stages without meeting criteria.

Stage 0 — Pipeline Generation: Prospecting → Qualified interest confirmed Stage 1 — Discovery: Environment/pain/requirements → Pain identified, stakeholders mapped Stage 2 — Demonstrating: Product demo, champion building → Champion identified Stage 3 — Proving Value: POC/trial → Technical validation complete Stage 4 — Proposal: Pricing, terms, scope → Proposal delivered, EB aligned Stage 5 — Paper Process: Legal, procurement, security → Approvals secured Stage 6 — Closed Won: Deal signed → Customer success handoff

Exit Criteria Matter:

Don't move from Stage 2 → Stage 3 until you have a champion. Don't move from Stage 3 → Stage 4 until POC success criteria are met. Don't move from Stage 4 → Stage 5 until EB has approved.

Common Mistake:

Advancing stages based on activity, not criteria. "We demoed, so we're in Stage 3" — but if they haven't agreed to POC, you're still in Stage 2.

企业销售遵循明确的阶段划分，每个阶段都有清晰的退出标准。未满足标准前不要推进到下一阶段。

阶段0 — 线索生成： 潜在客户开发 → 确认有合格意向 阶段1 — 需求探索： 环境/痛点/需求 → 明确痛点，梳理利益相关者 阶段2 — 产品演示： 产品演示、培养内部支持者 → 确定内部支持者 阶段3 — 价值验证： POC/试用 → 技术验证完成 阶段4 — 提案提交： 定价、条款、范围 → 提交提案，与EB对齐 阶段5 — 流程审批： 法务、采购、安全 → 获得审批 阶段6 — 交易成交： 签署合同 → 移交客户成功团队

退出标准至关重要：

不要在确定内部支持者前从阶段2推进到阶段3。不要在POC成功标准达成前从阶段3推进到阶段4。不要在EB批准前从阶段4推进到阶段5。

常见误区： 基于活动而非标准推进阶段。"我们做了演示，所以进入阶段3"——但如果客户未同意进行POC，你实际上仍处于阶段2。

Decision Trees

决策树

Do I Need a Full Account Plan?

我是否需要制定完整的客户规划？

Is deal size above average ACV?
├─ No → Simplified plan (summary + MEDDICC)
└─ Yes → Continue...
    │
    Sales cycle >60 days?
    ├─ Yes → Full account plan
    └─ No → Simplified plan

交易金额是否高于平均ACV？
├─ 否 → 简化规划（摘要 + MEDDICC）
└─ 是 → 继续...
    │
    销售周期是否超过60天？
    ├─ 是 → 完整客户规划
    └─ 否 → 简化规划

Is This Deal Actually Moving?

这笔交易是否真的在推进？

Is MAP being updated weekly?
├─ Yes → Healthy
└─ No → Continue...
    │
    Has it been >3 weeks since last MAP update?
    ├─ Yes → Dead deal (qualify out or reset)
    └─ No → At risk (escalate to champion)

MAP是否每周更新？
├─ 是 → 状态健康
└─ 否 → 继续...
    │
    距离上次MAP更新是否已超过3周？
    ├─ 是 → 交易失败（淘汰或重新规划）
    └─ 否 → 存在风险（联系内部支持者升级沟通）

Should I Send the Proposal?

我是否应该发送提案？

Have you met the Economic Buyer?
├─ No → Don't send yet (get EB access first)
└─ Yes → Continue...
    │
    Does EB agree on problem and success metrics?
    ├─ Yes → Send proposal
    └─ No → Align with EB before sending

你是否已对接经济决策人？
├─ 否 → 暂不发送（先对接EB）
└─ 是 → 继续...
    │
    EB是否认同问题和成功指标？
    ├─ 是 → 发送提案
    └─ 否 → 先与EB对齐再发送

Common Mistakes

常见误区

1. Creating account plan too late

Build before first engagement, not after deal is in motion

2. MEDDICC filled with assumptions

Validate each element with customer, don't guess

3. Stale Mutual Action Plan

If MAP isn't updated weekly, deal is stalling. 3+ weeks = dead.

4. Mapping only the buyer

Need full org chart: influencers, users, blockers

5. Ignoring personal wins

People buy for career/reputation reasons, not just business ROI

6. Not tracking deal health

Green/yellow/red indicators catch dying deals early

7. Skipping champion validation

Without internal champion, you're selling alone

1. 客户规划制定过晚

应在首次对接前完成，而非交易推进后

2. MEDDICC内容基于假设

每个要素都需与客户确认，不要猜测

3. 共同行动计划（MAP）停滞

如果MAP未每周更新，交易已停滞。超过3周=交易失败

4. 仅梳理采购方联系人

需要完整的组织架构图：影响者、使用者、反对者

5. 忽略个人收益

人们是为了职业/声誉利益而购买，而非仅为了业务投资回报率

6. 未跟踪交易健康度

绿/黄/红预警指标能提前发现濒临失败的交易

7. 未验证内部支持者

没有内部支持者，你就是在孤军奋战

gtm-enterprise-account-planning

Original

Translation

Enterprise Account Planning

企业客户规划

When to Use

适用场景

Core Frameworks

核心框架

1. If Your MAP Hasn't Been Updated in 3 Weeks, That Deal Is Dead

1. 若你的MAP已超过3周未更新，这笔交易已失败

2. The EB Discovery Problem (And Why Deals Die at Week 8)

2. EB对接缺失问题（以及为什么交易常在第8周失败）

3. Personal Win Mapping (People Buy for Themselves)

3. 个人收益映射（人们为自己而购买）

4. Enterprise Account Plan Structure (Four Components)

4. 企业客户规划结构（四个组成部分）

5. LinkedIn Keyword Analysis for Account Intelligence

5. 用于客户情报的LinkedIn关键词分析

6. The Unified Sales Process (Stage Gates)

6. 统一销售流程（阶段门控）

Decision Trees

决策树

Do I Need a Full Account Plan?

我是否需要制定完整的客户规划？

Is This Deal Actually Moving?

这笔交易是否真的在推进？

Should I Send the Proposal?

我是否应该发送提案？

Common Mistakes

常见误区

Quick Reference

快速参考

Related Skills

相关技能