Multi-brand communications stack audit
See what your brands really cost to run and where a message can reach you with nobody responsible for it. A 30-minute-per-brand worksheet that maps every mailbox, tool, list, portal, and owner, totals the spend you pay twice, and runs nine gap tests before you decide what to consolidate.
The multi-brand communications stack audit maps five things per brand: the mailboxes people write to, the tools holding contacts, the lists that receive campaigns, the public portals collecting messages, and the named owner of each. It totals cost per brand, multiplies out the tools billed per workspace, and runs nine gap tests for the failures that cost most: a mailbox nobody owns, a list with no suppression source, a form that posts nowhere, and an AI draft nobody approves. A consolidation decision table and a migration order close it.
For: Studio, agency, and portfolio operators answering for more than one brand, ideally before the next tool renewal ยท Published 2026-08-26
What is inside
- A per-brand worksheet: mailboxes, contact stores, lists, portals, owners, cost
- The duplicated-spend calculation that turns per-brand cost into the portfolio number
- Nine gap tests, each with the failure it catches
- A consolidation decision table: what to merge, what to leave alone, what to connect at the boundary
- The migration order: suppression first, mail last
Thirty minutes per brand buys you two things most operators have never seen written down: the real monthly cost of the portfolio, and every route by which a message can reach your organization with nobody responsible for answering it. Run the worksheet once per brand, then the gap tests, then decide what to consolidate. It usually finds money spent twice and at least one mailbox nobody owns.
1. The per-brand worksheet
| Item | What to record |
|---|---|
| Mailboxes | Every address people write to, including aliases and shared mailboxes. Who reads each, and what happens when they are away. |
| Contact stores | Every system holding contacts for this brand: CRM, email tool, spreadsheets, form tool, event platform. |
| Lists and audiences | Every list that can receive a send, with its size, its source, and where its suppression lives. |
| Public portals | Help center, feedback board, roadmap, chat widget, booking link, and every form on the website. |
| Owners | A named person per mailbox, per list, and per portal. A role name is not an owner. |
| Cost | Monthly cost per tool, per brand. Include seats you pay for on a tool used by one brand. |
2. The duplicated-spend calculation
- Total the monthly cost per brand.
- Identify tools you pay for more than once because they bill per workspace.
- Multiply by the number of brands to get the real portfolio figure. This is usually the number that changes the conversation.
- Add the hidden cost: hours per week spent switching between tools, and the cost of the context that never crosses between them.
3. Nine gap tests
- Send a message to every listed mailbox. Does a person answer within your target? An unowned mailbox is the most common finding.
- Submit every public form. Does the submission arrive somewhere with an owner, and is there an acknowledgement?
- Pick a contact who unsubscribed from one brand. Can another brand's tool still email them? If yes, you have a consent gap, not a technical one.
- Ask who can see the sponsor pipeline. If the answer is everyone with the login, you have an access gap.
- Find the newest list. Can anyone say where every address came from?
- Check a departed employee. Are their mailbox and their access actually removed everywhere?
- Look for the same person in three tools. Do the three records agree?
- Ask what happens to a reply to a campaign. Does it land in a mailbox that is synced, or in a no-reply void?
- Ask who approves an AI-drafted message. If the answer is nobody, that is the first thing to fix.
4. Consolidation decision table
| Signal | Consolidate | Leave alone |
|---|---|---|
| The tool is paid per workspace and you run several brands | Yes | |
| The tool holds contacts that also exist elsewhere | Yes | |
| The tool is the system of record for a regulated function (accounting, HR, fund admin) | Leave alone; integrate instead | |
| The tool is deeply embedded in a client's own stack | Leave alone; connect at the boundary | |
| The tool exists because one person likes it | Yes, after talking to that person | |
| The tool sends mail from your domain | Consolidate the sending and the suppression |
5. Sequence the migration
- Start with the brand that hurts most, not the easiest one. The easy brand teaches you nothing.
- Move suppression first, then contacts, then campaigns, then portals.
- Keep the old tool read-only during the cutover rather than deleting it.
- Move mail last, and remember that with a Microsoft Graph connection there is no mail migration at all: the mail stays where it is.
- Only after one brand is fully working, do the next.
This is how CommsOperator is run, not just written
If the practice makes sense to you, the product built around it is one request away. Tell us what you run and we will tell you if it fits.