Design system

At Wzór, a UX agency, you get a design system with a component library in Figma and in code, which our team or your own developers can then roll out across your products. This is how we built the shared design system for four Bosfor Group websites and the system behind the Fonia app. We build accessibility into the components from the start, and for products already live we begin with an accessibility audit.

Challenges

Which challenges do we help you with when building a design system?

Our approach

We assemble the first components straight onto real screens of your product, and any that cannot build a form or a list go back for rework before anyone uses them. We build the second part of the library in pairs with your designers and developers, so the team knows it from its own work rather than from the documentation.

Our approach

We keep the old and new components side by side behind a switch and move screens onto the library in batches that fit your sprints. Meanwhile the team keeps delivering its development plan, and every new feature picks up whatever is already finished.

Our approach

Before handover we agree with you who approves changes to the library, how the team requests a missing component and when a new release goes out. You rehearse those rules with us in a training session before the library passes into your hands.

Who it is for

Which companies do we build design systems for?

Groups running several websites

We bring order to groups where every website looks like it belongs to a different company, even though they all trade under one brand: that is how the four Bosfor Group websites got a shared component library. Charter, cruises and the catamaran dealer kept their own character, while the navigation, yacht cards and booking are built from the same parts.

Products in their first version

For a product that is only just entering the market, we design the system alongside the first version of the app. That is how Fonia came about: we designed the MVP in four weeks together with a system built around its brand, so that later versions of the product would stay consistent.

Software houses and agencies

We work under our partner's brand, for its clients, so one system has to carry many brands at once. Each client gets a theme built on shared components, and a new project starts without setting up a library from scratch.

Companies after an acquisition or a rebrand

When two products have to speak with one brand from tomorrow, we start with a shared layer of tokens and swap the values there before touching individual screens. The differences that cannot be evened out straight away go into the release plan with a specific date.

Internal systems and admin panels

In panels where people spend their whole working day, we bring the library in starting with forms and tables, because that is where inconsistency costs operators the most time. The remaining screens follow later, with no budget needed to rewrite the whole application.

First conversation

Free consultation

When the same form looks different in every module, we ask where that comes from and what holds your team back. After the call you get recommendations on whether a design system will help or the assumptions need revisiting first. No component list needed.

Patryk Korycki CEO, Business Analyst

Why us?

Why choose our UX agency?

  • Consistency across every product

    One set of components serves the website, the app and the admin panel, so customers recognise your brand on every screen. The next product speaks the same language as the rest from its first screen.

  • Faster delivery of new features

    Your team assembles a new screen from parts that have already been through design, an accessibility review and testing. Designer and developer time goes into what the product does not have yet.

  • A lower cost of change

    You make a fix to a form field in one place, and it reaches every product that uses it. A visual refresh is no longer paid for view by view.

  • A senior team

    A team of senior UX designers who have been designing interfaces for nine years, today for large organisations, SaaS companies and software houses, including the design systems of Bosfor Group and the Fonia app. Your library is built by people who know how a development team will actually use it.

  • Proven client trust

    We have designed for 115 brands, and most of them come back to us with another project.

  • Higher quality with AI

    We name our components and tokens and link them to the code so that AI tools generating interfaces reach for your library instead of inventing their own buttons. New screens are then easier to keep in line with the rest of the product.

Process

