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 is reviewed in scoping, and anything you are unsure about stays out.
Check my rangeWhere the story lives
Code by itself just shows the result. The history around it shows the thinking:
- Pull requests and their review comments
- Tickets, bug reports and how each was resolved
- Build and test history
- Specs, architecture documents and release notes
The worry: code that is not ours
If you build for clients, much of that code may belong to them, and some may need the client's permission. 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. 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 buyers really see
Picture a slow checkout reported in a ticket. A developer rewrites a query, a reviewer spots an edge case, a test fails, the fix lands and the release notes explain it. 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. 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.
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 with a long, active codebase may qualify too.
Worth knowing
- Is every repository needed?
- No. A few active repos with real review history can be enough to start.
- Who needs to take part?
- Most often the engineering lead or a founder, plus the person who manages your issue tracker and Git hosting.
- Do you need a way into our Git hosting?
- No. There is no request for logins or passwords, and your repos are left untouched.
Curious what your records are worth?
Three questions are all it takes. License Your Data has a specialist phone you within minutes to arrange a 15-minute call.
See my number