Writing · MARGIN NOTESFor founders
What a design system costs, and when it pays back
A design system pays for itself when a second surface has to feel like the first. Until then it is a folder of components.
- Author
- Nicola Riker Urdaneta
- Published
- October 10, 2026
- Reading time
- 1 min read
Contents
It is not a Figma file
A design system is the set of parts two or more products actually ship. Tokens, components, and the rules for when not to invent a new one. A library that only the design file knows about is a reference, not a system.
Where the cost actually sits
The first build is the obvious invoice: naming, the components people touch every day, and documentation that matches the code. The quieter cost is the one you already pay, every time a team draws a button that almost matches the last one. That tax shows up as review time, bugs at the edges, and a product that feels like several products.
When it pays back
It pays back on the second surface. A marketing site and an app. Cloud and the open-source twin. A dashboard and the admin tool beside it. If you only have one screen and no plan for another, a system is premature. If a second team is about to copy the first by eye, it is late.
The current bands for this kind of work live on Riker Web, not on this site. If you are deciding whether the second surface is real enough to justify the system, that is a scoping conversation, not a component count.