The account lands in your CRM with the prompt attached

Identification is only useful where your team already works. Every identified account is written to your CRM in real time — deduplicated against what's there, enriched, scored, and carrying the AI answer that produced it.

Mapping is automatic. You don't build a field schema before you can use this.

Identified accounts are matched against existing records before anything is written. An account you already have is enriched, not duplicated — the AI origin, the prompt, and the intent score attach to the record that exists. Only genuinely new organisations create new records.

Filters are yours to set. Write only above an intent threshold, only from named prompt sets, only certain firmographics — whatever keeps your CRM clean.

Records are written as the visit resolves, so a rep can act while the buyer is still in-market. Intent scores update on a batched cycle afterwards as return visits and further behaviour accumulate — the account gets sharper without the record being rewritten underneath your team.

HubSpot's company/contact/deal model, Pipedrive's organisation/person/deal, Attio's records-and-objects, and Zoho's account/contact/lead/deal differ enough that a shared paragraph would be wrong for at least three of them. See each CRM's own integration page for its exact field mapping.

Your CRM shapes what we track, too

Lead sync is the write direction. The read direction already runs: the personas and segments in your CRM build the prompts we track, so visibility is measured against the buyers who actually close rather than a guess about who they are. Both directions run on the same connection.