Direct answers to the questions that matter.

Connected workflow data: records that follow real work from the initial request through the information reviewed, the decision made, the action taken and the final outcome. A dataset that links a support ticket to its diagnosis, resolution and satisfaction result teaches far more than a folder of isolated documents.

Most opportunities involve established businesses with roughly 20 to 700 employees: large enough to run real systems at meaningful volume, small enough to make decisions quickly. That range is a guideline, not a rule. Smaller and larger companies can qualify, particularly with deep history or specialized workflows.

Strong operating datasets carry an indicative potential licensing value of $100,000 to $4 million or more; proprietary codebases $10,000 to $1 million or more. These are indicative potential ranges, not valuations or promises. Actual value depends on quality, volume, rights, permitted uses and buyer demand at the time.

Historical depth, number of records, connected systems, workflow complexity, specialized industry knowledge, the ability to link actions to outcomes, quality and consistency, clear ownership and consent, licensing scope, exclusivity, and whether future deliveries are possible. Buyer priorities also shift over time. Data that is sought after today may be commoditized later.

No. The initial assessment is based on a description: which tools you use, how many years of history you hold, approximate volumes and how your workflows run. Nothing leaves your systems unless a licensing agreement defines exactly what is shared, how it is prepared and what it may be used for.

That does not disqualify you, but it shapes the scope. You control which systems and fields are considered, and sensitive or third-party information can be excluded. Where customer or client data would be involved, appropriate rights and legal review come first. De-identification before delivery is standard practice, but anonymization alone does not resolve an ownership or contractual restriction.

Client information should not be included simply because it can be anonymized. We first determine what the firm owns and has the right to license. An opportunity may focus on firm-owned workflows, internal operations, administrative records or other information that does not require the inclusion of client data. Any dataset involving client information requires appropriate rights and legal review.

No. Licensing grants defined, limited rights, typically for approved AI-training or evaluation purposes, under negotiated terms. You keep ownership of your systems, records and intellectual property. Scope, duration and exclusivity are negotiated, not assumed.

Yes. You decide which systems and which fields are in scope, and sensitive or unnecessary fields can be excluded. Nothing is extracted until the scope and the permitted uses are defined contractually.

The engineering record around the code: commit history, issues, pull requests, code reviews, tests, CI/CD workflows and documentation. Buyers value repositories where a real problem can be traced to a tested solution, and where the project can actually be built and run. Source code alone, without that context, is generally worth less.

Yes. Age is often an advantage: older records and retired products tend to carry fewer active confidentiality constraints, and their history is complete. What matters is the quality of the record, not whether the product is still running.

The initial assessment is a short conversation and a written description. If there is a fit, rights review, scoping and buyer discussions typically run over weeks, and longer where legal or privacy review is involved. Complex or regulated datasets take more time.

No. Buyer interest varies with demand, quality and rights. We tell you early and honestly whether an opportunity is worth pursuing, and no transaction or compensation is ever guaranteed.

Use the form below and select “I am referring this company,” or send a high-level description of the business. We handle qualification, buyer discussions and the licensing process from there. Referral terms are agreed in writing before introductions are made. Never send client data, exports or credentials with a referral.