Design tokens: why agencies haven't moved to them yet

Design tokens aren't just CSS variables. They're a contract between designer and developer. But 70% of agencies we talked to in 2026 don't use them systematically. Why?

The usual excuses

1. "Our projects are small — tokens are overkill" 2. "Designer's slammed, we ship as fast as we can" 3. "We align colors in Figma anyway"

All three — from misunderstanding what tokens really are.

What a token really is

Token = semantic name + value + context.

Not `#ffd426` — but `--color-accent` with context "brand primary, used for CTAs and highlights".

Not `16px` — but `--space-4` with context "small gap inside cards".

What it gives you

- Change a bg color across the site = change 1 token - Light/dark theme = 2 token sets, components don't know the theme - Rebrand in a week instead of 3 months - Designer doesn't have to color every new component — the token picks itself

How we implemented

1. Figma Variables → JSON → Tailwind config (automated) 2. 6 semantic categories: bg / fg / accent / line / state / typography 3. Tokens are prefixed so they don't get confused with raw values

A real-world example

LKW Walter decided to rebrand mid-development. Instead of 3 weeks of rework — 2 days to update tokens + regression tests. The client was shocked. We weren't.

Bottom line

Tokens are a small investment that pays off the first time you rebrand. If you're an agency shipping products longer than 3 months — tokens are mandatory.