Multi brand strategy: managing many brands with one team

A multi brand strategy is the decision to run several distinct brands, each with its own audience, promise and look, from one business or team. It lets you serve customers who would never buy from the same brand, and it spreads risk. The cost is attention: every brand needs its own posts, profiles and care. Doing it well means being strict about two things at once: sharing everything behind the scenes, and sharing nothing the customer can see.

This page is about the strategy and the operating habits. If you are deciding whether one product deserves its own identity in the first place, start with sub-brands.

Give every brand a job

A portfolio works when each brand has a clear, different role. Write each one down in a single line. If two lines sound alike, those brands will compete with each other for the same customer, and one of them probably shouldn't exist.

Notice that the looks are as different as the audiences. Night Tide sharing Harbour Coffee's honey tones would confuse an evening guest about whether they had walked into a café. Brand positioning helps sharpen each line.

What to share and what to keep separate

Sharing the left column saves real time. Sharing anything in the right column slowly turns your portfolio into one blurry brand with several names. The line is simple to state and easy to cross on a busy day, which is why the habits below matter.

A quick way to test separation: shrink one recent post from each brand to the size of a grid thumbnail and put them side by side. If you can't tell which is which without reading, the surfaces are too close. The background is usually the fastest fix, because it fills most of every frame and changes how every colour around it reads. Distinctive brand assets explains why that matters for recognition.

Operating several brands with one team

1. 1

   One kit per brand

   Colours, fonts, logos, voice and signature look, each in its own place. Nobody should copy a colour from memory.

2. 2

   One owner per brand

   Even in a small team, one person is responsible for each brand looking right and has the final say on it.

3. 3

   Brand name first in every file

   For example nighttide-2026-10-wine-list-story. It sounds trivial and prevents most wrong file uploads.

4. 4

   One calendar, colour coded

   All brands on a single content calendar, so launches don't collide and nothing goes quiet.

5. 5

   Switch deliberately

   Finish one brand's batch before starting the next. Working on two at once is how colours migrate.

6. 6

   Check before publishing

   A two second test: right logo, right handle, right colours. Make it a habit, not a review meeting.

Roles, approvals and outside help

As soon as more than one person touches a brand, decide who can change what. A useful pattern: the brand owner can edit the kit, designers can make and edit designs, and anyone outside the team, a client or a partner, can view and comment but not publish. Brand asset management covers file organisation in more depth, and agency client branding looks at the same problem from an agency's side.

When to merge or retire a brand

Review the portfolio once a year. If two brands now serve the same audience with the same promise, merge them. If a brand gets little attention from the team and little response from customers, retire it gracefully: tell its followers where to go, point its profiles to the surviving brand and archive its kit. Fewer, better fed brands nearly always outperform a long list of neglected ones.

Running multiple brands in Gradiently

Gradiently is set up for this way of working. One account can run several brands, each with its own brand kit of logos, palettes, fonts, voice, audience and what the brand does, so switching brand switches everything the Designer uses. On Pro, team workspaces add owner, admin, editor and viewer roles and comments on designs. Giving each brand its own Mark means their surfaces stay distinct, and once claimed, nobody outside can export with them. Brands in Gradiently walks through the setup, and workspace roles explains each permission.