Trust resource
Know what a returned company finding cannot prove.
Public evidence can improve company research, but it does not reveal every internal system, contract, budget, owner, satisfaction level, or buying decision.
- External visibility is incomplete
- Website and technology findings can become stale
- Technology presence is not buying intent
- Missing evidence is not proof of absence
Claim limit
A concrete record, not an abstract claim
- Supported
- A public website exposes evidence associated with a named technology
- Not supported
- The company is satisfied with the technology or intends to replace it
- Supported
- A source provides an employee or revenue range
- Not supported
- The range is exact or current in every operating unit
- Published
- Jul 20, 2026
- Last reviewed
- Jul 22, 2026
- Reviewed by
- Kaiju research team
- Applies to
- Current CSV company-research product
Technology visibility
The public web is not the full internal stack
Private infrastructure, internal tools, blocked resources, and regional variants may not be externally observable.
- 1A missing detection is not proof that a technology is absent.
- 2A detected asset can be legacy, experimental, or limited to one website property.
- 3Technology presence does not establish contract value, satisfaction, or ownership.
Company information
Company fields are sourced records and estimates
Identity, employee ranges, revenue ranges, industries, and locations can be incomplete or stale.
- 1Subsidiaries and brands may not map cleanly to one parent company.
- 2Employee and revenue ranges should not be treated as audited financial statements.
- 3Conflicting source values require inspection rather than silent selection.
Using the returned data
Keep the limits attached to the company row
Each field describes public evidence or sourced company data. It does not reveal an internal contract, budget, owner, or next action.
- 1A technology field does not prove active purchase intent.
- 2Company size does not prove budget or buying authority.
- 3Ambiguous rows should not trigger irreversible actions.
Continue the evaluation
Follow the next question behind the result.
Move from one trust concern to the methodology, product explanation, or limitation that helps your team decide whether the data is safe to use.
Test the method
Review the limits beside the result.
Use companies you know to identify which returned fields are supported, which need inspection, and which should remain unresolved in the downloaded file.