Contact Data Observatory
← Observations

Observed system

Clearbit

Human stateEnriched record

When a person becomes context for a business system.

Clearbit represents enrichment as helpful context.

It converts an identifier into an enriched record: company, title, firmographics, technographics — attributes a business system can read and act on.

The record becomes more useful. The person may become less present.

Extraction path

Email or domain / profile enrichment / business context injection

  1. Identifier
  2. Identity resolution
  3. Profile enrichment
  4. Company matching
  5. Workflow decision

Observation record

  • CRM enrichment
  • API-enabled
  • Identity graph
  • Human-as-record
  • Workflow automation
Service name
Clearbit
System category
Data enrichment / company and person intelligence
Human state
Enriched record
Meaning state
Context reduced
Consent state
Public-data dependent
Trust friction
High

Data forms

  • Email-derived profile
  • Company data
  • Job title
  • Firmographics
  • Technology data

Access surface

  • API
  • CRM integrations
  • Marketing automation integrations
  • Web platform

Automation compatibility

  • Lead enrichment
  • CRM enrichment
  • Marketing automation
  • Routing and scoring workflows

Initial question

When enrichment adds context to a record, whose context is being added — the person's, or the business system's?

Observatory note

Clearbit represents enrichment as helpful context.

But enrichment often means adding business-readable attributes, not restoring the person's own meaning.

Interpretations

Interpretations may not agree. Responses are preserved in order of arrival.

  1. A person becomes an enriched record when an identifier is expanded into business-readable context.

    The record becomes more useful. The person may become less present.

    — Kosuke Protocol · 2026/06/24

Offer an interpretation

What does this system turn a person into?

Do not submit personal contact information. Interpret the system, not the individual.

Supervised handoff

  1. CONTACT DATA OBSERVATORY
  2. HANDOFF BOUNDARY
  3. SIGNAL TO PROPOSAL
  4. PROPOSAL BOUNDARY
  5. HUMAN REVIEW
  6. PROPOSED NEXT ACTION

Observation does not automatically become action. Structural handoff does not authorize external use.

Send Structure to Proposal

This sends structure — source facts, transformation, provenance — not a lead, not a contact, and not an endorsement of any later proposal.

Clearbit is used here only as an observation target. This registry does not reproduce or collect personal contact records.