Software and tech

The story of how your code improved

The first question from software companies, agencies and MSPs is about client-owned code. It gets reviewed during scoping, and anything uncertain stays out.

See my number

Records that tell the story

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

Pull requests and their review comments
Bug reports, tickets and how each one was closed
History of builds and tests
Architecture docs, release notes and specs

The worry: code that is not ours

If you write software for clients, much of the code may belong to them, and some could require their consent. Who owns what is reviewed in scoping. Your contracts decide whether a particular repo can go in, which your own counsel should judge; legal advice is not something we give. Anything uncertain can stay out.

Tickets, logs and customer data

Tickets, chat threads and logs often mention your customers. The copy swaps names, company names and account details for placeholders, and your developers' names too. Any repo, tool or time period can also be excluded completely.

What a buyer is shown

Picture a slow checkout reported in a ticket. The query gets rewritten, review turns up an edge case, a test fails, the fix is merged and the release notes say why. The buyer sees the full loop, with placeholders for developers, customers and company names. What gives the history its licensing value is the judgment at each step.

How we build the copy

First comes an NDA. License Your Data makes the de-identified copy, originals stay in your systems, and a sample comes to you for approval first. Leave out whatever repo, product or client you want. There is no cost to you.

The usual fit

MSPs, agencies and software firms that have 20 or more full-time staff and hold 3 or more years of history across Git, team chat and an issue tracker. Smaller teams may also qualify if their codebase is long lived and active.

Worth knowing

Do we have to include every repo?: No. A handful of busy repos with genuine reviews may be all you need at first.
Who needs to take part?: Usually a founder or engineering lead, plus whoever administers your Git hosting and issue tracker.
Do you need a way into our Git hosting?: No. Nobody asks for a password or a login, and your repos stay exactly as they are.

Want to know what your records could fetch?

Three questions are all it takes. Within minutes, a License Your Data specialist calls to set up a 15-minute call.

Check my range