> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/data/foundational-data.md).

# Firmographics

Firmographics are the company facts Kernel returns after it has resolved a CRM record to the right entity. They cover where the entity operates, whether it is still in business, how many people it employs, and what revenue figure belongs at the right scope.

Kernel researches these fields instead of copying one static vendor value. Each result is tied to the resolved entity, checked against multiple sources, and returned with enough context to understand how the value was chosen.

## Everything is entity level

Every firmographic data point is resolved to a specific legal entity, not a vague "company" record. Because many companies are really a family of legal entities, Kernel attributes each value to the exact entity it belongs to.

* **Entity level** is the value for that specific legal entity on its own.
* **Consolidated** is the value for the entity plus its subsidiaries. It is provided for headcount and revenue, where group scale can matter.

For holding companies and group parents, the consolidated figure is usually the useful one. For operating companies, subsidiaries, and business units, the entity-level figure is usually the right fit. When an entity has no subsidiaries, the two are the same.

For headcount and revenue, Kernel also provides a single **primary** value for CRM and export workflows. It uses consolidated scope for holding companies and group parents, and entity-level scope for operating companies, subsidiaries, and business units.

## Core firmographic fields

| Data point         | What it answers                                                                                              | Learn more                                                          |
| ------------------ | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- |
| Headcount          | How many people are on the entity's payroll, at entity or consolidated scope.                                | [Headcount](/data/foundational-data/headcount.md)                   |
| Revenue            | What annual top-line revenue belongs to the entity, with currency, fiscal year, source, and scope preserved. | [Revenue](/data/foundational-data/revenue.md)                       |
| Location           | Where the entity operates, and where it is legally registered.                                               | [Location](/data/foundational-data/location.md)                     |
| Operational status | Whether the entity is active, absorbed into another brand, out of business, or unclear.                      | [Operational status](/data/foundational-data/operational-status.md) |

## Reasoning and confidence

Firmographic values are meant to be inspectable, not just usable as a final number. The exact fields vary by integration, but the same ideas show up across the product:

* **Reasoning** explains how the value was determined, including sources, scope decisions, and important caveats.
* **Confidence** appears on headcount and revenue, and reflects how strong the evidence is.
* **Source** appears on headcount and revenue, and records whether the figure was identified directly from evidence or estimated by Kernel.

Operational status does not use a separate confidence field. `Undetermined` is the uncertainty value when the evidence is incomplete or conflicting.

If you disagree with a finding, the feedback field in your CRM lets you flag it for review.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kernel.ai/data/foundational-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.