I am building out an 8-company multi-brand account. Master + 7 subs, all CMS websites built out, marketing automations, but now we’re bringing in 14 sales reps to work their brand’s contacts, companies, and sales pipelines. Should I create separate pipelines for each sub-brand, or for the master with team access? We need to keep all sales team members’ owned contacts, companies, and owners visible to only the brand teams. I’m hoping someone out there has a multi-brand, sizable HubSpot account with 12+ active sales users who can do a show-and-tell of their account (I’m in dental B2B, so anything outside of that) and share some warnings and tricks before I let everyone in. TIA
Hey @JenOBrickman !
I’m in fact currently setting an account for a client with a similar escenario, just mind to have teams propertly setup by brand and to manage access on assests like contacts, campaigns, forms, workflows, lists(segments) based on brands.
That would help to keep data clean and to avoid having all users looking at different brand assests they dont really need to look at.
Hope this helps! If you need extra support on this, feel free to schedule your free consultation here: https://meetings-eu1.hubspot.com/ruben11/zuid-jef-ruben-
ZUID.
Goirkekanaaldijk 12
5046 AT Tilburg
Nederland
Hi there @JenOBrickman Thanks for posting
I want to share two Knowledge Base articles that offer more context into your issue:
And this community thread that offers more help: https://community.hubspot.com/t5/CRM/How-to-Create-Multiple-Contact-Pipelines-in-HubSpot/m-p/1113140
Also I’m tagging a few community experts who can help you out here: Hey there @CarolinaDeMares @danmoyle @Jonathan_Vaz Any thoughts here? Thanks!
Victor
Welcome to the Community @JenOBrickman! Here’s what I’d plan for if I were in your shoes. First, I’d suggest as clean of a set-up as possible, and probably lean toward one shared pipeline per sales process, controlling visibility with teams and permissions, rather than building 7–8 separate pipelines, unless a brand truly has a different set of stages.
So if all 8 brands sell in roughly the same way (same core stages), keep one main pipeline and use:
- Deal properties for Brand (dropdown or multi-checkbox).
- Filters/views by Brand + Team.
Only create separate pipelines if:
- Stages, probabilities, or required fields are meaningfully different.
- Reporting needs to be completely separate per motion (like new business vs renewals vs channel).
To your teams and permissions (for “brand silos”) question, in order to keep each brand’s reps from seeing the others’ data, I’d lean on teams + “Team only/Owned only” permissions. Here’s how I’ve seen it done.
Set up:
- One parent team: “Sales – All”
- Seven child teams: “Sales – Brand A”, “Sales – Brand B”, etc
In permission sets, configure:
- Contacts/Companies: “Owned only” or “Team only” view/edit as needed
- Deals: “Team only” (so they only see deals owned by their team in the shared pipeline)
Then on the pipeline, use pipeline access rules (Manage access) to restrict who can see/work which deals by team membership.
As for the multi-brand features I’d use, the Brands / Business Units add-on gives you some good power for things like segmentations and reporting. So I’d use the Brand or Business Unit property to segment by brand for reporting, segments, and workflows. Associate each website domain and email sending domain to the correct brand. For anyone who doesn’t have the add-on, you have to get innovative and create custom properties like “Brand” on contacts, companies, and deals and drive them via forms, workflows, and initial imports.
The brands features in HubSPot are great, but nothing is perfect. Here are a few thinigs to keep in mind so you don’t get hosed.
Mixed-brand contacts:
A single contact can legitimately interact with multiple brands; support this with a multi-select Brand/Business Unit property rather than duplicated records.
Decide upfront: if a contact crosses into another brand, who owns it and can the second brand’s reps see it?
Workflows:
Lock down who can edit/activate workflows so a Brand A marketer can’t accidentally enroll Brand B’s contacts. Use team-based permissions for automation.
Data mess risk:
Running multiple brands in one portal can “become an absolute mess” if you don’t consistently tag everything by brand and enforce team segmentation from day one.
Hopefuly that helps!
Thank you for all of the details, Dan. This all lines up with how I’ve been working the account and has me second-guessing the multiple pipelines vs 1. Thank you!
@JenOBrickman right on - happy to help!