Client work,
cleanly separated.
Client isolation, scoped seats, and pricing you can quote with confidence.
Client data should never share a list.
Agencies end up managing a client's email account, or worse, running several clients through one. Either way the risk is the same: a shared suppression list, a sender identity that belongs to the wrong brand, or a junior teammate with access to everything because access is all-or-nothing.
Every client is a brand with a hard boundary around it. Team membership is scoped per brand, roles are permission bundles rather than blunt admin flags, and each client keeps its own domains, sender profiles, consent evidence, and reporting — under one account you control.
Agencies & studios, specifically.
A brand per client
Audience, lists, segments, topics, subscriptions, suppressions, templates, and history are scoped to the client that owns them. There is no shared pool to leak from.
Scoped seats and roles
Invite teammates and assign roles built from permission bundles, then scope membership to specific brands — a contractor sees one client, not the book of business.
Client-owned identity
Each brand carries its own legal entity, postal address, privacy contact, and privacy policy URL — the details the footer of a compliant marketing email legally requires.
Their domains, their reputation
Sending, tracking, and return-path domains are verified per brand, and daily reputation is scored per domain, sender, and provider — one client’s bad month never drags another down.
Bring the client’s provider
Connect the client’s own SES or SMTP account so delivery stays on their infrastructure and their invoice — you charge for the work, not for reselling volume.
Auditable handover
Consent evidence, exports of contacts, consent, suppressions, and submissions mean an account can be handed back cleanly when an engagement ends.
Built for the way agencies actually get audited.
When a client asks how you obtained an address, or a regulator asks who the data controller is, the answer is already recorded.
- Legal entities
- Data-controller identity, country, postal address, and privacy contact per client
- Roles
- Tenant permission bundles assigned to members, plus per-brand membership scope
- Consent events
- requested · granted · confirmed · withdrawn · migrated, each with lawful basis
- Lawful basis
- consent · contract · legal obligation · legitimate interest
- Exports
- contacts · list · segment · consent · suppression · submissions, as CSV, XLSX, or JSON
- Privacy requests
- Access, portability, correction, and erasure handled per contact with due dates
Bring your provider.
Keep your brands distinct.
Start today.
Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.