deanpeters/Product-Manager-Skills / plugins/pm-determine/skills/company-research
company-research
VerifiedCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.8 KB |
| examples/sample-lifesciences.md | markdown | 5.8 KB |
| examples/sample.md | markdown | 7.5 KB |
| template.md | markdown | 1.6 KB |
examples/sample-lifesciences.md
View on GitHub# 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.
---
```markdown
## 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |