Twelve brands, one login, zero crossover

There are two ways to run several brands on tooling built for one, and both of them are bad.

One account per brand. Clean separation, and an operational tax that compounds: a login per brand, a subscription per brand, a template library per brand, and no way to see the portfolio at once. Every process you improve has to be improved n times.

One account, several audiences. One login and one bill, and a persistent low-grade risk that something global leaks across. The sender defaults, the suppression list, the domain, the frequency logic — in most tools at least one of these is account-wide, and it is usually the one you find out about after a send.

The interesting question is not “does the tool support multiple brands”, because everything claims to. It is which objects are scoped to a brand, and which are global. That list is the whole product.

The scoping checklist

When we designed SendNectar, this is what we decided has to belong to the brand rather than the account. It is worth using as an evaluation checklist against anything you are considering:

Audience — lists, segments, tags, subscription topics, subscriptions, suppressions. If suppressions are account-wide, an unsubscribe from a side project silently kills deliverability on your main brand. If topics are account-wide, you cannot ask for granular consent per brand.

Delivery — sending, tracking, return-path, and landing-page domains; sender profiles; sending routes. Shared domains mean shared reputation, and shared reputation means the least careful brand sets the ceiling for the most careful one.

Content — templates, reusable blocks, RSS feeds. Sharing content deliberately is useful. Sharing it by default is how a client’s footer ends up in another client’s email.

Capture — forms, landing pages, preference centres, and the websites they are allowed to be embedded on. Origin allow-listing per brand is what stops a form being lifted onto a site you did not authorise.

Messaging — campaigns, frequency caps, workflow definitions. A frequency cap that is not brand-aware either over-restricts the quiet brands or under-restricts the loud one.

Governance — consent evidence, retention policies, legal holds. Different brands often sit under different legal entities in different jurisdictions. If retention is one global number, it is the strictest one, applied to everything.

The bit people forget: legal identity

Compliant marketing email has to carry the identity and postal address of the entity actually sending it. When brands sit under different companies — common in agencies and holding structures — that footer differs per brand, and it is not a cosmetic setting.

So brands in SendNectar nest under a legal entity, which carries the legal name, country, postal address, and privacy contact. A brand inherits the correct identity rather than having it typed in per template and drifting.

What one login should still give you

Isolation is only half the requirement. The reason not to run n accounts is that you want portfolio-level operations:

• One team, with membership scoped per brand — a contractor sees the client they work on and nothing else.
• One set of provider connections, routed per brand and per message class.
• Reporting that rolls up across brands or filters down to exactly one.
• One bill, priced on how many brands you run rather than how much you send.

That combination — hard isolation of data, shared operation of the account — is the entire thesis. It is not a feature you can add to a single-audience product later, because it is a decision about what the primary object is.

A practical migration order

If you are consolidating today, the order that causes the least pain:

1. Create the legal entities first. Everything hangs off them, and retrofitting is tedious.
2. Create one brand and move your least critical audience into it. Verify domains, connect the provider, send one real campaign.
3. Import consent with preserve_evidence if you have real records, pending_confirmation if you do not. Do not attest to consent you cannot substantiate.
4. Only then move the brand that matters most.

The temptation is always to migrate the big brand first because it is the one that justifies the project. Resist it. The first migration is where you discover what you got wrong about your own data.