Industries / Software teams
How your team really builds and ships
Tickets, architecture docs, pull requests and review threads trace years of building and maintaining software. That is the record labs want. Client code and customer details can be excluded.
Check my estimateValuable records
What usually qualifies
You choose which of these to include. It is always fine to leave any out.
- Pull requests and reviewsWhat reviewers spot, what they challenge, and the reasons.
- Design docsWhy systems are built the way they are.
- Commit and CI historyWhich changes broke the build and how each was fixed.
- Bugs and issue threadsHow problems get reproduced, prioritized and closed.
The question we hear most: client-owned code
Agencies and consultancies often build code their clients own. Ownership is covered in scoping, and client projects can be excluded. Whether a client needs to agree is for you and your counsel.
Logs and tickets name customers. In the de-identified copy, customer and developer names are replaced with placeholders.
How the copy is made
It all begins under an NDA. Nobody 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.
Short answers
Three things owners ask
Do we need to include our main product?
No. Any repository can be left out.
Will just an issue tracker do?
It can be. A long, well-kept tracker is a good start.
Do we pay anything for this?
No. There is no cost to you, and asking for an estimate does not commit you to anything.