Yes, for work the agency owns or has cleared with its clients. AI buyers ask for Figma files together with the production code for the same projects, from a portfolio of shipped work over three or more years. Client contracts decide most of it: if the contract assigned the work to the client, the agency needs the client's written permission. Template sites, AI-generated sites and open-source design systems do not count.
- The pair is the product: the design file and the code that shipped from it.
- Proprietary design systems, award-level sites and 3D or WebGL work are in highest demand.
- Briefs, iterations and client feedback add value.
- Who owns each project is a contract question, answered project by project.
What do AI buyers ask a design or web agency for?
The design file and the code that shipped from it. A public listing for design and web agencies (one buyer's public listing, read 15 November 2026) asks for "Figma files and production code for the same projects", "A portfolio of shipped sites or products over 3+ years" and "The right to license the work, either your own or cleared with clients".
It also says what is wanted most: "Proprietary design systems, award-quality websites, and 3D or WebGL projects are in the highest demand, especially with briefs and revision history." A design alone shows what something should look like. The matching code shows how a professional team built it. Together they are an example of the whole job.
| Record | Form buyers ask for | What it pairs with |
|---|---|---|
| Design files | The Figma file with its pages, components and version history | The repository for the same project |
| Production code | The front-end repository with its commit history | The design file and the live URL |
| Design systems | Component library, tokens and documentation | The coded component package |
| 3D and WebGL work | Three.js or React Three Fiber source with models and shaders | The brief and the shipped build |
| Revision trail | Brief, rounds of iterations and client feedback | The final design it led to |
| Brand work | Guidelines and presentation decks | The identity files they describe |
What a .fig file holds and how to export one is covered in the FIG file guide. A brief that buyers can read years later is covered in the creative brief template.
Which agencies qualify?
The listing names "Product design studios, web and front-end agencies, branding agencies, 3D and WebGL studios, in-house design teams", with 10 to 200 employees and no country limit.
The practical test is whether you can open one project and hand over three things for it: the design file, the code, and proof you may license both. An agency that kept designs but lost the repositories, or kept code but designed in a client's Figma account, has half of the pair.
Who owns the work: the agency or the client?
It depends on the contract for each project. The starting point is copyright law. Work by the agency's employees belongs to the agency, because for a work made for hire "the employer or other person for whom the work was prepared is considered the author" (17 U.S.C. 201). Work by freelancers belongs to them unless a signed writing transfers it: a transfer "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" (17 U.S.C. 204).
Then the client contract moves it again. Many agency agreements assign the final deliverables to the client on payment and leave the agency its tools, methods and unused concepts. Under a contract like that the shipped site is the client's, and the agency needs the client's written permission to license it. The agency's own design system, internal tools and studio projects are usually the cleanest part of the archive.
Confidentiality clauses are a second gate. A project under a non-disclosure agreement may be off limits even where the agency kept the copyright. The same split applies to engineering firms, as the guide to client CAD files at design consultancies shows. This page is general information, not legal advice.
| Work | Usual owner | What to check |
|---|---|---|
| Agency's own site, design system and studio projects | The agency | Freelancer agreements |
| Client deliverables, assigned on payment | The client | Whether the client will give written permission |
| Client deliverables, licensed to the client | The agency | Exclusivity and confidentiality terms |
| Unused concepts and rejected rounds | Often the agency | What the contract says about work not selected |
| Freelancer contributions | The freelancer, unless assigned in writing | The signed agreement |
Does Figma already train AI on your files?
It depends on the plan and on a setting an admin controls. Figma's help page says "By default, content training is turned on for Starter teams" and "By default, content training is turned on for Professional teams", while "By default, content training is turned off on Organization and Enterprise plans" (Figma help).
Figma's AI Terms describe what the setting does: when it is on, "Figma may use Customer Content to maintain, improve, and enhance Figma's products and services by training machine learning and artificial intelligence algorithms and models" (Figma AI Terms).
Two things follow for an agency. Check the setting, because a client contract may promise that client work is not used this way. And treat it as a separate matter from a licence you sign: the setting is a term of using the tool, while a licence is a deal you negotiate with a buyer for files you choose.
Why do template, AI-generated and open-source work not count?
The listing excludes "Template or AI-generated sites" and "Open-source design systems such as Material". Each fails for a different reason.
A template site is someone else's design with your content in it, so the valuable part is not yours to license. An open-source design system belongs to its licensors and is already public. AI-generated work has an ownership gap of its own: the Copyright Office says "it is well-established that copyright can protect only material that is the product of human creativity", and that when an AI system determines the expressive elements of its output, "the generated material is not the product of human authorship" (Copyright Office guidance).
Mixed projects are common. A site built on an open-source component library with a custom design layer on top can still qualify for the custom part. Mark which parts are yours.
What makes an agency archive worth more or less
The listing says its range "Depends on archive size and rights". Within that, the pairing and the trail matter most.
| Raises value | Lowers value |
|---|---|
| Design file and repository for the same project, both with history | Design or code alone |
| A proprietary design system with coded components | A themed copy of a public system |
| Briefs, iterations and client feedback kept with the project | Final files only |
| Sites that shipped and can be shown live or archived | Pitch work that never launched |
| Written client permission, project by project | Rights assumed from silence |
Example: an agency sorts five years of projects
A fictional web agency with 35 staff lists its shipped projects and sorts them by what it holds and what it may license.
| Group | Projects | Design + code? | Rights | Decision |
|---|---|---|---|---|
| Agency site and internal design system | 1 system, 3 site versions | Both, with history | Agency-owned | Ready |
| Client sites, contract assigns work to client | 41 | Both for 33 | Client-owned | Ask the 33 clients; 12 agree in writing |
| Client sites, agency kept ownership | 9 | Both for 9 | Agency-owned, two under NDA | Include 7 |
| WebGL campaign pieces | 6 | Code only for 2 | Mixed | Include 4 after client permission |
| Template-based sites | 18 | Not applicable | Theme belongs to its vendor | Excluded |
Fictional example. Of 75 projects, 24 end up licensable. That ratio is normal: the count that matters is the cleared pairs, not the portfolio.
What a licence usually allows and how long it takes
A licence for design files and code usually lets the buyer copy the material and use it to train and test its own models. It usually bars the buyer from publishing the files or shipping your designs as its own. Repositories need a pass for credentials, API keys and third-party packages before delivery.
Ask whether the licence is exclusive, whether client names are removed, and whether the buyer can use the work to evaluate models as well as train them. The data licensing agreement guide covers the clauses and the source code guide covers what buyers check in a repository. There is no standard timetable. The order is usually the same: a written description of the archive, a small sample, a rights review, agreed terms, then delivery. The rights review sets the pace. Client permissions are the slow part for an agency.
Common mistakes agencies make
Most come from treating the portfolio as the archive.
- Counting every project in the portfolio, including work the client owns.
- Offering design files without the code, or code without the design.
- Designing in the client's Figma account and losing access at handover.
- Deleting repository history or squashing it to one commit before sharing.
- Leaving API keys, environment files and client credentials in the repository.
- Including freelancers' work with no signed assignment.
- Asking clients for permission by a vague email, with no list of what is covered.
An agency archive as a data asset
One published company range for design and web agencies runs from $20,000 to $890,000 (one buyer's public listings, read 15 November 2026). Read it as a published ceiling, not as a typical outcome. The listing says the figure "Depends on archive size and rights", and client rights cut most archives down.
Start with the projects you own outright, then list the clients worth asking. An agency that is being sold or closed can treat the cleared archive as one more asset. Brands and studios with image archives have their own page: licensing product and campaign photos. Game studios are covered in the game studio guide. Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
Can a design agency license client work to AI companies?
Only with the right to do so. If the contract assigned the work to the client, the agency needs the client's written permission. If the agency kept ownership, it still has to respect confidentiality and exclusivity terms. The agency's own systems and studio projects are the cleanest part.
Who owns the design files and code, the agency or the client?
The contract decides. Under copyright law employees' work belongs to the agency and freelancers' work belongs to them unless assigned in a signed writing. Many agency contracts then assign final deliverables to the client on payment.
Why do AI buyers want the Figma file and the code together?
The pair shows how a design became a working product. A public listing read on 15 November 2026 asks for Figma files and production code for the same projects, and says briefs and revision history make the work more valuable.
Does Figma use our design files to train its AI?
Figma's help page says content training is on by default for Starter and Professional teams and off by default on Organization and Enterprise plans. An admin can change it. Check the setting against what your client contracts promise.
Do open-source or template-based sites count?
No. The listing excludes template or AI-generated sites and open-source design systems. A custom design layer built on top of an open-source library can still count for the custom part.
Is an agency archive still worth something when the agency closes?
It can be, for the projects the agency owns or has cleared. The work has to be exported while the Figma and code hosting accounts are still active, and someone with authority over the agency's assets has to sign.
Sources and further reading
- 17 U.S.C. 201: ownership of copyright (initial ownership, works made for hire)
- 17 U.S.C. 204: execution of transfers of copyright ownership
- Figma help: manage AI settings and content training for your team or organization
- Figma: AI Terms
- U.S. Copyright Office: registration guidance for works containing AI-generated material (88 FR 16190)
