Industries / Software teams
How your team actually ships software
Review threads, pull requests, tickets and architecture docs show software being built and maintained over years. That is the record labs want. Client code and customer details can be excluded.
Check my estimateValuable records
Records that often qualify
Which of these go in is your call, and skipping any of them is always fine.
- Bug reports and issuesThe way issues get reproduced, prioritized and resolved.
- Design docsWhy systems are built the way they are.
- CI and commit historyWhich changes broke the build and how they got fixed.
- Reviews and pull requestsWhat reviewers spot, what they challenge, and the reasons.
The question we hear most: client-owned code
Agencies and consultancies frequently write code that belongs to clients. Ownership is covered in scoping, and client projects can be excluded. You and your counsel decide whether a client needs to consent.
Logs and tickets name customers. In the de-identified copy, customer and developer names are replaced with placeholders.
How your copy gets made
It all begins under an NDA. No one asks for tokens, keys or passwords. You approve a sample before anything goes out, and you can hold back any repo or product you consider core.
Quick answers
Three things owners ask
Do we need to include our main product?
No. Any repo can stay out.
Is there any cost to us?
No. It is free for you, and requesting an estimate commits you to nothing.
Is an issue tracker on its own enough?
It can be. A long, well-kept tracker is a good start.