The build-vs-borrow decision for design systems usually comes down to one question: does your product have enough surface area yet to justify the maintenance cost of a custom system?
“A design system is not a project you finish. It is a service you maintain. If you are not prepared to staff it full-time, borrow instead of building.”
Jason Azarr, Azarr Technologies
When to borrow
Early-stage startups (pre-Series B) benefit from borrowing from established systems like Material UI, Chakra UI, or Tailwind UI. The time saved can be reinvested into product-market fit.
- Team size under 10 designers/developers
- Product is still finding market fit
- You need to ship features quickly
- Resources for maintenance are limited
When to build
Once you have a stable product team and a mature product with multiple surfaces, building a custom system starts to pay off through consistency and velocity gains.
- Multiple products or platforms in the same ecosystem
- A dedicated design and frontend team
- Your product differentiates through design quality
- Existing libraries no longer meet your needs
References
- Nielsen Norman Group, "Design Systems Research", 2025
- Brad Frost, "Atomic Design"
- Radix UI — open-source component primitives