customer-persona

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Customer Persona

客户角色（Customer Persona）

Create data-backed customer personas with research and visuals via inference.sh CLI.

通过inference.sh CLI，结合研究与视觉素材创建数据驱动的客户角色（Customer Persona）。

Quick Start

快速开始

bash

curl -fsSL https://cli.inference.sh | sh && infsh login

bash

curl -fsSL https://cli.inference.sh | sh && infsh login

Research your target market

调研目标市场

infsh app run tavily/search-assistant --input '{ "query": "SaaS product manager demographics pain points 2024 survey" }'

Generate a persona avatar

生成角色头像

infsh app run falai/flux-dev-lora --input '{ "prompt": "professional headshot photograph of a 35-year-old woman, product manager, friendly confident expression, modern office background, natural lighting, business casual attire, realistic portrait", "width": 1024, "height": 1024 }'

undefined

undefined

Persona Template

客户角色模板

┌──────────────────────────────────────────────────────┐
│  [Avatar Photo]                                      │
│                                                      │
│  SARAH CHEN, 34                                      │
│  Product Manager at a Series B SaaS startup          │
│                                                      │
│  "I spend more time making reports than making       │
│   decisions."                                        │
│                                                      │
├──────────────────────────────────────────────────────┤
│  DEMOGRAPHICS          │  PSYCHOGRAPHICS             │
│  Age: 30-38            │  Values: efficiency, data   │
│  Income: $120-160K     │  Personality: analytical,   │
│  Education: BS/MBA     │    organized, collaborative │
│  Location: Urban US    │  Interests: productivity,   │
│  Role: Product/PM      │    leadership, AI tools     │
├──────────────────────────────────────────────────────┤
│  GOALS                 │  PAIN POINTS                │
│  • Ship features       │  • Too many meetings        │
│  faster                │  • Manual reporting (15     │
│  • Data-driven         │    hrs/week)                │
│  decisions             │  • Stakeholder alignment    │
│  • Team alignment      │    is slow                  │
│  • Career growth to    │  • Tool sprawl (8+ apps)   │
│    Director            │  • No single source of      │
│                        │    truth                    │
├──────────────────────────────────────────────────────┤
│  CHANNELS              │  BUYING TRIGGERS            │
│  • LinkedIn (daily)    │  • Peer recommendation      │
│  • Product Hunt        │  • Free trial experience    │
│  • Podcasts (commute)  │  • Integration with Jira    │
│  • Lenny's Newsletter  │  • Team plan pricing        │
│  • Twitter/X           │  • ROI calculator           │
└──────────────────────────────────────────────────────┘

┌──────────────────────────────────────────────────────┐
│  [头像照片]                                      │
│                                                      │
│  SARAH CHEN，34岁                                      │
│  B轮SaaS初创公司产品经理          │
│                                                      │
│  "我花在做报告上的时间比做决策的时间还多。"                                        │
│                                                      │
├──────────────────────────────────────────────────────┤
│  人口统计特征          │  心理特征             │
│  年龄：30-38岁            │  价值观：效率、数据驱动   │
│  收入：12-16万美元     │  性格：善于分析、有条理、注重协作 │
│  学历：本科/硕士     │  兴趣：生产力提升、领导力培养、AI工具     │
│  所在地：美国城市地区    │  职位：产品经理/PM      │
├──────────────────────────────────────────────────────┤
│  目标                 │  痛点                │
│  • 更快交付功能       │  • 会议过多        │
│  • 基于数据做决策             │  • 手动报告（每周15小时）                │
│  • 团队协作对齐      │  • 利益相关者对齐效率低    │
│  • 晋升为产品总监                │  • 工具繁杂（8+款应用）   │
│                        │  • 缺乏统一数据源                    │
├──────────────────────────────────────────────────────┤
│  信息渠道              │  购买触发因素            │
│  • 领英（每日使用）    │  • 同行推荐      │
│  • Product Hunt        │  • 免费试用体验    │
│  • 播客（通勤时收听）  │  • 与Jira集成    │
│  • Lenny通讯  │  • 团队版定价        │
│  • Twitter/X           │  • ROI计算器           │
└──────────────────────────────────────────────────────┘

