Your Figma files and the code you shipped from them, project by project: AI data buyers list what they pay agencies for that.

Product design studios, web and front-end agencies, branding agencies, 3D and WebGL studios and marketing agencies with years of shipped work: owners, founders and creative and technical directors.

Mercor's listing for design and web agencies puts a deal at $20,000 to $890,000 ("Depends on archive size and rights").

AIData.Broker represents you in selling it: we value your data against public prices, describe it without your name to every buyer whose published rules it meets, at the same time, and help you negotiate the terms, for holders based in the United States, the United Kingdom and Canada. Our fee is 12% of the first $250,000 a sale pays you, and nothing if no sale closes.

3

buyers quoted below on what they want from companies like yours

4 of 5

kinds of record below that the valuation measures or values

4

rights questions to settle before a buyer sees a record

Short answers · figures from the market's records, last reviewed 30 Oct 2026

Can a web design agency sell its Figma files and code to AI companies?

Yes, the work it has the right to license. Mercor's listing for design and web agencies asks for Figma files and production code for the same projects, over several years of shipped work, and puts a deal at $20,000 to $890,000; template sites and client work you cannot license are out. Most agency contracts give the client the deliverables, so your own design systems, tools and the projects your contracts leave to you count first, and the rest needs each client's written clearance. AIData.Broker values an agency's archive for free and, where buyers' published rules fit, runs the sale for it, its fee due only if a sale closes.

What companies like yours hold

What you typically have, where it sits, and whether the valuation can measure or value it. Buyers price what exists together, over how many years, and how well it links.

  • Design files
    Where it sits, and what the evidence shows
    Figma or Adobe files for every project, with their versions, components and the design system behind them.
    How the valuation reads it
    From your answers
  • Production code
    Where it sits, and what the evidence shows
    The front-end code you shipped from those designs, in GitHub with its history: sites, products and 3D or WebGL work.
    How the valuation reads it
    Measured from your code history exportCounted with code with its historyValue a codebasepriced on its own, per repository
  • Briefs, revisions and client feedback
    Where it sits, and what the evidence shows
    The brief, every round of comments and the decision behind each change, in email, Slack or the project tool.
    How the valuation reads it
    Measured from your documents exportCounted with documents and knowledge
  • Project and client records
    Where it sits, and what the evidence shows
    Proposals, statements of work, timelines and invoices in your project and finance tools.
    How the valuation reads it
    Measured from your documents exportCounted with documents and knowledge
  • Campaign and performance records
    Where it sits, and what the evidence shows
    For marketing agencies: briefs, copy, ad performance and client reports over the years.
    How the valuation reads it
    Measured from a CSV or JSON export

What buyers say they want from companies like you

In their own words, from their own pages or from reporting on what they bought. Each opens its source.

  • “License design systems, websites and the code behind them.”
    Mercor, its listing "Design & Web Agency"Its own page, 30 Oct 2026
  • “Figma files and production code for the same projects. A portfolio of shipped sites or products over 3+ years. The right to license the work, either your own or cleared with clients”
    Mercor, what the listing asks forIts own page, 30 Oct 2026
  • “Proprietary design systems and component libraries, with code. Award-level websites. Three.js, React Three Fiber or WebGL projects. Browser games. Briefs, iterations and client feedback. Brand guidelines and presentation decks”
    Mercor, what it would also likeIts own page, 30 Oct 2026
  • “Creative & design Briefs, drafts, revisions, final assets and client feedback”
    HUMXN Research LabsIts own page, 31 Oct 2026
  • “Marketing & agencies Campaign briefs, copy, ad performance, client reporting”
    HUMXN Research LabsIts own page, 31 Oct 2026
  • “Industries of interest ... Marketing Agencies”
    Scale AIIts own page, 31 Oct 2026

What raises the value

  • The design file and the code shipped from it, kept together for the same project.
  • The brief and every round of revision with the reason for the change, not only the final files.
  • Your own design systems and component libraries, which are yours outright.
  • Several years of shipped work in the same tools.
  • History the listing measures in its own words: "3+ years of shipped work".

What lowers the value

  • What the listing rules out: "Template or AI-generated sites", "Open-source design systems such as Material", "Client work you can't license".
  • Portfolio images and case-study pages alone.
  • Sites built from templates or page builders with little of your own design or code.

