Back to Details

company-research

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

目的

Create a comprehensive company profile that extracts executive insights, product strategy, transformation initiatives, and organizational dynamics from publicly available sources. Use this to understand competitive landscape, evaluate partnership opportunities, benchmark best practices, prepare for interviews, or inform market entry decisions by understanding how successful companies think about product management and strategy.
This is not surface-level research—it's strategic intelligence gathering focused on product management perspectives and executive vision.
创建一份全面的公司概况，从公开来源提取高管洞见、产品战略、转型举措和组织动态。通过了解成功企业对产品管理和战略的思考方式，以此来洞悉竞争格局、评估合作机会、对标最佳实践、为面试做准备，或是为市场进入决策提供依据。
这并非表面研究——而是聚焦于产品管理视角和高管愿景的战略情报收集。

Key Concepts

核心概念

The Executive Insights Framework

高管洞见框架

This framework synthesizes company intelligence across multiple dimensions:
Core Components:
  1. Company Overview: Basic info, history, industry context
  2. Executive Quotes: Strategic vision from CEO, COO, VP Product, Group PM
  3. Product Insights: Strategy, recent launches, innovation focus
  4. Transformation Strategies: Digital, AI, Agile transformations
  5. Organizational Impact: How PM influences strategy, cross-functional collaboration
  6. Future Roadmap: Upcoming initiatives and anticipated challenges
  7. Product-Led Growth (PLG): PLG strategies, data-driven decisions
该框架从多个维度整合公司情报：
核心组件：
  1. 公司概述： 基本信息、发展历程、行业背景
  2. 高管语录： CEO、COO、产品副总裁、集团产品经理的战略愿景
  3. 产品洞见： 战略方向、近期发布成果、创新重点
  4. 转型战略： 数字化、AI、敏捷转型
  5. 组织影响： 产品管理如何影响战略、跨职能协作
  6. 未来路线图： 即将开展的举措和预期挑战
  7. 产品驱动增长（PLG）： PLG战略、数据驱动决策

Why This Works

为何该框架有效

  • Executive perspective: Captures leadership thinking, not just marketing copy
  • Product-centric: Focuses on PM-relevant insights (strategy, process, culture)
  • Multi-source: Synthesizes interviews, earnings calls, blog posts, case studies
  • Strategic intelligence: Informs competitive positioning, partnership evaluation, or interview prep
  • 高管视角： 捕捉领导层的真实思考，而非仅营销话术
  • 产品聚焦： 专注于与产品管理相关的洞见（战略、流程、文化）
  • 多源整合： 综合访谈、财报电话会议、博客文章、案例研究等信息
  • 战略情报： 为竞争定位、合作评估或面试准备提供依据

Anti-Patterns (What This Is NOT)

反模式（框架不包含的内容）

  • Not financial analysis: Focus is product strategy, not valuation or stock performance
  • Not SWOT analysis: This documents their perspective, not strengths/weaknesses assessment
  • Not surface scraping: Go deeper than "About Us" pages—find executive interviews, product blogs, earnings transcripts
  • 非财务分析： 聚焦产品战略，而非估值或股票表现
  • 非SWOT分析： 记录企业自身视角，而非优劣评估
  • 非表面信息抓取： 深入挖掘，不止步于“关于我们”页面——需找到高管访谈、产品博客、财报文字记录

When to Use This

适用场景

  • Competitive analysis (understanding how competitors approach PM)
  • Partnership evaluation (assessing cultural fit and strategic direction)
  • Interview preparation (understanding company culture, product philosophy)
  • Benchmarking best practices (learning from successful companies)
  • Market entry decisions (understanding how incumbents operate)
  • 竞品分析（了解竞争对手的产品管理思路）
  • 合作评估（评估文化契合度和战略方向）
  • 面试准备（了解公司文化、产品理念）
  • 最佳实践对标（向成功企业学习）
  • 市场进入决策（了解现有企业的运营模式）

When NOT to Use This

