- If independently verified accuracy benchmarks are required
- Public materials include methodology statements and vendor-provided metrics but do not include independently audited accuracy results.
- If procurement requires published trust center documentation and certifications
- Public SOC 2/ISO attestations were not found in accessible sources; if procurement requires these publicly, a larger provider with mature published compliance artifacts may be preferred.
- If the primary requirement is contact details (emails and phone numbers) rather than employment-change verification
- LDT's positioning focuses on job-change and employment verification; other providers may be stronger for direct contact information coverage depending on segment.
- If live, query-time verification is available and cheaper for a narrow workflow
- Community discussions indicate that live query approaches may outperform databases for certain point checks, but those approaches carry operational and compliance trade-offs.
- Public information gaps (diligence required)
- Security certifications not publicly documented.
- Data residency and hosting details not clearly published.
- Limited third-party review coverage, making it hard to benchmark support and reliability.
- Product/metric ambiguities
- Different dataset counts appear across pages (160M tracked vs 80M verified on API page). Buyers should clarify definitions, segment coverage, and SLAs per field (company vs title vs start date).
- Operational limitations common to open-web job-change data (industry-wide)
- Identity resolution challenges (name collisions, company name normalization).
- Delayed updates (individuals may not update public profiles immediately).
- Compliance and terms-of-service sensitivity around sources, even when data is pulled from publicly accessible web pages.