Case study · Brand system

Building the
Branding Center

A business’s brand used to live in a document outside the product, so changing a logo meant redoing every email and landing page by hand. I designed one place to keep the brand, and everything else reads from it. It covers four parts of the product and sixteen teams. Landing page builder adoption rose 20% after it shipped.

Watch the tourPrototype (demo data)

CompanyKeap
RoleLead designer · research & IA owner
Team2 designers · 1 PM · 1 tech manager · 2 development teams
Scope4 surfaces · 16 dependent teams
Timeframe2024
FocusResearch · IA · Systems

Prototype (demo data)

TL;DR

A business’s brand lived in a document outside the product, so a new logo meant partners redoing every email and landing page by hand. I designed one brand definition that every builder references instead of copying, and pushed for the slower build that lets sharing expand later. Colors, logos, custom fonts and shared content support shipped, and 16 teams build on it. Landing page builder adoption rose 20%, and a landing page went from 25 to 15 minutes to build.

At a glance
16
Teams still build on it today
25→15
Minutes to build a landing page, and 15→10 for an email
+20%
Landing page builder adoption after it shipped
3:1
Logos uploaded for every color, the reverse of what discovery predicted

Build times (landing page 25→15 min, email 15→10 min) were measured in timed, moderated usability tests with 13 participants. The +20% landing page builder adoption is from product analytics, comparing 90 days before and after launch.

01 · The problem

Changing a logo took hours, sometimes weeks

Partners build campaigns for their clients: fifteen or more emails and landing pages in a single campaign. When a client sent a new logo or changed a button color, the partner opened every asset in every automation and redid it by hand.

No way to apply a brand

There was no good way to apply a brand to emails and landing pages, so old assets and the wrong logos kept going out.

Hours to weeks, per client

Partners told us the workaround took anywhere from a few hours to a few weeks for a single client app. Reported in 13 partner interviews, not measured.

Shared content arrived unbranded

Campaigns shared into a client’s own app showed up with none of that client’s branding.

The partner workflow before the Branding Center, in three stages. Create campaign: build 15 or more emails and landing pages for a client, once. Customize per client: open every asset in every automation and apply the brand by hand, hours to weeks per client. Client rebrands: open every asset again and redo it, hours to weeks every time.
The partner workflow before the Branding Center. Brand work happened once per asset, then again on every rebrand. The highlighted steps are where the time went.
02 · My role

What I owned

I owned the research and the information architecture, and carried the design across four teams and a builder we don’t own. A junior designer worked on it with me and then took it over.

01

Ran the research

Thirteen one to one sessions of 45 minutes with partners, onboarding coaches and end users. After that, a competitor audit of five platforms and a concept test before anything got built.

02

Set the rules

Where brand assets live, what a “primary” logo means, and how one definition reaches every surface that renders it.

03

Worked across sixteen teams

I pitched connecting a new landing page builder to the Branding Center. My two teams built it, and sixteen teams build on it with our support. My job was keeping one brand definition working for all of them without owning any of them.

04

Ran the cross team workshop

I ran a workshop with the PM, tech leads, engineers and the content sharing team: current state, future vision, then two rounds of sketching on the same board.

Before: brand guidelines kept outside the product, applied by hand to 15 or more assets one at a time, so logos drifted and outdated assets went out. After: one brand definition, referenced and never copied, read by the email builder, landing page builder, popup builder and shared content.
Before and after. A document nobody in the product could see, replaced by one brand definition that every surface reads.
03 · The rules

Three rules every surface follows

It looked like a settings page, but the hard part was getting one brand to show up correctly everywhere. So I wrote down three rules that had to hold on every surface, no matter who built it.

Reference, never copy

Surfaces point to the brand asset instead of keeping their own copy, so one change updates it everywhere.

Exactly one primary

One logo is marked primary. That’s the one that goes along when content is shared into someone else’s app.

Degrade to a placeholder

If an asset is missing, the surface shows a placeholder, never another business’s brand.

