---
name: ravn-meeting-prep
description: Use before a call or meeting when someone wants a short brief on the person they are meeting and that person's company, from an email, name or LinkedIn URL.
title: Meeting Prep Brief on a Person and Company — Ravn
---
# Meeting prep: person and company

Before a call, look up who the user is meeting and the company they work for, and return a short brief: role, seniority, background, company basics and a few talking points grounded in what the data says.

## When to use

- "I'm meeting jane@acme.com at 3pm, who is she?"
- The user pastes a calendar invite, an email signature or a LinkedIn URL and wants context.
- For a deeper company-only brief, use account-research-brief.

## Before you start

1. Check the connection: call `get_account` with `{}` or run `npx ravn whoami`.
2. The person and company lookups (`reverse_email_lookup`, `reverse_linkedin_lookup`, `search_business_profile_by_name`, `domain_to_company`) need your own provider key connected — run `ravn keys add pdl` first; these tools run on your own provider account. If a tool returns 403 `provider_key_required`, stop and tell the human to add their key. `scrape_website` is ours and needs no key. Every call is one lookup; misses are free.
3. Work out what you were given: an email, a name plus company, or a LinkedIn URL. Each has its own lookup.

## Steps

1. Get the person profile with the tool that matches the input:
   - Email: `reverse_email_lookup` with `{ "email": "jane@acme.com" }`.
   - LinkedIn URL: `reverse_linkedin_lookup` with `{ "linkedin_url": "https://www.linkedin.com/in/janedoe" }`.
   - Name and company: `search_business_profile_by_name` with `{ "name": "Jane Doe", "company": "acme.com" }`.
2. If `status` is `not_found`, try the next input you have (for example name plus company from the email signature). If all miss, say so and continue with the company only.
3. From the person, use `full_name`, `title`, `headline`, `seniority`, `city`, `state`, `country`, `industry`, `linkedin_url`, `company` and `last_updated_at`. If `last_updated_at` is old, warn that the title may have changed.
4. Get the company. Use `company.domain` from the person, or the email's domain if it is not a free provider.

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

Call `domain_to_company` for size, industry, founded and location, then `scrape_website` for the site description and `technologies`.
5. Write three to five talking points that link the user's goal for the meeting to facts you found (for example the person's department, the company's size, a technology on their site). Ask the user for the meeting goal if you do not know it.
6. Keep the brief to what fits on one screen.

## Output

A short Markdown brief:

- **Who**: full name, title, seniority, location, LinkedIn URL, and how fresh the record is.
- **Company**: name, domain, industry, size and employee count, founded, HQ, one-line description from their site.
- **Context**: department, headline, notable technologies on the site.
- **Talking points**: three to five bullets, each tied to a fact above.
- **Unknowns**: what was not found, and anything to ask in the meeting.

## Rules

- Use this only for business meetings. Do not profile people for personal reasons.
- If the person has opted out, the lookup will not return them; do not try to work around that. See [/privacy#optout](https://askravn.com/privacy#optout).
- No FCRA uses: never use a brief to screen a candidate, tenant, borrower or policy holder.
- Never present a guess as a fact. If a field is missing, say it is missing.
- On a 429 `fair_use_exhausted` or a 403 `provider_key_required`, stop and tell the human. Deliver whatever you already found.

## Example prompt

> I have a call in 20 minutes with marcus.bell@brightpath.io. Who is he, what does BrightPath do, and what should I bring up?