agency-multi-client-outboundlisted

# Multi-Client and Multi-Brand Outbound Running outbound for several clients is the same work multiplied, plus one hard requirement: **nothing crosses between clients.** Not data, not deliverability, not suppression, not reporting. Every serious incident in agency outbound is a crossing. A lead from one client's list appearing in another's campaign. A bounce incident on shared infrastructure taking down three clients at once. An opt-out honoured for one client and not the others. Each is avoidable by structure rather than by care. ## Separate everything that can be separated | Thing | Shared? | Why | |---|---|---| | Sending domains | **Never** | Client A's reputation must not touch client B's | | Mailboxes | **Never** | Same | | Tracking domains | **Never** | Reputation carries | | Suppression lists | **Per client**, plus a global list | Different relationships, but a global "stop" must apply | | Lead lists | **Never** | Contractually and ethically theirs | | Sequences and copy | Per client | Different voice, different offer | | Reporting | Per client | Obviously | | Templates and process | **Shared** | This is where the leverage is | The last row is the point. What scales across clients is method — the ICP framework, the launch checklist, the review cadence, the sequence structure. What must never be shared is infrastructure and data. ## Domains and mailboxes per client Each client sends from domains that look like theirs, not like yours. `getclientname.com`, not `age