Don't Do It Yourself

How to Sell Design Agency Data to AI Companies

A design agency sells its data to AI by licensing the design files and the production code behind the work it has shipped, to a buyer like Mercor.

Mercor pays design and web agencies $20,000 to $890,000. It wants three or more years of shipped work from a studio of 10 to 200 people, anywhere.

The hard part isn’t the archive. It’s the rights. Most of what you’ve shipped was made for a client, and your contract may have handed the copyright over at final payment.

For the full process across every industry, start with our guide to how to sell your company’s data to AI companies.

Key takeaways

  • Mercor’s design and web agency listing pays $20,000 to $890,000 and wants the Figma files and the production code for the same projects.
  • That 44x spread is the widest of Mercor’s 25 listings, because rights and archive size move the number so far.
  • Template sites, AI-generated sites and open-source design systems such as Material are all ruled out.
  • Work your employees made belongs to the agency under 17 U.S.C. 201(b). Work a freelancer made doesn’t, unless they signed it over.
  • Copyright moves only by a signed written transfer, under 17 U.S.C. 204(a). A paid invoice isn’t one.
  • Proprietary design systems, WebGL work and browser games raise what you earn.
  • Your files hold other people’s fonts, stock and packages. Those aren’t yours to relicense.

What design data do AI companies buy?

AI companies want the design decision and its result together. Mercor asks for the Figma files and the front-end code for the same projects, with the briefs and revision history that show how the work got there.

Mercor’s design and web agency listing, read November 9, 2026, sorts it like this:

Data Mercor’s view Main risk
Design source files Core of the license Client marks and unreleased work
Front-end code with history Core of the license Keys in the repo, and code the client owns
Briefs, iterations and client feedback Core of the license Named client staff, budgets and rates
Design systems and component libraries, with code Adds to what you earn Third-party component licenses
Award-level websites Adds to what you earn NDAs on work that never launched
Three.js, React Three Fiber and WebGL projects Adds to what you earn Licensed models, textures and HDRIs
Browser games Adds to what you earn Licensed audio and sprite packs
Brand guidelines and presentation decks Adds to what you earn The client’s confidential strategy
Template or AI-generated sites Not a fit Rejected outright
Open-source design systems such as Material Not a fit Rejected outright

Mercor names the studios it wants: product design studios, web and front-end agencies, branding agencies, 3D and WebGL studios, and in-house design teams.

It works with exports from Figma, Adobe Creative Cloud, GitHub, Webflow, Framer and Three.js.

Its opening questions tell you what it’s checking. Do you keep the Figma files and the code for the same projects? How big is the archive? Can you license client work, or only your own?

How much is design agency data worth to AI companies?

Mercor’s listing pays $20,000 to $890,000, and says the figure depends on archive size and rights. Those two words do most of the work: a studio with 200 shipped sites it can’t license is worth less than one with 20 it owns.

The spread is the story. A floor of $20,000 and a ceiling of $890,000 is 44 times, the widest range of the 25 listings on Mercor’s board.

Mercor listing Company earns Size bar
Design and web agency $20,000 to $890,000 10 to 200 employees
Accounting and tax firm $25,000 to $865,000 5 to 200 employees
Investment firm $50,000 to $800,000 5 to 200 employees
Software company $50,000 to $500,000 15 to 500 employees
Publisher or education company $35,000 to $370,000 10 to 500 employees
Consulting and advisory firm $150,000 to $300,000 10 to 500 employees

A design studio’s ceiling beats an accounting firm’s and an investment firm’s. Its floor is among the lowest on the board, tied with cybersecurity companies and call centers.

Polyshares publishes one agency deal: $110,000 to a global marketing agency for its own operational record, on a perpetual exclusive license. That’s the agency’s email and ticket history, not its design work.

Mercor also shows a $55,000 referral fee on this listing. That goes to whoever refers the studio, not to the studio.

Our guide to how much company data is worth to AI compares published payouts across industries.

