I Built Three Brand Portals Through a Rebrand and an Acquisition — Here's the Playbook
In seven years at one company, I've lived through three brand transitions: a proactive cleanup of our original identity, a full rebrand, and an acquisition that split the business into two new brands. Each time, the thing that kept the chaos contained was the same system — a dedicated brand portal acting as the single source of truth for every asset, template, and usage rule. This is how I built it, why Google Drive and shared folders always fail at this job, and the playbook I'd hand anyone facing a rebrand.
TL;DR
- Shared drives and link hubs always fail as brand asset systems — they're storage, not governance. People get lost, links rot, and old templates leak into client-facing work.
- The playbook: structure assets into logical categories → build a sitemap → collect everything → write how-to guides → then choose the platform. Tooling last, architecture first.
- Launch the portal the same day you unveil the brand. It converts launch-day excitement into adoption, and the new brand never has a "where do I find this?" phase.
Why does brand inconsistency cost more than it looks?
Internally, a rebrand generates a hundred small questions: Where's the latest logo? Is my email signature still okay? Which deck template is current? Each question seems trivial. At scale, they compound into outdated templates in client reports, old logos in live social posts, and a brand that looks unsure of itself at exactly the moment it's claiming a new direction.
Externally, that's expensive. Inconsistency reads as carelessness, and carelessness erodes trust — with clients, partners, and the new stakeholders a rebrand is meant to win over. The brands that hold enduring value hold it through discipline: the same marks, the same colors, the same voice, everywhere, for years. A rebrand only works if the new identity is adopted with that same discipline from day one. That's an operations problem, not a design problem.
Why don't Google Drive, OneDrive, or Linktree work as brand hubs?
We tried all of them. They failed for the same root reason: they're storage tools, not brand governance tools. Folders nest into rabbit holes. Links get buried in old emails. There's no way to attach usage guidance to an asset, no way to retire an outdated file without breaking someone's bookmark, and no signal telling a non-designer "this is the current, approved version."
A brand portal is a different category of tool. It pairs every asset with its rules — when to use which logo lockup, how the color system works, where the templates live — and it gives the whole organization, including outsourced agencies, one URL to remember. We built ours on Frontify, but the platform was deliberately the last decision we made.
What's the playbook for building a brand portal that people actually use?
The sequence matters more than the software:
- Audit and categorize. Collect every brand element — logos, type, color, templates, photography, motion — and structure it into logical categories before touching any platform.
- Design the sitemap. Treat the portal like a product. Map how a salesperson, a designer, and an external agency would each navigate to what they need.
- Write the how-to guides. Assets without guidance just recreate the old chaos in a prettier interface. Every section got clear "how to use this" documentation.
- Then choose the platform. Only with the architecture defined could we evaluate tools honestly. Frontify won because it was built for exactly this job.
- Launch with the brand, not after it. We unveiled the portal the same day we unveiled the new RISE identity. Workshops and creative onboarding followed, so the portal became the default habit, not an afterthought.
How did the system survive an acquisition?
The real test came in 2025, when Elevate acquired RISE Group. The sports, culture and entertainment business was folded into Elevate's global brand, while the public-private advisory practice launched independently as Apex Advisory — meaning one company became two brands, fast, with assets and teams in motion.
Because the portal playbook already existed, standing up a complete brand portal for Apex was a repeat of a known process, not a scramble. Same sequence: categorize, sitemap, guides, Frontify, launch. That's the point of building systems instead of one-off projects — the third time costs a fraction of the first, and the brand never has an undefined period where nobody knows which assets are real.
A brand portal isn't a nice-to-have for design teams. It's infrastructure for moments of change — and every brand eventually has one.
