Services

Design systems

A design system is not a page of swatches. It is the set of components, tokens and rules your engineers build against — and it only pays for itself if it is the fastest way for them to ship the next screen.

Where teams usually start

  • Every screen is a new argument about spacing, and both sides are right.
  • There is a library in Figma, and the code it is supposed to describe stopped matching it a year ago.
  • The team doubled, and so did the number of shades of grey in the product.
  • Accessibility is a ticket nobody can close, because it has to be fixed one screen at a time.

What the work covers

Audit first

What is actually in the product today: every button, every grey, every one-off. The inventory is usually the argument-ender.

Tokens

Colour, type, spacing and radii as named decisions, so a change lands everywhere instead of in the files someone remembered.

Components

Each with its states, its content rules and its edge cases — an empty table, a 40-character label, a failed save.

Accessibility built in

Contrast, focus order and touch targets decided once, in the component, at AA and AAA rather than screen by screen afterwards.

Documentation your team will read

When to use a component, when not to, and what to do when nothing fits. Short, and next to the component.

Adoption

A system nobody uses is a folder. We migrate real screens with your engineers until the system is the path of least resistance.

How it runs

  1. Audit, then agree the scope

    We inventory the product and show you what exists. Most teams need less than they expect, and in a different order.

  2. Built against real screens

    Components are designed for the screens that need them next, not in the abstract. The system grows out of the product rather than beside it.

  3. In your stack

    Figma libraries and tokens that match what your engineers build against. Where the code already has a system, we work inside it.

  4. Handed over, not handed off

    Your team uses it while we are still there, so the gaps show up while someone is around to close them.

What it costs

Two monthly subscriptions and a fixed-price option. Pause for up to two months or cancel with three weeks’ notice — the terms are the same whichever you pick.

Selected work

See all work
Easy Tiger

UXBOX Company LTD

We are building easytiger.vn, Vietnam's only platform dedicated to helping people navigate the country's bureaucracy by connecting them with verified local experts. Built for AI agents, every expert profile is structured for AEO and GEO so answer engines surface them directly.

GoTeach

GoTeach Collective

GoTeach.vn is Vietnam’s first platform connecting private tutors and coaches with students. In just 3 months, we helped them validate their idea, design their brand, build the platform, and launch—aided by AI, low-code technology, and a localized go-to-market strategy.

Invoicing.mu

Netch Digital

Invoicing.mu aims to become Mauritius’s leading e-invoicing SaaS in terms of user experience and seamless onboarding. With new legislation pushing SMEs to adopt compliant digital invoicing, Invoicing.mu positions itself as the affordable, user-friendly solution businesses can trust.

Send us three screens.

Any three that should look related and do not. That is usually enough to say what the system needs to be.

Other services

Where this sits in our product plan 

What is a design system?

The components, tokens and rules a product is built from, in one place, with the decisions written down: what a primary button is, what the spacing scale is, what happens to a table with no rows. It is design and engineering sharing one source rather than two.

Do we need one?

If the product has one screen and one designer, no. If new screens are slow because every detail is decided again, or the same component exists five times in code, the system pays for itself quickly.

How long does it take to build?

A working core — tokens, the components a team actually reaches for, and the rules around them — is usually a matter of weeks. Adoption across an existing product takes longer and is the part worth planning for.

What do we get at the end?

A Figma library with tokens and components in their states, documentation next to each one, and the migrated screens we did with your engineers. It is yours: it keeps working after the engagement ends.

Can you work with what we already have?

Yes, and we would rather. Starting again throws away the decisions your team has already made and creates a second system to keep in step with the first.

How much does a design system cost?

Fractional is $4.2K a month, Full-time is $7.7K a month, and fixed-price projects start from $30K. The pricing page states all three in your own currency.

Work with us

Book a discovery call

I want to discuss designs for our
The engagement I have in mind is