Company Revenue Data: 5 Sources and How to Compare Estimates

Yananai A. ChiwutaPublished ·11 min readUpdated
Company Revenue Data: 5 Sources and How to Compare Estimates

TL;DR

  • A company revenue field may be a reported figure, a modelled estimate, a range or a parent-company total. Those are different kinds of evidence.
  • People Data Labs and Crustdata offer company data through APIs; inspect the field definition, range and entity match before using a value in a CRM rule.
  • Dun & Bradstreet and ZoomInfo are broader commercial-data candidates. Ask for the specific revenue field, source, date and legal-entity context in your contract.
  • Companies House provides UK company filings where available, but a filing does not always disclose turnover. Small companies and micro-entities can omit the profit and loss account from the public filing.
  • When sources disagree, preserve the source, period, currency and entity. A band crossing your qualification threshold should usually remain uncertain rather than being converted to a precise number.

What does a company revenue field actually mean?

A revenue number can be useful for assigning accounts, sizing a market or deciding which sales motion to use. It can also produce confident-looking errors. The figure might describe a global parent rather than the subsidiary buying your product, a previous financial year rather than the current one, or a statistical estimate rather than a filed amount.

Before using the field as an ideal-customer-profile filter, record five things: the legal or operating entity, the period, the currency, whether the amount is reported or estimated, and the source or methodology available to you. A range such as $10 million–$50 million is not the same as a reported $30 million. A provider's update date can describe when the record was refreshed, not the financial period the revenue covers.

The five sources below are routes for investigation, not an independent accuracy ranking. The B2B company data guide covers broader firmographics; this article focuses on interpreting and using the revenue field responsibly.


Five sources at a glance

Source Starting fit Revenue question Buying or access question
People Data Labs API-based company enrichment What does the returned field or range mean for this entity? Field bundle, match billing and refresh
Crustdata API-delivered company firmographics Are lower and upper bounds estimates, and how current are they? Endpoint, credits and data rights
Dun & Bradstreet Business identity and commercial data Does the value refer to this location, legal entity or corporate family? Product, source metadata and contract
ZoomInfo Revenue context in a sales-intelligence workflow Is the value reported, estimated or banded for this account? Contract, exports, refresh and CRM fields
Companies House UK legal-entity filing evidence Does the filed document actually disclose turnover? Public filing access, document period and extraction work

A public registry and a commercial enrichment API have different roles. A registry can help verify the entity and retrieve filed accounts; a vendor may provide normalised fields or estimates across many markets.


1. People Data Labs: for company data via API

People Data Labs provides company data and enrichment APIs for applications that need structured records. It is a candidate when an engineering team wants revenue context alongside company identifiers and other firmographics.

Inspect the exact schema and the field bundle in the current contract. PDL's company-data overview labels inferred_revenue as estimated annual revenue in US dollars in its Premium bundle and lists the numeric inferred_revenue_integer under a separate named bundle. Do not assume the numeric field is included simply because the estimated-revenue range is available. Ask how the value was derived, which period it represents and whether the record corresponds to a parent or operating entity. A matched domain can still represent a group rather than the entity making a purchase.

PDL fits a pipeline that already manages matching and field-level provenance. It may be insufficient as the sole evidence for a hard financial threshold where the source or period is unavailable. Test the target accounts and keep a value marked unknown when the response does not meet the team's evidence rule.


2. Crustdata: for estimated revenue bounds

Crustdata's firmographic documentation describes lower and upper estimates of annual revenue in US dollars. A bounded estimate can be more honest than a single invented point value, but the range must remain visible to the user of the CRM.

If the qualification threshold is $20 million and a provider returns an estimated $10 million–$50 million range, the range crosses the threshold. The correct conclusion is not automatically “qualified” or “disqualified.” Ask for additional evidence or place the account in an uncertain segment. Check the observation date, entity, source and contract for the particular record.

Crustdata is a candidate for an API-first enrichment workflow that can use estimated bounds. It is less appropriate as a substitute for a filed financial statement when an exact reported amount is required. Confirm endpoint credits, minimums and refresh rules before applying the data to a large account list.


