Who we work with / Software teams
For software teams
How your code got good
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.
Show my rangeWhere the story lives
Code alone shows the answer. The history around it reveals the reasoning:
- Pull requests and the review comments on them
- Tickets, bug reports and how each was resolved
- Test and build history
- Specs, architecture documents and release notes
The question of client code
If you build for clients, much of that code may belong to them, and some may need the client's 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. If in doubt, it stays out.
Customer data in tickets and logs
Your customers often come up in tickets, chat threads and logs. The copy swaps names, company names and account details for placeholders, and your developers' names too. You may also keep out whole repos, tools or periods.
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. A buyer sees that whole loop, with developers, customers and company names replaced by placeholders. It is the judgment along the way that makes the history worth licensing.
A typical 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.
Good to know
- Do we have to include every repo?
- No. A small set of active repositories with real reviews can be a good start.
- Who should be on the call?
- Most often the engineering lead or a founder, plus the person who manages your issue tracker and Git hosting.
- Do you need access to our Git hosting?
- No. There is no request for logins or passwords, and your repos are left untouched.
Making 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. You pay nothing.
Curious what your records are worth?
Answer three questions. Within minutes, a License Your Data specialist calls to set up a 15-minute call.
Get my range