For software teams

The story of how your code improved

Software firms, agencies and MSPs first ask about code their clients own. It is reviewed in scoping, and anything you are unsure about stays out.

Check my range

Records that tell the story

Code by itself just shows the result. The history around it shows the thinking:

Pull requests and their review comments
Bug reports and tickets, with how each got closed
History of builds and tests
Specs, architecture documents and release notes

The concern: code we do not own

When you build for clients, a lot of the code may be theirs, and some may need their permission. Ownership gets checked during scoping. Your contracts decide whether a particular repo can go in, which your own counsel should judge; legal advice is not something we give. Whatever is uncertain can be left out.

Customer data in tickets and logs

Your customers often come up in tickets, chat threads and logs. In the copy, people, companies, account details and your developers' names all become placeholders. Any repo, tool or time period can also be excluded completely.

What buyers really see

Imagine a ticket about a slow checkout. A developer reworks a query, a reviewer catches an edge case, a test breaks, the fix ships and the release notes describe it. The buyer sees the full loop, with placeholders for developers, customers and company names. It is the judgment along the way that makes the history worth licensing.

How we build the copy

An NDA comes first. License Your Data makes the de-identified copy, originals stay in your systems, and a sample comes to you for approval first. Any repo, product or client can be excluded. It costs you nothing.

The usual fit

Software companies, agencies and MSPs with 20 or more full-time staff and 3 or more years of history in Git, an issue tracker and team chat. Smaller teams may also qualify if their codebase is long lived and active.

Quick answers

Do we have to include every repo?: No. A few active repos with real review history can be enough to start.
Who should be on the call?: Normally a founder or engineering lead, along with whoever administers Git hosting and the issue tracker.
Do you need access to our Git hosting?: No. Nobody asks for a password or a login, and your repos stay exactly as they are.

Wondering what your files could be worth?

Answer three questions. Within minutes, a License Your Data specialist calls to set up a 15-minute call.

See my number