Who owns the work, you or the client?

It depends who made it and what the contract says. Work your employees made in their jobs belongs to the agency. Work a freelancer made belongs to the freelancer unless they signed it over, and work you assigned to a client belongs to the client.

Three rules decide almost every case.

  • Employees: under 17 U.S.C. 201(b), the employer is the author of a work made for hire and owns the copyright unless a signed agreement says otherwise.
  • Freelancers: a commissioned work counts as made for hire only if it’s used as one of the nine categories in 17 U.S.C. 101, such as a contribution to a collective work or a compilation, and both sides signed a document saying so. A website design usually isn’t on that list.
  • Transfers: 17 U.S.C. 204(a) makes a transfer of copyright invalid unless it’s in writing and signed by the owner. A paid invoice or an email isn’t a transfer.

So sort the archive into three piles before you talk to a buyer.

  1. Yours outright. Your own site, internal tools, your design system, pitch work that never shipped, and anything your staff made with no assignment clause attached.
  2. Yours on paper, the client’s in practice. Work where no signed assignment exists. You hold the copyright, the client holds a license, and the relationship is still worth protecting.
  3. Assigned away. Work your contract transferred at final payment. You need the client’s written clearance, which is what Mercor means by “cleared with clients.”

Check the freelancer side too. If contractors built half your best work and nobody signed an assignment, that work isn’t yours to license, and a buyer’s diligence will find it.

Then check the NDAs. Unlaunched work, killed concepts and anything under an embargo stay out until the client says otherwise.

What about the fonts, stock and packages in your files?

They’re someone else’s property sitting inside your work. A design file is rarely one thing you own: it’s your layout wrapped around licensed type, stock photography, icon sets, 3D models and npm packages.

Before you scope a deal, list every third-party asset your files depend on and read what each license actually permits.

  • Desktop and web font licenses, which usually cover using the font in a design, not passing the font file on
  • Stock photo, video and audio licenses, including the ones your client bought
  • Icon sets and illustration packs
  • 3D models, textures and HDRIs in WebGL projects
  • npm packages and paid UI kits compiled into the front-end build
  • Webflow and Framer templates you started from

Most of these permit use, not resale. Ask the buyer to exclude third-party assets from the license in writing, and to accept files with those assets stripped or swapped.

That clause protects you twice. It keeps you out of a breach, and it stops a buyer claiming you warranted rights you never had.

What has to come out before you ship?

Client identities, anything under NDA, secrets in the repo and personal data in your CMS exports. Design archives leak in an unusual way: the client’s name is in the file name, the folder, the commit message and the brief.
Item What to do
Client names, logos and trademarks Replace with consistent codes, unless the client cleared being named
Unlaunched or killed work under NDA Hold it back until launch or written clearance
API keys, tokens and CMS credentials Remove from the files and from the commit history, not just the current branch
Personal data in CMS and form exports Strip or pseudonymize; this is personal data under the GDPR and state privacy laws
Client budgets, rates and contract terms in briefs Cut; they add nothing a model can learn from
Licensed fonts, stock and 3D assets Exclude by name, or swap for assets you own
Analytics and session exports Leave out; visitor identifiers bring their own consent problem

Keep the codes consistent. “Client A” across 40 projects teaches a model how an agency works over time, and you give up nothing by keeping that link.

Mercor says it signs an NDA, scopes the data and runs the export, removing or protecting personal information. Have your own lead read a sample before delivery anyway.

Our guide to anonymizing data for AI training covers the tools and the standards.

Who buys design and web agency data?

Mercor is the only buyer publishing a payout range for design work itself. Polyshares buys an agency’s operational record instead, and micro1 buys engineering and support process data, which covers how your studio runs rather than what it designed.
  • Mercor: design files, front-end code with history, briefs and revisions, for studios of 10 to 200 people anywhere, with three or more years of shipped work. Pays $20,000 to $890,000.
  • Polyshares: a company’s own operational record, such as email and ticket history. It paid a global marketing agency $110,000. Its licenses are perpetual and exclusive, so read that before signing.
  • micro1: software and engineering, support, sales, legal and operations process data, listed on its data partnerships page, for companies with 30 or more full-time staff. It names no design categories, so this is your delivery process, not your design work. You can apply to micro1 here.

