Avelence and Turing's Project Lazarus describe different kinds of service. Avelence is an owner-side commercial advisory service focused on research, dataset positioning, licensing strategy and introductions. Turing publicly describes Lazarus as a program to acquire a company's operating record in a one-time transaction and prepare it as training data. An owner should compare the scope, rights, control and obligations in the actual proposal, not assume either route is suitable from its headline description.

This is a comparison of publicly described models, not an endorsement or a claim that either party will accept a particular company. Program terms can change, and company descriptions are provider statements. Verify current terms directly before making a decision. This article does not provide application instructions.

What the public descriptions say

Turing's official Lazarus page, checked on 3 November 2026, describes a one-time acquisition of a company’s operating record and preparation for AI training. It names software, financial services, healthcare, marketplaces, infrastructure and businesses retiring legacy systems among its examples. These are Turing’s published descriptions; the company-specific contribution, rights and commercial terms need to be established in the actual proposal.

Avelence provides commercial advisory rather than acquiring the data. It includes commercial research, dataset positioning and licensing strategy, with the possibility of introductions. A company can authorize Avelence in writing to lead specified buyer discussions, work alongside it, or identify opportunities the company closes. The engagement should identify the research or negotiation output the owner needs.

The same Lazarus description says that owners retain their underlying data and that defined rights are acquired under one agreement. Consequently, the word acquisition should not be read here as proof of a copyright assignment. Ask which rights the proposed agreement actually grants.

Is the company assessing an acquisition or choosing its licensing strategy?

A one-time acquisition route asks the company to evaluate a transfer or acquisition proposal for a defined operating record. The key questions include what material and rights are covered, which uses and parties are included, what happens to copies and derivatives, and how payment and any continuing obligations work.

An advisory route helps an owner assess and position a potential licensing opportunity. It may involve researching more than one potential use or recipient, but it does not promise multiple offers or a better price. The owner retains decisions unless it grants a specific written mandate. A mandate to lead discussions is separate from permission to disclose the company's name, share data or authorize a recipient's access.

The labels can obscure overlap. A direct acquisition proposal may contain terms about licensing, reuse, confidentiality and ongoing support. An adviser may be authorized to help evaluate one proposal. Read the contract, not the marketing category.

Questions that make the comparison concrete

What exactly is covered? Identify systems, date ranges, record types, versions, derived material and exclusions. “Operating record” needs a specific definition in a contract.

What rights move, and for how long? Check ownership, exclusive or non-exclusive rights, sublicensing, territory, field, term, termination and post-expiry use. Ask what the owner may still do and what the recipient may pass onward. Review the actual grant and restrictions rather than treating an acquisition or licensing label as an answer.

Who prepares the material? Clarify extraction, redaction, transformation, privacy review, quality checks, delivery, rework and cost allocation. A party offering to prepare data does not thereby take every legal or privacy responsibility from the owner.

What does the company receive and when? Separate fixed commitments from conditional amounts and projections. Define acceptance, reporting, payment dates, adjustments and recourse. A public program description does not establish a valuation.

How much choice remains with the company? Ask whether the owner can compare alternatives, negotiate scope, retain some rights, or decline without an ongoing restriction. A broad archive and a bounded license can have different consequences.

How do the stated acquisition and advisory roles compare?

Decision question Turing Lazarus public description Avelence service
Stated role One-time company operating-record acquisition and preparation for AI training Commercial advisory, buyer research, positioning, licensing strategy and introductions
Who should examine scope? Company and counterparty through the proposed agreement Company, with advisory support only within an agreed mandate
Does the public description prove eligibility or acceptance? No No buyer acceptance or transaction is promised
Does it determine rights or price? No; review actual terms No; negotiate based on actual scope and evidence
Is data access automatic? No; separate permission and contract terms matter No; disclosure and recipient access require separate authority

The comparison concerns stated responsibilities. Fees, licensing restrictions and counterparties need to be established in the actual proposed agreements.

When each kind of conversation may help

An owner focused on a potential one-time transfer may want to understand exactly what is being acquired and whether the rights, term, payment and continuing obligations fit its strategy. An owner still deciding which data categories or licensing uses to pursue may value independent scoping and market research before authorizing a particular discussion. Both may require legal, privacy, technical and financial review.

If the first conversation would require identifying a company or sending a sample, pause to confirm the authorized recipient, purpose and permission. An inquiry or a confidentiality agreement alone is not a transfer of rights.

What should the owner clarify before progressing?

Create a one-page scope note: what material is potentially in scope, what is excluded, what rights are known, what permission questions remain, and what decision the company wants to make. Then request written terms from any counterparty and compare them using the same questions. Keep unknowns visible and avoid accepting generic assurances in place of defined obligations.

The appropriate route depends on the company's objectives and the terms actually offered. Neither a buyer program nor an advisory service should be treated as proof of demand, price or acceptance.

The company data profile can describe the finite historical scope, systems and known gaps before the company requests acquisition terms or advisory work. The same description helps reveal whether the two conversations concern materially different contributions.

Explore these topics

Yananai A. Chiwuta

About the author

Yananai A. Chiwuta is the Founder of Avelence. His work covers data-owner relationships, enterprise buyer research, and the commercial decisions behind operational-data licensing.