Skip to content

License your agency's project archive to AI labs

Agencies hold years of delivered code across many stacks. Most of it belongs to clients, so title decides what can be licensed.

Price Index, Q4 2026
  • Private repo, standing-rate license$150 to $1,500 per repoMedium confidenceRightmark summary of public code licensing programs, Q3 2026
  • Training task built from real code$200 to $2,000 per taskMedium confidenceEpoch AI, Jan 2026
AI-generated footage

A software agency can license delivered projects to AI labs when it owns the code or the client consents in writing. Repos typically fetch $150 to $1,500 per sale (indicative). Internal tools and your own products carry the cleanest title; client code usually needs a consent letter, which can offer the client a share of proceeds.

  • Private repos typically license for $150 to $1,500 per repo per sale (indicative). Rightmark,
  • Published licensing programs accept client work only with the client's written consent or clear contractual ownership, plus IP assignments from every contributor. Rightmark,

Updated

Timeline
4 to 10 months
from submission to first payment (inferred), then paid again on each further license
You keep
Ownership
Code is non-exclusive by default, so one repo can be licensed to several AI developers.

Why AI buyers want it

Agency archives cover many projects across industries and stacks, written by professional teams under real deadlines and real client feedback. That variety is what coding models need, and buyers look for breadth rather than one more web app. Ownership is the question to settle first, because most of the archive belongs to clients.

Think of it this way

Think of a session musician's recordings. The artist owns the song, but with a signed release the session can be licensed and everyone gets paid.

Client code needs a rights decision before it needs a price

General information, not legal advice.

Repository access or a statement that the agency “built” the software does not answer the title question.

US copyright law starts with the author and allows ownership or individual rights to be transferred, but the details depend on the agreement and facts. 17 USC 201 addresses ownership and transfer Office of the Law Revision Counsel, US House of Representatives, (opens in a new tab). The Copyright Office’s works-made-for-hire circular describes employee work and certain commissioned works under a written agreement, and warns that the concept can have serious consequences US Copyright Office, (opens in a new tab). These are starting points for your own lawyer, not a conclusion about an agency project.

Use the matrix

Use the matrix (table)
Project or componentLikely rights pathEvidence to locateReview route
Agency internal toolAgency ownership or assignmentEmployment and contractor terms, repository historyTechnical scan and title review
Agency productAgency ownership, subject to components and contributorsFormation records, contributor assignments, component listTitle and open-source review
Client deliverable with express assignmentClient may own the relevant rightsStatement of work, master agreement, payment and assignment clausesClient permission or exclude
Client deliverable with retained agency rightsAgency rights may be limited by confidentiality or use termsContract, NDA, client restrictions and scopeYour own lawyer reviews the exact license
Mixed repositoryDifferent folders have different ownersComponent map and agreement for each partSplit scope, carve out or obtain consent
Subcontractor contributionRights depend on the subcontractor agreementWritten assignment or work-made-for-hire languageObtain missing rights or exclude
Unknown or disputed titleNo safe assumptionContract register and evidence logStop and ask your own lawyer

“Likely” is intentional. The matrix helps you route evidence. It is not a legal finding.

What a client consent letter should answer

If a client owns or controls a project, a consent letter should identify the client and agency, name the repositories or data in scope, describe the permitted AI-training or evaluation use, state whether the permission is exclusive, address confidentiality and personal data, identify the term, and say how any proceeds are handled. It should be signed by someone who can bind the client. Do not copy a generic consent template into a contract without your own lawyer’s review.

Also check the edges. A client NDA can limit disclosure even when the agency owns some code. A vendor component can impose its own terms. A contractor may have written rights over a contribution. A repository can contain customer data or credentials that must be removed. The agency’s rights decision should cover the whole delivery, not only the files written by employees.

Worked fictional example

Fictional agency “Sample Studio” reviews three repositories:

Worked fictional example (table)
RepositoryEvidenceDecision
Internal deployment toolEmployee assignments and no client materialCandidate, after Repo Check
Client portalAgreement assigns deliverables to clientRequest written client permission or exclude
Shared integration libraryAgency code plus subcontractor moduleSplit the scope, verify subcontractor assignment and review components

