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

# Company Data Bundles

Field-level dictionary for Multi-source Company Data covering fresh firmographics, funding, technographics, workforce trends, salaries, and more.

The company data contains more than 600 fields covering questions such as who the company is, how it is funded, how its headcount is changing, what its current organizational structure looks like, and how it appears in the market. Bundles group these fields by the questions they help answer, rather than by their locations in the underlying schema. Each field belongs to one of five bundles – explore them below or review the [complete record sample](/company-data/record-sample.md).

***

{% content-ref url="/pages/54HSb5H7oLqBbwceGZZC" %}
[Core](/company-data/bundles/core.md)
{% endcontent-ref %}

**Core company bundle** forms the foundation of every company record, encompassing verified identity, web and social presence, industry and business model, company size, headquarters, and related companies and people, all in one place. It offers the deepest and most consistent coverage across the dataset, making it the starting point for every workflow, including enrichment, segmentation, and lead scoring.

***

{% content-ref url="/pages/FWWdsRvDMl300rSByKcc" %}
[Financial Information](/company-data/bundles/financial-information.md)
{% endcontent-ref %}

**Financial Information bundle** reveals revenue indicators, funding and initial public offering (IPO) history, ownership structure, and mergers and acquisitions (M\&A) activity, providing the context that distinguishes a resourceful startup from a well-capitalized enterprise, or a subsidiary from an independent business.

***

{% content-ref url="/pages/vw6wOLwFWUixOTB2geqd" %}
[Growth Signals](/company-data/bundles/company-growth-signals.md)
{% endcontent-ref %}

**Growth Signals bundle** tracks the trajectory that static company data cannot reveal, including headcount trends, hiring velocity, attrition, web and social engagement, and reputation trends that reflect shifts in employee and product sentiment over time.

***

{% content-ref url="/pages/jdtP8UYo6X6aY73b2jSt" %}
[Workforce Intelligence](/company-data/bundles/workforce-intelligence.md)
{% endcontent-ref %}

**Workforce Intelligence bundle** provides a real-time view of leadership, workforce composition, employee tenure, compensation benchmarks, and employee sentiment. It also reveals talent flows, including where talent comes from and where it goes next. Gain a comprehensive understanding of the people driving the business.

***

{% content-ref url="/pages/6SrSlUvj4rov3xKUfh4v" %}
[Company Intelligence](/company-data/bundles/company-intelligence.md)
{% endcontent-ref %}

**Company Intelligence bundle** completes the profile with competitor mapping, technology footprint analysis, product reviews, website engagement assessments, and news updates. Hiring activity and product surface indicators show what a company is currently developing and offering. Together, these capabilities turn a company record into a source of competitive advantage.

***


---

# 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.coresignal.com/company-data/bundles.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.