Factoryouthe Data Alliance See my range

Who we work with / Software teams

Software teams

How your code got good

Software firms, agencies and MSPs first ask about code their clients own. It gets reviewed during scoping, and anything uncertain stays out.

Show my range

Records with a story to tell

The code on its own shows only the answer. The history around it shows the thinking:

  • Pull requests and the review comments on them
  • Bug reports, tickets and how each one was closed
  • Test and build history
  • Architecture docs, release notes and specs

The concern: code we do not own

If you write software for clients, much of the code may belong to them, and some could require their consent. Ownership gets checked during scoping. Whether any repo may be included comes down to your contracts and your own counsel, and we offer no legal advice. Whatever is uncertain can be left out.

Customer data in tickets and logs

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. You can also leave out any repo, tool or period entirely.

What a buyer is shown

Say a ticket reports that checkout is slow. The query gets rewritten, review turns up an edge case, a test fails, the fix is merged and the release notes say why. A buyer follows that loop end to end, and developers, customers and companies all show as placeholders. The judgment shown along the way is what makes this history worth licensing.

The usual fit

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

Good to know

Do we have to include every repo?
No. A handful of busy repos with genuine reviews may be all you need at first.
Who should be on the call?
Usually a founder or engineering lead, plus whoever administers your Git hosting and 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.

How the copy is made

It starts with an NDA. The de-identified copy comes from License Your Data, your originals never move, and nothing goes out until you approve a sample. Leave out whatever repo, product or client you want. There is no cost to you.

Curious what your records are worth?

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

See my range