A solo-operator brand was drifting. Two token systems, an uninvited typeface, nine unresolved palette boards, and three site drafts on three palettes. We didn’t pick a look — we audited the evidence and let the repo tell us what it already was.
The starting state was entropy. The studio ran two parallel token systems — a grey “Cyberspace” palette in tokens.css and a navy “Rays” palette in tokens-studio.css — with no rule for which won.
Syne had crept in uninvited across pages that were never meant to carry it. Nine palette-exploration boards sat unresolved, none promoted, colors scattered and duplicated across docs. And the site existed as three different drafts — v3.0 (dark, text-led), v33 (light, image-grid), and an mvp — each built on a different palette.
A brand that can’t answer “what color are we?” can’t answer the harder question underneath it: who are we?
The pivot was structural before it was visual. The brand had to express a two-sibling entity model — MFA Group ↔ JMH Studio, owned directly, no holdco — split by capital intensity. Studio is IP, creative, and capital-light; MFA is asset-owning and capital-intensive. The positioning that falls out of that: “we brand it AND build it.”
So the method couldn’t be a mood board. We ran three parallel audits — every color, every font, every type value across the whole tree — and let the evidence decide. The canonical answer turned out to be the one the repo already half-implied: SW-paint-derived greys tied to the physical studio, and the v1.1 accent legibility-lift that had already been made and never formalized.
The audits surfaced the key insight: the two siblings aren’t two brands — they’re two expressions of one DNA. Studio steel #6b9fd4 and MFA Columbia #2f6db0 are the same blue family. Only the ground changes — grey for Studio, navy for MFA.
Consistency signals “same hand.” That’s the trust mechanic for a sibling ↔ sibling structure. Creative flex doesn’t disappear — it just lives at the venture brand layer, not at the sibling level. The entity layer stays disciplined so the ventures can be loud.
Same blue family, different ground. The MFA ground/accent above are shown as documentary evidence of the sibling’s palette — this page itself renders entirely on the Studio theme.
The insight became architecture. One token base — the shared :root primitives (fonts, type scale, spacing, radius) — plus two themes that override color only: [data-brand="studio"] (grey) and [data-brand="mfa"] (navy).
Type was locked: Cormorant Garamond + DM Mono. Syne was dropped and the sunburst demoted — both evidence-driven, not preference. A page that imports the system with no data-brand renders Studio by default, preserving every existing surface.
The brand is now canonical and locked, and it has been applied to its first real surface — the surface you are reading, and the Active Dashboard pilot before it. The legacy drift is reconciled: exploration superseded, accent drift fixed, and the two token files collapsed to a single base + themes.
This is the differentiator versus taste-driven agencies. We don’t hand you a mood board — we audit what exists, decide from evidence, architect a token system, and apply it to a real surface. The output isn’t a logo; it’s a system you can extend without us.
This case study is itself a Studio deliverable — the method, made visible. The page you are reading is the brand system applied to its own story.