Industries / Software teams
How your team actually ships software
Tickets, architecture docs, pull requests and review threads trace years of building and maintaining software. Labs are looking for exactly that record. Client code and customer details can stay out.
Check my estimateRecords that help
Records that often qualify
You choose which of these to include. It is always fine to leave any out.
- Architecture docsWhy your systems are built as they are.
- Issues and bug reportsThe way issues get reproduced, prioritized and resolved.
- Pull requests and reviewsThe catches, pushback and reasoning of your reviewers.
- Commit and CI historyWhich changes broke the build and how they got fixed.
The concern we hear most: code we do not own
Agencies and consultancies often build code their clients own. Scoping covers ownership, and client projects can be left out. Whether a client needs to agree is for you and your counsel.
Customers show up in tickets and logs. In the de-identified copy, customer and developer names are replaced with placeholders.
How your copy gets made
Everything starts under an NDA. You are never asked for keys, tokens or passwords. A sample needs your approval before anything goes out, and any repo or product you see as core can be held back.
In brief
What owners usually ask
Is an issue tracker on its own enough?
Sometimes, yes. A well-kept tracker with a long history is a good start.
Is there any cost to us?
No. It is free for you, and requesting an estimate commits you to nothing.
Is our main product required?
No. Any repository can be left out.