Building a Persona Step-by-Step

分步创建客户角色

Step 1: Research

步骤1：调研

Start with data, not assumptions.

bash

undefined

从数据入手，而非假设。

bash

undefined

Market demographics

市场人口统计数据

infsh app run tavily/search-assistant --input '{ "query": "product manager salary demographics 2024 survey report" }'

Pain points and challenges

痛点与挑战

infsh app run exa/search --input '{ "query": "biggest challenges facing product managers SaaS companies" }'

Tool usage patterns

工具使用模式

infsh app run tavily/search-assistant --input '{ "query": "most popular tools product managers use 2024 survey" }'

Content consumption habits

内容消费习惯

infsh app run exa/answer --input '{ "question": "Where do product managers get their industry news and professional development?" }'

undefined

infsh app run exa/answer --input '{ "question": "Where do product managers get their industry news and professional development?" }'

undefined

Step 2: Demographics

步骤2：人口统计特征

Use ranges, not exact values. Personas represent a segment, not one person.

Field	Format	Example
Age range	X-Y	30-38
Income range	$X-$Y	$120,000-$160,000
Education	Common degrees	BS Computer Science, MBA
Location	Region/type	Urban US, major tech hubs
Job title	Role level	Senior PM, Product Lead
Company size	Range	50-500 employees
Industry	Sector	B2B SaaS

使用范围值，而非精确值。角色代表一个群体，而非个人。

字段	格式	示例
年龄范围	X-Y	30-38岁
收入范围	$X-$Y	$120,000-$160,000
学历	常见学位	计算机科学本科、工商管理硕士
所在地	地区/类型	美国城市地区、主要科技 hub
职位	职级	高级产品经理、产品负责人
公司规模	范围	50-500名员工
行业	领域	B2B SaaS

Step 3: Psychographics

步骤3：心理特征

What they think, value, and believe.

Category	Questions to Answer
Values	What matters most to them professionally?
Attitudes	How do they feel about their industry's direction?
Motivations	What drives them at work?
Personality	Analytical vs intuitive? Leader vs collaborator?
Interests	What do they read/watch/listen to professionally?
Lifestyle	Work-life balance preference? Remote/hybrid/office?

他们的想法、价值观与信念。

类别	需要回答的问题
价值观	职业上对他们来说最重要的是什么？
态度	他们对行业发展方向的看法如何？
动机	工作中的驱动力是什么？
性格	善于分析还是凭直觉？领导者还是协作者？
兴趣	职业上他们会读/看/听什么内容？
生活方式	对工作与生活平衡的偏好？远程/混合/办公室办公？

Step 4: Goals

步骤4：目标

What they're trying to achieve (both professional and personal).

Professional:
- Ship features faster with fewer meetings
- Make data-driven decisions (not gut feelings)
- Get promoted to Director of Product within 2 years
- Build a more autonomous product team

Personal:
- Leave work by 6pm more often
- Be seen as a strategic leader, not a ticket manager
- Stay current with industry trends without information overload

他们想要实现的目标（职业与个人层面）。

职业目标：
- 更快交付功能，减少会议
- 基于数据做决策（而非直觉）
- 2年内晋升为产品总监
- 打造更自主的产品团队

个人目标：
- 更经常在6点前下班
- 被视为战略领导者，而非工单管理员
- 在不被信息淹没的前提下紧跟行业趋势

Step 5: Pain Points

步骤5：痛点

Quantify whenever possible. Vague pain = vague persona.

❌ "Has trouble with reporting"
✅ "Spends 15 hours per week creating manual reports for 4 different stakeholders"

❌ "Too many tools"
✅ "Uses 8 different tools daily (Jira, Slack, Notion, Figma, Analytics, Sheets, Docs, Email) with no unified view"

