Design systems
Your teams ship screens that match by default, in Arabic and in English.
Get your free growth audit
A free written audit of your brand, website and social media.
The design decisions that live in someone's head become shared values (tokens), components and written rules. Right to left is set up once for your whole system, and you decide who can change what. Your new screens then match by default, instead of by someone checking each one.
- Timeline
- 3 to 5 weeks
- Price
- Fixed, quoted after a free audit
- Languages
- Arabic and English
Is this for you?
- More than one team ships screens, and they no longer match.
- You have a component library nobody can use without asking someone.
- Right to left is fixed screen by screen instead of once.
What you get
Audit report
Every screen and component you have today, collected and compared, so the duplicates and conflicts are visible.
Design tokens
Colour, type, spacing and motion as named values: one source that both design and code read from.
Component library
The components your products need, designed, and documented with guidance on when to use each one.
Right to left at the foundation
Direction handled in the tokens and layout rules, so Arabic works everywhere without fixing each screen.
Accessibility rules
Contrast, sizes and states checked against accessibility standards, and written into the rules.
Governance
Who can add or change a component, how, and how a change reaches every team.
How it works
You start with a free growth audit of what you already have, and a fixed price. Then:
Audit
Week 1
You see everything that exists, inventoried, and the inconsistencies become your backlog.
Foundations
Weeks 1 to 2
Tokens for colour, type and spacing, with right to left and accessibility built in.
Components
Weeks 2 to 4
The library, designed and documented, starting with the components used most.
Adoption
Weeks 4 to 5
Governance agreed, teams trained, and a plan agreed with your engineers for moving the first product onto the system.
Related work
ForgeSaaS & Software · 2026What we did: Product design · Design system · EngineeringView the case study
Cairo Amman BankBanking & Finance · 2026What we did: Product design · Design system · UX researchView the case study
BasisMusic & AudioWhat we did: Typography · Brand strategy · Logo systemView the case studyQuestions about design systems
We already have a component library. Why would we need this?
A component library is a folder. A system is the rules that stop it drifting: what each token means, which direction a layout mirrors in, who is allowed to add a variant. A library can be accurate and still unusable, because nobody wrote down the part that was in somebody's head.
How much does a design system cost?
It depends on how many products and platforms it has to serve, how many components they need, and whether we also build the coded library. You get a fixed price once we have seen what already exists.
Will our engineers actually use it?
It is the part that decides whether a system gets used. The tokens are delivered in a form your codebase can read, the documentation says when to use each component, and adoption is part of the project, not an afterthought.
What do you need from us?
Access to your current products and design files, and one lead from design and one from engineering who can agree decisions.
Want this for your business?
Tell us what you're making, and you'll get a plan, a timeline and a fixed price back, at no cost.
Free, no obligation, and you get the plan whether or not you hire us.