Deploy Studio Design System

Deploy Studio DS

Deploy Studio moves fast. Projects come in with tight timelines, shifting requirements, and little room for inconsistency. Without structure, delivering high-quality work at that pace becomes risky.


As the lead designer, I built the design system to give the team structure under pressure and to help junior designers produce strong work without oversight.

Speed was high. Structure was missing.

Speed was high. Structure was missing.

Speed was high. Structure was missing.

Product design, 2025

Projects moved fast, but design decisions were repeated across files and teams. Junior designers sometimes lacked clear guidance, which led to inconsistencies and rework. Reviews took longer than necessary because basic patterns were not standardized.

Create clarity without slowing the team down.

Create clarity without slowing the team down.

Create clarity without slowing the team down.

Product design, 2025

The goal was to create a practical foundation that designers could rely on daily, scale across projects, and adapt to different client needs.

Built for real work.

Built for real work.

Built for real work.

I focused on the components we actually reused across projects . Variations were intentional and limited to avoid choice overload. Naming conventions were simple, predictable, and easy for new designers to understand. Every component was designed with reuse in mind.

Some of the key foundations.

Some of the key foundations.

Product design, 2025

Inter

Ag

ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 !@#$%^&*()

Inter

Ag

ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 !@#$%^&*()

Inter as the Backbone

Inter as the Backbone

Inter was chosen for its clarity, scalability, and ability to stay readable across varied product contexts.

Primary

Primary

50

50

#F3F3F4

#F3F3F4

100

100

#E0E1E3

#E0E1E3

200

200

#B9B9BB

#B9B9BB

300

300

#99999B

#99999B

400

400

#606060

#606060

500

500

#23232B

#23232B

600

600

#101011

#101011

700

700

#1e40af

#1e40af

800

800

#1e3a8a

#1e3a8a

900

900

#172554

#172554

Secondary

Secondary

50

50

#eff6ff

#eff6ff

100

100

#dbeafe

#dbeafe

200

200

#bfdbfe

#bfdbfe

300

300

#93c5fd

#93c5fd

400

400

#93c5fd

#93c5fd

500

500

#3b82f6

#3b82f6

600

600

#2563eb

#2563eb

700

700

#1e40af

#1e40af

800

800

#1e3a8a

#1e3a8a

900

900

#172554

#172554

Tertiary

Tertiary

50

50

#eff6ff

#eff6ff

100

100

#e5dcf9

#e5dcf9

200

200

#d4c5f5

#d4c5f5

300

300

#93c5fd

#93c5fd

400

400

#93c5fd

#93c5fd

500

500

#7F51E1

#7F51E1

600

600

#553696

#553696

700

700

#402870

#402870

800

800

2A1B4B

2A1B4B

900

900

#172554

#172554

Acccent 1

Acccent 1

50

50

#e9f9f8

#e9f9f8

100

100

#D2f2f0

#D2f2f0

200

200

#b3e9e5

#b3e9e5

300

300

#8eded9

#8eded9

400

400

#5bdcd4

#5bdcd4

500

500

#09CBBE

#09CBBE

600

600

#137D77

#137D77

700

700

#0E5E59

#0E5E59

800

800

#093F3B

#093F3B

900

900

#072F2C

#072F2C

Acccent 2

Acccent 2

50

50

#e9f9f8

#e9f9f8

100

100

#D2f2f0

#D2f2f0

200

200

#fdceb4

#fdceb4

300

300

#fcb58f

#fcb58f

400

400

#fa9c6a

#fa9c6a

500

500

#F98444

#F98444

600

600

#f86b1f

#f86b1f

700

700

#a54715

#a54715

800

800

#7c3610

#7c3610

900

900

#53240a

#53240a

Neutrals

Neutrals

50

50

#fcfdfd

#fcfdfd

100

100

#f9fafb

#f9fafb

200

200

#f2f4f7

#f2f4f7

300

300

#e4e7ec

#e4e7ec

400

400

#d0d5dd

#d0d5dd

500

500

98A2B3

98A2B3

600

600

#667085

#667085

700

700

475467

475467

800

800

#1d2939

#1d2939

900

900

#09C13

#09C13

Functional, but still decorative

Functional, but still decorative

Button styles and states define priority and intent, keeping actions consistent and predictable across products.

Action hierachy

Action hierachy

Button styles and states define priority and intent, keeping actions consistent and predictable across products.

Forms without friction

Forms without friction

Inputs and controls are designed to guide users, surface errors early, and reduce mistakes in complex workflows.

Cards for all use cases.

Cards for all use cases.

Cards allow users to access and view quick actions without losing their place, keeping workflows focused and efficient.

The system in use.

Designed to be shared.

The system made collaboration easier by giving designers a common language. Files became easier to review and hand over. Developers had clearer patterns to follow, which reduced misalignment and unnecessary back-and-forth.

Design systems matter more in fast-moving teams.

While working on this system, I realised how much I enjoy designing design systems, not just the components, but the thinking behind them.

I also gained clearer insight into the debate around whether design systems are still relevant. In a high-paced environment like Deploy Studio, the value became obvious.

The system reduced design time, improved consistency, and made collaboration smoother when multiple designers worked on the same product at different times and on different flows. Instead of rethinking decisions or second-guessing patterns, the system created a shared baseline that kept everyone aligned.

Designed to be shared.

The system made collaboration easier by giving designers a common language. Files became easier to review and hand over. Developers had clearer patterns to follow, which reduced misalignment and unnecessary back-and-forth.

Design systems matter more in fast-moving teams.

While working on this system, I realised how much I enjoy designing design systems, not just the components, but the thinking behind them.

I also gained clearer insight into the debate around whether design systems are still relevant. In a high-paced environment like Deploy Studio, the value became obvious.

The system reduced design time, improved consistency, and made collaboration smoother when multiple designers worked on the same product at different times and on different flows. Instead of rethinking decisions or second-guessing patterns, the system created a shared baseline that kept everyone aligned.

The system in use.

Designed to be shared.

The system made collaboration easier by giving designers a common language. Files became easier to review and hand over. Developers had clearer patterns to follow, which reduced misalignment and unnecessary back-and-forth.

Design systems matter more in fast-moving teams.

While working on this system, I realised how much I enjoy designing design systems, not just the components, but the thinking behind them.

I also gained clearer insight into the debate around whether design systems are still relevant. In a high-paced environment like Deploy Studio, the value became obvious.

The system reduced design time, improved consistency, and made collaboration smoother when multiple designers worked on the same product at different times and on different flows. Instead of rethinking decisions or second-guessing patterns, the system created a shared baseline that kept everyone aligned.