Why a design system beats one-off pages
Designing page by page feels faster at the start and costs more every month after. Here is how a small system pays for itself.
Founder & Creative Director
Key takeaways
- A system is a decision made once and reused, not a style guide nobody reads.
- Consistency is cheaper to maintain than inconsistency is to fix.
- Start with type, spacing and colour — the parts every page touches.
The hidden cost of one-off pages
Every page designed in isolation re-decides the same things: heading sizes, spacing rhythm, button weights, image treatment. Those decisions are small individually. Across twenty pages they add up to a site that looks like it was assembled rather than designed.
The cost shows up later. A new page takes a designer three times longer than it should, because there is nothing to inherit from.
What a system actually contains
A useful system is small. It defines a type scale, a spacing scale, a colour set with clear roles, and a handful of components — buttons, cards, form fields, sections.
Everything else is composition. Once those primitives exist, new pages become assembly rather than invention.
- A type scale with named steps, not arbitrary sizes
- A spacing scale that every margin and padding uses
- Colour tokens with roles (surface, text, border, accent)
- A small component set, documented where the team works
Start smaller than you think
The common failure is trying to build the whole system before shipping anything. Define the scale, use it on one real page, then extract the components once you can see the repetition.
Systems should be discovered from real work, not designed in the abstract.
The Dawnwire Agency Deck
A look at how we work: the process, the services, and the design and motion work behind them.