Brief is a creative brief manager that adopts each client's brand environment — so writing a brief feels like working inside the client, not inside another SaaS dashboard.
A freelance designer spends Tuesday morning inside a fintech client's brand world — cold navy, sharp serif. By lunch they're inside an indie soap brand's — warm peach, editorial type.
FRICTION → THE META-TOOLS DON'T COME ALONG.They'll spend hours inside those brands in Figma. But the moment they open their brief manager, file tracker, or project notes, it's all the same gray SaaS chrome. The tool that should help them stay grounded in each client's context strips the context away the second they switch surfaces.
Brief is the bet that the tool itself can be the context cue. Each client gets a full brand environment inside Brief — colors, type, corner radius, even mood. Switch clients and the entire surface re-themes in 420 ms.
The chrome — workspace home, sidebar, command palette — stays a neutral dark Drafting Table. Client-themed surfaces sit on it like prints pinned to a gallery wall.
CHROME = NEUTRAL. CLIENT SURFACES = THEMED. THE CONTRAST IS THE POINT.They live in brand-shaped containers. Every Figma file is in somebody's world — that client's typeface, that client's palette, that client's tone of voice.
Their work is essentially a long sequence of mental check-ins: "which brand am I in right now?" Figma confirms it. The brand book confirms it. The Slack channel sort of confirms it. Their brief manager, file tracker, and project notes confirm nothing.
That mismatch is friction. It also flattens what should be a felt distinction between "I'm in Acme mode" and "I'm in Sundial mode." Two clients, two completely different visual and verbal vocabularies, one identical workspace — pretending they're the same.
THE PRODUCT MUST FEEL LIKE A DIFFERENT ROOM PER CLIENT.When I open the app on a Tuesday morning, I want the surface itself to tell me which client I'm in.
Goals, audience, references, deliverables, timeline — without juggling four apps.
Drop a logo or brand PDF and have a defensible starting environment without picking ten tokens.
Three clients, one afternoon. The transition should feel like walking into a different studio, not opening a different tab.
Notion, Asana, Linear, Bonsai. All competent. All polished. All identical the moment you set them next to each other and squint.
A neutral chrome, a faint accent picker, an avatar in the corner. The same surface no matter who you're working for. The brand of the SaaS is the only brand in the room.
This is fine for project work that has no client — internal teams, personal docs, public communities. It is actively wrong for client services work, where the entire job is holding a brand in your head and producing for it.
SAMENESS IS A FEATURE FOR ENTERPRISE. A BUG FOR FREELANCERS.If the surface itself confirms which client you're working in, the cognitive shift happens at the level of the room you're sitting in — not inside your head.
This re-frames theming from decoration to information architecture. The look of the page is no longer a finishing layer applied at the end; it is one of the primary signals the product transmits. It tells you, before you read a word, who this surface belongs to.
THEMING AS WAYFINDING. THEMING AS MEMORY AID."Switch a client. Watch the entire surface re-theme in 420 milliseconds — colors, type, corner radius, even the focus ring."
ease-out-quintBrief is not a maximalist. The product's own personality is restrained on purpose — because almost every surface a user spends real time on is wearing somebody else's brand.
When the chrome is loud, the client themes have nowhere to live. When the chrome whispers, the client themes get to speak.
Voice is plain and confident. Short sentences. Specific nouns. No emoji. Editorial without being precious. Like the most trusted designer in a studio — the one who doesn't oversell.
"DRAFTING TABLE" IS BOTH A PALETTE AND A POSTURE.The Drafting Table palette is intentionally a hair warmer than pure neutral — enough that any client theme, warm or cool, lands on it without fighting. Type pairs an editorial serif (used sparingly, for headlines and moments) with a humanist sans for body and UI, and a monospace for labels, metadata, and code-adjacent material.
All in oklch · warm 60–80° hue · chroma capped at 0.012 so the chrome never competes with a client theme.
Chrome uses 6px by default. Client themes override to whatever fits their brand — Dandy 3px, Sundial 16px, Halo 0px.
Two-stage. Colors first (CSS transition, 420 ms ease-out-quint); content cross-fades (Motion, 220 ms) starting at 200 ms. The user reads the shift as a single, deliberate gesture.
Never spring. Never elastic. The wow is in the choreography, not the springiness.
A token system is only worth designing if there's a design idea that demands it. Per-client theming is that idea.
Each layer narrows from the abstract to the consumed. Primitives are raw values; chrome semantics name the neutral surface; client semantics override those names per client; components consume the names — never the raw values.
A single attribute on a single root — [data-client-theme="dandy"] — flips Layer 3. Every component below it animates over 420 ms via a transition declared once.
Read top to bottom. Each layer references only the layer above. Components never reach past Layer 4 into raw primitives — the rule that makes the whole thing re-theme cleanly.
Switching a client only rewrites Layer 3. Layers 1, 2, and 4 are stable.
oklch(0.42 0.13 248) · 16px · 420ms--bg · --fg · --rule · the Drafting Table--client-accent · --client-radius · --client-display · scoped by [data-client-theme]--btn-bg: var(--client-accent) · components consume Layer 3, never Layer 1Surfaces split cleanly into chrome (no client; you're in Brief itself) and themed (in a client's world). Every screen is one or the other — never a hybrid. The contrast between the two is the whole experience.
The cost of an empty client should be one decision, not ten. New clients pick whichever path they have material for; every path lands on the same editable token sheet, so a user can drop a logo, accept a starter, and still tweak the radius before saving.
Upload a logo, brand PDF, or screenshot. Brief extracts a starter palette and suggests a type pairing. Editable from there.
For: brands with existing material.Curated theme presets — Apothecary, Editorial, Console, Studio Default, others. Each is a complete, opinionated set of tokens.
For: new brands, side projects, prototyping.Open the token sheet and set every variable directly — color, type, radius, density, motion. Every other path lands here eventually.
For: brand owners; designers who know what they want.Below: the brief detail screen rendered three times, no per-client component swap. Every difference here is a token override on a single CSS scope. The exercise is to make the three feel like three different studios.
Anchor the new label in apothecary tradition while staying legible at retail scale. Carry the new wordmark across packaging, web, and a printed care card.
Build the launch story around a 16-page editorial mini-zine; carry the same warmth and pacing across the site, the launch email, and three Instagram tiles.
cover the lp-04 release across a 12" sleeve, a one-page site, and a lyric pdf. one visual system, three formats. monospace everywhere.