All skills
deanpeters avatar

/company-research

@b68bf96

Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/company-research

This session only. Nothing lands on disk.

examplessample-lifesciences.md

≈1.5k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Company Research Example — Life Sciences

A research brief on Brightwater Biologics, a clinical-stage biotech, prepared by a PM ahead of an interview for a product role on its Trialpath platform team.

Why this domain changes the research: a biotech's public record is unusually rich — trial registries, regulatory filings, conference presentations — and unusually misleading if you read it as a software company. Revenue may be zero by design. Headcount growth may signal a trial phase, not commercial traction. The signals mean different things.


## Executive Insights Company Profile: Brightwater Biologics

### 1. What This Entity Is
Clinical-stage biotech developing therapies in a specialty indication. Pre-commercial:
no approved product, no product revenue. Funded by venture rounds and a partnership.
~180 employees, roughly a quarter in clinical operations.
[FACT — company site, public funding announcements]

### 2. How It Makes Money
It does not, yet. Capital comes from investors and partnership milestones. The economic
model is: spend years generating evidence, then either commercialize or license.
[FACT — funding disclosures]

**Why this matters for a PM:** every internal product competes with the trial program
for the same capital. "Is this worth building" is really "is this worth NOT spending on
the program." [INFERENCE]

### 3. Who It Serves
Two distinct populations. Externally: patients, investigators, regulators.
Internally, for Trialpath: study coordinators at sites, CRA monitors, CRO partners.
The internal users do not work for Brightwater — sites are independent organizations.
[FACT — trial registry lists participating sites]

### 4. What It Sells or Delivers
Currently: evidence. The deliverable is a data package that supports a regulatory
submission. Trialpath exists to make producing that package faster and cleaner.
[INFERENCE from the trial-stage profile]

### 5. Key Product Lines
- Lead therapeutic program (the company's actual product)
- Trialpath, internal platform — recently the subject of external licensing interest
[FACT — job postings reference "platform productization"]

### 6. Business and Market Pressures
- Trial timelines drive everything; a delayed readout moves the funding calendar
- Site staffing shortages slow enrollment industry-wide
- Small-sponsor funding is rate-sensitive
[FACT/INFERENCE mix — see sources]

### 7. Competitors and Alternatives
For the therapy: other programs in the indication. For Trialpath: incumbent trial
platforms, and the status quo of spreadsheets plus email at small sponsors.
[INFERENCE — no public statement on platform competitors]

### 8. Important Trends and Risks
- Decentralized trial designs shifting coordinator workflows
- AI-assisted document review maturing, regulatory acceptability unsettled
- **Concentration risk:** one lead program. A trial setback is a company event, and the
  platform team's funding is downstream of it [INFERENCE — high confidence]

### 9. Strategic Signals
- **Hiring:** three product roles posted in six months, all platform-facing, none
  therapeutic. Language emphasizes "multi-tenant" and "validation documentation"
  [FACT — job postings, dated]
- **Leadership:** a VP Product hired last year from a trial software vendor, not from
  pharma [FACT — public announcement]
- **Conference activity:** presentations focus on operational efficiency, not
  clinical results — consistent with a program in an interim period [INFERENCE]

**Read together:** a hire from a software vendor, plus "multi-tenant" and "validation
documentation" in postings, plus operational-efficiency messaging, suggests Trialpath
productization is being seriously explored rather than idly considered. [INFERENCE —
three independent signals converging]

### 10. What This Means for Product Management
- You would be building for users employed by other organizations. Access is scheduled,
  bounded, and mediated by site leadership
- Validation documentation is likely the gating work item, not a compliance follow-up
- The role's scope may hinge on a licensing decision that is not yours to make
- **Interview question worth asking:** "Is Trialpath a product, an internal tool, or
  undecided — and who decides?" The answer defines the job

### 11. Sources and Confidence
- Company site, funding announcements, trial registry, job postings, conference agenda
  — all public, all dated
- **Confidence: Medium-High** on structure and signals; **Low** on strategic intent,
  which is inferred from hiring language rather than stated anywhere
- **Thin:** no public information on Trialpath's current scale or internal satisfaction

What this example teaches that the SaaS one can't

  • Zero revenue is a finding, not a red flag. Reading a clinical-stage biotech through a SaaS lens produces "pre-revenue, high risk" and stops. The useful read is that capital allocation, not revenue, is the tension every internal product lives inside.
  • Job postings did the heaviest lifting. "Multi-tenant" and "validation documentation" in postings for an internal tool is the strongest available signal that productization is real. No press release said it.
  • Three weak signals converging beat one strong claim. The hire, the posting language, and the conference focus each mean little alone. Section 9 states the convergence explicitly and labels it Inference.
  • Section 10 produced an interview question, not a summary. "Is Trialpath a product, an internal tool, or undecided — and who decides?" is the question the whole brief exists to surface.
  • The confidence section admits what it doesn't know. Low confidence on strategic intent, and "thin" on platform scale. A brief that claims uniform confidence across eleven sections hasn't been read critically by its own author.

Source: SKILL.md on GitHub

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is an instructional template for conducting company research briefs. It contains no executable code, packages, or malicious patterns.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    3 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b68bf96. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago
argument-hint
[company name] [purpose]
type
component
theme
market-intelligence
Other metadata
intent
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.
best_for
[
  "Preparing for a PM interview with real company context",
  "Building a competitor or partner brief before a first meeting",
  "Understanding a company's product strategy from public signals"
]
scenarios
[
  "I have a PM interview next week and need real context on their product strategy",
  "We're meeting a potential partner and I need a brief on how they actually make money"
]
estimated_time
20-40 min
  • company-research
  • competitive-analysis
  • product-strategy
  • executive-insights
  • interview-prep
  • market-research
  • organizational-culture
  • partnership-evaluation

README badge

README badge for deanpeters/product-manager-skills/company-research

Gathers executive quotes, product strategy, transformation initiatives, and organizational structure from public sources to build a strategic company profile. Use for competitive analysis, partnership evaluation, interview preparation, or understanding how established companies approach product management and market positioning.

Generated from the current SKILL.md.

Does this skill help with financial analysis or valuation?
No. This skill focuses on product strategy and executive vision, not financial metrics or stock performance.
Can I use this for internal company research?
No. This skill is designed for external research on publicly available sources about other companies.
What if a company hasn't published executive interviews or earnings calls?
The skill won't work well without primary sources. It requires public statements from executives, not just marketing materials or secondary reporting.
Is this a substitute for customer research?
No. This skill captures how a company thinks about itself and its strategy, not how customers perceive or use the product.

Generated from the current SKILL.md. These answers refresh after source changes.