Inventory the operating dependencies before connecting tools
Start with domain and mailbox administration, then map CRM, enrichment, sequencing, routing and analytics dependencies. Identify which account owns each subscription and where data and suppression live. Keep credentials out of shared documents; use appropriate access management.
Document field meanings, account identifiers, integration logic and error handling. If a workflow runs in an agency-owned tool, clarify what survives the engagement. An export can preserve records while losing automation, history or suppression semantics, so test continuity with a small sample.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Identity and sending | Client domain/mailbox administration and recovery | Agency access can change without losing sender control |
| Account and conversation data | Identifiers, sources, messages and suppression | The next team can interpret and responsibly act on records |
| Workflow logic | Integrations, permissions, dependencies and recovery | The client can operate or replace the system |
Work through the decision
Illustrative inventory: the CRM is client-owned, but reply routing runs in a proprietary agency account. At exit, the client can export contacts but cannot pause the routing or inspect suppression. That is a dependency, not complete ownership.
Resolve it before delivery by moving the workflow into a client-controlled account, providing a tested replacement or clearly licensing continued access. Use a controlled test reply and opt-out to demonstrate the continuation path rather than relying on a promise of handover.
The contact list transfers but suppression does not
A successor can accidentally recontact people if opt-out and account-state data are absent or unclear. Treat suppression as a first-class ownership asset, with appropriate retention and access rules. Test it during transfer.
A concrete next step
Build the outbound asset inventory with owner, administrator, export, dependency and recovery fields. Test one response and suppression path using controlled data.
Sources and research notes
- Attio: Back up workspace dataProduct documentation
- Attio: Sharing and permissionsProduct documentation
- Google: Email sender guidelinesMailbox-provider requirements
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