customer-persona-builder
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCustomer Persona Builder
客户角色构建工具
Structured frameworks for creating data-driven customer personas, ideal customer profiles, and user archetypes.
用于创建数据驱动型客户角色、理想客户档案和用户原型的结构化框架。
Persona vs ICP Distinction
角色(Persona)与ICP的区别
When to Use Which
适用场景区分
IDEAL CUSTOMER PROFILE (ICP):
- Company-level / account-level description
- Used by: Sales, marketing (targeting), product (roadmap)
- Answers: "What companies should we sell to?"
- Firmographic: industry, size, revenue, tech stack
BUYER PERSONA:
- Individual-level description
- Used by: Sales (conversations), marketing (messaging), content
- Answers: "Who are the people making buying decisions?"
- Behavioral: goals, pain points, decision process
USER PERSONA:
- End-user description (may differ from buyer)
- Used by: Product, design, engineering
- Answers: "Who uses the product daily?"
- Task-based: workflows, jobs-to-be-done, frustrations
RELATIONSHIP:
ICP (company) contains multiple Buyer Personas (people)
who may differ from User Personas (daily users).IDEAL CUSTOMER PROFILE (ICP):
- 企业/客户账户层面的描述
- 使用方:销售、营销(目标定位)、产品(路线规划)
- 解决问题:“我们应该向哪些企业销售产品?”
- 企业特征:行业、规模、营收、技术栈
BUYER PERSONA:
- 个人层面的描述
- 使用方:销售(沟通对接)、营销(内容触达)、内容创作
- 解决问题:“谁是做出采购决策的人?”
- 行为特征:目标、痛点、决策流程
USER PERSONA:
- 终端用户描述(可能与买家不同)
- 使用方:产品、设计、工程
- 解决问题:“谁是日常使用产品的用户?”
- 任务特征:工作流、待办任务、使用痛点
关联关系:
ICP(企业)包含多个买家角色(个人),而这些买家角色可能与日常使用产品的用户角色不同。Ideal Customer Profile Template
理想客户档案(ICP)模板
ICP Framework
ICP框架
IDEAL CUSTOMER PROFILE:
FIRMOGRAPHICS:
- Industry: [specific verticals]
- Company Size: [employee range]
- Annual Revenue: [revenue range]
- Geography: [regions/countries]
- Growth Stage: [startup/growth/enterprise]
TECHNOGRAPHICS:
- Current Stack: [tools they use today]
- Infrastructure: [cloud, on-prem, hybrid]
- Maturity: [early adopter, mainstream, laggard]
BUSINESS CHARACTERISTICS:
- Pain Intensity: [how acute is the problem we solve]
- Budget Authority:[does this level have budget]
- Buying Process: [simple, committee, procurement]
- Contract Value: [expected ACV range]
QUALIFYING SIGNALS:
- Positive: [hiring for X role, using Y tool, in Z market]
- Negative: [too small, wrong industry, already solved]
DISQUALIFYING CRITERIA:
- [specific reasons to exclude]IDEAL CUSTOMER PROFILE:
企业特征:
- 行业: [具体垂直领域]
- 企业规模: [员工数量范围]
- 年营收: [营收范围]
- 地域: [地区/国家]
- 发展阶段: [初创/增长/成熟企业]
技术特征:
- 当前技术栈: [他们目前使用的工具]
- 基础设施: [云部署、本地部署、混合部署]
- 技术成熟度: [早期 adopters、主流用户、滞后用户]
业务特征:
- 痛点强度: [我们解决的问题有多迫切]
- 预算权限:[该层级是否有对应预算]
- 采购流程: [简单流程、委员会决策、采购部对接]
- 合同价值: [预期ACV范围]
合格信号:
- 正向信号: [招聘X岗位、使用Y工具、布局Z市场]
- 负向信号: [规模过小、行业不符、问题已解决]
disqualify 标准:
- [具体排除理由]ICP Scoring Matrix
ICP评分矩阵
| Attribute | Ideal (5) | Good (3) | Poor (1) | Weight |
|---|---|---|---|---|
| Industry | [exact verticals] | [adjacent verticals] | [unrelated] | 20% |
| Company Size | [sweet spot range] | [workable range] | [too small/large] | 15% |
| Pain Intensity | Active seeking solution | Aware of problem | Unaware | 25% |
| Budget | Dedicated budget exists | Can find budget | No budget | 20% |
| Tech Fit | Perfect stack match | Partial overlap | Incompatible | 10% |
| Champion | Identified internal advocate | Potential champion | No access | 10% |
SCORING THRESHOLDS:
4.0-5.0: Tier 1 — pursue aggressively
3.0-3.9: Tier 2 — pursue selectively
2.0-2.9: Tier 3 — qualify carefully
< 2.0: Disqualify| 属性 | 理想(5分) | 良好(3分) | 较差(1分) | 权重 |
|---|---|---|---|---|
| 行业 | [精准垂直领域] | [相邻垂直领域] | [无关领域] | 20% |
| 企业规模 | [最优范围] | [可合作范围] | [规模过小/过大] | 15% |
| 痛点强度 | 主动寻找解决方案 | 已意识到问题 | 未察觉问题 | 25% |
| 预算 | 有专用预算 | 可协调出预算 | 无预算 | 20% |
| 技术适配 | 完全匹配技术栈 | 部分重叠 | 不兼容 | 10% |
| 内部支持者 | 已确定内部倡导者 | 潜在倡导者 | 无对接渠道 | 10% |
评分阈值:
4.0-5.0: 一级客户 — 重点跟进
3.0-3.9: 二级客户 — 选择性跟进
2.0-2.9: 三级客户 — 谨慎筛选
< 2.0: 排除Buyer Persona Template
买家角色模板
Full Persona Document
完整角色文档
BUYER PERSONA:
──────────────────────────────────────────────
NAME: [Representative name, e.g., "Marketing Maria"]
ROLE: [Title / function]
REPORTS TO: [Their boss's role]
──────────────────────────────────────────────
DEMOGRAPHICS:
- Age Range: [25-35, 35-45, etc.]
- Education: [Degree, field]
- Career Stage: [IC, manager, director, VP, C-level]
- Income Range: [if relevant to pricing]
PROFESSIONAL CONTEXT:
- Team Size: [who they manage]
- Budget Authority: [Y/N, amount range]
- KPIs They Own: [what they're measured on]
- Tools They Use: [current stack]
- Reports They Read: [information sources]
GOALS (what they're trying to achieve):
1. [Primary business goal]
2. [Secondary business goal]
3. [Personal career goal]
PAIN POINTS (what frustrates them):
1. [Primary pain point]
Impact: [time, money, reputation]
2. [Secondary pain point]
Impact: [time, money, reputation]
3. [Tertiary pain point]
Impact: [time, money, reputation]
BUYING BEHAVIOR:
- Trigger Event: [what initiates their search]
- Research Process: [where they look for solutions]
- Decision Criteria: [ranked priorities]
1. [e.g., ease of use]
2. [e.g., integration with existing tools]
3. [e.g., price/value]
4. [e.g., vendor reputation]
5. [e.g., implementation speed]
- Decision Timeline: [typical buying cycle length]
- Influencers: [who else is involved]
OBJECTIONS:
1. [Common objection]
Root Cause: [underlying concern]
2. [Common objection]
Root Cause: [underlying concern]
MESSAGING THAT RESONATES:
- Value Prop: "[specific statement that speaks to their goals]"
- Proof Point: "[customer story or metric that builds credibility]"
- CTA: "[appropriate next step for this persona]"
QUOTE:
"[A representative statement capturing their perspective,
drawn from interviews or synthesized from research]"BUYER PERSONA:
──────────────────────────────────────────────
姓名: [代表性名称,例如“营销人Maria”]
职位: [头衔/职能]
汇报对象: [上级职位]
──────────────────────────────────────────────
人口统计特征:
- 年龄范围: [25-35, 35-45等]
- 教育背景: [学历、专业]
- 职业阶段: [执行层、经理、总监、副总裁、高管]
- 收入范围: [若与定价相关]
职业场景:
- 团队规模: [管理的员工数量]
- 预算权限: [是/否,预算范围]
- 负责的KPI: [考核指标]
- 使用工具: [当前技术栈]
- 参考报告: [信息来源]
目标(他们想要达成的结果):
1. [核心业务目标]
2. [次要业务目标]
3. [个人职业目标]
痛点(困扰他们的问题):
1. [核心痛点]
影响: [时间、成本、声誉]
2. [次要痛点]
影响: [时间、成本、声誉]
3. [三级痛点]
影响: [时间、成本、声誉]
采购行为:
- 触发事件: [启动搜索的契机]
- 调研流程: [寻找解决方案的渠道]
- 决策标准: [优先级排序]
1. [例如:易用性]
2. [例如:与现有工具集成]
3. [例如:性价比]
4. [例如:厂商声誉]
5. [例如:实施速度]
- 决策周期: [典型采购周期时长]
- 影响者: [其他参与决策的人]
常见异议:
1. [常见异议]
根本原因: [潜在顾虑]
2. [常见异议]
根本原因: [潜在顾虑]
有效触达话术:
- 价值主张: "[针对他们目标的具体表述]"
- 案例佐证: "[客户案例或数据,提升可信度]"
- 行动号召: "[针对该角色的合适下一步动作]"
代表性语录:
"[体现他们观点的代表性表述,
来自用户访谈或调研总结]"Data Sources for Persona Building
角色构建的数据来源
Primary Research Methods
一手研究方法
| Method | Best For | Sample Size | Time Investment |
|---|---|---|---|
| Customer interviews | Deep qualitative insights | 10-20 per persona | 2-4 weeks |
| Sales team interviews | Patterns from prospect conversations | 5-10 reps | 1 week |
| Customer success interviews | Post-purchase behavior, retention drivers | 5-10 CSMs | 1 week |
| Win/loss analysis | Decision criteria and competitive dynamics | 15-30 deals | 2-3 weeks |
| Surveys | Quantitative validation of qualitative findings | 100-500+ | 2-3 weeks |
| On-site observation | Real workflow and context understanding | 5-10 visits | 4-6 weeks |
| 方法 | 适用场景 | 样本量 | 时间投入 |
|---|---|---|---|
| 客户访谈 | 获取深度定性洞察 | 每个角色10-20人 | 2-4周 |
| 销售团队访谈 | 挖掘潜在客户对话中的规律 | 5-10名销售 | 1周 |
| 客户成功团队访谈 | 了解售后行为、留存驱动因素 | 5-10名CSM | 1周 |
| 赢单/丢单分析 | 分析决策标准与竞争动态 | 15-30个交易案例 | 2-3周 |
| 问卷调查 | 定量验证定性发现 | 100-500+样本 | 2-3周 |
| 现场观察 | 理解真实工作流与场景 | 5-10次走访 | 4-6周 |
Secondary Research Methods
二手研究方法
| Source | Data Type | Actionability |
|---|---|---|
| CRM data | Firmographics, deal history, conversion rates | High |
| Product analytics | Feature usage, engagement patterns, drop-off | High |
| Support tickets | Pain points, confusion areas, feature requests | High |
| G2/Capterra reviews | Buying criteria, competitor sentiment | Medium |
| Social media | Interests, content consumption, influence | Medium |
| Census / industry data | Market sizing, demographic baselines | Low-Medium |
| Job postings | Role responsibilities, tools, priorities | Medium |
| 来源 | 数据类型 | 可执行性 |
|---|---|---|
| CRM数据 | 企业特征、交易历史、转化率 | 高 |
| 产品分析数据 | 功能使用情况、参与度模式、流失点 | 高 |
| 支持工单 | 痛点、困惑点、功能需求 | 高 |
| G2/Capterra评价 | 采购标准、竞品口碑 | 中 |
| 社交媒体 | 兴趣、内容消费、影响力 | 中 |
| 人口普查/行业数据 | 市场规模、人口统计基线 | 中低 |
| 招聘信息 | 岗位职责、工具、优先级 | 中 |
Interview Question Bank
访谈问题库
DISCOVERY QUESTIONS (for persona interviews):
ROLE & CONTEXT:
- "Walk me through a typical day in your role."
- "What are the top 3 things you're measured on?"
- "Who do you report to, and what do they care about most?"
- "What tools do you use every day?"
GOALS:
- "What are you trying to accomplish this quarter/year?"
- "What does success look like in your role?"
- "If you could wave a magic wand, what would change?"
PAIN POINTS:
- "What's the most frustrating part of [process we address]?"
- "How do you currently solve [problem we address]?"
- "What have you tried that didn't work?"
- "How much time/money does this problem cost you?"
BUYING BEHAVIOR:
- "When you last evaluated a new tool, how did you start?"
- "Who else was involved in that decision?"
- "What was the single most important factor in your decision?"
- "What almost stopped you from buying?"
INFORMATION SOURCES:
- "Where do you go to learn about new tools or approaches?"
- "Which blogs, podcasts, or communities do you follow?"
- "Whose opinion do you trust most when making decisions?"角色访谈的探索性问题:
职位与场景:
- "请描述你日常工作的典型一天。"
- "你最重要的3个考核指标是什么?"
- "你向谁汇报,他们最关注什么?"
- "你每天都使用哪些工具?"
目标:
- "你本季度/今年想要达成什么目标?"
- "你职位上的成功是什么样的?"
- "如果你能一键改变一件事,会是什么?"
痛点:
- "[我们解决的流程中]最让你头疼的部分是什么?"
- "你目前是如何解决[我们解决的问题]的?"
- "你尝试过哪些无效的解决方案?"
- "这个问题会花费你多少时间/成本?"
采购行为:
- "你上次评估新工具时,是如何开始的?"
- "还有哪些人参与了那次决策?"
- "你决策时最重要的因素是什么?"
- "什么差点让你放弃采购?"
信息来源:
- "你会去哪里了解新工具或新方法?"
- "你关注哪些博客、播客或社区?"
- "做决策时,你最信任谁的意见?"Jobs-to-Be-Done Integration
待办任务(Jobs-to-Be-Done)整合
JTBD Framework for Personas
角色的JTBD框架
JOB STATEMENT FORMAT:
When [situation/trigger],
I want to [motivation/goal],
so I can [expected outcome].
EXAMPLE:
When I'm preparing the monthly board report,
I want to pull real-time metrics from all our tools,
so I can present accurate data without 4 hours of manual work.
JOB MAP:
1. DEFINE — What triggers the need?
2. LOCATE — Where do they search for solutions?
3. PREPARE — What setup is required?
4. CONFIRM — How do they validate it works?
5. EXECUTE — What does actual usage look like?
6. MONITOR — How do they track ongoing results?
7. MODIFY — What adjustments happen over time?
8. CONCLUDE — What does completion look like?任务陈述格式:
当[场景/触发事件]时,
我想要[动机/目标],
以便[预期结果]。
示例:
当我准备月度董事会报告时,
我想要从所有工具中提取实时指标,
以便无需4小时手动工作就能呈现准确数据。
任务地图:
1. 定义 — 需求的触发点是什么?
2. 寻找 — 他们去哪里搜索解决方案?
3. 准备 — 需要哪些前置设置?
4. 确认 — 他们如何验证方案可行?
5. 执行 — 实际使用场景是什么样的?
6. 监控 — 他们如何跟踪持续结果?
7. 调整 — 随着时间推移会做哪些调整?
8. 完成 — 完成的标准是什么?Outcome-Driven Persona Layer
结果导向的角色分层
FOR EACH PERSONA, MAP:
FUNCTIONAL JOBS:
- [Core task they need to accomplish]
- [Supporting tasks around the core]
EMOTIONAL JOBS:
- [How they want to feel]
- [How they want to be perceived]
SOCIAL JOBS:
- [How they want others to see them]
- [Status or recognition they seek]
RELATED JOBS:
- [Adjacent tasks that affect their success]
- [Upstream/downstream dependencies]针对每个角色,梳理:
功能性任务:
- [他们需要完成的核心任务]
- [核心任务的配套支持任务]
情感性任务:
- [他们希望获得的感受]
- [他们希望被如何看待]
社会性任务:
- [他们希望他人如何看待自己]
- [他们追求的地位或认可]
相关任务:
- [影响他们成功的相邻任务]
- [上下游依赖关系]Segmentation Approaches
细分方法
Segmentation Decision Matrix
细分决策矩阵
| Approach | Data Needed | Complexity | Actionability |
|---|---|---|---|
| Demographic | CRM / survey data | Low | Medium |
| Firmographic | Company data | Low | High (for B2B) |
| Behavioral | Product analytics, CRM | Medium | High |
| Needs-based | Interviews, surveys | Medium-High | Very High |
| Value-based | Revenue, CLV data | Medium | High |
| Psychographic | Survey, social data | High | Medium |
| 方法 | 所需数据 | 复杂度 | 可执行性 |
|---|---|---|---|
| 人口统计细分 | CRM/调研数据 | 低 | 中 |
| 企业特征细分 | 企业数据 | 低 | 高(B2B场景) |
| 行为细分 | 产品分析数据、CRM | 中 | 高 |
| 需求细分 | 访谈、调研 | 中高 | 极高 |
| 价值细分 | 营收、CLV数据 | 中 | 高 |
| 心理细分 | 调研、社交数据 | 高 | 中 |
Behavioral Segmentation Template
行为细分模板
BEHAVIORAL SEGMENTS:
POWER USERS:
- Usage: Daily, multiple features
- Engagement: High (>X sessions/week)
- Value: High CLV, likely to expand
- Strategy: Upsell, advocacy program
REGULAR USERS:
- Usage: Weekly, core features
- Engagement: Moderate
- Value: Stable, predictable revenue
- Strategy: Feature education, expansion
AT-RISK USERS:
- Usage: Declining, sporadic
- Engagement: Low (dropping)
- Value: At risk of churn
- Strategy: Re-engagement, CSM outreach
NEW USERS:
- Usage: Onboarding phase
- Engagement: Variable
- Value: Unknown (measuring)
- Strategy: Guided onboarding, quick winsBEHAVIORAL SEGMENTS:
核心用户:
- 使用频率: 每日使用,用到多个功能
- 参与度: 高(每周>X次会话)
- 价值: 高CLV,有扩展潜力
- 策略: 交叉销售,推荐计划
常规用户:
- 使用频率: 每周使用,用到核心功能
- 参与度: 中等
- 价值: 稳定、可预测的营收
- 策略: 功能教育,拓展使用场景
高流失风险用户:
- 使用频率: 下降、零散
- 参与度: 低(持续下降)
- 价值: 有流失风险
- 策略: 召回活动,CSM对接
新用户:
- 使用频率: 入门阶段
- 参与度: 波动
- 价值: 未知(待评估)
- 策略: 引导式入门,快速上手Validation and Iteration
验证与迭代
Persona Validation Checklist
角色验证清单
| Validation Step | Method | Status |
|---|---|---|
| Based on real data (not assumptions) | Cite sources for each attribute | [ ] |
| Validated with sales team | Sales reps recognize and agree | [ ] |
| Validated with CS team | Matches real customer behavior | [ ] |
| Quantitatively sized | Know how many of each persona exist | [ ] |
| Differentiated | Each persona triggers different actions | [ ] |
| Actionable | Marketing can write copy for each | [ ] |
| Prioritized | Clear tier 1 / tier 2 / tier 3 personas | [ ] |
| Reviewed with product | Product roadmap aligns to persona needs | [ ] |
| 验证步骤 | 方法 | 状态 |
|---|---|---|
| 基于真实数据(而非假设) | 为每个属性标注数据来源 | [ ] |
| 经销售团队验证 | 销售代表认可并同意 | [ ] |
| 经客户成功团队验证 | 匹配真实客户行为 | [ ] |
| 量化规模 | 清楚每个角色的数量 | [ ] |
| 差异化 | 每个角色对应不同行动策略 | [ ] |
| 可执行 | 营销团队可针对每个角色撰写内容 | [ ] |
| 优先级明确 | 清晰划分一级/二级/三级角色 | [ ] |
| 与产品团队对齐 | 产品路线图匹配角色需求 | [ ] |
Persona Anti-Patterns
角色构建常见误区
COMMON PERSONA MISTAKES:
1. OPINION-BASED PERSONAS
Problem: Built on internal assumptions, not data
Fix: Ground every attribute in interview/data evidence
2. TOO MANY PERSONAS
Problem: 8+ personas dilute focus and confuse teams
Fix: 3-5 primary personas maximum; merge similar ones
3. DEMOGRAPHIC-ONLY PERSONAS
Problem: "Female, 35-45, suburban" tells you nothing useful
Fix: Focus on goals, pain points, and buying behavior
4. STATIC PERSONAS
Problem: Created once and never updated
Fix: Quarterly review cadence with new data
5. PERSONAS WITHOUT PRIORITY
Problem: All personas treated equally
Fix: Rank by revenue potential and market size
6. PERSONA-MESSAGE DISCONNECT
Problem: Personas exist but messaging ignores them
Fix: Each persona gets specific value props and contentCOMMON PERSONA MISTAKES:
1. 主观臆断的角色
问题: 基于内部假设而非数据构建
修正: 每个属性都要有访谈/数据支撑
2. 角色数量过多
问题: 8个以上角色会分散精力、混淆团队
修正: 最多3-5个核心角色;合并相似角色
3. 仅基于人口统计特征的角色
问题: “女性,35-45岁,郊区居住”这类信息毫无实用价值
修正: 聚焦目标、痛点和采购行为
4. 静态角色
问题: 创建后从未更新
修正: 每季度结合新数据回顾
5. 无优先级的角色
问题: 所有角色被同等对待
修正: 按营收潜力和市场规模排序
6. 角色与话术脱节
问题: 角色存在但话术未针对性设计
修正: 为每个角色定制专属价值主张和内容Iteration Cadence
迭代周期
QUARTERLY REVIEW:
- Validate against latest win/loss data
- Check product analytics for behavior shifts
- Interview 3-5 recent customers
- Update pain points and priorities
- Refresh proof points and quotes
ANNUAL REBUILD:
- Full primary research cycle
- Re-validate ICP and persona segments
- Check market shifts and new competitors
- Align with updated company strategy
- Present updated personas to full org季度回顾:
- 结合最新赢单/丢单数据验证
- 查看产品分析数据,确认行为变化
- 访谈3-5位新客户
- 更新痛点与优先级
- 刷新案例佐证和代表性语录
年度重构:
- 完整的一手研究周期
- 重新验证ICP和角色细分
- 关注市场变化和新竞品
- 与更新后的公司战略对齐
- 向全公司展示更新后的角色See Also
相关链接
- Marketing
- Product Management
- Sales
- Data Science
- 营销
- 产品管理
- 销售
- 数据科学