// Industries · IT and software companies
Every pull request is a decision, reviewed in writing.
Software teams write down how they work: tickets, specs, code review threads, incident reviews, and the chat in between. Years of that history, linked across Jira, GitHub and Slack, is the kind of trail AI developers review. We help you see whether yours is ready.
The systems your team already writes in
Nothing new to install. What counts is years of work on the same systems, connected across them.
// Your written record
Years of connected work
8 systems, one trail
What's in, and what stays out
Typically licensable
- Pull requests with review comments
- Tickets, specs and design docs
- Incident reviews and runbooks
- Internal chat about how work gets done
Stays out
- Customer data and production records
- Credentials, keys and secrets
- Client-owned or licensed third-party code
- Code written by AI tools
Who counts toward the 30
Count engineers, product managers, designers, support and operations staff who work in your tools daily.
Questions owners ask
- Is our code part of this?
- It can be, when you own it outright and it has a real review history. Client-owned and licensed third-party code stays out. Code repositories also have a program of their own on the other programs page.
- Our tickets mention customers.
- Customer data stays out; that's agreed in writing before anything moves. What's evaluated is how your team works.
- We moved from GitLab to GitHub.
- Only years on the current system count, unless the history came across intact. Tell us both on the form, with the years on each.
Book your data consultation
Tell us about your company. A data specialist calls you by the next business day. Nothing you tell us commits you to anything.