company-research

deanpeters/product-manager-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/deanpeters/product-manager-skills --skill company-research
0 commentsdiscussion
summary

Comprehensive company research brief extracting executive strategy, product vision, and organizational dynamics from public sources.

  • Synthesizes executive quotes, product launches, and transformation initiatives across eight structured research dimensions to build strategic intelligence
  • Focuses on product management perspectives and leadership thinking rather than financial analysis or surface-level company facts
  • Includes anti-patterns guidance (what this is not) and common pitfalls
skill.md

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

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

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.

Step 1: Define Research Scope

Clarify what you're researching and why:

## 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?"]

Step 2: Gather Company Overview

Document basic company information:

### 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)

Step 3: Extract Executive Quotes on Strategic Vision

Find recent quotes from key executives:

### 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

Step 4: Document Product Insights

Synthesize product strategy and recent launches:

### 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

Step 5: Identify Transformation Strategies

Document how the company is evolving:

### 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

Step 6: Understand Organizational Impact of Product Management

Document how PM functions within the organization:

### 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)

Step 7: Analyze Future Roadmap and Challenges

Identify where the company is headed:

### 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)

Step 8: Document Product-Led Growth Insights

If applicable, capture PLG strategies:

### 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
  • G
how to use company-research

How to use company-research on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add company-research
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/deanpeters/product-manager-skills --skill company-research

The skills CLI fetches company-research from GitHub repository deanpeters/product-manager-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/company-research

Reload or restart Cursor to activate company-research. Access the skill through slash commands (e.g., /company-research) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.766 reviews
  • James Singh· Dec 28, 2024

    I recommend company-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Valentina Park· Dec 12, 2024

    company-research reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kwame Khan· Dec 12, 2024

    company-research has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Mei Zhang· Dec 8, 2024

    Solid pick for teams standardizing on skills: company-research is focused, and the summary matches what you get after install.

  • Shikha Mishra· Dec 4, 2024

    Registry listing for company-research matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sofia Mensah· Nov 27, 2024

    company-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yash Thakker· Nov 23, 2024

    company-research reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sakura Martin· Nov 19, 2024

    Keeps context tight: company-research is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kwame Perez· Nov 15, 2024

    Useful defaults in company-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Torres· Nov 15, 2024

    company-research has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 66

1 / 7