> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/account-research/researching-an-account.md).

# Researching an account

Look up any company to see its profile, who it sells to, how it advertises, and how it engages with you.

Account research profiles any company by its domain: what it does, who it sells to, and how it advertises. You can run it from the **Account Research** page or from [Chat](https://support.sayprimer.com/primer/chat/using-chat.md).

Researching a company never changes your own organization's data or [ICP definition](https://support.sayprimer.com/primer/settings/icp-definition.md).

## On the Account Research page

Enter a company's domain to see its company card (industry, headcount, revenue and more), followed by:

* **Business Profile** — how the company describes itself, its **Market** (for example *Narrow and high-intent* or *Broad and horizontal*) and what Primer is seeing.
* **Who {company} sells to** — its primary and adjacent buyers, target industries, company sizes and geographic focus.
* **Ad Strategy Summary** — a read of how the company advertises.

Each section fills in as its research finishes. If one can't load, try again or search a different domain.

## In Chat

When Chat names a company, click **Research** on its card. Research runs in the background, so you can keep chatting; choose **Notify me when it's done** to get a browser notification, and Primer also tells you when it's ready if you've moved elsewhere in the app.

The research opens beside the chat and adds to the page view above:

* whether the company is **In your ICP** or **Outside your ICP**;
* **Engagement** — what your own data shows about the company: CRM records, deals, paid and organic engagement, form fills, audiences and intent;
* **How they advertise** — the ads it's running on LinkedIn, Google and Meta, with what they target, the messaging and offers they use, and what it means for you.

Ask follow-up questions about the research in the same chat. Every company you've researched is listed on the **Reports** page under **Account Research**.

## How research is saved and reused

Research run from Chat is saved and reused, so opening it again is instant. The date shown, **Researched {date}**, is when your organization first researched it. Research older than 30 days refreshes when you open it, and **Research again** runs it afresh. Saved research describes the company itself and holds none of your organization's data: the **Engagement** section is read from your own data, for your organization only.

## Downloading research

**Download PDF** saves the research as it appears, with an **Include engagement** option for your own engagement data. It's available from Chat and the Reports page.

## Account research doesn't send alerts

Research runs only when you ask for it. It doesn't watch companies or send intent alerts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.sayprimer.com/primer/account-research/researching-an-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
