MCP Scraper
Log inFree to Start

Native Research + CRM

Knowledge and relationships stay separate.

Research preserves what you know about a subject. CRM manages a relationship you intentionally chose to manage. X-Ray adds evidence without becoming the record owner.

Choose by intent.

A living person, an email address, or a company domain does not make a subject a CRM record. Use Research when you are learning; use CRM when you intend to manage the relationship.

People

Research People

Sourced claims, roles, topics, time periods, and citations.

Organizations

Research Organizations

Sourced organizational knowledge and citations.

CRM People

CRM People

Managed relationships, contact fields, owners, optional lifecycle, deals, and tasks.

CRM Organizations

CRM Organizations

Managed accounts, related people, domains, deals, tasks, and owners.

Operator workflow

Create in the intended domain, inspect field authority and freshness, and use governed preview/apply flows for every boundary-crossing operation.

Create deliberately

CRM requires a relationship type. A commercial lifecycle is optional.

Link without copying

A counterpart link connects independent Research and CRM records and mutates neither record.

Preview changes

Conversion and import previews show exact proposed values, sources, validation issues, and duplicates.

Apply the receipt

Apply requires the exact owner-scoped handle, digest, confirmation, and idempotency key.

Agent workflow

Use the governed research_* tools for sourced subjects and crm_* tools for managed relationships. Raw Memory writes, path-shaped display names, email-only titles, and provider-shaped records fail the contract.

Link is not conversion

Counterpart linking copies no fields. Create-from-Research requires a preview that names every proposed value and source, followed by explicit apply. The Research record remains independently editable.

X-Ray is evidence, not authority.

CRM stays usable if X-Ray is locked or unavailable. When evidence exists, seven observed attribution models can inspect the same journey. Position based defaults to 40/20/40. Observed credit and customer-reported impact remain separate ledgers.

Observed journey

Consent-eligible sessions, touches, conversions, and revenue remain read-only evidence.

Reported influence

Survey answers remain labeled customer reports and never become tracked touchpoints.

Exact values

Every decision visual provides units, freshness, model context, and an exact-value table.

External providers remain unavailable.

Salesforce and Pipedrive have not passed the provider release contract. Stripe enrichment is unproven for this release. Native CRM exposes no provider connect or sync controls and does not depend on any of them.

CapabilityStateWhat works now
Native Research and CRMAvailableGoverned Memory records, imports, quality, audit, counterpart previews, deals, and tasks.
Salesforce / Pipedrive syncUnavailableNo public wrapper or setup continuation.
Stripe enrichmentUnprovenNo frontend control or production claim.