Software companies generate the records buyers want most for coding and support agents: issues, pull requests, reviews, incidents, support tickets, and the documentation that connects them. The records are already structured, timestamped, and linked across systems. The question is usually rights, not relevance.
No dataset needed to start. Current threshold: 20+ desk staff, 3+ years of records, data in 3+ systems.
Every industry has records that are excluded as a class, records that need consent, and records that are clearly yours. These are the ones that come up in technology & software manifests. Your counsel draws the final line.
Informational only. We do not provide legal, tax, or compliance advice, and we do not decide what your company is permitted to license. Every seller we represent has counsel review the manifest before buyers see it.
Technology and software companies tend to land toward the upper part of the range: buyer demand for engineering and support records is the strongest in the market, the data is already structured, and rights are usually clear for proprietary code.
Years of continuous history, outcomes attached, and linkage across systems move the number more than industry does. A manifest tells you where your company actually sits; the estimator is a rough first pass.
The multiplier is one of several published factors behind the estimator. It reflects current buyer demand for this sector's workflows and the usual share of records that survive the rights screen.
Indicative range observed across the market for single-company operational data licenses. Not a quote. Actual value depends on buyer demand, data quality, rights, and exclusivity.
Issue triage, code review, release and incident records.
Issue → diagnosis → resolution, thousands of times over.
How your team solves problems in real time.
Playbooks, templates, proposals, checklists, process docs.
Deal stages, notes, and why customers said yes or no.
No. Many software sellers license the records around the code (issues, reviews, incidents, support, docs) and keep the code out, or include only the diffs under review. Where code is included, the license defines the field of use and you choose the repositories.
Using open-source dependencies does not. The manifest covers your own repositories and records with third-party code excluded. Forks of open-source projects and contributions you made upstream are not yours to license, and your counsel confirms ownership of each repository in scope.
That is what field-of-use terms are for. A license can restrict the buyer to model training and exclude building a competing product from your records. Competing offers make those terms negotiable, which is one reason we run a process rather than take the first offer.
Seven questions. No dataset. First offer in 24 to 48 hours of a complete manifest.
Measured from a complete data manifest. A first offer is a process target, not a guarantee; buyers decide eligibility, price, and terms.