❌ "Meetings are a problem"
✅ "Averages 6 hours of meetings per day, leaving only 2 hours for deep work"

尽可能量化。模糊的痛点=模糊的角色。

❌ "报告有困难"
✅ "每周花费15小时为4位不同的利益相关者创建手动报告"

❌ "工具太多"
✅ "每天使用8种不同的工具（Jira、Slack、Notion、Figma、Analytics、Sheets、Docs、邮件），但没有统一视图"

❌ "会议成问题"
✅ "平均每天开会6小时，仅剩下2小时用于深度工作"

Step 6: Jobs-to-be-Done (JTBD)

步骤6：待办任务（Jobs-to-be-done，JTBD）

Three types of jobs:

Job Type	Description	Example
Functional	The task they need to accomplish	"Prioritize the product backlog based on customer impact data"
Emotional	How they want to feel	"Feel confident presenting to the exec team"
Social	How they want to be perceived	"Be seen as the person who makes data-driven decisions"

三类任务：

任务类型	说明	示例
功能性	他们需要完成的具体任务	"基于客户影响数据对产品待办事项排序"
情感性	他们想要获得的感受	"在向高管团队汇报时感到自信"
社会性	他们希望被他人如何看待	"被视为基于数据做决策的人"

Step 7: Buying Process

步骤7：购买流程

Stage	Behavior
Awareness	Reads blog posts, sees peer recommendations on LinkedIn
Consideration	Compares 3-4 tools, reads G2/Capterra reviews, asks in Slack communities
Decision	Requests demo, needs IT/security approval, evaluates team pricing
Influencers	Engineering lead, VP of Product, CFO (for budget)
Objections	"Will my team actually adopt it?", "Does it integrate with Jira?"
Trigger event	New quarter with aggressive goals, new VP demanding better reporting

阶段	行为
认知阶段	阅读博客文章，在领英上看到同行推荐
考虑阶段	对比3-4款工具，阅读G2/Capterra评论，在Slack社区咨询
决策阶段	申请演示，需要IT/安全审批，评估团队版定价
影响者	工程负责人、产品副总裁、CFO（负责预算）
异议	"我的团队真的会用吗？"、"它能与Jira集成吗？"
触发事件	新季度目标激进、新上任副总裁要求更完善的报告

Step 8: Generate Avatar

步骤8：生成头像

bash

undefined

bash

undefined

Match demographics: age, gender, ethnicity, professional context

匹配人口统计特征：年龄、性别、种族、职业背景

infsh app run falai/flux-dev-lora --input '{ "prompt": "professional headshot photograph of a 34-year-old Asian American woman, product manager, warm confident smile, modern tech office background, natural lighting, wearing smart casual blouse, realistic portrait photography, sharp focus", "width": 1024, "height": 1024 }'


**Avatar tips:**
- Match the age range, ethnicity representation, and professional context
- Use "professional headshot photograph" for realistic results
- Friendly, approachable expression (not stock-photo-stiff)
- Background suggests their work environment
- Business casual or industry-appropriate attire


**头像提示：**
- 匹配年龄范围、种族代表性与职业背景
- 使用"professional headshot photograph"以获得真实效果
- 表情友好、平易近人（不要像库存照片那样僵硬）
- 背景暗示他们的工作环境
- 商务休闲或符合行业的着装

The Anti-Persona

反角色

Equally important: who is NOT your customer.

ANTI-PERSONA: "Enterprise Earl"
- CTO at a 5,000+ person enterprise
- Needs SOC 2, HIPAA, on-premise deployment
- 18-month procurement cycles
- Wants white-glove onboarding and dedicated CSM
- WHY NOT: Our product is self-serve SaaS for SMB/mid-market.
  Enterprise needs would require 2+ years of product investment.

Anti-personas prevent wasted effort on customers you can't serve.

同样重要：谁不是你的客户。