How will we build your design system, step by step?

  1. A conversation with your team

    We agree what the design system covers and who will use it

    We start with the products, platforms and brands the system has to bring together, and with the people who will use it every day. We also agree on one person on your side who makes decisions about the library, because without one the system has no owner.

    Key steps

    • A list of the products, platforms and brands in scope
    • Conversations with designers, developers and the product owner
    • Your tech stack and the way you style components
    • Choosing the person responsible for the library

    Deliverables

    • Design system scope
    • List of products and platforms
    • Brief
  2. Interface inventory

    We gather everything already in your products and look for repeats

    We go through the screens of every product in scope and break them down into parts: buttons, fields, tables, dialogs. The result is a map showing what to keep, what to merge into a single component and what to redesign.

    Key steps

    • Collecting views from every platform: website, app, admin panel
    • Side-by-side comparison of variants of the same elements
    • Conversations with your designers and developers
    • An initial accessibility review: contrast, states, focus

    Deliverables

    • Interface inventory
    • Inconsistency map
    • List of components to build
  3. Tokens and component library

    We turn the inventory into tokens and a component library

    We start by setting the tokens, the named decisions about colour, typeface, spacing and motion, and build the components in Figma and in code on top of them. Every component has its states and variants documented, along with when to use it and when to reach for a different one.

    Key steps

    • Tokens in the Design Tokens (DTCG) format, with light and dark modes
    • A Figma component library with variants and states
    • Code components in React or Vue, catalogued in Storybook
    • Components checked on screens from your product
    • An accessibility review of every component

    Deliverables

    • Tokens
    • Figma library
    • Code components
    • Usage documentation
  4. Rollout or handover

    We move screens onto the library or hand it over to your team

    Who moves the screens onto the library depends on how you work: our team does it, or your developers do with our review. At handover you get the documentation, the files and training for designers, developers and the people running the product.

    Key steps

    • A plan for moving screens in batches that follow your sprints
    • Old and new components running side by side until the switch
    • Review of components built by your team
    • Written rules for requesting and approving changes
    • Training for designers, developers and product owners

    Deliverables

    • Screens on the library or a complete handover package
    • Documentation
    • Library change rules
    • Team training
  5. Growth after launch

    We check that the system has taken hold and grow it with the product

    After rollout we measure coverage: how much of the screens and imports in the repository use the library, and where local copies still live. That measurement produces the plan for the next releases, so you know which products and screens still need work.

    Key steps

    • Measuring screen and import coverage
    • Reviewing requests from teams
    • New library releases with release notes
    • Support for the team after handover

    Deliverables

    • Coverage report
    • Plan for the next releases
    • List of modules still to move

Methods and technologies

Tools, standards and methods we use to build a design system

  • Figma

    We build Figma components with variants, auto layout and usage notes for each of them. Design files easily drift away from the repository, which is why we sync the values from Figma with the code through Tokens Studio.

  • Storybook

    In Storybook we show every component in every state and variant. A catalogue nobody updates soon parts ways with the code, so we run the same examples as interaction and accessibility tests.

  • React

    We write components in React or Vue, depending on your team's stack. A component everyone adds an exception to soon has more settings than uses, so we agree its settings with you before any code.

  • Design Tokens

    We store design tokens in the Design Tokens Community Group format at W3C, so one file generates code for the website and the apps. The format belongs to no vendor, and your tokens will not get stuck in a tool you may one day replace.

  • WCAG

    We check WCAG requirements in every component before it enters the library. A flaw in a single field or dialog repeats on every screen that uses it, so we fix it at the source.

  • Atomic Design

    Atomic Design organises the library from the smallest elements up to page templates. Screens and system grow together: while designing a view we see straight away which component the library is missing.

Build your design system with us

Tokens, components and documentation your team will build its next screens on.

Client voices

What our clients say

Jonasz Więcławski Chief Executive Officer, Wolumen
“UX Agency Wzór advised us to develop a design system, which in the end made working on our brand much easier. We have ready-made elements to combine, and our image has become even more consistent. The calculator on our site is more convenient for users and looks much better. I recommend working with this collective.”
Mateusz Swół Chief Operating Officer, Sellace
“Our cooperation with UX Agency Wzór started with our own website. We really liked the way they work, so we decided to subcontract projects for our clients to them on a White Label basis. We loved their workflow, the way they hand projects over to our team, their documentation and their work on the design system. Now we can take on bigger risks.”
Maja Wieloch-Silecka Operations Director, Bosfor Group
“Working with the Wzór team was a genuinely great experience! They always answered our questions quickly and were flexible about our comments. They have no shortage of creative ideas and are at the same time thoroughly reliable and on time. The end result fully met our expectations; we recommend them to anyone looking for professionals who care.”
Marcin Ostrzycki Chief Operating Officer, Selectivv
“We're glad we chose to work with Wzór UX Agency. The time it took to deliver the project, and their commitment, went beyond our expectations. They did solid work for us, which is why we recommend them at every turn.”
Meet our clients (115)