A line that quotes a buyer names it. The others are our checklist, drawn from the factors buyers state in general: no buyer publishes how much each one moves a price. How often each factor matters across 156 kinds of data.

The rights to settle first

These stop a sale more often than price does. Each can be settled before any buyer sees a record.

The full rights checklist
  • Client work is usually the client's: most agency contracts assign the deliverables, and sometimes the working files, to the client. Count in only what your contracts leave to you, or what each client clears in writing.
  • Fonts, stock images, icon sets and plugins inside the files come under their own licences and stay out.
  • Clients' names, logos and confidential briefs come out or are cleared before anything is offered.
  • Export access is not a licence: "Your ability to export a record does not by itself establish permission to license it" (Nyne).

What is already on offer from companies like you

Read this morning from the brokers' and marketplaces' own catalogues. A buyer compares your records with these; settled rights, more years and more linked systems are what set one apart.

Every lot on offer

27

lots on offer like yours

6 years

of history in the middle of them

4 of 25

say the rights are settled

What holders like you ask

Our client contracts give the client the work. What is left to sell?
Often more than you think: your own design systems, component libraries, internal tools, templates and the projects whose contracts leave the working files with you, plus whatever a client clears in writing. The listing names it as a condition: "The right to license the work, either your own or cleared with clients".
What is a design agency's data worth to an AI buyer?
Mercor's listing for design and web agencies puts a deal at $20,000 to $890,000 ("Depends on archive size and rights"). It asks for 10–200 employees (Anywhere). What moves an offer within the range is what the listing names: how complete the records are, how far back they go and whether you can license them.
What exactly does the buyer ask for?
Mercor's listing asks for "Figma files and production code for the same projects", "A portfolio of shipped sites or products over 3+ years", "The right to license the work, either your own or cleared with clients". It would also like "Proprietary design systems and component libraries, with code", "Award-level websites", "Three.js, React Three Fiber or WebGL projects", "Browser games", "Briefs, iterations and client feedback", "Brand guidelines and presentation decks". It rules out "Template or AI-generated sites", "Open-source design systems such as Material", "Client work you can't license".
What will a buyer ask us first?
Mercor's listing names its first questions: "Do you keep Figma files and code for the same projects?", "How many shipped sites or design systems are in your archive?", "Can you license client work, or only your own?", "Do you have 3D, WebGL or game projects?". Have the answers before you start.
How do we sell through you?
Start with the valuation. It reads what you hold against public prices and against the rules each buyer publishes; then either we run the sale for you, describing your records without your name to every buyer whose rules they meet, or, where a buyer's own programme fits you better, we introduce you to it, free for you. The holder pays us a fee fixed in the mandate, and only if a sale closes. Besides that, a buyer pays us only through its own published referral programme when we introduce you to it, out of its own money: you see the most it may pay us before we introduce you, and which buyer it is once we have.

In this topic

