Findable from outside design
b/brand is the same shortcut for designers, PMs, marketers, and engineers. Stop pinning the Figma URL in five Slack channels.
Use case · Design systems & brand
A brand system
the whole company can find.
A brand system that lives across Figma, Notion, a dribbble link, and four Slack pins is not a system. b/brand puts the typography spec, the colour tokens, the live components, and the do/don’t guides on one canvas — current, governed, and accessible to every team.
The shape of the work
Three steps to a brand that travels.
Most brand systems fail to scale because nobody outside design knows where to find them. Fix the find problem first; the consistency problem fixes itself.
- 1
Give the system a slug
b/brand. Every PM, marketer, and engineer types the same shortcut. The Figma file, the colour tokens, the typography spec — all on one board.
- 2
Live components, not screenshots
Embed Figma frames live. When design ships an update, every team sees it without anyone re-pasting screenshots.
- 3
Audit the rest of the site
Drop a sitemap-audit node into the board. Crawl your marketing site, get a per-page accessibility and SEO score, and assign fixes as tasks on the same canvas.
Brand system board template
b/brand — eight blocks for the whole org.
Designed to be useful to non-designers. The PM looking up a button colour, the marketer checking line height, the engineer needing a token — all land here.
b/brand
8 nodes- Live Figma cover
Embedded Figma frame: the brand system overview. Updates flow through automatically.
- Colour tokens
Table node: name, hex, OKLCH, usage rule. Copyable cells. The single source of truth.
- Typography spec
Type scale, line heights, font weights. Live preview, not a screenshot of a Figma page.
- Do / don’t panel
Side-by-side correct vs incorrect usage. Notes pin to the artwork they reference.
- Asset library
Logos, illustrations, photography. Each tile is a slug — b/logo-primary, b/photo-hero — for cross-team reuse.
- Site audit
Sitemap-audit node: crawl your site, score every page on accessibility and SEO. Track fixes as tasks on the board.
- Decision log
Why we picked the type, why the spacing scale, why this many tones. Future designers thank you.
- Versioning timeline
A timeline node tracking releases (v1.4, v2.0). Each version pinned to its frame snapshot for reference.
Why this works
Six things a Figma file alone cannot do.
Live components, automatic updates
Embedded Figma frames stay current. Update the source; every team sees the new spec without a re-share dance.
Site audits on the same board
Drop a sitemap-audit node, crawl the live site, find pages drifting from the brand. Score accessibility + SEO at the same time.
Searchable everything
Tokens, components, decisions — searchable by name and by usage rule. Workspace search hits the brand board first.
A decision log future designers thank you for
Why this scale, why this palette, why this contrast ratio. Notes pinned to the relevant section, not buried in a Notion subspace.
External brand handoff in one URL
Agency partner needs the brand? Send b/brand as a guest link. Free guest seats; read-only by default.
We replaced a Figma project, a Notion subspace, and a Slack channel with one b/brand board. Reviews actually finish now.
MC
Mei-Lin Cordova
Head of Design · Aperture Foundry
Frequently asked
Questions, answered.
No — Figma stays the source of truth for components and tokens. The board is the discovery layer for everyone who is not a designer: PMs, marketers, engineers, agency partners. Most teams pin the Figma URL as a slug (b/figma-brand) and live-embed key frames on the board.
A sitemap-audit node takes a starting URL, crawls the site to a configurable depth, and scores every page on accessibility (axe-core) and SEO (technical + on-page). Findings appear as a table you can filter; each row can be turned into a task on the same board.
Yes. Per-board permissions support read-only for the company at large, comment-only for stakeholders, and edit access for the design team. The audit log records every change.
Most teams use one parent board (b/brand) with sub-boards per product (b/brand-web, b/brand-mobile, b/brand-marketing) all linked from the parent. Tokens stay shared at the top level; product-specific decisions live one click down.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial