Why a design system pays for itself by the third campaign

The cost you are already paying

Without a system, every campaign restarts. A designer picks colours from memory, a developer rebuilds a button, and six months later you have four button styles, three greys called "brand grey" and a brand that looks slightly different on every page. That inconsistency is a real cost — in hours and in trust.

What a design system actually is

Three layers. Tokens: the colours, type scale, spacing, radii and shadows, named semantically so intent survives. Components: the buttons, inputs, cards and navigation built once and reused. Rules: written guidance on when to use what, including the things not to do.

It is not a Figma file with some swatches. It is a shared vocabulary that design and engineering both reference.

The maths

A landing page from scratch takes us roughly forty hours of design and build. The same page assembled from an established system takes twelve to fifteen. By the third campaign the system has paid for itself, and every campaign after that is pure margin — with fewer QA rounds because the components are already tested across breakpoints.

Where teams go wrong

Documenting too much too early, before patterns have stabilised. Building components nobody requested. And treating the system as finished — it needs an owner and a changelog, or it drifts back into inconsistency within a year.

Getting started

Audit what exists, consolidate to one scale per concern, name tokens by role rather than appearance, then build the ten components that cover eighty percent of your pages. See WordPress versus headless for how the system meets your platform, and landing page anatomy for what to build first.