Contact Data Observatory
← Observations

Observed system

Lusha

Human stateContact object

When a professional profile becomes a directly reachable contact.

Lusha does not merely describe a professional.

It converts a visible profile into a contact object: a name, a role, a company, a revealed email, a possible phone number — a surface made ready for outreach.

The person remains visible. But reachability arrives before permission is examined.

Extraction path

Professional profile / contact reveal / CRM enrichment

  1. Professional visibility
  2. Contact matching
  3. Contact reveal
  4. CRM sync
  5. Outbound workflow

Observation record

  • API-enabled
  • AI-assisted
  • Contact discovery
  • Sales intelligence
  • CRM enrichment
  • Human-as-record
  • Opt-out available
Service name
Lusha
System category
Contact data / sales intelligence
Human state
Contact object
Meaning state
Context reduced
Consent state
Opt-out available
Trust friction
High

Data forms

  • Work email
  • Phone number
  • Company data
  • Job title
  • Professional profile

Access surface

  • Web platform
  • Browser extension
  • API
  • CRM integrations

Automation compatibility

  • CRM enrichment
  • Sales prospecting
  • Recruiting workflows
  • Outbound workflows

Initial question

When a professional profile becomes directly reachable, what happens to the boundary between visibility and permission?

Observatory note

Lusha represents a familiar transformation: the professional profile becomes a contact surface.

The person is not merely described.

They are made reachable.

Interpretations

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

  1. A person becomes a contact object when professional visibility is reorganized as direct reachability.

    The question is not whether the person exists online. The question is whether existence has become permission.

    — 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.

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