What to Look For When Outsourcing Design System Work
House of Arali — July 2026 · 5 min read
Agencies take on design system briefs for many reasons: client demand, scope expansion, category growth. The problem is that building a rigorous design system is a specialist skill — and most agencies discover this after they have committed to delivering one.
Outsourcing is the sensible answer. The question is how to evaluate who to outsource to, and what to check before accepting the handoff.
Questions to ask before engaging a studio
The purpose of these questions is not to test knowledge — it is to distinguish between studios that produce design systems as a discipline and those that produce them as an interpretation of what a design system might be.
- How do you structure your token architecture?A studio that has thought carefully about this will have a clear answer: naming conventions, semantic layering, role assignments. Vague answers about colour palettes and font choices describe a brand kit, not a system.
- What does your Figma file structure look like at handoff?The answer should include specifics: named variables, organised component pages, usage documentation. If the studio has not thought about file structure, the Figma file will be usable only by the person who built it.
- How do you handle components that do not fit the system?Every system encounters edge cases. A studio with a real process will have a clear answer about how exceptions are documented and how the system is extended. A studio without one will not have considered the question.
- What is included in the brand guidelines document?The document should explain not just what the rules are but why they exist — so that the people using the system can apply the underlying principles to new situations, not just follow the examples.
Red flags to watch for
- The studio conflates brand identity work with design system work. A logo redesign is not a design system. A colour palette is not a token architecture. If a studio cannot articulate the difference, they are not design system specialists.
- The portfolio shows visual work but not system work. Screenshots of beautiful interfaces are not evidence of system thinking. Ask to see Figma files, token documentation, or guidelines documents — the artefacts that actually constitute a system.
- The handoff is described as a Figma file and a PDF. A complete handoff includes a structured Figma file, a written guidelines document, a walkthrough session, and ongoing availability for questions. A file and a PDF is a starting point, not a system.
- The studio does not ask about your client's team and workflow. A design system that works for a solo designer is different from one that works for a team of five across multiple tools. If the studio is not asking how the system will be used, they are not designing for use.
What a rigorous handoff looks like
A design system handoff is complete when a designer who had no involvement in the project can use the Figma file to produce on-brand work without asking questions. That is the functional test.
The structural components of a complete handoff: a Figma file with named variables, documented components, and organised pages; a brand guidelines document that explains the system in writing, including the reasoning behind the rules; a walkthrough session covering how to use and extend the system; and full transfer of ownership — files, documentation, and any code tokens.
Anything short of this is an incomplete handoff, regardless of how polished the visual output looks.
Common Questions
- How do we brief a studio on design system work?
- Start with what exists — share your current brand assets, guidelines, and any Figma files, however incomplete. Then describe the problem: where is the inconsistency showing up, who is producing output under the brand, and what does a successful outcome look like for your team and your client? The brief does not need to specify the system architecture — that is what you are commissioning expertise to determine.
- What should be included in a design system handoff?
- A complete handoff includes: the Figma file structured for use with named variables and documented components; a brand guidelines document that explains the system in writing; a walkthrough session covering how to use the system and how to extend it; and full transfer of ownership. If the engagement includes code tokens, those should be delivered with documentation on how to integrate them.
- How do we evaluate the quality of a design system before accepting delivery?
- Test it against a new brief. Give the Figma file to a designer who was not involved in the project and ask them to produce something new — a page, a component, a layout. If they can produce on-brand work without asking questions, the system is doing its job. If they struggle or make decisions the system should have made for them, the system is incomplete.
Working on a design system brief?
Tell us about the engagement. We work discreetly with agencies on design system briefs that require specialist depth.
Make an Enquiry