One brand definitionreferenced, never copied Email builderLanding page builderPopup builderShared content → other apps Third party vendor
In the interactive prototype, a new primary logo appears in the Branding Center card, then lines carry it to four surfaces: the landing page builder and the email builder, both marked third party, the popup builder and shared content, each ticking up to its count with a check
Prototype (demo data) Reference, never copy, in the interactive prototype. Change the primary logo and every surface that uses it updates, including the two builders made by a third party. Demo data.
Three landing page builder screens side by side, each with a Branding panel open: logos with one badged Primary, brand colors as hex swatches, and the brand font list
Shipped The brand shows up right inside the builder, so nobody has to go back to settings. Logos, colors and fonts are picked from the brand instead of uploaded again for each page.
A landing page builder in the interactive prototype with the Logos panel open: Manage logos above the brand logos, one badged Primary and selected, and the page logo following it
Prototype (demo data) The same rule in a third party builder, in the interactive prototype. The logo block follows the primary logo, and More logos lists the rest of the brand’s logos.

I also designed for what accounts would look like on day one: accounts with no logo, and accounts where the existing profile logo didn’t match the new one. That second case is the one that turns into support tickets.

Thryv AI review card in the interactive prototype: it found 4 logos, 6 colors and 2 fonts on a website, and asks whether the website logo or the business profile logo should be primary
Concept In the interactive prototype. When the logo Thryv AI finds on the website doesn’t match the profile logo, it asks the owner which one should be primary instead of picking for them.
04 · Key decisions

Why I pushed for the slower build

Engineering proposed universal keys with a dependency mapping table instead of raw IDs. It was the slower build, and I pushed for it anyway, because I could show that sharing would need to expand later and raw IDs would have ruled that out. I won that argument on design grounds.

Marketing or Settings?
In testing, people looked under Marketing first but found it in Settings without much trouble. I chose Settings. It’s a little harder to find, but there’s only one place the brand lives.
One surface or three tabs?
Splitting Branding from a Style Guide confused people about where logos, colors and fonts lived. I tested the two structures against each other. I went with one place, because people could guess where things were.
Custom fonts in email?
Most email clients don’t show them at all. I said no and locked the option in the email builder, with a note explaining why, instead of letting people pick a font that would never show up.
How many assets?
Every extra asset is one more thing every surface has to handle. I set a cap on purpose, with a banner that warns people before they reach it.
The Settings page in the interactive prototype, listing My profile, My account, Business profile, then Branding Center with a Set up with AI tag, Users, Text message verification, Sales settings and Integrations
Prototype (demo data) The Branding Center lives in Settings, in the interactive prototype on demo data. The Set up with AI tag is a concept.
An email builder in the interactive prototype: the brand fonts are listed but locked with Not in email, above a note that most email clients cannot show custom fonts, so the email uses Georgia and Arial
Prototype (demo data) Locked fonts in the email builder, in the interactive prototype. Brand fonts stay listed, with the reason they’re off and the fallback fonts every inbox can show.
The Branding Center in the interactive prototype at its logo cap: Logos 8 of 8, a warning that reads You have 8 logos, the most a brand can hold. Delete one to add another, a grid of eight Harbor Bloom logos with one marked Primary, and Colors at 6 of 18
Prototype (demo data) The asset cap in the interactive prototype, on demo data. At 8 logos, the upload tile goes away and a warning says how to make room.
05 · Outcome

What shipped, and what the usage data showed

Discovery ranked colors first and logos second. Usage in the first 180 days was three logos for every color
Logos and colors uploaded in the first 180 days, next to the order discovery predicted.
ShippedColors and logos, reusable across emails and landing pages. I had every account’s existing logo added as its primary, so nobody started with an empty page.
ShippedShared content support. When content is installed in another app, it picks up that app’s primary logo, or a placeholder if there isn’t one.
ShippedCustom fonts, rolled out in stages. Uploads are scanned for malware, and a quarantined font switches to the fallback on its own.
UnfundedMore was scoped but didn’t get funded. What shipped is what the usage data could justify.

Adoption of the landing page builder rose 20% once brand assets became reusable inside it (product analytics, 90 days before and after launch). Sixteen teams still build on the Branding Center today.

Discovery told me colors mattered most and logos second. Six months after launch, people had uploaded three logos for every color. I took that into my next project: get the baseline numbers before drawing anything.

Concept in the interactive prototype: Thryv AI reads a website while logos, brand colors and fonts appear on the Branding tab one by one, with a progress panel ticking off each step
Concept In the interactive prototype. Thryv AI reads a business website and fills in the Branding Center with the logos, colors and fonts it finds, so no account starts empty.
Concept in the interactive prototype: Thryv AI sets up the style guide from a website while the Style Preview changes its colors, then its fonts, then its buttons
Concept The same setup started from the Style guide, where the preview changes as Thryv AI drafts colors, type and buttons from the website.

Let’s talk