Buyer profile · Turing (Project Lazarus)

How to apply to Turing (Project Lazarus)

Updated October 25, 2026 · How we research

Before you apply

1. Check you meet Turing (Project Lazarus)'s published rules: no minimum published; accepts operating, closing, closed companies.
2. List your systems, years of history and who can export each one. The data inventory worksheet helps.
3. Confirm the records are yours to license and note what must stay out (HR, legal, customer data held under contract, regulated data).
4. Decide in advance whether you would accept an exclusive license, and for how long.

Get the free data inventory worksheet

What Turing (Project Lazarus) takes

• Team communication: threads, channels and decision context
• Source code, code reviews, tickets and iteration history
• Wikis, runbooks, schemas and internal knowledge
• Records of how decisions and trade-offs were made
• Areas named: software and engineering, finance and accounting, customer support, sales and CRM, legal and contracts, operations and logistics

Turing (Project Lazarus)'s process

1. Intake call under NDA, usually scheduled within one business day
2. Sampling: Turing reviews a representative slice, usually within a week
3. Offer: a single valuation and one contract

How it pays

upfront: one payment, no retainer or recurring commitment; Turing confirms the figure after sampling. Payment timing: Not published. Turing says it confirms the figure after sampling, usually within a week.

Questions to ask before you sign

• Who signs the agreement with us, and in which state is that company registered?
• When exactly are we paid, and what has to happen first?
• Is the license exclusive? For how long, and for which uses?
• Who de-identifies the records, where, and can we review a sample of the result?
• What happens to the copy when the license ends?

Not a fit? See alternatives to turing (project lazarus), or check which programs fit.