Can a design or web agency sell its data to AI companies?
Partly. An agency keeps a record of how vague requests turn into finished work: the brief, the first draft, the client reaction and the version after. That process is the interesting part. The finished design usually belongs to the client, so the question for an agency is which of its own records are separate from the client's property.
What a design or web agency has that is licensable
| Briefs and scoping notes | How a client described what they wanted, the questions the agency asked back and the scope that was agreed. Plain writing in many different industries. |
| Revision rounds | A draft, the comments on it and the next version. A run of changes with reasons attached shows how taste is turned into instructions. |
| Client feedback and approval emails | Short, often unclear messages such as "make it pop", matched to what the designer did in response. |
| Project threads and status notes | Internal discussion about timing, trade-offs and who does what, in a project tool or chat. |
| Handoff files and build documentation | Style guides, component notes, ticket lists and developer handoff documents, once client names and brand assets are removed. |
Where the records live
Design work is split across tools: design files in a shared canvas, tasks in a project board, feedback in email or comment threads, and finished sites in a code repository. The writing about the work is easier to license than the work.
We ask which systems hold briefs, comments and revision history, and how many years each goes back. An agency whose feedback lives only in clients' own tools may hold less than it thinks.
The client usually owns the output
Most agency contracts either assign the finished work to the client on payment or give the client a license to it. Either way, the agency often cannot hand the deliverable to a third party. What it normally does hold is its own working material: its notes, its process documents, its templates and its internal discussion.
Many contracts also include a confidentiality clause covering what the client shared, such as unreleased products and pricing. Read yours before pulling anything. Where a clause is unclear, ask counsel. This is general background and does not replace your own counsel.
Stock, fonts and third-party code
Agencies use licensed fonts, stock photos, plugins and themes. Those come with terms that often bar reuse outside the project they were bought for. Files that embed them are checked, or the assets are stripped, before anything leaves.
What stays out for an agency
| Finished client designs and brand assets | Logos, layouts and copy that the client owns are not part of a package unless the client agrees in writing. |
| Client names and unreleased plans | Company names, launch dates, product details and budgets are replaced, or the thread is dropped. |
| Licensed fonts, stock images and themes | Anything bought under a license that limits reuse stays with the license. |
| Login details and hosting credentials | Project threads often contain passwords and access links. They are scanned for and deleted first. |
More on this: how personal details are removed, who carries the risk and how you get paid.
A worked case
A branding and web agency with twenty-five staff has seven years of briefs, comment threads and project board history. Its first package pairs each brief with the feedback rounds and the notes on what changed, with client names and brand details replaced. Finished designs and source files are not included. The agency's leadership reads the sample before any decision.
Questions owners ask about this
Can we license a case study we published?
The public text is ours to describe, but the client may hold the rights to the images and the results quoted. A short check with the client settles it.
Do we need every client to agree?
Not for records that hold only the agency's own words with client details removed. For anything that carries client content, the contract decides, and written consent is the cleanest answer.
What about work done by freelancers?
A freelancer's notes and files may still be theirs if the contract did not assign them. The agency confirms its agreements before including that material.
Is a small studio too small?
The check looks at how many people work at computers and how much history exists. A small studio with long, well-kept threads can still be assessed, and we say so early if it falls short.
Didn't find your question? Ask us directly.
Keep reading
Records to look at first
- Team chat: Slack and Teams threads, where one person must stay one person and direct messages stay out.
- Project and task history: Jira, Asana, Linear, Monday, Trello, ClickUp and Airtable comments and status changes, not task titles.
- Client deliverables and drafts: Each draft beside its final version with the comments that changed it, kept only where the client agrees.
- Google Drive export: How to keep the comments and the version history when documents leave Google Drive.
- Slack data export: Channels, threads and the settings that decide how much of your chat history can leave.
- Gmail data export: Shared mailboxes, labels and the export routes that fit a Google Workspace domain.
Other industries
- Consulting firms: The draft beside the final report and the firm’s own methods, with every client kept out unless they agree.