The studio should not present all three as one clean archive. It can prepare the internal tool while the other two follow separate evidence paths. A client consent letter can make a project reviewable, but it does not erase an NDA, privacy duty or third-party license.

Before the appraisal

Make a project list with the rights status, evidence reference, excluded paths and next owner. Keep client names, private code and contract text out of a public worksheet. Run Repo Check locally for the technical report. Use the Trust page to see how title evidence becomes part of an ownership pack. Then use the appraisal for a route estimate. The appraisal is not a substitute for the consent or contract review.

If the evidence cannot answer who can license a repository, mark it unresolved. A narrower, documented scope is more useful than a broad claim that later fails review.

What sets the price

  • Internal tools and your own products first. They carry the cleanest title.
  • Client code where the IP never transferred, per your contract.
  • Client code with a signed consent letter.
  • Full history, tests and reviews, as with any repo.

The estimate on this page prices an agency archive of client repos licensed with consent. Title decides whether a repo can be licensed at all, and a client share comes out of the proceeds.

What blocks a deal, and the fix

Contracts that assign IP to the client
A consent letter that offers the client a share of proceeds can help a client agree. You choose the share.
Client NDAs covering the code
Code under a client NDA needs the client's written release before it can be offered. We draft the request.
Contractors without the right transfer wording
Contributors sign a confirmation that meets their local formalities and names AI training as a field of use.

What owners overlook

  • Title follows a ladder: internal tools, then your own products, then client code you still own, then client code with consent.
  • Engineers between projects can build training tasks from your repos, a route that can pay more than the code alone.

Market evidence

  • Founders who build training tasks for AI labs put the typical price at $200 to $2,000 per task built from real repos.Epoch AI, (opens in a new tab)
  • Published licensing programs exclude any repo with a client claim, an NDA restriction or an unpaid contributor, and the owner gives warranties on title.Rightmark,

How a deal works

  1. Appraise

    Answer a few questions about your repositories. See what affects the price and whether an indicative range is available. No files, no access.

    About a minute

  2. Verify title

    Repo Check runs on your own machine and reports the contributor, license and secrets checks buyers look for. With your IP documents, that report becomes the ownership pack.

    Before any offer

  3. Route

    Each repo goes to the route that fits it: a non-exclusive standing-rate license, or training tasks for repos whose tests run.
  4. Sign and get paid

    You approve the agreement and its scope. On code routes, signing covers future non-exclusive sales, and you can withdraw code that has not been licensed yet. We never hold your passwords. Transfers use scoped, revocable connections your admins approve, or exports.

    About 4 to 10 months from submission to first payment

Questions

Can we license code we built for a client?

Only if you kept the IP or the client consents in writing. Many agency contracts transfer IP on payment, and an unpaid invoice does not by itself give you the rights. We read your contracts and send consent letters for the repos worth licensing; take legal advice on anything unclear.

What do our clients get?

Whatever you agree with them. One structure is a share of your proceeds from their repos, paid when you are paid. You set the share; we put it in the consent letter.

Do we approve each sale, and do our clients?

You approve the agreement and its scope, and each client approves its repos through the consent letter. On code routes, signing covers future non-exclusive sales. You can withdraw any repo that has not been licensed yet.

What could our archive be worth?

Each repo is priced like any private repo, typically $150 to $1,500 per sale, and each further license pays again. The estimate on this page (30 repos at $310 to $1,500 each, per sale) comes to $9,300 to $44,000 at Medium confidence. Indicative estimate, not an offer.

Source: Rightmark,

Can the same repo be licensed more than once?

Yes. Code licenses are non-exclusive by default, so each repo can be licensed to several AI labs and you are paid on each sale. Exclusive deals need a separate signed agreement.

What do we warrant?

That you own each repo or have written permission to license it, with IP assignments from every contributor. On some code agreements the indemnity for ownership claims is uncapped, so leave out any repo whose title is in doubt.

Do you need access to our repositories?

Not for the appraisal. Repo Check runs on your own machine and you share only its report. We never hold your passwords.

Get an indicative range for your Agency project archives.

About a minute to appraise. No files, no access.

Find out what your data could be worth.

Start with an indicative appraisal. No files or system access needed.

Appraise your data

What brings you to Rightmark?