反角色："企业Earl"
- 员工规模5000+的企业CTO
- 需要SOC 2、HIPAA合规，本地部署
- 18个月的采购周期
- 需要专属的白手套式入职服务和客户成功经理（CSM）
- 不适合的原因：我们的产品是面向中小企业（SMB）/中端市场的自助式SaaS。满足企业需求需要2年以上的产品投入。

反角色可避免在你无法服务的客户身上浪费精力。

Multiple Personas

多角色

Most products have 2-4 personas. More than 4 = too many to serve well.

Priority	Persona	Role
Primary	The main user and buyer	Who you optimize for
Secondary	Influences the buying decision	Who you need to convince
Tertiary	Uses the product occasionally	Who you support, not target

大多数产品有2-4个角色。超过4个=无法很好地服务所有用户。

优先级	角色	定位
主要	核心用户与购买者	产品优化的核心对象
次要	影响购买决策的角色	需要说服的对象
tertiary	偶尔使用产品的角色	需要支持但不作为目标的对象

Validation

验证

Personas based on assumptions are fiction. Validate with:

Method	What You Learn
Customer interviews (5-10)	Real language, real pain points
Support ticket analysis	Actual problems, not assumed ones
Analytics data	Actual behavior, not reported behavior
Survey (50+ responses)	Quantified patterns across segments
Sales call recordings	Objections, buying triggers, language

基于假设的角色是虚构的。通过以下方式验证：

方法	可获得的信息
客户访谈（5-10人）	真实的语言表达、真实痛点
支持工单分析	实际存在的问题，而非假设的问题
分析数据	实际行为，而非自述行为
调研（50+回复）	跨群体的量化模式
销售通话录音	异议、购买触发因素、常用语言

Common Mistakes

常见错误

Mistake	Problem	Fix
Based on assumptions	Fiction, not research	Start with data
Too many personas (6+)	Can't serve everyone well	Max 3-4
Vague pain points	Not actionable	Quantify everything
Demographics only	Misses motivations and behavior	Add psychographics, JTBD
Never updated	Becomes outdated	Review quarterly
No anti-persona	Wasted effort on wrong customers	Define who you're NOT for
Single persona for all	Different users have different needs	Primary/secondary/tertiary

错误	问题	解决方法
基于假设创建	角色是虚构的，而非基于研究	从数据入手
角色过多（6+个）	无法很好地服务所有用户	最多3-4个
痛点模糊	无法落地	尽可能量化
仅关注人口统计特征	忽略动机与行为	添加心理特征、JTBD
从不更新	角色过时	每季度回顾更新
没有反角色	在错误的客户身上浪费精力	明确你的非目标客户
单一角色覆盖所有用户	不同用户有不同需求	划分主要/次要/ tertiary角色

customer-persona

Original

Translation

Customer Persona

客户角色（Customer Persona）

Quick Start

快速开始

Research your target market

调研目标市场

Generate a persona avatar

生成角色头像

Persona Template

客户角色模板

Building a Persona Step-by-Step

分步创建客户角色

Step 1: Research

步骤1：调研

Market demographics

市场人口统计数据

Pain points and challenges

痛点与挑战

Tool usage patterns

工具使用模式

Content consumption habits

内容消费习惯

Step 2: Demographics

步骤2：人口统计特征

Step 3: Psychographics

步骤3：心理特征

Step 4: Goals

步骤4：目标

Step 5: Pain Points

步骤5：痛点

Step 6: Jobs-to-be-Done (JTBD)

步骤6：待办任务（Jobs-to-be-done，JTBD）

Step 7: Buying Process

步骤7：购买流程

Step 8: Generate Avatar

步骤8：生成头像

Match demographics: age, gender, ethnicity, professional context

匹配人口统计特征：年龄、性别、种族、职业背景

The Anti-Persona

反角色

Multiple Personas

多角色

Validation

验证

Common Mistakes

常见错误

Related Skills

相关技能