Firmographic data describes a company: its identity, size, industry, location, and other organizational attributes. For a first lead-routing model, company identity, headcount, industry, and headquarters are useful starting fields. Connect each to a real decision, preserve missing values, and distinguish company context from a person's role or location.
What counts as firmographic data?
Firmographic data is company-level context used to describe and group organizations.
Company type and founded year are also firmographic attributes. Other datasets may include additional information, but your workflow should depend only on fields the chosen product supports and your evaluation can verify.
Firmographics differs from product activity, which records what an account does in your product, and person data, which describes an individual. Use each for its own question.
Which four fields should you start with?
Start with the fields that establish the company and the rules your team can explain.
These four are a starting set for the example, not a claim that every B2B team needs exactly the same attributes.
| Field | Question it can answer | Supported company result | Boundary |
|---|---|---|---|
| Company identity | Which organization does this record describe? | name and domain | An input domain can resolve to another canonical domain. |
| Headcount | Which size band does it fall into? | employee_count or employee_range | Size is not a seat forecast or proof of budget. |
| Industry | Does it fit the selected use case? | primary_industry | Map the returned label to your own taxonomy. |
| Headquarters | Does the company meet your territory rule? | headquarters | Company location is not necessarily the person's location. |
See the company field documentation for inputs and returned data. Some fields can be missing; a successful lookup does not guarantee a complete routing record.
How do these fields become a routing rule?
Specify what each field changes and what happens when it is unknown.
For an illustrative workflow, a team serves logistics companies with at least 50 employees and assigns accounts by company headquarters country.
| Input | Illustrative rule | If missing or disputed |
|---|---|---|
| Company identity | Confirm the returned company matches the intended account | Review the association; preserve the existing account. |
| Industry | Map Logistics to the team's Logistics segment | Use Unknown or an explicit unmapped label. |
| Headcount | Place verified counts of 50 or more in the target-size band | Leave the size criterion unknown. |
| Headquarters country | Assign under the company's written headquarters-based territory policy | Use the named unassigned/review queue. |
A complete company result can pass fit while the account has no product intent. Combine the fit state with first-party behavior when deciding whether sales should act.
Keep the rule version and reason visible. That makes it possible to inspect a routing decision later without guessing which thresholds applied.
What should you check before using headcount?
Check the value, reporting band, and purpose of the size rule.
Do not replace a missing number with zero. Do not treat an employee range as an exact count without stating the conversion rule. Preserve the source value and the banding version.
Company size can help group accounts. It does not tell you how many eligible roles need your product, how many seats will be purchased, or whether the account is ready to buy. Those questions need first-party or confirmed customer information.
What should you check before using industry and location?
Map the industry label and name the location concept explicitly.
Keep a small industry mapping table with the returned label, your CRM value, mapping version, and an Unmapped destination. Adding every returned category to your picklist can make it harder for your team to use the segments consistently.
For location, distinguish company headquarters, person location, and your customer's actual service or purchasing region. A headquarters-based policy can be valid, but the field should not quietly stand in for all three concepts.
Test several complete, incomplete, and conflicting records before enabling automatic assignment.
How do you obtain company context from a signup?
Use a supported company identifier, then retrieve the completed result.
A domain extracted from a work email can be a candidate company identifier. A confirmed LinkedIn company URL is another supported input. Shared personal-email service domains do not identify the signup's employer.
A successful company request uses one credit at documented rates. A person request by work email uses three or by LinkedIn profile URL one, and full company enrichment is separate. A returned employer name does not guarantee a usable domain. The task documentation explains submission, retrieval, and charges.
For a native Close connection, map company data to the supported lead fields under your chosen write rules. For other systems, verify the actual API/HTTP receiving workflow rather than assuming a native connector exists.
Which fields should wait?
Defer any field that has no defined decision, is unavailable, or fails the required quality check.
Company type may matter for one buyer and not another. Founded year can support a particular analysis. Additional categories such as technographics answer different questions and require separate product verification.
The useful limit is your workflow specification. Adding fields without an action increases the mapping and review work without necessarily improving qualification.
FAQ
What is the difference between firmographic and person data?
Firmographic data describes the company, such as its identity, industry, size, and headquarters. Person data describes an individual and their professional context. The two can support one workflow, but a known-person result is not a full company record and the company association may need confirmation.
Does a company's headquarters determine the contact's territory?
Only if your territory policy explicitly uses company headquarters. A person can work in another location, and the buying or service location can differ again. Store and name these concepts separately so a returned headquarters value does not silently become the contact's region.
Should a missing headcount make a lead low fit?
No. Missing or unusable headcount leaves that size criterion unknown. Keep a separate review or first-party qualification path. Defaulting null to zero creates an unsupported decision, and it can hide otherwise suitable accounts from your routing or reporting.
Evaluate company data on a few representative records, then test the fields against your own routing table.