Design systems for lean startups — what you actually need

Most startups don't need a 400-component design system. They need consistency they can actually maintain. Building Google's Material Design when you're five people is a way to feel productive while shipping nothing.

Here's what a lean team actually needs.

Start with tokens, not components

Colours, typography, spacing, radius. Define these once as variables and 80% of your visual consistency is solved — no component library required. This is the layer that hurts most when it's inconsistent and costs least to fix.

Build components when you've repeated yourself three times

Don't design a component in the abstract. When you've hand-built the same card or button for the third time, then extract it. Premature abstraction is as expensive as no abstraction.

Document decisions, not just parts

The valuable part of a system isn't the button — it's when to use which button. A one-line rule ("one primary action per screen, never two") saves more time than a perfectly spec'd component.

A design system is a shared language, not a warehouse of parts. If your team can't apply it without asking, it's not done.

Add structure when the pain of not having it is real — not before. Need a system your team can actually run? That's what we build.