A design system costs whatever it takes to make the decisions your team keeps re-making, once, and then keep them up to date. For a small product that can be a few weeks of work. For an organisation with several products, several brands and several platforms, it’s a permanent team. The useful question isn’t “how much?” but “how much of it do we need yet?”

What you’re actually paying for

Most of the cost isn’t drawing buttons. It’s deciding things and writing them down.

  • Tokens: agreeing the colours, type sizes, spacing and other small decisions, naming them, and wiring them into code and Figma. Quick to start, slow to get right, because naming is where teams argue.
  • Components: building each one properly, with every state (hover, focus, disabled, error, loading), in code and in Figma, and keeping the two in step.
  • Accessibility: contrast in every theme, keyboard behaviour, screen reader labels. Done once in the component, it’s done everywhere it’s used. Done later, it’s done on every screen.
  • Documentation: what each part is for, when not to use it, and examples. This is the bit teams skip, and the bit that makes a system usable by anyone who didn’t build it.
  • Looking after it: someone has to review new requests, fix bugs and publish changes. A system nobody owns goes stale within a year.

If you’re not sure what each of those words means, our plain-English dictionary covers them.

What drives the price up or down

Cost driver Cheaper Dearer
Number of products using it One Several, built by different teams
Brands and themes One brand, light mode Several brands, light and dark
Platforms Web only Web, iOS and Android
Starting point A tidy product with some consistency Years of one-off screens to untangle
Documentation A short guide for one team A public or company-wide site
Who maintains it Part of an existing role A dedicated team

The biggest single factor is usually the starting point. Building a system for a new product is mostly design. Building one for a five-year-old product is mostly archaeology: finding the 14 slightly different blues and agreeing which one survives.

How it pays back

The return comes from three places.

Speed. Figma ran a study where designers with a design system completed a task 34% faster than without one. Developers see a similar effect: a new screen built from existing components is mostly assembly.

Fewer bugs and less rework. When the button, the form field and the error message are built once and tested once, a fix lands everywhere. Without a system, the same accessibility bug gets fixed screen by screen, and comes back on the next one.

Changes that used to be projects become edits. A rebrand, a dark mode or a second brand is a change to tokens, not a redesign of every screen. We show this on our own system, Somnia DS: switch the brand at the top of any page and every component follows. You can even make your own theme in a minute.

A rough way to check the sums: count how many designers and developers touch your interface, estimate how many hours a week each spends recreating or fixing things that already exist somewhere, and multiply. If that number is small, you don’t need a system yet. If it’s a person or more, you’re already paying for not having one.

When it isn’t worth it yet

  • You haven’t found product–market fit and the interface may change completely next quarter.
  • One designer and one developer are building one product and talk every day.
  • Nobody will own it after it’s built.

In those cases, start smaller: a handful of tokens and the five or six components you use most, in code. That’s cheap, it’s useful straight away, and it grows into a full system when you need one. We wrote more about the timing in do you need a design system yet?

How we price it

We scope a design system the way we scope any project: start with what’s costing you time now, build the smallest system that fixes it, and add to it as the product grows. That might be a fixed-scope piece of work for the foundations and core components, then ongoing support to look after it. We can also build, host and maintain the documentation site, as we do for Somnia DS.

Wondering what a design system would cost for your product, or whether you need one at all? Get in touch and we’ll give you an honest answer.

See a design system working

Somnia DS is the design system this website runs on, published in full: tokens, components, patterns, accessibility and governance. We build systems like it for clients, prototype on it, and host and look after the documentation for you.

Same components, different brand:

← Back to all insights