Design systems for startups who don't have time

At some point a founder reads about Material or Polaris, panics, and asks their designer to “build a design system.” Three months later there's a Figma file with 400 components and no shipped UI. This is the trap.

The twelve-component paved road

For the first year of a product, you need exactly twelve components. Get them right, use them everywhere, and 90% of your UI consistency problem is solved:

1. 1Button (primary / secondary / ghost)
2. 2Input (text, email, password, textarea)
3. 3Select / combobox
4. 4Checkbox and radio
5. 5Card
6. 6Modal / dialog
7. 7Toast / banner
8. 8Table / list row
9. 9Tabs
10. 10Avatar
11. 11Badge / status chip
12. 12Empty state

Everything else is a composition of these twelve. If someone on the team is about to build a thirteenth, they should have to write a 200-word justification.

Tokens before components

Start with design tokens — color, spacing, radius, typography scale — and get them into Tailwind (or CSS variables) before you draw a single component. When tokens change, the whole system changes for free. When components are baked with hex values, every change is a manual sweep.

• 8-step neutral scale, 6-step brand scale, 2–3 semantic accents.
• 4px spacing scale. 4 / 8 / 12 / 16 / 24 / 32 / 48. That's it.
• Three font sizes for body, three for display. Four weights total.
• One border radius, maybe two. Rounded and pill.

Accessibility as a floor

Set an a11y floor on the twelve components and never go below it. Focus rings visible. 4.5:1 contrast on text. Keyboard nav works everywhere. Build it in once, enforce it with a Storybook audit, and stop having the conversation for every new screen.

When to graduate

You know you've outgrown the paved road when three things happen at once:

1. 1You have more than five engineers writing UI regularly.
2. 2You have more than one surface (web + mobile web, web + native, etc.).
3. 3You have a dedicated product designer.

At that point, and not before, invest in a proper component library. Before that, you're paying the cost of a design system without getting the benefit.

Keep reading

Engineering

What we actually mean by “vibe coding”

It's not vibes instead of rigor. It's vibes plus AI plus senior taste, so the boring 80% of work gets compressed into a morning.

Process

How we ship an MVP in three weeks (and why you should)

A play-by-play of our 21-day MVP process: what we cut, what we keep, and how we keep quality from collapsing.