Company Size Filters: Check What the Employee Count Actually Measures
An employee-count field is useful for company-size filtering only when you understand which people it counts, which company entity it describes, and when the value applies. An estimate, a size band, and a dated company disclosure are not interchangeable. Do not assume a provider includes every contractor, subsidiary, or geography unless its evidence establishes that scope.
Before including or excluding an account, identify the field’s definition and source. Keep unclear population, entity, and date information unresolved. A filter can apply correctly to a number while selecting the wrong business population for your sales motion.
Which population does the employee count describe?
Start by asking what qualifies someone to be counted. Does the source describe employees, full-time-equivalent positions, people associated with a company profile, or another population? Does it distinguish full-time and part-time staff? What does it say about contractors, temporary workers, and people on leave? Record the stated definition rather than filling gaps with an assumption.
Then check the geographic scope. A global workforce figure and a local operating-unit count answer different questions. Headquarters location alone does not tell you where the counted people work. Nor does a contact’s location establish the geography covered by the company’s employee count.
Unify’s standard company attributes document employee_count as an integer described as an estimated employee count. That establishes the field’s form and estimated nature. It does not establish a universal rule for contractor inclusion, subsidiary consolidation, or every underlying source’s methodology.
Use the B2B enrichment data dictionary to keep field definition, entity level, provenance, and null meaning separate. A field named company size is not a complete measurement specification.
How do an estimate, a range, and a disclosed figure differ?
| Value form | What it establishes | What still needs checking |
|---|---|---|
| Estimated employee count | A source supplies a numerical estimate | Estimation method, covered population, entity, and effective date |
| Employee-count range | A source places the entity within a band | Band definition and whether it overlaps your target interval |
| Dated public disclosure | The organization reports a figure under stated wording | Reporting entity, population, period, and any exclusions |
| Profile-associated count | The source reports associations under its own method | Whether association means current employment and which entity it covers |
A more precise-looking value is not automatically better evidence. An integer can still be an estimate. A public report can be clear about its scope but describe an earlier period. A range can be sufficient for broad segmentation while leaving a boundary decision unresolved.
Do not silently replace a range with its midpoint or upper bound and treat the result as an observed employee count. If the range crosses your targeting boundary, decide whether your process permits provisional inclusion, requires review, or leaves the account unclassified. Preserve the original value and the decision rule.
Likewise, do not convert between headcount and full-time equivalents without the required definition and evidence. The question is whether the measurement suits the sales decision, not whether every source can be forced into the same numeric column.
Is the value attached to the operating company or its parent?
Identify the entity before comparing figures. A legal parent, subsidiary, operating brand, regional office, and CRM account can represent different boundaries. A consolidated workforce disclosure should not become a subsidiary count simply because the records share a brand or website reference.
Check the source’s company name and entity description against the account you intend to target. Keep the domain and record identifier with the evidence, but do not assume a domain alone resolves a corporate hierarchy. If the source covers a wider group, retain that scope explicitly.
The guide to parent and subsidiary account targeting separates the company generating a signal from the entity employing contacts or owning a buying decision. Apply the same discipline to headcount. Decide whether your size rule concerns the contracting entity, operating unit, or consolidated group before applying it.
Avoid adding parent and subsidiary figures together unless the sources establish non-overlapping populations. Differences between two counts may reflect different boundaries rather than an error by either source. Investigate scope before choosing the larger or newer value.
Which date belongs to the measurement?
Record the date or period the count describes, the source’s publication date, and when you retrieved it. These dates can differ. If a source reports an average over a period, do not relabel it as the workforce on the publication date. If no measurement date is available, say so.
Unify’s record inspection view exposes record identifiers, attribute values, and a last-update timestamp. That record timestamp alone does not establish when employee count was measured or verified. The guide to created, updated, and verified dates explains why those events should remain distinct.
A later record update may concern another attribute. A newly retrieved source may repeat an older figure. Keep the evidence’s effective date attached to the count instead of treating the latest visible timestamp as proof of freshness.
How should you state the rule before filtering?
Write the rule in business terms first: target entity, accepted population definition, size interval, acceptable date or period, and treatment of ranges and missing values. Decide which source or field is authoritative for this motion, and what happens when it conflicts with another source.
In Unify’s filter builder, select the field source carefully. A Unify company field and a similarly named connected CRM field can contain different values. Numeric and categorical fields also support different comparisons. Review the selected operator and boundary behavior, then inspect matching records.
Use audience conditions to keep the company-size rule distinct from contact-role conditions. A qualifying company does not make every associated person suitable for outreach. If a shared definition is reused through company segments, review the places that depend on it before changing the rule.
A missing employee count is not evidence of zero employees or an account outside the target range. The filter builder supports missing-value checks. Keep unresolved records visible for review rather than letting missing data silently become a business conclusion.
Use a blank company-size interpretation card
Complete this card for a value that materially affects inclusion or exclusion. It is a proposed worksheet, not a completed analysis. Leave cells blank until you have evidence; mark unknown scope explicitly when recording the result.
| Interpretation field | Your evidence or decision |
|---|---|
| Company name, domain, and record identifier | |
| Entity represented: parent, subsidiary, or operating unit | |
| Field name and source system | |
| Original value and form: estimate, band, or reported figure | |
| Population definition and geographic scope | |
| Source URL or document reference | |
| Measurement date or period | |
| Publication and retrieval dates | |
| Conflicting evidence and unresolved scope | |
| Target rule and treatment of missing or overlapping values | |
| Include, exclude, or review decision and owner |
How can Unify support the review?
Use company and contact data to identify the company attributes available for targeting, and company research with agents to investigate relevant evidence. A product’s access to headcount context does not make every value equally current or establish a single population definition across sources.
With list research in chat, ask for the intended company, the available count, its supporting source where available, and any unresolved entity or date question. Inspect the research before treating the value as a qualification fact. Do not infer that a completed research action guarantees a definitive count.
The account prioritization workflow combines fit with other context. Company size can contribute to fit once its meaning is clear; it does not establish budget, purchase authority, or demand on its own. Keep the interpretation card with the decision so a later reviewer can see why the account was included or held for review.
Frequently asked questions
Does employee count always include contractors?
No uniform inclusion rule should be assumed. Check the source’s population definition and retain contractor coverage as unresolved when the evidence does not specify it.
Is an estimated employee count the same as an exact headcount?
No. A numerical estimate can look precise without being an exact count. Keep its estimated status, entity scope, source, and effective date attached to the value.
Can I use the parent company’s size for a subsidiary?
Only if your targeting rule intentionally concerns the parent or consolidated group and the evidence supports that scope. Do not relabel a group figure as a subsidiary count.
What should I do when a size range crosses my target boundary?
Apply a documented review rule rather than converting the band into an invented exact count. Preserve the original range and whether the account is included provisionally, excluded, or unresolved.
Does a recent record-update timestamp prove the count is current?
No. The update can relate to another field or repeat an older source. Check the measurement date or period and the evidence associated with the employee-count value.
