Most marketing teams keep their brand palette in three places: Figma, the codebase, and a Notion doc. Decks and presentations get whatever the slide template defaults to. The result is six weeks of off-brand pitch decks.
The fix is mechanical. The export panel here gives you four formats — CSS variables, Tailwind, SCSS, Figma Tokens. Paste the hex codes one more time into your slide tools.
Notion. Notion accepts hex codes for callouts, dividers, and database tags via custom CSS only on enterprise plans, but the workspace cover image and emoji shortcuts can carry the brand. Make a one-pager that lists the five hex codes, the URL of the palette, and a contact for changes. Pin it in the team space.
Google Slides and Keynote. Both accept custom theme colors. In Slides, Theme → Theme colors → Custom; paste hex codes for primary, secondary, accent, light, dark into the corresponding slots. In Keynote, the Format Inspector lets you save a custom palette to the user library. Save it once; every new deck inherits it.
Linear. Project icons accept color emojis but not custom hex. Use the brand palette to pick which built-in colors to assign to which project type — primary for product work, accent for marketing, secondary for ops.
Figma. Skip the manual swatch frame. Import the Figma Tokens JSON via the Tokens Studio plugin (free), and your colors flow in as proper variables tied to light and dark themes. Components built with these variables auto-update when you tweak the palette.
For email signatures and social headers, treat the brand palette as a strict constraint, not a starting point. The full primary on white. The accent on dark. The secondary nowhere — it muddies headshots and social cards. Save two PNG templates and reuse forever.
This whole pipeline takes 90 minutes the first time and 10 minutes for every subsequent palette change. The point is not perfection; the point is that everyone in the company is shipping decks, emails, and social posts in the same five colors.