“At Kroger, we built Meridian because our ad platform and internal tools needed components that carried Kroger-specific patterns, data density, and accessibility requirements no off-the-shelf library could own. Buy when the problem is generic and speed matters; build when the component is a competitive surface or sits at a workflow your product cannot compromise on.”

“I buy when the component is a commodity, like a date picker or a data grid, because no one on my team wants to maintain that. I build when the component is where our product actually competes, because that is where the design system earns its keep.”

“At Capital One, I tried to reuse existing components for the Help Center redesign until it became obvious that three new components were the only way to make the content feel intentional. Buy when the library gets you 80% of the way there; build when the remaining 20% is what users actually notice.”

“I bought Bootstrap's patterns back in the day, then spent longer unpicking their generic assumptions than I would have spent building our own. Now I build when the component carries the brand's distinctiveness, and buy only the stuff no visitor should ever notice.”

“I buy when the component is table stakes and my team’s time is better spent on the patterns that actually move the business. I build when the interaction is core to the product’s differentiation or when I’ve watched a federated component library collapse because no one owned it.”

“I build when the component carries a product-specific behavior that a library can't know about, like the run cards in Runbook with inline approvals grouped by trade. I buy when it's standard infrastructure, because at Reducto rebuilding every component from scratch taught me that custom work only pays off where it changes the user's outcome.”

“At Vividly I built a component library in Figma because off-the-shelf kits couldn't handle the trade-management workflows our engineers needed to template quickly. Buy when the patterns are generic and speed matters; build once the same component needs to behave differently across three product surfaces.”

“I buy when the component is invisible infrastructure: tables, forms, date pickers. I build when it carries the brand's logic, like the customization panels or responsive cards I had to own for Dickies and Sundays, because that is where the system either earns trust or becomes generic.”

“I ran design systems at places like the New York Times and SuperFriendly, and the call usually came down to connection, not components. If a bought library can stay connected to your product pipeline and your team’s real workflow, it’s a real option; if you’re copying and pasting, you’re just buying a faster way to drift.”