What sells

  1. Start hereWhich data do AI labs want, and who holds it?Each kind of data the market prices, the businesses that hold it, what labs are asking for now and what they turn away.
  2. GuideWhat Are RL Environments? Who Builds, Buys and Prices ThemAn RL environment is a sandbox where an AI agent attempts tasks with tools and a verifier scores each try. Who builds them, who buys them and what they cost.
  3. GuideHow to Sell Your Videos for AI Training: Prices and BuyersAI companies pay to license your videos for training, by the hour or the minute. What each buyer pays, which footage sells, and the rights every frame needs.
  4. GuideSelling audio and speech recordings for AI trainingWhat AI companies pay for call recordings, podcasts, radio, meeting audio and voice data, why archive audio sells cheapest, and the recording-consent law state by state.
  5. GuideSelling photos and image archives for AI trainingWho buys photos for AI training, what stock agencies pay contributors (shares and bonuses, not prices), what image archives sell for, consent and releases agency by agency, and how to prepare a library for a sale.
  6. GuideSelling your company's Slack data for AI training: what the export allows and who buys itYes, a company can license its Slack history to AI buyers. What Slack's export and API terms allow on each plan, whose messages are inside, what buyers pay and the steps.
  7. GuideSelling company documents and shared drives for AI trainingYes, a company can license its documents, wikis and shared drives to AI buyers. Which documents they pay for, what Google Workspace, Microsoft 365, Confluence and Notion let you export, who owns the files, and the steps.
  8. GuideSelling customer support tickets and chats for AI trainingOften yes, after three checks: your customer contracts and privacy notice, your help desk's export terms, and removing personal data. What buyers want in a ticket, what records with tickets fetch, and the steps.
  9. GuideSelling a company's email archive for AI training: exports, consent and priceYes, a company can license its own email to AI buyers. How Google Workspace and Microsoft 365 let you export a whole organisation's mail, the deadlines when a subscription lapses, the law on staff and customer messages, and what buyers pay.
  10. GuideSelling CRM data for AI training: Salesforce and HubSpot records, consent and priceA company can license its CRM history to AI buyers, but CRM records are customer data first. What buyers value in Salesforce and HubSpot, how each lets you export, why the contact list usually stays out, and what CRM history fetches.
  11. GuideSelling meeting recordings and transcripts for AI trainingCan a company license its Zoom, Google Meet or Teams recordings and notetaker transcripts to AI buyers? Recording consent state by state, what Zoom's terms allow, what meeting audio and transcripts fetch, and the steps.
  12. GuideSelling accounting and finance records for AI training: QuickBooks, Xero and NetSuiteA company can license its accounting history to AI buyers, but finance records carry customers', suppliers' and lenders' confidential terms and staff payroll. What buyers value in QuickBooks, Xero and NetSuite books, how each lets you export, what has to come out, and what finance records fetch.
  13. GuideSelling Jira and Linear issue history for AI trainingYes, a company can license its Jira or Linear issue history to AI buyers. It is valued when each issue links to the code that closed it. What each export keeps, what buyers ask for, and what it fetches.
  14. GuideSelling design files and product history for AI training: Figma and beyondYes, a company can license its Figma files and design history to AI buyers. What buyers value, what Figma lets you export, client work, fonts and other assets that are not yours, who owns the designs, and the steps.
  15. GuideSelling IT service desk records for AI training: ServiceNow tickets, runbooks and incidentsOften yes. IT tickets, incidents and runbooks teach agents to resolve real problems, once credentials, hostnames and people are removed. What ServiceNow and Jira Service Management let you export, what buyers ask for, and what the records fetch.
  16. GuideSelling Books to AI Companies: Prices, Deals and Who Gets PaidAI companies license books by the title, mostly from publishers' backlists. What deals paid per book, how much reaches the author, and how to sell a catalogue.
  17. GuideSelling Game Code and Game Data to AI CompaniesAI companies license game studios' code with its history and gameplay recorded with the player's inputs. Who buys, what studios are offered, and what you may not sell.
  18. GuideSelling a company's paper archive for AI trainingYes, a paper archive can be licensed to AI buyers once it is scanned into searchable text. What scanning costs, what text fetches, who owns old records, and the steps.
  19. GuideSelling robot and first-person video data for AI trainingRobotics companies pay for first-person video and teleoperation data, mostly recorded to their spec. What each kind pays, why bulk footage collapsed, consent, and the steps.
  20. GuideSelling sales call recordings and sales emails for AI trainingYes, if each call was lawfully recorded and the prospects come out. Who buys sales calls and sales emails, what they fetch, and the consent and AI-agent rules.
  21. GuideSelling CAD files and engineering drawings for AI trainingYes, if the company owns the designs and export rules allow it. Who buys CAD files and drawings for AI training, what they pay, and what to check first.
  22. GuideCan You Sell AI-Generated or AI-Assisted Data for AI Training?Rarely if a model made it: buyers screen generated data out. Work people made with AI tools still sells when you can show which parts a model wrote.
  23. GuideAI Content Licensing: How Publishers Get Paid, and How MuchAI companies license content to train models or to ground answers. What publishers have been paid, which platforms pay per use, and how to choose a route.
  24. PageWhere data comes fromWho holds each kind of data, how much exists and how it reaches buyers.
  25. RegisterCompanies closingCompanies closing, sold or gone dark, and the records they leave.

See what you hold, measured on your own computer. Only the counts leave it.

Value your company's recordsCheck an offer you have