Design the record before the integrations
Define which system is authoritative for account, contact, conversation and opportunity state. Agree identifiers and field meanings before importing data. Then map transitions: research approved, contact attempted, response received, discovery held and opportunity accepted.
For each transition, state the trigger, responsible owner and evidence. Test duplicates, missing fields, suppressed contacts and stale updates. An integration should not invent opportunity value or bypass the receiving seller's acceptance rule. Give failure alerts an owner and recovery instruction.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Identity | Stable account/contact keys and duplicate handling | Keep one coherent buyer record |
| State and ownership | Shared definitions and named transition owners | Make work visible without double counting |
| Recovery | Error detection, review and replay boundaries | Repair failures without duplicate outreach or lost context |
Work through the decision
Illustrative failure: a reply is received while the CRM synchronization is temporarily unavailable. The system retains the response, flags the failure and prevents another sequence from sending blindly. An owner checks account matching and replays the update without creating a duplicate opportunity.
A clean demonstration includes this case, not only the happy path. At handover, an internal administrator should be able to use the same recovery guide. Keep sensitive conversation content out of generic analytics events.
The same account exists differently in every tool
Conflicting identifiers and states create duplicate sends, lost context and attribution errors. Resolve the authoritative record and matching rule before adding more integrations. Synchronization is not the same as consistent meaning.
A concrete next step
Trace one controlled account through research, reply, discovery and acceptance. Add a duplicate and synchronization failure, then document the behavior before rollout.
Sources and research notes
- HubSpot: Pipeline rulesProduct documentation
- Attio: Sharing and permissionsProduct documentation
- Attio: Back up workspace dataProduct documentation
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic