Why we started Loom
We are here to turn the design system that now gives you trouble and headaches into a powerful tool.
Xavier Sorribas, founder of Loom.
Design systems matter more than ever, and they have fewer people than ever. AI tools now build interface every day, and they copy whatever they find. The tools around design systems describe what exists and serve it to agents. They assume the system is healthy.
Most systems are not. They drift between Figma, code and documentation, they lose adoption, and the teams that look after them are too small to fix everything by hand. Most organisations cannot start again: they have years of product code and design files, and nobody can order a rewrite.
So we decided to do the work that matters most and that nobody packages: repair the system you have, govern it across tools and teams, and keep it current.
We fix the system, not document it.
Loom is founder-led
Loom was founded by Xavier Sorribas, a design-system and UX Ops leader. Built by a group of design-system specialists. We are a small company based in Singapore, looking for our first design partners.
Our founder, Xavier Sorribas, led Digital & UX Ops for Yara's global design system, Ahua.
We work beside your team, never instead of it
Loom is a service with experts, a framework and a tool together. It is never sold as software that takes over.
- People decide; agents do the routine work. The owner of each area chooses how much agents may do.
- Privacy and ownership. Your code and designs stay yours, in your repository. We do not train models on your data. Our commitment
- Keep the look, raise the structure. Conversion changes how a system is built and governed, not how it looks.
- Truthful by default. Every capability on this site carries an honest status: working, partial or concept.
The first system we converted was our own team's
The first system converted with Loom is Story Atelier, the design system of Seamline, a service design product from our own team. It is a strong system with real gaps. It scored 59 out of 100, "Loose threads". Working After Loom's service it scores 83, "Holding together", with five of eight areas Tightly woven. Working That result is on our copy of the system, scored with Loom's own open rubric. The founder has not yet accepted the records, and Usage and Brand stay low without the product's code and brand material.
We apply our standard to ourselves
Loom's own control area was built before our standard existed. On our own audit it scores 26 out of 100. We are rebuilding it on Loom Base, our own design system, which scores 73. Working
Early pilots found gaps, and we fixed them the same day
On 25 October 2026, two pilots on real, private apps found gaps in how our audit reads apps without a standard structure. We fixed the engine the same day, with tests. Our pilots stay anonymous unless they choose otherwise. Working
Loom is a working name
"Loom" is a working name while we choose the company's final name.
Design systems that never fall behind. That is what we work for.