Exclusivity closes doors. Mercor rules out data already licensed exclusively through a broker, so one perpetual exclusive deal can end the conversation with everyone else.

Our list of companies that buy business data for AI has each buyer’s terms.

What are the steps for an agency, start to finish?

A studio licenses its archive in eight steps: count projects that have both files and code, check who owns each one, clear what the client owns, list third-party assets, apply to a buyer, scrub identities and secrets, have counsel review the license, then test a sample.
  1. Count complete projects. Design files and production code for the same work, over three or more years. Mercor asks for both.
  2. Check ownership project by project. Employee or freelancer, assignment signed or not.
  3. Clear the client work you want to include. A short amendment or written consent turns your biggest pile into a licensable one.
  4. Apply to a buyer. Mercor scopes the data on a call and signs an NDA first.
  5. List third-party assets. Fonts, stock, models and paid packages, with the license terms for each.
  6. Scrub identities and secrets. File names, folders, commit messages and briefs, not just the designs.
  7. Have counsel review the license. Our AI data licensing agreement checklist lists the clauses to check, including exclusivity and third-party assets.
  8. Test a sample. Ask someone outside the project to name the client from 20 anonymized files.

Start with the pile you own outright. Your own site, your design system and years of pitch work owe nobody a clearance, and they prove to a buyer that the archive is real.

If your studio shoots video too, our guide to selling video production data to AI covers footage, talent releases and music rights.

Common mistakes when selling design agency data to AI

The most common mistake is assuming the agency owns everything it made. These are the others:

  • Treating a paid invoice as a copyright transfer, when 204(a) wants a signed writing
  • Forgetting that freelance work stayed with the freelancer
  • Including fonts, stock and 3D assets that are licensed for use, not resale
  • Shipping design files without the code, when Mercor wants the pair
  • Offering template or AI-generated sites, which the listing rejects
  • Leaving client names in file names, folders and commit messages after scrubbing the designs
  • Showing unlaunched work that’s still under NDA
  • Signing a perpetual exclusive deal on the whole archive before testing one buyer
  • Reading the $55,000 referral fee as what the studio gets paid

Frequently asked questions

Can a design agency sell its data to AI companies?

Yes, for work it owns or has cleared with the client. Mercor’s listing takes studios of 10 to 200 people anywhere, with three or more years of shipped work, and pays $20,000 to $890,000.

How much do AI companies pay for design agency data?

Mercor publishes $20,000 to $890,000, depending on archive size and rights. Polyshares paid a global marketing agency $110,000 for its operational record. The $55,000 referral fee goes to whoever refers the studio.

Does the client own the design work, or does the agency?

Whoever the contract says. Work by employees belongs to the agency under 17 U.S.C. 201(b), but a signed assignment can move it to the client, and 17 U.S.C. 204(a) means only a signed writing counts.

Can you license work a freelancer designed for you?

Only if they signed it over. A commissioned work is made for hire only in the nine categories listed in 17 U.S.C. 101 and only with a signed agreement, and website design usually isn’t one of them.

What design work do AI companies not want?

Template and AI-generated sites, open-source design systems such as Material, and client work you can’t license. Mercor lists all three as not a fit.

Can you include the fonts and stock images in your design files?

Usually not. Most font and stock licenses cover using the asset in a design, not passing the file on, so exclude third-party assets from the license in writing or swap them for assets you own.

Last updated: November 9, 2026

Disclosure: some links on this page are affiliate links. If you sign up through one, we earn a commission at no extra cost to you.

This isn’t legal advice. Have counsel review your client contracts and any data license before you sign.

Don't Do It Yourself
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.