That is where our work begins, so we would rather work with agencies than around them.
Your work stays yours
Loom does not change how a system looks. It changes how the system is governed and kept current. After handover, Loom runs in your client's own repository and CI, with their own model key. Owners, rules and exceptions become records in that repository, and agents review pull requests and answer questions under rules the client's people set.
The system you designed keeps its shape, and your client keeps a reason to call you back.
We are looking for two kinds of partner
Design agencies and studios that build design systems for clients. You might introduce a client at handover, run the build while we run the audit and the governance design, or include our setup in your final phase so the client receives a governed system on day one.
A partner in Japan. We are looking for one Japanese design or development firm, or a systems integrator with a design practice, to work with us in Japan. The partner leads Japanese-language workshops and the client relationship. We bring the audit, governance design and the tooling.
How we work with partners
- Truth first. We describe only what runs today, and we ask partners to do the same.
- Client data stays with the client. Loom runs in the client's repository and CI. Nothing is sent to Loom, and partners follow the same rule.
- People decide. Agents do the routine work, and the client's own people own every decision.
- Terms are agreed with each partner. Referral, joint delivery or local contracting each work differently, and we agree the commercial terms in a conversation, not on a web page.
We are early, and we say so
Loom is looking for its first clients and its first partners. Our tools run today on our own systems and two internal pilots on our own products, and no paying client has used them yet. The first partners will shape how this programme works.
If your clients keep asking who will look after the system once you have gone, we would like to talk.