> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/getting-started/key-concepts/records/companies.md).

# Companies

A company is the account level of your CRM: contacts belong to one, deals are done with one, and emails, meetings and LinkedIn activity roll up to it through the people involved. Companies are identified by their **Website Domain**, and a company can hold several domains in **All Domains** — activity on any of them lands on the same record.

Companies can also be nested. Set a **Parent company** to build account hierarchies; the parent lists its **Child companies**.

## What Zero fills in for you

{% hint style="success" %}
**You rarely have to type company data in.** Add a company — a domain is enough — and Zero looks it up and fills the profile in for you.
{% endhint %}

Enrichment only fills fields that are empty, so it never overwrites something you or a teammate typed. It can fill **Name**, **Website Domain**, **Description**, **Location** and **LinkedIn**, plus the company profile: **Industry**, **Employee amount** and its growth rates, **Revenue**, **Total funding amount**, **Latest funding type**, **Latest funding round date** and **amount**, **Investors**, **Founders**, **Categories**, **Jobs**, **Acquisitions** and **Investments**.

It runs automatically when a company is created and again whenever you change its **Website Domain** or **LinkedIn**; on import, unless you ask Chat to skip enrichment when it shows the import for approval; and on demand, by selecting companies in a list and clicking **Run enrichment** in the floating toolbar, or the same button in the record header. Enrichment uses credits, and the confirmation tells you the cost first.

## Adding companies

* **Manually** — **Add company** at the top of any company list (and of **Companies**), or from the command menu (**Cmd + K**, then **B**). Setting the **Company** property on a contact creates or links the company too.
* **From a contact** — a contact created with an email address or LinkedIn profile brings its company with it. Personal mailbox domains like gmail.com are skipped.
* **From Lead Search** — select companies in the results and use **Add to list**. See [Lead Search](/features/lead-search.md).
* **Import** — CSV or a migration from another CRM. See [Data Import](/getting-started/data-import.md).
* **Agents** — an agent action can create or update companies. See [Agents](/features/agents.md).
* **Chat, MCP and the API** — `add_company` for Chat and MCP clients, `POST /api/companies` for REST. See [MCP](/developers/mcp.md).

## Standard properties

* **Name**, **Website Domain**, **All Domains**, **LinkedIn**, **Location** (with **Location → City**, **State**, **Country**), **Description**
* **Owners** — the workspace members responsible for the account
* **Contacts** and **Deals** — the related records
* **Parent company** and **Child companies** — for account hierarchies
* **Lists** — the lists the company is in
* **Churned** and **Churn reasoning**
* Enrichment properties from the company profile, such as **Employee amount**, **Industry**, **Revenue**, **Total funding amount**, **Investors**, **Founders**, **Jobs** and **Categories**
* Activity roll-ups: **First activity**, **Last activity**, **Next activity**, **Last email**, **Last meeting**, **Next meeting**, **Next steps** (open tasks)
* **Created at**, **Created by**, **Updated at**, **Updated by**, **External ID**, **Archived**

Anything beyond this is a [custom property](/settings/custom-properties.md).


---

# 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://docs.zero.inc/getting-started/key-concepts/records/companies.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.