Design systems · Built on every plan, maintained on Scale
A system your engineers actually use.
Tokens as Figma variables, components with variants, and a written rule for each one. Named after the names in your codebase, versioned so nobody argues about which button is current, and kept alive after handover rather than handed over and abandoned.
What it is
A contract between design and engineering, with someone responsible for it.
A design system is an agreement: these are the colours, these are the sizes, these are the components, this is how they behave. Most of them die within a quarter because they arrived as a file and nobody owned them afterwards. The product moved; the file did not.
On Scale, we own it. The system is built, then maintained every month as the product changes — new components, deprecations, a changelog your engineers can read. On Starter and Growth it is built in your stream, one part at a time, starting with the pieces that unblock the most screens: usually the form fields and the table, rarely the logo.
We read your repository before we name anything. If your code says Button/Primary, so does Figma. If your tokens are already JSON, the variables map to them; if they are not, you get the JSON.
What you get
Every part of it is a file you can open on Monday.
Delivered in the order that unblocks screens, with a version note each time something changes.
Tokens as Figma variables
Colour, type, space, radius and shadow in primitive and semantic layers, light and dark if you ship it, exported as JSON your build consumes directly.
Components with variants and auto-layout
Buttons, fields, selects, tables, navigation, dialogs, toasts, empty states. Properties match the props in your code, so a variant in Figma is a prop in React.
One usage rule per component
When to use it, when not to, and the one thing people get wrong with it. A paragraph on the component page, not a wiki nobody opens.
Type and spacing scales that survive Arabic
Line-heights that clear Arabic ascenders, a spacing scale written in logical properties, and a numerals rule — so one system produces both directions.
Names that match your codebase
We read the repo first. Component and token names in Figma are the names in code, which is the only way engineers keep using the file.
A changelog and version notes
Every release states what changed, why, and what needs a migration. On Scale this arrives monthly, with the work already done.
A real deliverable
The token sheet and the library, in HTML.
Both built from the tokens this site uses. The sheet maps primitives to semantic names; the library shows each component with the variants that actually exist.
Who it is for
Three situations this fixes.
“Three designers have touched the file and there are four blues.”
A quarter of drift costs a week every sprint in reconciliation nobody budgeted. We consolidate what you have, keep the names engineers already know, and leave one source of truth with a changelog.
“The Arabic launch is next quarter and the system has never met an Arabic letter.”
Latin line-heights clip Arabic ascenders. Physical margins break in RTL. We rebuild the tokens and components so the same system produces both directions, and hand your engineers a bidi checklist.
“Engineering built components without design and now nobody can change them.”
We start from the code — read the props, match the names, design the missing states — so the system describes what ships, and the next screen is assembled rather than drawn.
Which plans include it
Design systems by plan
Built on every plan, one part per request. Scale adds ownership: the system is maintained every month with a named design lead accountable for it, and a quarterly roadmap review with our Head of Design.
Compare all three plansStarter
$1,999/mo
IncludedBuilt in your stream, part by part
1 stream · 48-hour first concepts
Growth
$3,499/mo
IncludedBuilt in your stream, part by part
2 streams · 24–48-hour first concepts
Scale
$4,999/mo
IncludedBuilt, then maintained monthly
3 streams · Same-day or next-business-day first pass
Start with the part that unblocks the most screens.
File the form fields, the table or the button set first — whichever your engineers are rebuilding by hand this sprint. On Scale we own the system from there; on Starter and Growth it grows in your stream, one request at a time.
From $1,999/mo. 14-day full refund on every self-serve plan. Pause any month — unused days carry forward.