不适用场景

  • For internal analysis (this is external research)
  • When primary sources are unavailable (executives haven't spoken publicly)
  • As a substitute for customer research (this is company perspective, not customer perspective)
  • 内部分析（本框架针对外部研究）
  • 无公开高管信息时（高管未公开发表言论）
  • 替代客户研究（本框架是企业视角，而非客户视角）

Application

应用方法

Use 
template.md
for the full fill-in structure.
使用
template.md
作为完整的填写模板。

Step 1: Define Research Scope

步骤1：定义研究范围

Clarify what you're researching and why:
markdown
undefined
明确研究对象和目的：
markdown
undefined

Research Objective

研究目标

  • Company Name: [e.g., "Stripe"]
  • Research Purpose: [e.g., "Understand payment platform product strategy for competitive positioning"]
  • Key Questions:
    • [Question 1: e.g., "How does Stripe think about platform extensibility?"]
    • [Question 2: e.g., "What's their approach to developer experience?"]
    • [Question 3: e.g., "How do they prioritize roadmap vs. custom enterprise requests?"]

---
  • 公司名称： [例如："Stripe"]
  • 研究目的： [例如："了解支付平台产品战略，用于竞争定位"]
  • 核心问题：
    • [问题1：例如："Stripe如何看待平台扩展性？"]
    • [问题2：例如："他们的开发者体验策略是什么？"]
    • [问题3：例如："他们如何平衡路线图优先级与企业定制需求？"]

---

Step 2: Gather Company Overview

步骤2：收集公司概述信息

Document basic company information:
markdown
undefined
记录公司基本信息：
markdown
undefined

Company Overview

公司概述

Basic Information:
  • Name: [Official company name]
  • Headquarters: [Location]
  • Industry: [Primary industries, e.g., "Fintech, Payment Processing, Developer Tools"]
  • Founded: [Year]
  • Size: [Employees, revenue if public, funding if private]
Brief History:
  • [Key milestones that shaped current market position]
  • [Example: "2010: Founded by Patrick and John Collison. 2011: Launched 7-line integration. 2018: Launched Stripe Atlas. 2021: $95B valuation."]

**Sources to check:**
- Company website (About, Press, Blog)
- LinkedIn company page
- Crunchbase / PitchBook (for funding/valuation)
- Wikipedia (for history)

---
基本信息：
  • 名称： [官方公司名称]
  • 总部： [地点]
  • 行业： [核心行业，例如："金融科技、支付处理、开发者工具"]
  • 成立时间： [年份]
  • 规模： [员工数量，上市公司填写营收，非上市公司填写融资情况]
简要发展历程：
  • [塑造当前市场地位的关键里程碑]
  • [示例："2010年：由Patrick和John Collison创立。2011年：推出7行代码集成功能。2018年：推出Stripe Atlas。2021年：估值达950亿美元。"]

**参考来源：**
- 公司官网（关于我们、新闻、博客板块）
- LinkedIn公司主页
- Crunchbase / PitchBook（融资/估值信息）
- Wikipedia（发展历程）

---

Step 3: Extract Executive Quotes on Strategic Vision

步骤3：提取高管战略愿景语录

Find recent quotes from key executives:
markdown
undefined
收集核心高管的近期言论：
markdown
undefined

Executive Quotes on Strategic Vision

高管战略愿景语录

Quote from the CEO:
  • "[Recent quote discussing long-term vision and market approach]"
  • Source: [Link to interview, earnings call, blog post, conference talk]
  • Date: [When the quote was made]
  • Context: [Brief explanation of what prompted this quote]
Quote from the COO:
  • "[Recent quote focusing on operational strategies and challenges]"
  • Source: [Link]
  • Date: [When]
Quote from the VP of Product Management:
  • "[Recent quote detailing product strategy and innovation focus]"
  • Source: [Link]
  • Date: [When]
Quote from the Group Product Manager:
  • "[Recent quote discussing specific product initiatives and customer engagement]"
  • Source: [Link]
  • Date: [When]

**Sources to check:**
- Earnings call transcripts (if public)
- Podcast interviews (e.g., Lenny's Podcast, Masters of Scale, How I Built This)
- Conference talks (YouTube, company blog)
- Blog posts by executives
- LinkedIn posts
- Industry publications (TechCrunch, The Verge, etc.)

**Quality checks:**
- **Recent:** Prioritize quotes from the last 12-24 months
- **Substantive:** Look for strategy/philosophy, not generic PR statements
- **Attributed:** Always cite source and date

---
CEO语录：
  • "[讨论长期愿景和市场策略的近期言论]"
  • 来源： [访谈、财报电话会议、博客文章、会议演讲链接]
  • 日期： [言论发表时间]
  • 背景： [言论发表的触发场景简要说明]
COO语录：
  • "[聚焦运营策略与挑战的近期言论]"
  • 来源： [链接]
  • 日期： [发表时间]
产品管理副总裁语录：
  • "[详述产品战略与创新重点的近期言论]"
  • 来源： [链接]
  • 日期： [发表时间]
集团产品经理语录：
  • "[讨论具体产品举措与客户互动的近期言论]"
  • 来源： [链接]
  • 日期： [发表时间]

**参考来源：**
- 财报电话会议文字记录（上市公司）
- 播客访谈（例如：Lenny's Podcast、Masters of Scale、How I Built This）
- 会议演讲（YouTube、公司博客）
- 高管发布的博客文章
- LinkedIn帖子
- 行业媒体（TechCrunch、The Verge等）

**质量审核标准：**
- **时效性：** 优先选择过去12-24个月的言论
- **实质性：** 聚焦战略/理念，而非通用公关话术
- **可溯源：** 始终标注来源和日期

---

Step 4: Document Product Insights

步骤4：记录产品洞见

Synthesize product strategy and recent launches:
markdown
undefined
整合产品战略与近期发布信息：
markdown
undefined

Detailed Product Insights

详细产品洞见

Product Strategy Overview:
  • [Describe overall product strategy, emphasizing integration of market needs with technological capabilities]
  • [Example: "Stripe's product strategy centers on developer experience: reduce integration complexity, provide powerful primitives, enable rapid experimentation"]
Recent Product Launches and Innovations:
  1. [Product/Feature 1] - [Description and market impact]
    • [Example: "Stripe Tax (2021): Automated sales tax calculation. Removed compliance barrier for global expansion."]
  2. [Product/Feature 2] - [Description and impact]
  3. [Product/Feature 3] - [Description and impact]
Product Philosophy:
  • [Key principles that guide product decisions]
  • [Example: "Start with developer needs, not enterprise sales. Build for 10x scale before you need it. Default to public APIs."]

**Sources to check:**
- Product blog or changelog
- Product Hunt launches
- Release notes
- Product team blog posts or case studies

---
产品战略概述：
  • [描述整体产品战略，强调市场需求与技术能力的结合]
  • [示例："Stripe的产品战略以开发者体验为核心：降低集成复杂度、提供强大基础组件、支持快速实验"]
近期产品发布与创新：
  1. [产品/功能1] - [描述与市场影响]
    • [示例："Stripe Tax（2021年）：自动化销售税计算。消除了全球扩张的合规障碍。"]
  2. [产品/功能2] - [描述与影响]
  3. [产品/功能3] - [描述与影响]
产品理念：
  • [指导产品决策的核心原则]
  • [示例："从开发者需求出发，而非企业销售需求。在需要前就为10倍规模构建。默认提供公开API。"]

**参考来源：**
- 产品博客或更新日志
- Product Hunt发布记录
- 版本说明
- 产品团队博客文章或案例研究

---

Step 5: Identify Transformation Strategies

步骤5：识别转型战略

Document how the company is evolving:
markdown
undefined
记录企业的演进方式：
markdown
undefined

Transformation Strategies and Initiatives

转型战略与举措

Digital Transformation:
  • [Describe approach to digital transformation, emphasizing integration of cutting-edge technology with existing processes]
  • [Example: "Migrated from monolith to microservices architecture (2019-2022). Enabled 10x faster feature deployment."]
AI Transformation:
  • [Explain how AI is incorporated into core processes, product offerings, and market positioning]
  • [Example: "Launched Radar for fraud detection (ML-powered). Reduced false positives by 40%, processing $640B annually."]
Agile Transformation:
  • [Detail adoption of Agile methodologies, highlighting improvements in collaboration, project management, product delivery]
  • [Example: "Adopted Shape Up methodology (6-week cycles, no sprints). Improved focus, reduced meeting overhead."]

**Sources to check:**
- Engineering blog
- Case studies or white papers
- Conference talks by engineering/product leaders
- LinkedIn posts about process changes

---
数字化转型：
  • [描述数字化转型方法，强调前沿技术与现有流程的整合]
  • [示例："从单体架构迁移到微服务架构（2019-2022年）。实现了10倍速的功能部署。"]
AI转型：
  • [说明AI如何融入核心流程、产品服务和市场定位]
  • [示例："推出基于机器学习的欺诈检测工具Radar。将误报率降低40%，年处理交易量达6400亿美元。"]
敏捷转型：
  • [详述敏捷方法论的应用，突出协作、项目管理、产品交付方面的改进]
  • [示例："采用Shape Up方法论（6周周期，无迭代冲刺）。提升了专注度，减少了会议冗余。"]

**参考来源：**
- 工程博客
- 案例研究或白皮书
- 工程/产品负责人的会议演讲
- 关于流程变更的LinkedIn帖子

---

Step 6: Understand Organizational Impact of Product Management

步骤6：理解产品管理的组织影响

Document how PM functions within the organization:
markdown
undefined
记录产品管理在组织中的作用：
markdown
undefined

Organizational Impact of Product Management

产品管理的组织影响

Role of Product Management in Strategic Decisions:
  • [Discuss how PM influences strategic decisions]
  • [Example: "PMs own P&L for their product area. Directly influence company roadmap through quarterly planning process. CEO reviews roadmap with PM leads, not just VPs."]
Cross-Functional Collaboration:
  • [Outline collaboration between PM and other departments]
  • [Example: "PMs co-located with engineering (not in separate 'product' org). Weekly design reviews with Design VP. Monthly GTM sync with Sales/Marketing."]
PM Career Paths:
  • [If available, describe how PMs grow and advance]
  • [Example: "IC track: PM → Senior PM → Staff PM → Principal PM. Manager track: PM → Group PM → Director → VP."]

**Sources to check:**
- PM job postings (describe role, responsibilities, team structure)
- LinkedIn profiles (track PM career progression)
- PM blog posts or interviews
- Glassdoor reviews (internal culture insights)

---
产品管理在战略决策中的角色：
  • [讨论产品管理如何影响战略决策]
  • [示例："产品经理负责其产品领域的损益。通过季度规划流程直接影响公司路线图。CEO与产品经理负责人而非仅副总裁审核路线图。"]
跨职能协作：
  • [概述产品管理与其他部门的协作方式]
  • [示例："产品经理与工程师同址办公（而非独立的‘产品’部门）。每周与设计副总裁进行设计评审。每月与销售/营销部门进行上市协同同步。"]
产品经理职业发展路径：
  • [若有相关信息，描述产品经理的成长与晋升路径]
  • [示例："个人贡献者路线：产品经理→高级产品经理→资深产品经理→首席产品经理。管理路线：产品经理→集团产品经理→总监→副总裁。"]

**参考来源：**
- 产品经理招聘启事（描述角色、职责、团队结构）
- LinkedIn个人资料（追踪产品经理职业发展）
- 产品经理博客文章或访谈
- Glassdoor评价（内部文化洞见）

---

Step 7: Analyze Future Roadmap and Challenges

步骤7：分析未来路线图与挑战

Identify where the company is headed:
markdown
undefined
明确企业的发展方向：
markdown
undefined

Future Product Roadmap and Challenges

未来产品路线图与挑战

Upcoming Product Initiatives:
  • [Detail planned initiatives and alignment with strategic goals]
  • [Example: "Expanding into embedded finance (Stripe Capital, Stripe Treasury). Goal: Become financial infrastructure for the internet, not just payments."]
Anticipated Market Challenges:
  • [Identify potential challenges and PM team plans to address them]
  • [Example: "Challenge: Increasing competition from Square, PayPal. Response: Double down on developer experience, global expansion (70+ countries)."]
Competitive Threats:
  • [Document acknowledged or observed competitive pressures]

**Sources to check:**
- Earnings calls (forward-looking statements)
- Analyst reports
- Industry news (funding rounds by competitors, market shifts)

---
即将开展的产品举措：
  • [详述计划中的举措及其与战略目标的契合度]
  • [示例："拓展嵌入式金融业务（Stripe Capital、Stripe Treasury）。目标：成为互联网的金融基础设施，而非仅支付服务商。"]
预期市场挑战：
  • [识别潜在挑战及产品团队的应对计划]
  • [示例："挑战：来自Square、PayPal的竞争加剧。应对：加倍投入开发者体验，推进全球扩张（覆盖70+国家）。"]
竞争威胁：
  • [记录已确认或观察到的竞争压力]

**参考来源：**
- 财报电话会议（前瞻性声明）
- 分析师报告
- 行业新闻（竞争对手融资、市场变化）

---

Step 8: Document Product-Led Growth Insights

步骤8：记录产品驱动增长洞见

If applicable, capture PLG strategies:
markdown
undefined
若适用，记录PLG战略：
markdown
undefined

Product-Led Growth Insights

产品驱动增长洞见

Implementation of PLG Strategies:
  • [Describe how the company employs PLG to enhance customer acquisition, retention, expansion]
  • [Example: "Self-serve onboarding: 7-line code integration. No sales calls required for <$1M ARR. 90% of customers start with free tier."]
Data-Driven Product Decisions:
  • [Explain role of data analytics in shaping product decisions and driving growth]
  • [Example: "Instrumented every API call. PMs have real-time dashboards. Feature adoption tracked within 24 hours of launch."]

**Sources to check:**
- Product analytics blog posts
- Growth team blog posts
- Case studies on activation, retention, expansion

---
PLG战略实施：
  • [描述企业如何运用PLG提升客户获取、留存与拓展]
  • [示例："自助式入职：7行代码集成。年经常性收入低于100万美元的客户无需销售对接。90%的客户从免费版开始使用。"]
数据驱动的产品决策：
  • [说明数据分析在产品决策和增长驱动中的作用]
  • [示例："对每个API调用进行监控。产品经理拥有实时数据仪表盘。功能发布后24小时内追踪采用情况。"]

**参考来源：**
- 产品分析博客文章
- 增长团队博客文章
- 关于激活、留存、拓展的案例研究

---

Step 9: Synthesize Key Takeaways

步骤9：整合核心结论

Summarize the most important insights:
markdown
undefined
总结最重要的洞见：
markdown
undefined

Key Takeaways

核心结论

Strategic Principles:
  1. [Principle 1] - [What you learned about their approach]
  2. [Principle 2] - [What you learned]
  3. [Principle 3] - [What you learned]
Product Management Lessons:
  1. [Lesson 1] - [Applicable insight for your context]
  2. [Lesson 2] - [Applicable insight]
  3. [Lesson 3] - [Applicable insight]
Questions for Further Research:
  • [Unanswered question 1]
  • [Unanswered question 2]

---
战略原则：
  1. [原则1] - [你学到的企业方法论]
  2. [原则2] - [你学到的内容]
  3. [原则3] - [你学到的内容]
产品管理经验：
  1. [经验1] - [可应用于自身场景的洞见]
  2. [经验2] - [可应用的洞见]
  3. [经验3] - [可应用的洞见]
待进一步研究的问题：
  • [未解决的问题1]
  • [未解决的问题2]

---

Examples

示例

See 
examples/sample.md
for a full company research example.
Mini example excerpt:
markdown
**Company Name:** Stripe
**Research Purpose:** Understand payment platform product strategy
**Key Questions:** Developer experience? Platform extensibility?
查看
examples/sample.md
获取完整的公司研究示例。
迷你示例片段：
markdown
**公司名称：** Stripe
**研究目的：** 了解支付平台产品战略
**核心问题：** 开发者体验？平台扩展性？

Common Pitfalls

常见误区

Pitfall 1: Surface-Level Research

误区1：表面研究

Symptom: "Stripe is a payments company. They process payments."
Consequence: No strategic insights.
Fix: Go deeper—find executive interviews, engineering blogs, product philosophy posts.
症状： "Stripe是一家支付公司，提供支付处理服务。"
后果： 无法获取战略洞见。
解决方法： 深入挖掘——找到高管访谈、工程博客、产品理念相关文章。

Pitfall 2: No Source Citations

误区2：未标注来源

Symptom: "The CEO said the company is focused on innovation"
Consequence: Unverifiable, low credibility.
Fix: Always cite source and date: "The CEO said X (Source: Lenny's Podcast, Episode 185, Sept 2023)."
症状： "CEO表示公司聚焦创新"
后果： 信息无法验证，可信度低。
解决方法： 始终标注来源和日期："CEO在Lenny's Podcast第185期（2023年9月）中提到X。"

Pitfall 3: Mixing Opinion with Facts

误区3：混淆观点与事实

Symptom: "Stripe's product strategy is great because they focus on developers"
Consequence: Analysis, not research.
Fix: Document what they do, not whether it's "good." Save analysis for "Key Takeaways."
症状： "Stripe的产品战略很棒，因为他们聚焦开发者"
后果： 这是分析，而非研究。
解决方法： 记录企业的实际做法，而非评价其优劣。分析内容放在“核心结论”部分。

Pitfall 4: Outdated Information

误区4：使用过时信息

Symptom: Using 5-year-old quotes or strategies
Consequence: Irrelevant insights (company strategies evolve).
Fix: Prioritize sources from the last 12-24 months.
症状： 使用5年前的言论或战略
后果： 洞见过时（企业战略会演变）。
解决方法： 优先选择过去12-24个月的来源。

Pitfall 5: Ignoring Negative Signals

误区5：忽略负面信号

Symptom: Only documenting successes, ignoring challenges or failures
Consequence: Incomplete picture.
Fix: Include "Anticipated Market Challenges" and competitive threats.
症状： 仅记录成功案例，忽略挑战或失败
后果： 信息不完整。
解决方法： 包含“预期市场挑战”和竞争威胁部分。

References

参考资料

Related Skills

相关技能

  • skills/positioning-statement/SKILL.md
    — Use company research to understand competitive positioning
  • skills/pestel-analysis/SKILL.md
    — Company research informs market context
  • skills/proto-persona/SKILL.md
    — Executive quotes may reveal target personas
  • skills/positioning-statement/SKILL.md
    — 利用公司研究了解竞争定位
  • skills/pestel-analysis/SKILL.md
    — 公司研究为市场背景提供信息
  • skills/proto-persona/SKILL.md
    — 高管言论可能揭示目标用户画像

External Frameworks

外部框架

  • Competitive intelligence frameworks
  • Strategic analysis methodologies
  • 竞争情报框架
  • 战略分析方法论

Dean's Work

Dean的相关成果

  • Executive Insights Company Profile Template
  • 高管洞见公司概况模板

Provenance

来源

  • Adapted from 
    prompts/company-profile-executive-insights-research.md
    in the 
    https://github.com/deanpeters/product-manager-prompts
    repo.
Skill type: Component Suggested filename: 
company-research.md
Suggested placement: 
/skills/components/
Dependencies: References 
skills/positioning-statement/SKILL.md
, 
skills/pestel-analysis/SKILL.md
  • 改编自
    https://github.com/deanpeters/product-manager-prompts
    仓库中的
    prompts/company-profile-executive-insights-research.md
    。
技能类型： 组件 建议文件名： 
company-research.md
建议存放路径： 
/skills/components/
依赖项： 参考
skills/positioning-statement/SKILL.md
、
skills/pestel-analysis/SKILL.md