The team

Who will build your design system?

  • Aleksandra Bondar

    Aleksandra Bondar

    Senior UX/UI Designer

    View profile
  • Katarzyna Adamczuk

    Katarzyna Adamczuk

    Prezes, Analityk Biznesowy

    View profile

    How can I help you?

    “I will agree with you which products and teams the system covers, and test it on a clickable prototype in code that your developers can take over without rewriting.”
  • Tadek Wadas

    Tadek Wadas

    Senior UX/UI Designer

    View profile

    How can I help you?

    “I will design the component library and write the documentation your team needs to keep screens consistent on every platform.”

FAQ

Frequently asked questions about design systems

What is a design system?

A design system is a set of tokens, ready-made components and rules from which a team designs and builds the interfaces of all of a company's products. It covers a Figma library, code components and documentation that says when to use each element. On top of that come the agreements on who changes it and how.

How long does it take to build a design system?

Building a design system takes roughly 6-8 weeks. The timeline depends on how many products and platforms the library has to serve, how many components come out of the inventory and whether existing screens move over with it. We confirm the exact timing once we know the scope.

How is a design system different from a component library?

A design system includes a component library but goes beyond it, adding tokens, usage documentation and rules for making changes. A library on its own tells you what a button looks like, while a design system also tells you when to use it and who decides when it changes.

Is it better to build your own design system or base it on an existing one?

Your own design system pays off when an existing one, such as Material or MUI, would need so much reworking that the savings disappear. If your team already works on a ready-made library, we design on its components and tokens and add only what is missing. We tell you which route costs less once we have reviewed your products.

Does a design system include code components?

Our design systems include code components, unless your team prefers to build them itself from the Figma library. We write the components in React or Vue, with TypeScript and a Storybook catalogue.

Can you introduce a design system into a product that is already live?

We introduce a design system into a live product without pausing its development. We start with an inventory of what is already there and decide what to keep and what to redesign. Until the switch is complete, both versions of the components run in the product in parallel.

Who maintains a design system after rollout?

After rollout a design system is maintained by your team or, when nobody on your side has the time, by a designer from our Hire designers service. For the first 30 days after handover we answer the team's questions, and changes are decided by the person you named at the start of the project.

Does a design system help AI tools generate code?

A design system helps AI tools generate code that matches your product, provided the components and tokens have names a model can understand and counterparts in the repository. Without that, the tool assembles a screen from random elements that the team then fixes by hand. That is why we write component names and descriptions so that both a person and a model can understand them.

Can one design system serve several brands?

One design system serves several brands when colours, typefaces and corner radii live in tokens and the components stay shared. A new brand then gets its own set of values instead of a copy of the library. The stable 2025 version of the Design Tokens format provides for such themes directly.

Patryk Korycki CEO, Business Analyst
Send us a message

Related services

Services related to design systems

Your product is still taking shape.

We will sort out the product's assumptions and scope before any library is built.

You have one product and only a few screens.

Let's design the product first, and the system will grow out of its components.

You already have a design system, but it has stalled.

We will add a designer to your team or advise you on how to get it moving again.

Next step

Free consultation

We start by asking about the parts each of your teams builds its own way and what slows the product down most. You leave with recommendations on whether the answer is a design system or a fresh look at the product's assumptions. What you have is enough.

Patryk Korycki CEO, Business Analyst

Book a free consultation with an expert to discuss your project and get answers to your questions.

- Patryk Korycki, CEO

Schedule a meeting
Book a free consultation