Zarlent

Can a design or web agency sell or license its data to AI companies?

Yes, for work the agency owns. Buyers list design systems, sites and code from design and web agencies with 10 to 200 staff, with a published band of $750K to $1M as of November 2026. Most client work belongs to the client, which is the main limit.

No buyer pays to be mentioned

What could your company's records earn? Get a range in 30 seconds. Free, no obligation.

Can a design agency license its work to AI companies?

Yes, but first find out who owns it. Buyers publish a program for design and web agencies and list design systems, sites and code as what they want, for agencies of 10 to 200 staff, with a ceiling in the $750K to $1M band (published buyer listing, read 20 Nov 2026). See the price table by industry.

Agencies create a specific kind of record. A design system holds the reasons for each choice: spacing, color, component rules and accessibility notes. A finished site shows those rules applied. The code shows how they were built. Together they teach a model how designers turn a brief into a working product.

What are agency records worth?

ItemFigureSource
Published price band per agency$750K to $1MPublished buyer listing, read 20 Nov 2026
Staff band buyers list10 to 200Same listing
Records namedDesign systems, sites, codeSame listing
Who is the author of commissioned workThe commissioning party, but only if a signed written agreement says "work made for hire" and the work is in a listed categoryUS Copyright Office, Circular 30, read 21 Nov 2026

The agency's own materials hold the most weight in an offer. That includes internal design systems, template libraries, and pitch work that no client bought. A calculator range shows where you sit.

Which records do buyers want from an agency?

  • Design systems: component libraries, style guides, tokens, usage rules and the files behind them.
  • Sites: finished pages and their content structure.
  • Code: front-end and back-end source for builds, with commit history.

Version history is useful. It shows design reviews, client feedback and how a page changed between rounds, if that feedback can be separated from client confidential detail.

Which systems hold agency records?

Design files sit in a design tool and its cloud, assets on a shared drive, code in version control, and briefs and feedback in a project management tool, email and chat. Contracts live in a separate folder, often unsigned copies in email. Collect contracts first, because they decide what is in scope. See preparing company data.

What can a design agency not share?

  1. Client-owned work. The US Copyright Office explains that a work is made for hire when an employee creates it within regular duties, or when certain types of work are commissioned under an express written agreement. If both of the second route's conditions are met, including a signed agreement stating work made for hire, the commissioning party is the author and copyright owner (Circular 30, read 21 Nov 2026). Many agency contracts say the client owns the final deliverables. If yours do, the agency cannot license them. Read each contract.
  2. Client confidential material. Unreleased products, strategy documents, customer data and login details in files or code history stay out.
  3. Stock and licensed assets. Fonts, photos and icon sets bought for a client carry their own licenses.
  4. Freelancer contributions. Work by contractors without a signed assignment may belong to them.
  5. Personal data in sites. Customer lists, form entries and test accounts inside code or content need removal. See de-identification.

This page is general information, not legal advice.

How should an agency prepare?

Sort projects into three piles: the agency owns it, the client owns it, unclear. Offer only the first. Pull internal design systems, templates, pitch decks that were not bought, and any code the agency wrote for itself. Clean secrets out of code history. Then read the contract clauses to check.

What does a sample record look like?

Three samples of the design system, site and code records this page lists, tied to review rounds and outcomes.

Design system record
Components
48 components, 120 style tokens
Rules documented
Spacing, color and accessibility notes
Version
Release 3.2 after 5 revisions
Outcome
Adopted across 4 client builds
Personal details
Client names removed; agency-owned material only
Finished site record
Pages
32 pages, 9 templates
Content structure
Linked to its design system version
Feedback rounds
3 rounds, 41 comments
Outcome
Launched on schedule, May 2025
Personal details
Client confidential detail separated; contract checked
Code with commit history
Commits
612 commits over 5 months
Linked feedback
94 commits tied to review comments
Reverted change
Menu rebuilt after round 2 feedback
Outcome
Build approved for release
Personal details
Developer names replaced with roles

Illustrative samples: invented values, real record types.

What has company data sold for?

We record 40 public data sales, each with its price, date and source. Search all 40 recorded data sales.

Questions

Can I license sites I built for clients?

Only if your contract leaves you the rights, or the client agrees in writing. Most agencies cannot, so start with internal work.

Is a template library worth anything?

It is the best fit for this page. You own it, it carries no client information, and it shows your method.

Do small studios under 10 staff qualify?

The listing starts at 10. Smaller studios can ask but should expect lower offers.

Does the buyer see my clients' names?

Only if you leave them in. Remove client names and brand marks before any export.

Sources