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 estimateUseful records
What tends to qualify
Which of these go in is your call, and skipping any of them is always fine.
- Pull requests and reviewsThe catches, pushback and reasoning of your reviewers.
- Architecture docsThe reasons behind how your systems are built.
- CI and commit historyWhich changes broke the build and how each was fixed.
- Bug reports and issuesThe way issues get reproduced, prioritized and resolved.
The question we hear most: client-owned code
Much of what agencies and consultancies build is owned by their clients. Ownership is worked through in scoping, and any client project can stay out. You and your counsel decide whether a client needs to consent.
Customers show up in tickets and logs. The de-identified copy swaps customer and developer names for placeholders.
How the copy is made
An NDA is in place from the start. Nobody asks for tokens, keys 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
Do we need to include our main product?
No. You can exclude any repo.
Is an issue tracker on its own enough?
Sometimes, yes. A well-kept tracker with a long history is a good start.
Does any of this cost us?
Nothing. You pay no fee, and an estimate request carries no commitment.