October 7, 2025

Design SystemsROIProduct Velocity

Your Design System Is a Business Asset

A design system is one library of interface parts, built once and reused on every screen. It costs a few weeks up front and pays back in speed on every screen after, which makes it a business decision.

A design system is one library of the buttons, forms, tables and layouts your software is built from. Its payoff is speed on every screen after the first few, which makes it a business decision more than a design one.

Design systems are usually sold on consistency, the buttons looking the same everywhere, and that pitch persuades designers and few others. The case for the business is that a part built once is never built again, so each new screen costs less than the last.

The Investment Comes First

At first, the team with a design system is slower: it is building parts instead of screens.

With design system

Without design system

Illustrative: the shape of the argument, not data. The team with a design system starts behind, draws level around month five as each new screen reuses its parts, and pulls ahead from there; the other team improves at a steady rate.

One Library, Many Pages

Every essay in this section is built from one shared library of about twenty components. The expandable card appears in most of them, and the step diagram that draws a process in an essay also draws the pipelines on our scenario pages.

Build a Component

Once, with settings for what varies

Use It on a Page

Its first use, with real content

Reuse It Elsewhere

No build time, new content

Every Page After

Each one cheaper than the last

On a larger scale, at MJ Hudson between 2021 and 2023, a nine-person team led by our founder, Shan Peiris, rebuilt six legacy applications and brought all fourteen of the firm’s applications onto one design system.

Where the Time Goes

Without a design system, much of a new page’s build time goes to basic parts: cards, grids, animation, a layout for each screen size. With one, that time moves to content.

Basic interface parts

Basic interface parts 45%

Layout for each screen size 20%

Content 20%

Testing 15%

Illustrative: one new page without a design system. The shares show the argument; they are not a measurement.

Basic interface parts 5%

Layout for each screen size 10%

Content 55%

New components 15%

Testing 15%

Illustrative: the same page with one.

On these shares, content rises from 20% of the work to 55%, and content is what sets the product apart.

When It Pays Back

Investment: say a core library of eight to twelve components takes a small team two to four weeks. Call it three weeks, or 15 working days.

Saving per page: say each page that reuses the library saves 40 to 60% of its build time. For a five-day page, that is two to three days.

Breakeven: at 2.5 days saved a page, the 15 days are repaid by the sixth page. Every page after that is gain.

Compounding: components built for one page are there for every later page, so the saving per page grows over time.

How to Tell if You Have One

If you can describe a new page as “components X, Y and Z with this content” and have a working prototype by the end of the day, you have a design system. If a new page starts with “first we need to build…”, every page is still built from scratch.

It does not need to be published, catalogued or shared across teams at first. It needs to be a folder of components your team reaches for by habit, and in a modernization, the rebuilt screens are the natural place to start one.

How many of your applications build the same screen their own way?

Book Free Assessment