TL;DR
- LinkedIn Sales Navigator is the practical choice for sellers reviewing hiring and department trends on a focused account list. Its employee insights reflect LinkedIn member profiles.
- Crunchbase adds company, funding and predictive context. Its documented employee-count field is a range, so it is weaker for calculating precise headcount changes.
- Dealroom fits startup and technology-company research, with an employee history chart and growth fields in its API schema. Bulk/API access has a different purchase basis from a research seat.
- People Data Labs is the strongest of these four for a structured company-monitoring pipeline: counts, history and growth fields have explicit definitions and field-bundle gates.
- Preserve the estimate you received and its data version. A newly reconstructed historical series is not the same as what the provider reported three months ago.
- An illustrative 1,000-account monitor has a $1,610/month first-year licence ceiling from time savings, before external implementation charges. The cheapest base API is useful only if it includes the fields the decision needs.
Decide what growth means
Company headcount can answer several buying questions. A seller may want to know whether a team is expanding. An investor may want a consistent startup momentum measure. Sales operations may need a monthly prioritisation feature across thousands of accounts. Those jobs need different data products.
Start by distinguishing a disclosed employee total, a company-selected size range and a count reconstructed from professional profiles. A range such as 101–250 employees is useful for segmentation but does not establish that the company added 30 people. A profile-derived count can track direction while still differing from payroll.
The practical signal is a same-entity, same-definition change that connects to the seller's category. Engineering growth may matter to a developer-tool seller; new regional operations roles may matter to a reporting platform. Whole-company expansion is less specific than the function and location creating the need.
This article compares the original LinkedIn, Crunchbase, Dealroom and People Data Labs shortlist for that decision. The B2B intent data guide covers broader buying-interest sources. Headcount growth is business-change context, rather than direct evidence that an account is shopping for your product.
Compare the four providers
| Provider | Useful headcount surface | History and scope | Commercial basis | Best fit |
|---|---|---|---|---|
| LinkedIn Sales Navigator | Member-profile employee insights, hiring and department trends | Company Page and account context; observed profile population | Core starts at $119.99/month or $1,079.88/year per user | Sellers interpreting a focused account list |
| Crunchbase | Employee range alongside funding and company context | Firmographic range; predictive intelligence is a separate meaning | Pro $99 monthly on the official help-page basis; Business/API separate | Screening companies, then adding more specific growth evidence |
| Dealroom | Employee chart and relative/absolute growth fields | Technology/startup entity research; dated chart in API schema | Premium €12,600/year from three seats; API/custom route separate | Startup ecosystems and investment-oriented growth research |
| People Data Labs | Profile-derived counts, monthly history and growth fields | Explicit data definitions; historical fields depend on bundle | Company Pro base starts at $100/month for 1,000 credits; premium field scope additional | Repeatable company-monitoring pipelines |
Public primary evidence was reviewed on 1 October 2026. Capabilities below are documented product surfaces; the scenarios and budget are editorial examples, not measured accuracy tests.
Product choices and historical fields
LinkedIn: interpret the people behind the trend
LinkedIn's premium company insights show employee count over time, distribution and growth by function, notable alumni and job openings. The count refers to members associated with the company, not a certified payroll census. LinkedIn says profile information, self-reported company numbers and differing employee definitions can produce discrepancies; Pages with fewer than 30 employee profiles do not show Premium Insights. Insight definitions.
Sales Navigator's account research supports hiring and department trends and shows decision makers joining or leaving. That helps a seller interpret the change alongside the relevant people. A rising operations team and a newly appointed regional leader can create a useful conversation angle, even without turning the count into an exact number of approved positions. Account research.
Pricing: Core starts at $119.99/month or $1,079.88/year per licence. Advanced starts at $159.99/month or $1,799.88/year; Advanced Plus is custom for the deeper CRM purchase. These are starting US bases, with taxes and purchase context separate. Current plans.
Choose LinkedIn for human research on a manageable account set, particularly when people and functions determine the next action. Choose another for a licensed machine-readable historical dataset. A Sales Navigator seat is a research-product purchase; it should not be budgeted as an unrestricted bulk headcount API.
Crunchbase: connect company scale with business change
Crunchbase's data dictionary identifies num_employees_enum as the organisation's employee-count range. That supports size filtering, but a range is not a dated exact count series. Funding, company changes and growth predictions add context; they should not be relabelled as observed workforce additions. Data field definition.
The current official product comparison separates Pro research from Business predictions and CRM integrations. Pro includes up to 1,000 results per search and 2,000 exported rows/month; API access is a separate paid product. Product scope.
Pricing: the official buying article supports Pro at $99 billed monthly. Annual introductory offers apply to new users' first year and should not be treated as a permanent renewal tariff. Business and API have their own commercial purchase routes. Pro buying basis.
Choose Crunchbase when funding and company trajectory are as important as size. Choose another when the core output is a defensible three-month headcount delta. A company moving from one employee range to another can be interesting, but there is no sound basis for choosing the midpoint of each range and calling the difference new hires.
Dealroom: growth in startup and technology-company context
Dealroom's Premium API company schema includes employees_chart, dated employee observations, and relative/delta employee-growth fields over three, six and twelve months. It also exposes resource update timestamps. Those fields make it more directly useful for growth monitoring than a single employee range. Company schema.
Its research context suits technology companies, funding, investors and startup ecosystems. The growth series can sit beside a funding event or hiring signal to help a researcher decide which company deserves attention. The presence of a field in the schema does not make every subscription a complete data licence.
Pricing: Premium is €12,600/year, starting from three seats, with 10,000 export credits per user. Premium Plus is €17,000/year, also from three seats, with 30,000 export credits per user. Enterprise and API + MCP are custom. Use the API purchase for a recurring data pipeline rather than treating research exports as interchangeable with API calls. Pricing, API access.
Choose Dealroom for a startup/technology universe where funding and ecosystem context improve the growth decision. Choose another for a broad local-business list or when a researcher only needs occasional professional-role checks. Its multi-seat annual base needs a recurring research programme, rather than a single analyst's occasional headcount lookup.
People Data Labs: explicit company fields for a monitoring pipeline
PDL distinguishes current profile-derived employee_count from the company's selected size range. Its company schema includes monthly employee counts, role breakdowns and growth rates. Historical monthly data ends with the last full month before the monthly data build; a growth ratio of 0.20 means 20%, not 0.20%. Company schema.
Field gate: monthly counts and the twelve-month growth field appear in the Premium bundle; additional growth windows and breakdowns have Comprehensive scope. Base company enrichment should not be priced as if it automatically includes every historical insight. Field bundles.
Pricing: the official Pro table gives Company Enrichment/Search a $0.10 monthly first-tier credit rate, with a 1,000-credit minimum costing $100. Annual first-tier pricing is $0.08/credit, starting at 12,000 credits or $960/year. Successful enrichment matches consume credits; search is charged per returned company, so one bulk request is not one company credit. These are base prices, with the required premium field scope assessed separately. Company credit pricing.
Choose PDL when engineering can maintain a company monitor with explicit entity IDs and dated records. Choose another when no one will operate the pipeline. The cheap base record does not remove interpretation, matching and administration from the budget.
Read a headcount change correctly
Use a fictional company, Northstar Analytics. A saved June observation showed 100 associated profiles. The September observation shows 130. A simple snapshot comparison gives 30 additional profiles and 30% growth.
However, the September delivery also reconstructs June at 110 after newly collected or corrected profile history. Using the current series gives (130 ÷ 110) − 1 = 18.18%. Both calculations describe their inputs correctly. They answer different questions:
| Calculation | Result | Meaning |
|---|---|---|
| September observation versus the saved June observation | 30% | Change between what the team received at the two dates |
| September count versus revised June in the current history | 18.18% | Growth implied by the provider's current reconstruction |
| Revised June versus saved June | +10 profiles | Historical revision, not ten new September hires |
Keep both the received snapshot and the current reconstructed series. That lets the team improve its present view without rewriting the history of why an account was prioritised earlier.
Suppose 20 of the 30 additional profiles belong to an acquired subsidiary that was folded into the parent record. A scope-adjusted parent comparison might be 110 versus the original 100, or 10%, under that explicit assumption. Do not apply the adjustment silently or subtract the subsidiary twice from a revised baseline. Preserve the entity decision with the calculation.
Now add functional context. If the same-scope engineering team rises from 30 to 42, that is 12 profiles and 40% growth. For a developer-tool seller, this is a more relevant research reason than total-company growth alone. It still does not establish a project, purchasing budget or active software evaluation.
A useful seller conclusion would be: “Engineering appears to be expanding; ask how the team is handling build capacity.” “They hired 30 people and must need our product” overstates both the observation and the commercial inference.
The signal-based outbound playbook explains how to turn business change into a relevant question. The headcount signal should shape that question, rather than manufacture buying intent.
Keep entity scope and revisions visible
Store provider company ID, CRM account ID, domain, parent/subsidiary relationship, count definition, observation month, retrieval time and data version. Record the window used by each growth field. A three-month ratio and a twelve-month ratio are different signals even when they are delivered in adjacent columns.
Company identity matters as much as the number. A regional subsidiary can share a parent brand while hiring for a separate operating unit. PDL's count documentation explains bottom-up person aggregation and subsidiary handling; it also notes that job-level categories can count a person more than once when the title has multiple levels. Do not sum those level buckets and present the result as unique employees. Count methods.
PDL documents monthly API data updates, with flat-file delivery on monthly or quarterly schedules. Repeatedly calling the same monthly build does not create a daily workforce feed. Schedule the monitor around fresh deliveries and use the saved version to explain changes. Update cadence.
An absent observation is not zero employees. A zero baseline makes percentage growth unsuitable; use an absolute change or retain the item as newly observed. Likewise, keep an acquisition, rebrand or changed company ID separate from organic expansion until the scope is reconciled.
For a practical account-prioritisation rule, require both a relative and absolute change, then interpret the function or region. A 50% rise from two to three profiles is one additional profile. A 10% rise from 1,000 to 1,100 represents 100. Neither threshold is universally right; choose the one that changes the seller's workload sensibly.
Cost a thousand-account monitor
Assume 1,000 target companies are evaluated monthly. This fictional workload produces 900 provider matches, 760 records with comparable scope/history and 100 candidate growth signals. A researcher spends eight minutes interpreting each candidate at $60/hour. Sixty become useful, seller-ready signals.
The acceptance path matters: 900 matched companies do not imply 900 usable growth histories, and 100 flagged changes do not imply 100 commercial opportunities.
| Monthly component | Editorial assumption | Cost |
|---|---|---|
| Base PDL Company Pro allowance | Minimum 1,000 credits at the documented monthly tier | $100 |
| Required history/breakdown field scope | Incremental premium/comprehensive amount, called H | H |
| Signal interpretation | 100 × 8 minutes × $60/hour | $800 |
| Monitor administration | 4 hours × $75 | $300 |
| Storage/scheduling | Budget allowance, not a vendor tariff | $40 |
| Operating subtotal | Base plus operation and field scope | $1,240 + H |
This yields $20.67 + H/60 per useful signal. The 100-credit difference between purchased minimum and 900 matched records is unused capacity in the model, rather than a discount on the minimum payment. Additional successful retries or search results can consume more credits.
The annual base minimum is $960, equivalent to $80/month, for 12,000 credits. That saves $240 versus twelve $100 base months. It does not establish an all-in historical-data price, nor does it create a daily refresh requirement for a monthly dataset.
Compare manual tracking across all 1,000 accounts at three minutes each and $60/hour: $3,000/month. With $1,140/month of operation before the licence, the recurring time-value ceiling for the total data purchase is $1,860/month. Initial engineering setup of 30 hours at $100 costs $3,000; spread over the first year, that reduces the licence ceiling to $1,610/month, before external implementation fees. Under the monthly base model, H must be at most $1,510 to remain within that first-year ceiling.
If the total qualifying data purchase is an illustrative $500/month, operating cost is $1,640 and the assumed monthly capacity value is $1,360. The $3,000 setup is recovered in about 2.21 months. At an illustrative $1,500 licence, operation becomes $2,640 and the value falls to $360/month, giving about 8.33 months. These are budget sensitivities, not vendor quotes or measured savings.
For a smaller research team, two Sales Navigator Core annual licences cost $2,159.76/year, or $179.98/month equivalent. One Crunchbase Pro monthly subscription adds $99. This $278.98 software base supports human research; it does not buy the same API history as the PDL monitor.
Dealroom's Premium base is €1,050/month equivalent on the €12,600 annual term, with its stated three-seat starting scope. Keep that currency and export model separate from the US dollar API budget. Its API/custom licence should be evaluated for the pipeline, while the research-seat purchase also serves funding and ecosystem work.
The buying unit is a comparable, useful growth observation. A cheaper matched company record can be more expensive per useful signal if its history, scope or functional fields do not support the decision.
Make the buying decision
Choose LinkedIn Sales Navigator when sellers need to interpret a shortlist through hiring, departments and people. It is the simplest starting point for a human research process.
Choose Crunchbase as a complementary layer when funding and company trajectory help select the accounts. Its employee range is useful for scale, while a precise growth model needs additional evidence.
Choose Dealroom for technology/startup research where historical growth, funding and ecosystem context belong together. Use the annual research package for that programme and the separate API basis for a machine pipeline.
Choose People Data Labs for repeatable monitoring with engineering ownership. Its defined fields and bundles make it the strongest fit here for a structured dataset, provided the purchased historical scope serves the rule being built. Preserve observations and revisions rather than treating the current series as immutable truth.
Start with one headcount source and a clear entity model. Adding several sources before defining the measure can produce more conflicting numbers without a better buying decision.
FAQ
Is a profile-derived count the company's actual workforce?
It is an observed population associated with the company in that provider's data. Coverage, profile updates, contractors, duplicate records and entity mapping can affect it. Use it for direction and account research, and use a disclosed company figure when the exact reporting-period workforce is the question.
Can Crunchbase employee ranges establish growth percentages?
A range can establish a size category or a change of category. It cannot support an exact percentage without a more precise count. Treat funding and predictive growth context as additional reasons to research the account, rather than converting a category midpoint into a headcount fact.
Why did last quarter's count change in a new delivery?
A provider can reconstruct historical values from newly collected or corrected profile information. Retain the original received observation and the revised history. The new series improves the current interpretation; the saved observation explains the decision the team made at the earlier date.
Does the cheapest PDL Company plan include all growth fields?
The base API credit price and the field bundle are separate buying dimensions. Monthly history and twelve-month growth have Premium scope, while additional windows and breakdowns have Comprehensive scope. Price the fields the monitor needs, then evaluate the resulting total against the useful-signal budget.
Should a company growth alert automatically trigger outreach?
Use it to prioritise interpretation. Identify the function, region and plausible business need, preserve the account relationship and give the seller a supported question. A workforce increase is a business change; it does not establish that the company is evaluating your category.
