A one-page account brief before your sales call: who they are, funding, offices, whether they're hiring, and 3–5 people worth talking to. Four calls, five minutes — call prep, not a research project.
/api/v1/companies/name-lookup10 credits/call/api/v1/companies/enrich10 credits/call/api/v1/companies/jobs10 credits/call/api/v1/companies/employees-data10 credits/callBallpark: ~400 credits for 10 typical runs. Signup includes 300 free credits.
Download comes with your API key baked in — sign up (300 free credits, one minute) or open this skill in your dashboard.
---
name: linkedin-account-intel
description: Use when the user needs fast intel on ONE company before a sales call, partnership conversation, or application — who they are, funding, size and offices, whether they're hiring, and who works there. Triggers on "prep me for my call with X", "brief me on this company", "is X hiring", "who should I talk to at X". For a full multi-page dossier with SWOT and PDF, use Company Deep Research instead.
---
# Account Intel (via Zooq)
You build a one-page account brief from live LinkedIn data: identity, funding, footprint, hiring signal, and the people worth talking to. Four to five calls, done in minutes — this is call prep, not a research project.
## Inputs you need from the user
- **The company**: LinkedIn slug (the part after `linkedin.com/company/`), a LinkedIn company URL, or just the name.
## Step 1 — resolve the company (only when given a name)
```
GET https://zooq.dev/api/v1/companies/name-lookup?name=<NAME>
Headers:
X-API-Key: REPLACE_WITH_YOUR_KEY
```
Pick the right match from `data[]` (headcount and industry disambiguate), read its `slug`. If several plausibly match, show the top 3 and ask — one wrong guess wastes every call after it.
## Step 2 — the live company profile (the core call)
```
GET https://zooq.dev/api/v1/companies/enrich?slug=<SLUG>
Headers:
X-API-Key: REPLACE_WITH_YOUR_KEY
```
This is the freshest read Zooq has, and it returns three things the standard record doesn't: **funding signals**, the **full office list** (not just HQ), and the **corporate family** (parent / affiliated pages). Not-found costs nothing.
## Step 3 — hiring signal + open roles
```
GET https://zooq.dev/api/v1/companies/jobs?slug=<SLUG>
Headers:
X-API-Key: REPLACE_WITH_YOUR_KEY
```
Open roles are the single best conversation hook: what they're hiring for is what they're investing in. Note count, functions, and locations of the openings.
## Step 4 — the people
```
GET https://zooq.dev/api/v1/companies/employees-data?slug=<SLUG>
Headers:
X-API-Key: REPLACE_WITH_YOUR_KEY
```
Pull the people relevant to the user's angle (selling → the buyer's function + leadership; partnership → founders/BD). List 3–5 names with title and handle. If the user wants depth on one person, `GET /api/v1/profile/full?handle=...` is one call away.
## Output format — one page, in this order
1. **Who they are** — one sentence: what they do, HQ, headcount, founded.
2. **Money & structure** — funding (if any), parent/affiliates, office locations.
3. **Hiring signal** — hiring or not, how many roles, in what functions. Say "not hiring" plainly if so; that's signal too.
4. **Who to talk to** — 3–5 people with titles and one-line whys.
5. **Openers** — two concrete conversation hooks drawn from the above (a fresh funding round, a hiring spike, a new office). Skip generic flattery.
Cost: 40–50 credits per brief. Say what was spent at the end.
## Failure rules
- Company not found → say so and show the closest name-lookup matches; never guess a slug.
- Sparse data (no funding, no posts) is a finding, not a failure — small private companies look like that. Write the brief from what exists.
- Prospecting across MANY companies ("find fintechs that are hiring") is a different job: point the user at `GET /api/v1/search/companies-live?keyword=...&hasJobs=true` — its `hasJobs` filter finds actively-hiring companies directly, then this skill briefs the shortlist one by one.