Design system audit
Know what is wrong with your design system before you rebuild it.
Two weeks, fixed scope, fixed price. You leave with a map of what exists, where it gets bypassed and what fixing it would cost, including the option of changing nothing.
A rebuild is the expensive way
to find out what was wrong.
Most design systems that are not working have enough components. What they are missing is agreement: on which tokens are real, on who decides what gets added, and on why people quietly build around the library instead of with it.
A rebuild started without that answer repeats the old system's mistakes at a higher cost. The audit finds the answer first, in two weeks, for a price fixed before we start.
Two weeks,
four questions.
What exists
Every component, token and pattern, in the design files and in the code, and where the two have drifted apart.
What gets bypassed, and why
Where screens are built around the system instead of with it, and the reasons from the people who do it. The reason is rarely carelessness; it is usually a missing state or a rule nobody wrote down.
Who decides
How a new component gets added today, who approves it and whether anyone does. Most systems fail on governance, not on inventory.
What it would cost to fix
Every gap we find, prioritised and costed, so the decision about what to do next is made on numbers rather than on frustration.
Fixed scope, fixed price.
Two weeks, fixed scope. The fastest way to find out whether you need a system, a rebuild, or a decision nobody has made yet.
Fixed price: ask us for the current figure. If it becomes a build, the audit fee comes off the first invoice.
- A map of what exists today: components, tokens, and where they diverge
- Where the system gets bypassed, and why people bypass it
- A prioritised list of gaps, costed
- A written recommendation, including the option of doing nothing
What you hold
at the end of two weeks.
- A map of your components and tokens, in design and in code, with every divergence marked
- Where and why the system gets bypassed, from the people who bypass it
- A prioritised list of gaps, each one costed
- A written recommendation, to extend, rebuild or change nothing, and why
Asked often enough
to answer here.
01What does it cost?
A fixed price, agreed before we start. Ask us for the current figure. If the audit leads to a build with us, the fee comes off the first invoice.
02What do you need from us?
Read access to the design files and the code, and time with the people who use the system every day. We agree who, and how much of their time, at kickoff.
03What if we do not have a design system yet?
Then the audit maps what you have instead: the patterns that repeat across the product, whether or not anyone named them. That is usually where a system should start.
04Do we have to hire you for the build afterwards?
No. The recommendation is written to be used by whoever does the work, including your own team.
Tell us about
your design system.
What exists, what is not working and who uses it. We reply within two working days.