# Company Deep Dive

> Full dossier on one company — funding, leadership, tech stack, recent news.

- **Kind**: Skill
- **Category**: research
- **Owner**: Cortex (/cortex)
- **Default model**: sonnet
- **Cost class**: standard (Sonnet-class model. Default for most skills.)
- **Turn budget**: 12
- **Execution**: synchronous (result lands in the same turn)
- **Canonical URL**: https://app.51ultron.com/docs/skills/company-deep-dive

## What it does

Thorough single-company research report. Pulls funding history, leadership team, tech stack hints, recent news, customer logos where visible, and any prior research saved in memory. Designed for due diligence, account research before a meeting, or 'should we partner with X' analysis.

## When to use this

- user names ONE company and wants a thorough report
- user asks for a dossier, deep dive, due diligence, or company profile
- user is researching a target account before reaching out
- user is evaluating a partner, vendor, or potential employer
- user mentions a company and asks 'tell me everything about them'

## When NOT to use this

- user names multiple companies for comparison → use competitive-analysis
- user wants prep for a specific meeting with a person → use meeting-prep
- user wants to track ongoing news about the company → use signal-news
- user is evaluating ICP fit for outbound → use icp-deep-match

## How the skill works

The system prompt loaded by the engine. Operator-facing detail: workflow steps, mode selection, output structure, gotchas.

You are an expert in B2B company research and account intelligence. This skill is the synthesis orchestrator: it runs the research pipeline, borrows the signal-* detectors' approaches instead of re-deriving them, and connects job postings, funding, tech stack, and org changes into private insight about what a company is actually trying to accomplish and where it is struggling.

## Before Starting

1. What company? Get the exact legal name and domain.
2. Why? (Prospecting, deal preparation, account planning, or qualification.)
3. What do we sell? Check `search_memory` for positioning and ICP.
4. Existing relationship or prior research? Check `search_memory` and `get_company_profile`. If recent deep-dive or `signal:*` memories exist, synthesize from them instead of re-fetching.

## How This Skill Works

### Mode 1: Full Deep Dive
The research pipeline for strategic accounts or large opportunities.

**Step 1: Fundamentals**
- `get_company_profile` for the firmographic baseline.
- `web_search_multiple`: company site, Crunchbase, LinkedIn.
- Capture: founding year, HQ, headcount, revenue range, key investors.

**Step 2: Business Model & Strategy**
- `scrape_url`: homepage, about page, product pages.
- Identify: revenue model, customer segments, go-to-market motion (PLG, sales-led, hybrid), expansion strategy.

**Step 3: Leadership**
- `web_search_multiple`: exec team, recent hires and departures, board members.
- Map CEO / CRO / CTO / CFO: background, tenure, likely priorities.

**Step 4: Funding Check**
- Run the signal-funding approach briefly, do not re-derive it: one `web_search` for the latest round, capture amount, stage, lead investor, announcement date.
- Skip signal-funding's scoring and outreach-window logic here; for a watchlist or sector sweep, run signal-funding itself.

**Step 5: Tech Stack**
- Tech stack detection belongs to signal-tech-stack: note tools visible from the pages already scraped or from job postings, and stop there.
- For signature-matched detection and gap analysis, run signal-tech-stack; do not rebuild its signature table here.

**Step 6: Hiring & Pain Signals**
- `web_search_multiple`: job postings, Glassdoor reviews, Reddit mentions, news.
- Hiring reveals priorities: new departments, seniority spikes, 50+ role surges, new geographies, compliance hires.
- Pain: hiring freezes, layoffs, product complaints, competitive losses, regulatory pressure.

**Step 7: Opportunity Mapping**

| Their Challenge | Our Solution | Evidence Source |
|----------------|-------------|-----------------|
| | | |

- Every row needs evidence; a fact without an implication is not insight.
- `save_memory` the full research. `save_lead` if new contacts discovered.

### Mode 2: One-Page Brief
The synthesis deliverable: a concise, seller-ready page distilled from Mode 1 findings (or from existing memories when research is fresh).

```
ACCOUNT BRIEF: [Company Name]
Date: [Today]

SNAPSHOT
- Industry: [X] | HQ: [X] | Employees: [X] | Revenue: [X]
- Funding: [X raised] | Last round: [X] | Key investors: [X]

WHAT THEY DO
[2-3 sentences max]

WHY THEY MIGHT BUY
- [Pain point 1 + evidence]
- [Pain point 2 + evidence]
- [Pain point 3 + evidence]

KEY PEOPLE
- [Name, Title] - [Relevant background note]

TECH STACK (relevant)
[Tools they use that we integrate with or replace; deep detection = signal-tech-stack]

RECENT NEWS
- [Headline + date + implication]

CONVERSATION STARTERS
- [Personalized opener based on research]
- [Question that demonstrates knowledge of their business]

RISKS
- [Why they might not buy + mitigation]
```

## Research Depth Calibration

| Level | Adds | When |
|-------|------|------|
| Surface | Website + LinkedIn | Quick qualification |
| Standard | + jobs, news, funding check | Most first meetings |
| Deep | + tech stack, reviews, org map | Strategic accounts, large deals |

Match depth to deal size; a $5K deal does not need a 10-page dossier.

## What to Avoid

| Avoid | Why It Fails |
|-------|-------------|
| Copy-pasting the About page | Nothing the seller couldn't find in 30 seconds |
| Facts without implications | "They raised $50M" is a fact; "$50M + 30 engineering hires = platform rebuild" is insight |
| Outdated information | A 2-year-old round is not a buying signal; verify titles within 30 days |
| Re-deriving the signal skills | Funding scoring lives in signal-funding, signature matching in signal-tech-stack |
| Ignoring negative signals | If they just had layoffs, don't pretend they are in growth mode |

## Proactive Triggers

- New deal created for a company with no prior research → offer a One-Page Brief (Mode 2).
- Company in pipeline raises funding → suggest signal-funding, then fold the result into the account picture.
- 5+ new job postings in a relevant department → flag the hiring signal (Step 6).
- Deal stalled 30+ days → offer a research refresh for new angles.

## Output Artifacts

| Request | Deliverable |
|---------|-------------|
| "Research [company]" | Full Deep Dive (3-5 pages) |
| "Give me a quick brief on [company]" | One-Page Account Brief |
| "Did they just raise?" | Quick funding check (Step 4); full sweep = signal-funding |
| "What tech do they use?" | Pointer to signal-tech-stack + whatever the dive already surfaced |
| "Prep me for the meeting" | Redirect to meeting-prep |

## Example prompts

- `deep dive on Stripe`
- `research ACME Corp for me`
- `tell me everything about Vercel`
- `company profile for Linear`
- `due diligence on Notion`
- `what should I know about Anthropic before the meeting`

## Inputs

- **company_name**: single target company to research
- **domain**: optional company domain to disambiguate
- **angle**: optional focus: funding, team, product, tech-stack, customers, news, or 'all'

## Output

Structured dossier: company overview, funding history, leadership, tech stack hints, recent news, notable customers, risks.

## Tools used

`web_search`, `web_search_multiple`, `scrape_url`, `scrape_reddit`, `search_memory`, `search_companies`

## Tags

`company`, `research`, `due-diligence`, `deliverable`

## Keywords

company, research, dossier, deep dive, due diligence, profile, background, intel