States

Contact object

Definition: A person represented primarily as someone who can be found and reached.

Used when: The system emphasizes discoverability, email lookup, phone lookup, profile matching, or direct contactability.

Example: RocketReach

Lead object

Definition: A person represented as a target inside a sales or recruiting workflow.

Used when: The system turns a profile into a sequenced outreach object, pipeline stage, or campaign participant.

Example: Apollo

Callable entity

Definition: A person represented as something that can be returned, queried, enriched, or invoked through an API.

Used when: The system makes person data available as infrastructure for developers, automation, or downstream applications.

Example: People Data Labs

Enriched record

Definition: A person represented as a verified or enhanced business record.

Used when: The system adds titles, firmographics, buying signals, org-chart context, or revenue-facing metadata.

Example: ZoomInfo

Workflow object

Definition: A person represented as material inside a programmable workflow, often after enrichment, inference, or AI-assisted transformation.

Used when: The system chains data sources, enrichments, prompts, or automations around a person or account.

Example: Clay

Signal source

Definition: A person represented less as a contact and more as behavioral, intent, attention, or engagement data.

Used when: The system interprets attention, content activity, or engagement as buying intent or market signal.

Example: Bombora, 6sense

Account signal

Definition: A person's activity represented as part of account-level intelligence.

Used when: Individual behavior is aggregated into company, account, or buying committee signals.

Example: Demandbase

Navigable profile

Definition: A person represented as a searchable and filterable professional identity inside a network graph.

Used when: A professional platform becomes a sales or relationship navigation layer.

Example: LinkedIn Sales Navigator

Recruitable profile

Definition: A person represented as a potential candidate who can be found, contacted, and moved into a recruiting pipeline.

Used when: The system converts professional visibility into candidate sourcing or recruiting outreach.

Example: ContactOut

Verified contact object

Definition: A person represented as a reachable contact whose details have been validated for operational use.

Used when: The system emphasizes verification, accuracy, or human-checked contact data.

Example: SalesIntel

Triggered contact object

Definition: A person represented as reachable because an external event, company change, or market trigger made them relevant to a workflow.

Used when: A company event becomes the reason for individual outreach.

Example: Lead411

Market graph node

Definition: A person represented as part of a company, funding, investment, or market graph.

Used when: The person appears through structural relationships such as founder, executive, investor, company, or category.

Example: Crunchbase

Sequenced recipient

Definition: A person represented as the recipient of a planned series of messages, tasks, or touches.

Used when: The system manages timing, cadence, channels, or follow-up actions.

Example: Outreach, Salesloft, Instantly, Reply.io

Optimized recipient

Definition: A person represented as the target of message optimization, personalization, scoring, or AI-assisted writing.

Used when: The system shapes communication around predicted response or sender goals.

Example: Lavender

Business card record

Definition: A person represented through exchanged business cards, relationship history, company affiliation, and contact memory.

Used when: The system begins from business card management, professional relationship records, or organizational contact memory.

Example: Sansan, Eight Team, Remember

Relationship graph record

Definition: A person represented as part of an organizational relationship graph.

Used when: The system emphasizes who knows whom, which company is connected to which person, or how relationships can be activated.

Example: Sansan, FORCAS

Corporate registry subject

Definition: A person represented through corporate registration, legal representative status, shareholder relationships, executive roles, or business risk records.

Used when: The system emphasizes company registry data, legal identity, credit risk, corporate ownership, or business trust.

Example: Qichacha, Tianyancha, Qixinbao

Trust graph entity

Definition: A person or company represented inside a trust, credit, risk, ownership, or compliance graph.

Used when: The system links people, companies, legal records, risk signals, or commercial credibility.

Example: Qichacha, Tianyancha, D&B UAE

Commerce intent object

Definition: A person, company, or buyer represented through commerce behavior, sourcing activity, trade interest, or marketplace interaction.

Used when: The system observes trade, procurement, sourcing, or B2B marketplace activity.

Example: Alibaba.com / Alibaba Accio

Founder ecosystem node

Definition: A founder, investor, executive, or company represented as part of a startup, funding, or ecosystem graph.

Used when: The system maps startup ecosystems, funding events, investors, founders, or growth companies.

Example: MAGNiTT, Tech in Asia Database, e27, Tracxn, Dealroom, The VC

Local business identity

Definition: A company or professional identity represented within a regional business-data system.

Used when: The system is shaped by a specific country, region, business culture, language, or regulatory environment.

Example: Musubu, Zintlr, EasyLeadz, Kompass, NICE BizInfo

Context missing

Definition: The person is present as data, but the surrounding human context is absent.

Context abstracted

Definition: The person's context is converted into workflow logic, categories, or engagement stages.

Context reduced

Definition: The person's context is simplified into commercially useful attributes such as role, title, company, seniority, or intent.

Meaning displaced

Definition: The system's purpose replaces the person's own meaning. The person is understood mainly through the use case of the observer.

Unclear

Definition: The system may provide contactability, but the person's consent to that specific use is not visible.

Implied

Definition: The system appears to rely on inferred availability, professional visibility, or business context rather than explicit consent.

Public-data dependent

Definition: The system relies on publicly available or public-facing data, but the downstream use may go beyond the original context of publication.

User-unverified

Definition: The system may represent a person without that person actively checking, correcting, or confirming the resulting profile.

Opt-out available

Definition: The system provides an opt-out or removal path, but the existence of opt-out does not necessarily mean meaningful prior consent.

Low

Definition: The system's data use is relatively clear, limited, and close to the person's expected context.

Moderate

Definition: The system creates some context shift, but the transformation is visible and limited.

High

Definition: The system makes a person reachable, actionable, enriched, or automatable in ways that may not be visible to the person.

Severe

Definition: The system operates at scale, combines multiple data forms, or deeply embeds person records into revenue, automation, or intelligence workflows.