Multi-workspace outbound without mixing lists
Separate brands, regions, and offers into dedicated workspaces — each with its own contacts, templates, and SMTP.
One shared contact database sounds efficient until a product launch email goes to a partner list, or an APAC campaign inherits EU suppression rules it should never see.
The workspace unit
In OutboundOS, a workspace is the hard boundary:
- Contacts and lists live inside one space
- Templates and journeys do not leak across spaces
- SMTP credentials can differ per space (agency clients, sub-brands, regional domains)
- Analytics stay scoped so you can answer "how did this motion perform?"
That model maps cleanly to agencies, multi-brand operators, and founders who sell more than one offer.
When one space is enough
Stay on a single workspace if you have one ICP, one sending domain, and one team. Adding spaces too early just creates empty containers.
Split when any of these become true:
- Different legal entities or brands share an account
- Different SMTP / domains must not share reputation
- Teams need isolation so they cannot accidentally enroll the wrong list
- You want clean lifetime pricing per motion instead of one megaworkspace
Operating tips
Name workspaces after the motion, not the person ("EMEA partners", "Product launch Q3"). Document which domain and SMTP each space uses. Keep suppression and retired contacts per space so compliance stays local.
Create a free account and add a second workspace when your outbound stops fitting in one box.