Stable fields
Core identity, established locations and long-lived company attributes may require less frequent refresh.
DATA & RESEARCH STANDARDS
Define Quality Before Delivery.
“Verified” should mean something specific. We agree the matching, freshness, evidence and completeness rules that matter to the engagement before scaling.
Entity standard
- Legal / operating name and website matched
- Parent, subsidiary and location relationships resolved where relevant
- Duplicate records identified
- Ambiguity labeled instead of hidden
Evidence standard
- Direct source or dataset reference where appropriate
- Published / observed date retained where available
- Extracted evidence separated from interpretation
- Source quality and limitations considered
Buyer standard
- Function defined before title hunting
- Current role and company checked
- Relevance to the objective documented
- Contact verification status recorded when included
Delivery standard
- Required fields and formats agreed
- Reject / deprioritize reasons preserved
- Confidence and interpretation labeled
- CRM-ready structure and duplicate prevention
FRESHNESS
Different fields age at different speeds.
A legal entity, a job title, a technology install and a business event should not all be treated as if they have the same refresh window. The project defines freshness expectations based on the field and intended use.
Dynamic fields
Buyer roles, contact status, hiring and departmental change can become stale quickly.
Event-driven fields
Funding, M&A, leadership changes and other events should retain the event date and observation context.
START WITH EVIDENCE
Need a specific verification standard?
Tell us what your downstream workflow requires and we can define the acceptance rules before a pilot.