3. Dun & Bradstreet: for business identity and financial context

Dun & Bradstreet documents sales-revenue fields and business identifiers in its company-data products. Its corporate-family context can be useful when a team needs to distinguish a location, subsidiary and parent before applying a revenue rule.

Ask which product supplies the field, whether the amount is claimed, reported or estimated, and whether it refers to the individual entity or a broader group. Request the period, currency, update cadence and any available provenance or confidence indicators. The fact that a data dictionary defines annual sales does not establish that every private company has a recent filed value.

For a concrete integration check, the D&B Direct SDMR reference shows a sales-revenue amount with currency, unit of size and reliability attributes, together with financial-period and corporate-family fields. Preserve those attributes when they are returned and confirm their meaning for the product you buy. A populated reliability label is provider metadata, not a substitute for inspecting a filing when the decision requires one.

D&B can be a good candidate for a larger identity and firmographic programme. Compare the full contract and the value of hierarchy information against a narrower API if the only requirement is a small set of revenue bands.


4. ZoomInfo: for sales-intelligence context

ZoomInfo offers company information within a broader sales-intelligence platform. A team already considering it for account research can ask whether its revenue field is useful for the specific market and entities it targets.

Request a sample with the company identifier, revenue amount or band, source category, financial period and update date. Check how the product treats parent and subsidiary records and whether those fields can be exported or refreshed in your CRM under the proposed contract. Do not assume a value is a reported filing simply because it appears as a number in a sales interface.

ZoomInfo may fit an organisation that will use the broader account and contact workflow. A team needing only a traceable revenue field should compare the total commitment, data rights and usable yield with a narrower source. No vendor coverage or accuracy claim is inferred here.


5. Companies House: for UK filing evidence

Companies House provides access to filed company accounts for UK entities. A filing can supply strong traceable evidence when it contains the relevant turnover figure and period. It also helps confirm the company number and legal entity before matching a commercial data record.

Do not assume every filing contains revenue. Current official guidance says small companies and micro-entities can file accounts omitting the profit and loss account. Companies House has also paused a planned change that would have required small companies and micro-entities to file that account from April 2028. Check current guidance and the actual document; a missing turnover line is not zero revenue.

The registry is a useful benchmark for a disclosed UK figure, but it is not a complete global private-company revenue database. A filing may describe an earlier financial period, consolidated accounts or a different legal entity from the one your rep intends to sell to. The business registry API guide explains the related identity and access problem.


How do you handle five different revenue records?

Use a synthetic trace before turning any field into an automated qualification rule. These examples are invented to show treatment, not real company data or a vendor benchmark.

Example Evidence returned Appropriate treatment
A: public company Annual report shows $40m revenue for the last completed fiscal year Store $40m with filing, period, currency and entity; do not label it current-quarter revenue
B: private company Provider estimates $10m–$50m; threshold is $20m Preserve the range and mark threshold status uncertain
C: subsidiary Parent reports $2bn consolidated; subsidiary amount is absent Link the parent figure as context; leave subsidiary revenue unknown
D: UK small company Filed accounts omit the profit and loss account Record filing checked and revenue not disclosed; do not write zero
E: conflicting sources One estimate is €15m from an older period; another is $25m with no period Keep both with provenance; do not average them into a false precise figure

For an inspectable real example of a reported group figure, Apple's 2026 Form 10-K reports $478,834 million in consolidated net sales for the year ended 26 September 2026. Store that as $478.834 billion, with the filing and fiscal period attached. The same statement reports $416,161 million for the prior year; that older number is not the latest figure merely because a data provider retrieved it recently. Neither total establishes the revenue of a particular subsidiary. This checks a public filing, not the accuracy of any vendor listed above.

For currency conversion, retain the original amount and currency, the exchange rate source and date, and the converted value. A conversion is a calculation, not a new reported revenue figure. Compare like periods where possible: a 15-month accounting period and a 12-month year should not be placed side by side without explanation.

