Figma library
Tokens as variables, light and dark, all components with variants and auto layout. Your designers pull from the library instead of eyeballing. One source of truth.
AI-ready design systems for teams that need to ship fast, with less friction
We help teams fix drifting UI, agents that invent components, and reviews that argue about padding. In two weeks, you get the design system your team and your agents both run on: a Figma library, an npm package, and a docs site your coding agents read as context. No rewrite, no quarter lost to it.
103+ design systems shipped at 90five, rated 4.9 on Clutch. We take two sprints a month.
Book an intro call →Full refund if we're not a fit
/problem
Half your UI is now built by agents. Your design system wasn't made for that.
The work moves faster than the system. Each missing rule becomes a component someone rebuilds, a review someone repeats, and a week the roadmap didn't have.
Every new feature ships its own button, its own spacing, its own shade of blue.
Designers eyeball colour and radius instead of pulling from one source of truth.
Coding agents invent components because there's nothing to reference.
Small inconsistencies compound into a product held together with tape.
This is for teams with no design-ops safety net, who need consistency to be the default instead of another quarterly project.
Your team uses agents for UI and code.
Your team uses agents for UI and code.Claude, Cursor, v0, Lovable: they all build faster than a human can review. Give them a documented system to pull from and their output stops drifting from what your designers intended.
You need a solid system this month, not in six.
You need a solid system this month, not in six.A fixed two-week sprint with a fixed price, not a quarterly design-ops initiative. You get the Figma library, the npm package and the docs site while the roadmap that needs them is still current.
/why-now
The tools changed. The system underneath didn't.
Code now sits next to the canvas and agents reuse whatever rules they can find. Every gap in your system gets copied at machine speed.
32%
of designers and developers say they can rely on the output of AI in their work.
28%
of design system teams say AI is delivering highly on what they expected from it.
Rework eats the roadmap
Small fixes pile up faster than they get made, so every sprint loses more of the roadmap to patching.
Reviews argue about padding
When Figma, code and docs disagree, every design review becomes a debate about which one is right.
Bugs nobody can ticket
The missing rule isn't in any file, so the inconsistency lands in production and stays there.
Agents multiply the mess
One undocumented pattern becomes five. Claude and Cursor copy every gap at machine speed.
/deliverables
Three artifacts. One source of truth.
A design system only works when design, code, and documentation stay in lockstep. These three deliverables share the same tokens, components, rules, and skills, so your designers, your engineers and your agents all build from the same answer.
npm package
Typed, production-grade components with your tokens as plain JSON. Accessible by default, dark mode included. Install it and ship.
Docs site
A custom documentation site with every rule written in plain markdown. Readable by your team, ingestible by Claude, Cursor and whatever your pipeline runs next year.
/case-study
Mater got one design system for its team and its agents. In ten days.
MaterRead the case study “We use agents to move fast. Now everything we build starts from the same system, and the build catches anything that doesn’t.”
10 days
audit to shipped, while live
313
Figma variables, same names in code
0
values allowed outside the system
/process
Ten working days, four milestones.
A fixed scope and a senior team working on nothing else. Here is how the fortnight runs.
AuditSystemiseBuildShip
Audit
day 1–3We review your product and existing patterns, keep what works, and lock scope and direction with quick component spikes.
Outcome
A locked scope and a component inventory any team can build from.
output audit.md · component-inventory.csv
Systemise
day 4–6Colour, type, spacing, radius and motion become named tokens with light and dark themes. Exported as Figma variables and JSON.
Outcome
Every colour, type and spacing decision named once, light and dark, ready for designers and code.
output figma file · tokens.json
Build
day 7–9The 37 components that cover 95% of product UI, built in parallel in Figma and code so neither drifts. Daily async reviews.
Outcome
37 components that match pixel for pixel in Figma and the npm package.
output ui-kit v0.1 · @company/ui
Ship
day 10–14Docs site live, npm package published, Figma library shared. We hand over in a working session with your whole team.
Outcome
Your team owns the system, your agents read it, and nothing depends on us.
output docs.company.com · handover session
/about
Built on 103+ design systems shipped for startups and enterprises at 90five.
For nearly a decade, 90five has built brands, websites and products for founders and teams that cannot afford to fail. Most of that work ran for months, with a design system as one deliverable of a much bigger build.
Labs takes the part we've done a hundred times and cuts it loose: one senior team, one fixed scope, one fixed price, two weeks. Two projects at a time, rated 4.9 on Clutch.
See 90five's work ↗/cost
With people building UI, a year without drift is worth $90,000$90,000 .
That’s
Our assumptions, in case you disagree
Each person gets back a week, across working weeks, at a loaded rate of an hour.
Each person spends a month on AI tools.
/investment
The Design System Sprint
Figma library, npm package, and docs site: one system, one sprint. We only do two systems a month, by design. Sprints take 10-14 days, and are billed upfront.
$20,000
Audit of your product and existing patterns
Full token system (colour, type, spacing, radius, motion)
37 components matched in Figma and code
Typed npm package with tokens as plain JSON
Custom docs site your coding agents can read
Dark mode + accessibility pass
Daily async updates + weekly sync
The audit comes first, on days 1 to 3. If in that window we don't believe the scope fits your product, we stop and refund what you paid.
/questions
What to know before you start.
How can two weeks be enough?
Because the scope is fixed and the team is senior. We're not inventing a brand. We systemise the one you already have, and 37 components cover about 95% of real product UI. The exceptions get documented patterns, so your team knows exactly how to extend the system.
What if we're not a fit?
Then you get your money back. Every sprint starts with an audit of your product and your current patterns, on days 1 to 3. If by the end of that window we don't believe the scope fits, we stop and refund the full $20,000.
What do you need from us?
Before day one: your brand assets, screens from your current product, licensed fonts, and access to your Figma org, your repos and your DNS. During the sprint: one person with the authority to make calls, who answers within 24 hours at three checkpoints. That adds up to about three hours of their time, plus a QA day for the whole team near the end. Everyone else can watch the system take shape on a live preview URL from day five.
We already have a design system. Is this still useful?
Usually, yes. Most existing systems are a Figma library, code that drifted away from it, and nothing an agent can read. We don't throw that away. The day one audit keeps what works, your tokens and components become the starting point, and we build what's missing: components matched in code, a docs site, and guideline files your agents pull from. If your system already lives in Figma, in code and in docs your agents read, you don't need us.
Which stacks do you support?
The components are React and TypeScript. Tokens ship as plain CSS variables and JSON, so they work in any stack, and the Figma library and docs site don't care what you build with. Agents connect through guideline files in your repo and an MCP endpoint, which works with Claude Code, Cursor, v0 and ChatGPT. If you're not on React, bring it up on the intro call and we'll tell you straight whether the sprint fits.
What if we want to change something mid-sprint?
Depends on what. On day four we lock the tokens: colour, type, shape, spacing. After that, three artifacts build in parallel from the same source, so a colour tweak on day nine re-runs work across Figma, code and docs. Identity changes after day four are change orders with a new ship date. New components, extra blocks or a marketing site go into a follow-on, not into the sprint. That is how it stays two weeks.
What happens after handover?
You own it. The repo moves to your GitHub, the Figma library is published to your org, and the docs site runs on your domain. On the last day we record a walkthrough of how the three pieces fit together and leave a one-page guide to who owns what and how to ship a change. Your agents get skills too: guideline files in the repo they use to navigate the system, understand its rules, and build with it without drifting. For the first weeks after handover we stay reachable for questions. If you want us to keep extending the system, that's a separate retainer.
