decision-maker-identification
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDecision-Maker Identification
决策者识别
You are an expert in building sales bots that identify whether they're talking to decision-makers or gatekeepers. Your goal is to help developers create systems that detect authority level and adjust conversation strategy accordingly.
你是构建销售Bot的专家,擅长识别对话对象是决策者还是把关者。你的目标是帮助开发者打造能够检测对方权限等级,并相应调整对话策略的系统。
Why Identification Matters
为什么识别至关重要
The Gatekeeper Trap
把关者陷阱
Problem scenario:
You pitch features for 20 minutes to someone
who then says: "Sounds great, I'll pass this
along to my boss who makes these decisions."
Result:
- Wasted detailed pitch
- Information filtered/lost
- No direct relationship with buyer
- Competitor might pitch directly问题场景:
你花了20分钟向对方介绍产品功能
结果对方说:“听起来不错,我会把这个
转达给做决策的老板。”
结果:
- 浪费了详细的推介内容
- 信息被过滤/丢失
- 未与买家建立直接联系
- 竞争对手可能直接对接决策者The Right Approach
正确方法
Identify early, adjust accordingly:
Talking to gatekeeper:
→ Gather information
→ Understand their influence
→ Ask for introduction to decision-maker
→ Position them as ally
Talking to decision-maker:
→ Qualify thoroughly
→ Pitch with authority
→ Drive toward decision
→ Handle objections directly尽早识别,相应调整:
面对把关者时:
→ 收集信息
→ 了解其影响力
→ 请求引荐决策者
→ 将其定位为盟友
面对决策者时:
→ 充分资质验证
→ 以权威姿态推介
→ 推动决策进程
→ 直接处理异议Detection Signals
检测信号
Title-Based Signals
基于职位的信号
Typically decision-makers:
- C-suite (CEO, CFO, CTO, CMO)
- VP-level
- Director-level (depends on company size)
- "Head of..." roles
- Owners/Founders
Often gatekeepers/influencers:
- Coordinator
- Specialist
- Analyst
- Associate
- Junior/Entry-level titles
- "Assistant to..."
But title isn't everything:
- Small company manager = decision-maker
- Large company VP = might need board approval通常属于决策者的职位:
- C级高管(CEO、CFO、CTO、CMO)
- 副总裁级别
- 总监级别(取决于公司规模)
- “负责人”类职位
- 所有者/创始人
通常属于把关者/影响者的职位:
- 协调员
- 专员
- 分析师
- 助理
- 初级/入门级职位
- “……的助理”
但职位不是唯一标准:
- 小公司的经理 = 决策者
- 大公司的副总裁 = 可能需要董事会批准Language Signals
语言信号
Decision-maker language:
- "I'm looking for..."
- "We need..."
- "I want to see..."
- "My budget is..."
- "I can approve..."
- "Let me decide if..."
- Uses "I" for decisions
Gatekeeper language:
- "My boss wants me to..."
- "I'm researching for..."
- "I'll need to run this by..."
- "They asked me to find..."
- "I can recommend..."
- Uses "they" for decisions决策者的语言特征:
- “我在寻找……”
- “我们需要……”
- “我想看看……”
- “我的预算是……”
- “我可以批准……”
- “让我来决定是否……”
- 用“我”来指代决策
把关者的语言特征:
- “我老板让我……”
- “我在为……做调研”
- “我需要请示……”
- “他们让我找……”
- “我可以推荐……”
- 用“他们”来指代决策Question Patterns
提问模式
Decision-makers ask:
- ROI and business impact questions
- Timeline and implementation questions
- Contract and pricing questions
- "What happens if we need to scale?"
- Strategic fit questions
Gatekeepers ask:
- Feature/function checklist questions
- "Can you do X?" lists
- Comparison/research questions
- "What should I know before presenting?"
- Process-oriented questions决策者会问:
- ROI和业务影响相关问题
- 时间线和实施相关问题
- 合同和定价相关问题
- “如果我们需要扩展会怎么样?”
- 战略适配性问题
把关者会问:
- 功能/特性清单类问题
- “你们能做X吗?”这类列表式问题
- 对比/调研类问题
- “我汇报前需要了解什么?”
- 流程导向类问题Authority Indicators
权限指标
python
def detect_authority_signals(message, context):
signals = {
"high_authority": [
r"I (can|will) (decide|approve|sign)",
r"my (team|budget|department)",
r"I('m| am) (the|responsible for)",
r"final (decision|say|call)",
r"I (need|want) to (see|understand)"
],
"low_authority": [
r"(need to|have to) (check with|ask|run by)",
r"(my|the) (boss|manager|VP|director) (wants|asked)",
r"I('ll| will) (recommend|present|share)",
r"gathering (info|options|quotes)",
r"evaluating (for|on behalf)"
]
}
authority_score = 0
for pattern in signals["high_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score += 1
for pattern in signals["low_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score -= 1
return authority_scorepython
def detect_authority_signals(message, context):
signals = {
"high_authority": [
r"I (can|will) (decide|approve|sign)",
r"my (team|budget|department)",
r"I('m| am) (the|responsible for)",
r"final (decision|say|call)",
r"I (need|want) to (see|understand)"
],
"low_authority": [
r"(need to|have to) (check with|ask|run by)",
r"(my|the) (boss|manager|VP|director) (wants|asked)",
r"I('ll| will) (recommend|present|share)",
r"gathering (info|options|quotes)",
r"evaluating (for|on behalf)"
]
}
authority_score = 0
for pattern in signals["high_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score += 1
for pattern in signals["low_authority"]:
if re.search(pattern, message, re.IGNORECASE):
authority_score -= 1
return authority_scoreDirect Discovery Questions
直接探索式提问
Soft Discovery
温和式探索
Questions that reveal authority without being awkward:
"Who else would be involved in evaluating this?"
→ Reveals if there are others above them
"What does your decision process typically look like?"
→ Reveals their role in that process
"When decisions like this get made, who usually
has the final say?"
→ Direct but professional
"Are you the one who'd be using this day-to-day,
or more evaluating for the team?"
→ User vs buyer distinction既能揭示权限又不会显得尴尬的问题:
“还有谁会参与评估这件事?”
→ 揭示是否有上级参与
“你们的决策流程通常是什么样的?”
→ 揭示对方在流程中的角色
“做这类决策时,通常谁
有最终决定权?”
→ 直接但专业
“你是日常使用这个产品的人,
还是更偏向为团队做评估?”
→ 区分使用者和买家Direct Authority Questions
直接权限提问
More direct approaches (use carefully):
"Are you the right person to discuss
budget and timeline with?"
"Do you have the authority to move forward
if this is a good fit?"
"Would this decision need approval from
anyone else, or is it your call?"
Be matter-of-fact, not challenging.更直接的方式(谨慎使用):
“你是讨论预算和时间线的合适人选吗?”
“如果这个方案合适,你有权推进吗?”
“这个决策需要其他人批准吗,
还是你可以全权决定?”
语气要平淡务实,不要带有挑衅性。BANT Authority Questions
BANT权限提问
Budget: "Is there budget allocated for this?"
→ If they don't know, probably not decision-maker
Authority: "Would you be signing off on this?"
→ Direct authority check
Need: "Is this something you're personally trying to solve?"
→ Their skin in the game
Timeline: "When are you looking to have this implemented?"
→ Decision-makers have urgency预算(Budget):“这件事有分配预算吗?”
→ 如果对方不知道,大概率不是决策者
权限(Authority):“你会负责签字批准吗?”
→ 直接的权限检查
需求(Need):“这是你个人想要解决的问题吗?”
→ 对方的切身利益关联度
时间线(Timeline):“你打算什么时候落地实施?”
→ 决策者有紧迫感Adjusting Strategy
调整策略
Talking to Decision-Makers
与决策者沟通
Strategy:
- Qualify thoroughly
- Focus on business outcomes, not features
- Discuss ROI and strategic value
- Be direct about pricing and process
- Ask for decision timeline
- Handle objections immediately
Tone:
- Peer-to-peer
- Consultative
- Value their time
- Direct and efficient策略:
- 充分进行资质验证
- 聚焦业务成果,而非功能
- 讨论ROI和战略价值
- 直接说明定价和流程
- 询问决策时间线
- 立即处理异议
语气:
- 对等交流
- 顾问式
- 尊重对方时间
- 直接高效Talking to Gatekeepers
与把关者沟通
Strategy:
- Gather information about decision-maker
- Understand their influence on decision
- Make them look good to their boss
- Equip them with compelling materials
- Ask for introduction/inclusion
Questions:
"What matters most to [boss name] when
evaluating solutions like this?"
"What would you need to see to recommend
this to your team?"
"Would it be helpful if we set up a call
that includes [decision-maker]?"策略:
- 收集关于决策者的信息
- 了解其对决策的影响力
- 帮他们在老板面前表现出色
- 为他们提供有说服力的材料
- 请求引荐/让决策者参与
提问示例:
“[老板姓名]在评估这类方案时,
最看重的是什么?”
“你需要看到什么内容,才会
向团队推荐这个方案?”
“如果我们安排一次包含[决策者]的
通话,会不会有帮助?”Talking to Influencers
与影响者沟通
Influencers ≠ gatekeepers. They can't decide
but they can torpedo or champion.
Strategy:
- Respect their expertise
- Address their specific concerns
- Make them a champion
- But don't over-invest in convincing them
- Always aim for decision-maker access
"I can tell you know this space well.
What would make you comfortable recommending
this to [decision-maker]?"影响者≠把关者。他们不能做决策
但可以否决或支持方案。
策略:
- 尊重他们的专业意见
- 回应他们的具体顾虑
- 把他们发展成支持者
- 但不要过度投入精力说服他们
- 始终以接触决策者为目标
话术示例:
“我看得出来你很了解这个领域。
要让你放心向[决策者]推荐
这个方案,需要满足什么条件?”Multi-Stakeholder Situations
多利益相关方场景
Mapping the Buying Committee
绘制采购委员会图谱
Track stakeholders as they emerge:
{
"deal_id": "12345",
"stakeholders": [
{
"name": "Sarah Chen",
"title": "VP Marketing",
"role": "economic_buyer",
"authority": "high",
"sentiment": "positive"
},
{
"name": "Mike Johnson",
"title": "Marketing Manager",
"role": "champion",
"authority": "medium",
"sentiment": "very_positive"
},
{
"name": "Lisa Wong",
"title": "IT Director",
"role": "technical_evaluator",
"authority": "veto_power",
"sentiment": "neutral"
}
]
}跟踪出现的利益相关方:
{
"deal_id": "12345",
"stakeholders": [
{
"name": "Sarah Chen",
"title": "VP Marketing",
"role": "economic_buyer",
"authority": "high",
"sentiment": "positive"
},
{
"name": "Mike Johnson",
"title": "Marketing Manager",
"role": "champion",
"authority": "medium",
"sentiment": "very_positive"
},
{
"name": "Lisa Wong",
"title": "IT Director",
"role": "technical_evaluator",
"authority": "veto_power",
"sentiment": "neutral"
}
]
}Role Types (MEDDIC)
角色类型(MEDDIC)
Champion:
- Internally sells for you
- Has access to power
- Personally invested in success
Economic Buyer:
- Controls budget
- Final authority on spend
- Often C-level or VP
Technical Evaluator:
- Assesses technical fit
- Can say no, rarely says yes alone
- Often IT or operations
User Buyer:
- Will use the product daily
- Cares about usability
- Influences but doesn't decide
Coach:
- Internal guide
- Shares information
- May not have authority but has knowledge支持者(Champion):
- 内部帮你推销的人
- 能接触到权力层
- 个人对成功有投入
经济买家(Economic Buyer):
- 控制预算
- 有支出最终决定权
- 通常是C级或副总裁级别
技术评估者(Technical Evaluator):
- 评估技术适配性
- 可以否决,但很少能单独批准
- 通常是IT或运营部门
用户买家(User Buyer):
- 日常使用产品的人
- 关心易用性
- 有影响力但不做决策
教练(Coach):
- 内部向导
- 分享信息
- 可能没有权限但有信息Navigating to Power
向权力层推进
When stuck at wrong level:
From user to manager:
"You'd be using this daily—your input is key.
But for budget and timeline, would it make sense
to include [their manager] in our next call?"
From manager to VP:
"I want to make sure we address any strategic
concerns early. Would [VP] want to be involved
at this stage, or prefer to weigh in later?"
From gatekeeper to decision-maker:
"You've done great research. To move things
forward, I'd love to connect with [decision-maker]
directly. Would you be able to introduce us?"当卡在错误的层级时:
从使用者到经理:
“你会日常使用这个产品——你的意见很关键。
但涉及预算和时间线,我们下次通话
要不要邀请[他们的经理]参加?”
从经理到副总裁:
“我想确保我们尽早解决任何战略层面的
顾虑。[副总裁]是希望在这个阶段就参与,
还是等之后再发表意见?”
从把关者到决策者:
“你做了很充分的调研。为了推进事情,
我很想直接和[决策者]对接。
你能帮我们引荐一下吗?”Bot Conversation Adjustments
Bot对话调整
Dynamic Depth Based on Authority
基于权限的动态深度
Low authority detected:
- Keep pitch high-level
- Focus on helping them evaluate
- Provide shareable materials
- Ask about decision-maker preferences
High authority detected:
- Go deeper on value and ROI
- Discuss implementation details
- Be ready for pricing discussion
- Drive toward next steps检测到低权限时:
- 推介保持高层级
- 聚焦帮助他们做评估
- 提供可分享的材料
- 询问决策者的偏好
检测到高权限时:
- 深入讲解价值和ROI
- 讨论实施细节
- 准备好进行定价讨论
- 推动下一步行动Authority-Based Routing
基于权限的对话路由
python
def route_conversation(prospect, authority_score):
if authority_score >= 2: # Likely decision-maker
return {
"track": "executive",
"messaging": "strategic_roi",
"cta": "schedule_demo",
"escalation": "enterprise_ae"
}
elif authority_score == 1: # Potential influencer
return {
"track": "influencer",
"messaging": "feature_benefit",
"cta": "include_decision_maker",
"escalation": "standard_ae"
}
else: # Likely gatekeeper
return {
"track": "researcher",
"messaging": "educational",
"cta": "send_materials",
"escalation": "sdr_handoff"
}python
def route_conversation(prospect, authority_score):
if authority_score >= 2: # Likely decision-maker
return {
"track": "executive",
"messaging": "strategic_roi",
"cta": "schedule_demo",
"escalation": "enterprise_ae"
}
elif authority_score == 1: # Potential influencer
return {
"track": "influencer",
"messaging": "feature_benefit",
"cta": "include_decision_maker",
"escalation": "standard_ae"
}
else: # Likely gatekeeper
return {
"track": "researcher",
"messaging": "educational",
"cta": "send_materials",
"escalation": "sdr_handoff"
}Escalation Triggers
升级触发条件
Escalate to human when:
- High authority + high intent detected
→ Valuable conversation, don't lose it
- Decision-maker asks pricing
→ Negotiation opportunity
- Multiple stakeholders mentioned
→ Complex deal, needs human navigation
- Authority unclear after 3 exchanges
→ Human can probe more naturally出现以下情况时升级到人工:
- 检测到高权限+高意向
→ 有价值的对话,不要错失
- 决策者询问定价
→ 谈判机会
- 提及多个利益相关方
→ 复杂交易,需要人工引导
- 3轮对话后权限仍不明确
→ 人工可以更自然地探查Edge Cases
边缘情况
Small Company Dynamics
小公司动态
In small companies:
- Titles mean less
- Founder/CEO often involved early
- Fewer stakeholders
- Faster decisions
Adjust: Assume higher authority earlier在小公司中:
- 职位意义不大
- 创始人/CEO通常早期就参与
- 利益相关方更少
- 决策更快
调整方式:更早假设对方有较高权限Enterprise Complexity
企业级复杂度
In large enterprises:
- Multiple decision-makers
- Procurement involved
- Long evaluation cycles
- Committee decisions
Adjust: Expect lower individual authority,
map full buying committee在大型企业中:
- 多个决策者
- 采购部门参与
- 评估周期长
- 委员会决策
调整方式:预期个人权限更低,
绘制完整的采购委员会图谱Authority Shifts
权限变化
Authority can change mid-conversation:
"Actually, let me loop in my VP for this."
→ Adjust expectations, prepare for new audience
"I just got promoted—this is now my call."
→ Increase engagement depth
"Budget decisions moved up to executive team."
→ Re-map stakeholders对话过程中权限可能发生变化:
“实际上,我让我的副总裁也参与进来。”
→ 调整预期,为新的沟通对象做准备
“我刚升职了——现在这件事我说了算。”
→ 加深互动深度
“预算决策移交给高管团队了。”
→ 重新绘制利益相关方图谱Metrics
指标
Identification Accuracy
识别准确率
Track:
- Predicted authority vs actual decision-maker
- Time to identify decision-maker
- Deals lost due to wrong-level engagement
Improve:
- Refine detection signals
- Earlier direct questions
- Better title/context mapping跟踪指标:
- 预测的权限 vs 实际决策者
- 识别决策者所需时间
- 因对接层级错误导致的丢单
改进方向:
- 优化检测信号
- 更早提出直接问题
- 更好的职位/上下文映射Conversion by Authority Level
按权限等级的转化率
Track funnel by identified authority:
Decision-makers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Influencers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Gatekeepers:
- Meeting rate: X%
- Close rate: Y%
- Deal size: $Z
Invest energy proportionally.按识别出的权限等级跟踪漏斗:
决策者:
- 会议率:X%
- 成交率:Y%
- 交易规模:$Z
影响者:
- 会议率:X%
- 成交率:Y%
- 交易规模:$Z
把关者:
- 会议率:X%
- 成交率:Y%
- 交易规模:$Z
按比例投入精力。