For example, a fictional company reports £15 million over 15 months. A simple proportional annualisation gives £12 million over 12 months: £15 million × 12 ÷ 15. Store £15 million and the actual 15-month period as the reported fact; label £12 million as a derived comparison, not a filed annual result. That calculation assumes revenue was distributed evenly, so seasonality, acquisitions or a change in operations can make it a poor estimate. If the business needs a reliable annual threshold decision, review the underlying accounts instead of using the derived number automatically.

A useful CRM schema can include revenue_value, revenue_lower, revenue_upper, currency, period_end, period_length, entity_id, source_type, source_reference, retrieved_at and review_status. These are suggested internal fields, not a promise that every supplier returns them. Avoid overwriting a manually verified filing with a newer but weaker modelled estimate simply because the API response arrived later.


What does a usable revenue field cost?

Assume a pilot of 1,000 companies, including public and private firms. A provider returns a revenue value or band for 700. After checking entity, period, currency and source requirements, 400 are acceptable for the intended segmentation. Those numbers are synthetic; they do not describe the performance of any named source.

Suppose the data contract allocates $1,000 to the pilot, analyst review takes ten hours at $60 per hour and infrastructure costs $100. The total is $1,700, or $4.25 per usable revenue field at 400 accepted records. Dividing by 700 returned fields would produce about $2.43, but that denominator includes 300 records the workflow cannot use.

If a second source costs an additional $400 and review takes two more hours at the same rate, the added cost is $520. If it resolves 100 additional records, the total becomes $2,220 for 500 usable fields, or $4.44 each. The second source increases coverage in this scenario but raises average cost. It may still be worthwhile for strategically important accounts; calculate the incremental $5.20 per additional usable field as well.

Add minimum contract, refresh and export costs where relevant. A quarterly refresh of all 1,000 companies may be wasteful if only 200 are active prospects, but a stale annual value can be misleading for a fast-changing account. The waterfall enrichment guide helps decide which records need another source or refresh.


When should revenue remain unknown?

Leave the field or qualification status unknown when the entity is uncertain, the period is missing, the only value belongs to a parent and no subsidiary amount is available, or an estimate range crosses the threshold. Unknown is an operational state: route the account for research or use another relevant signal rather than silently excluding it.

For a threshold of $20 million, define explicit rules. A recent reported $25 million for the correct entity can satisfy a reported-revenue rule. An estimated $25 million might satisfy a separate estimate-based rule if the business accepts that risk. A $10 million–$50 million band needs review. A missing value should not be treated as $0. Record the rule version so a rep can understand why an account was routed.

Test the rule against accounts around the boundary and compare decisions with the evidence a reviewer can inspect. Headcount, funding or web traffic may be useful context, but none is a direct substitute for revenue. Our company headcount data guide explains the separate limitations of workforce estimates.


FAQ

Can I find revenue for every private company?

No. Disclosure requirements and public availability differ, and some companies file accounts without a publicly available profit and loss statement. Commercial vendors may provide estimates or ranges, which should be labelled accordingly.

Is an estimated revenue range enough for lead scoring?

It can be useful if the business accepts its uncertainty and the range is appropriate to the decision. A range crossing a hard threshold should not be converted into a precise value without a documented rule or additional evidence.

Does a parent company's revenue apply to every subsidiary?

Not automatically. Consolidated revenue may describe the group rather than the operating entity or buying unit. Keep the hierarchy and entity scope visible and avoid copying the parent total into every subsidiary record.

Yananai A. Chiwuta

Author

Yananai A. Chiwuta

CEO & Co-Founder

Yananai A. Chiwuta is the CEO and Co-Founder of Forma Nôrden, where he builds managed acquisition systems for B2B companies through signal-based outbound and precision paid ad acquisition. He has built and exited two companies, most recently FunnelVision.

Celine Sky-Chiwuta

Article reviewed by

Celine Sky-Chiwuta

Co-Founder & CMO

Celine Sky-Chiwuta is the Co-Founder and CMO of Forma Nôrden, where she shapes the positioning and marketing behind the company’s managed acquisition systems. She previously served as CMO of FunnelVision through its 2025 acquisition.

Related Articles