---
name: ravn-account-research-brief
description: Use when someone wants a one-page research brief on a company covering what it does, size, location, tech, public contacts and key people, from its domain.
title: Company Account Research Brief — Ravn
---
# Account research brief

Build a one-page brief on a company from its domain: what it says it does, how big it is, where it is, what its website runs on, public contact points and the leaders worth knowing. It combines the company's own website with a company profile and a short people search that run on your own data-provider account.

## When to use

- "Give me a rundown on acme.com before I pitch them."
- An account executive is planning an account and needs the basics in one place.
- For a brief on one person ahead of a call, use meeting-prep instead.

## Before you start

1. Check the connection: call `get_account` with `{}` or run `npx ravn whoami`.
2. `domain_to_company` and `search_people` need your own provider key connected — run `ravn keys add pdl` first; these tools run on your own provider account. `scrape_website` is ours and needs no key. Every call is one lookup; misses are free. If a tool returns 403 `provider_key_required`, stop and tell the human to add their key.
3. Confirm the domain. If the user gave a company name only, ask for the website.

## Steps

1. Read the company's own site.

```json
{ "domain": "acme.com" }
```

From `scrape_website`, take `name`, `title`, `description`, `address`, `emails`, `phones`, `socials` and `technologies`. The tool respects robots.txt; if it returns `not_found`, note that the site could not be read and carry on.
2. Get the firmographics.

```json
{ "domain": "acme.com" }
```

From `domain_to_company`, take `name`, `size`, `employee_count`, `industry`, `founded`, `city`, `state`, `country`, `linkedin_url` and `naics_codes`.
3. Find the leadership. Ask the user which function they sell to; default to the executive team.

```json
{ "company_domain": "acme.com", "seniority": ["C Suite", "VP", "Head"], "limit": 5 }
```

4. Compare sources. If the website and the company profile disagree (for example on location), show both and say which source said what. Do not blend them into one invented fact.
5. Group `technologies` into a few plain buckets (analytics, marketing, e-commerce, hosting, support) so the reader can scan them.
6. Write the brief. Only state what the tools returned. Where a field is empty, leave it out rather than guessing.

## Output

A one-page Markdown brief with these sections:

- **Snapshot**: name, domain, one-line description from the site, industry, founded, size and employee count, HQ location.
- **What they say about themselves**: the site `title` and `description`, quoted.
- **Tech on the website**: grouped `technologies`.
- **Public contact points**: emails and phones listed on the site, plus `socials`.
- **People to know**: name, title, seniority, LinkedIn URL for up to five leaders.
- **Sources and gaps**: which tool supplied each section, what was not found, and lookups used.

If the user wants the people as a list, also save a CSV with `full_name`, `title`, `seniority`, `linkedin_url`, `business_email` and `business_email_risk_score`.

## Rules

- Public emails on a website are for that company's stated purpose. Do not add them to a cold list without the user deciding to, and verify them first.
- Do not include anyone who has asked not to be contacted. Opt-outs: [/privacy#optout](https://askravn.com/privacy#optout).
- No FCRA uses: do not research a company or its staff to make credit, employment, insurance or housing decisions about people.
- On a 429 `fair_use_exhausted` or a 403 `provider_key_required`, stop, deliver what you have and tell the human.

## Example prompt

> I've got a first call with northwindtraders.com on Thursday. Put together a one-page brief: what they do, how big they are, what's on their site, and who runs the place.