Software and SaaS data
Your support tickets, docs and code history could fund the next release.
SaaS companies, software vendors, IT services firms and development shops hold years of support tickets, documentation, code with review history, product analytics and sales conversations that AI developers need. We handle de-identification, secrets scanning, buyer vetting and contracts alongside your counsel. You keep ownership and approve every use.
Who fits
- B2B SaaS companies with 25 or more employees
- Software vendors and ISVs with large installed bases
- IT services, MSPs and custom development shops
- Developer tools and API companies
Get a data valuation
Ten minutes, no files. We reply within one business day.
Most valuable data types
What buyers want from software companies.
Coding and technical assistants are among the most used AI products, and developers have largely exhausted public code and forums. Private repositories with review history, real support tickets and product documentation from working software companies teach models how software is built, broken and fixed in production.
Technical support tickets and chat transcripts
Real bug reports, configuration problems and their resolutions are among the most useful conversational data for technical assistants, and software companies have them in volume.
About support tickets and chatsInternal repositories with commit and review history
Production code with commit messages, review comments, tests and linked issues shows how software is actually built and maintained, which public repositories only partly capture.
About code repositoriesProduct documentation, runbooks and internal wikis
Precise technical writing paired with the code and tickets it describes trains models to answer grounded, product-specific questions.
About documents and knowledge basesSales demos, onboarding and customer success calls
Recorded calls where software is explained, questioned and configured are domain-specific speech that sales and support assistants need.
About call recordings and transcriptsProduct usage and event logs
De-identified usage data linked to tickets and churn outcomes trains models that predict problems and recommend next steps.
About transactions and operationsDeal histories and win and loss notes
Opportunity stages, objections and outcomes over years teach models how B2B software is bought and sold.
About crm and sales histories
Illustrative scenario
A 180-person B2B SaaS company
9 years of support tickets (1.1 million), 40 repositories with full review history, product documentation, and 15,000 hours of recorded customer calls
$200K to $1.2M
Illustrative estimates based on public benchmarks and our valuation model. Actual value depends on uniqueness, quality, rights and buyer demand. How we estimate
What drives the range
- Tickets linked to resolutions and code changes
- Review history adds value to code
- Customer DPAs and secrets exclusion narrow the set
Compliance
Customer contracts, DPAs, trade secrets and open source handled with your counsel
Customer names, personal data and anything covered by your data processing agreements are de-identified or excluded before any sample is shared, and your customer contracts and privacy policy are reviewed with your counsel for what they permit. Repositories are scanned for secrets, credentials and customer data, proprietary algorithms you designate are excluded, and open source licenses in the codebase are inventoried so that licensing never conflicts with them. Buyers are contractually barred from re-identification attempts, and permitted use is limited to model training.
Standards in play
- Customer contracts and DPAs
- Trade secret scoping
- Open source license inventory
- Secrets and credential scanning
FAQ
Software questions
Our customer contracts say we cannot share customer data. Does that end the conversation?
No. Customer data is removed or de-identified, and what gets licensed is your own tickets, documentation, code and de-identified patterns, reviewed against your DPAs and contracts with your counsel. Where a contract clearly prohibits any derivative use, that customer's data is excluded.
Does licensing our code mean giving up our competitive advantage?
Scope is yours to set. Proprietary algorithms, product roadmaps and anything you designate stay out, secrets are scanned and removed, and contracts restrict use to model training with no resale. Many companies start with tickets and documentation and consider code later.
What about open source libraries in our repositories?
Third-party open source code is inventoried and excluded or handled according to its license, so only your original work is licensed. The inventory is documented with your counsel and the buyer.
Find out what your software data is worth.
Ten minutes, no files, NDA on request. We reply within one business day.