01 / UNDERSTAND THE HISTORY
Today’s company and yesterday’s records are different things.
A current headcount describes the company now. A peak headcount helps describe the organization that created its historical records. Neither tells you, by itself, what is still retained or available for review.
That is why Liquidory asks for current full-time employees, the largest full-time team at any point, the approximate peak period and years operating. We ask separately about current US-based employees when that information is known.
Build the inventory around retained history.
| Question | What to establish |
|---|
| Where? | Systems, workspaces, shared drives, databases and archives. Include retired systems only when records are still accessible. |
| When? | Actual retained dates, missing periods and migrations. Years operating is not the same as years of usable history. |
| What? | Record types and the work they describe. Distinguish human-authored material from notifications, duplicates and generated artifacts. |
| Who controls it? | The owning entity, administrator and person authorized to evaluate a potential license. Access alone does not answer the ownership question. |
| How much? | Measured counts or storage estimates with their source and date. Mark unknown quantities instead of extrapolating from headcount. |
A smaller current team is not an automatic reason to stop. Explain what happened and what history remains. Any buyer still needs to apply its own criteria.
02 / DEFINE THE BOUNDARIES
Know what could be considered before preparing an export.
Start with a description of the collection and known exclusions. This lets the company assess the opportunity without sending raw records into an initial conversation.
Separate possession from permission.
An administrator may be able to export a workspace containing customer material, licensed content or employee information. That capability does not establish permission for a new use. Ask the relevant owners and advisers to review the actual contracts and obligations.
- Ownership and authority: which entity owns the material, and who can authorize the proposed scope?
- Third-party material: what belongs to customers, vendors, contributors or licensors?
- Exclusions: which systems, individuals, projects or record categories must stay out?
- Intended use: what is the named recipient proposing to do with the collection?
- Preparation: what filtering, removal, review and acceptance checks would be required?
Treat privacy as a review question.
Names are only one way records can reveal information about people or organizations. Context, combinations of attributes and free text can matter too. Do not treat a promise to remove names as proof that a transfer is appropriate.
This guide describes scoping questions, not a legal conclusion about a particular dataset. Liquidory’s initial form accepts company descriptions, not raw corpora. See the assessment privacy notice for what this website collects.
03 / EXAMINE THE QUALITY
Describe the evidence a collection preserves.
Liquidory’s review approach starts with the work a buyer wants to understand. A collection should be described in terms of its content, sequence, limitations and permitted uses—not an assumed value per gigabyte.
Context and continuity
A resolved support case is more interpretable when it includes the original problem, relevant investigation and resolution. A product change is easier to assess when the requirement, reviews and version history can be related. These are examples of useful questions, not a claim that any specific corpus will improve a model.
Provenance and coverage
Document the source system, export date, retained period and known gaps. Count records by type and period. Ask whether the archive overrepresents successful outcomes, active accounts or a recent migration.
Time and outcomes
When an evaluation concerns a decision, separate what was available at decision time from what became known later. Otherwise an answer may appear strong because the outcome is already present in the input.
Acceptance criteria
Agree what a reviewer would check in an authorized sample: linkage, readable content, duplicate rate, coverage, exclusions and any required labels. Define what passes, what needs remediation and what remains unknown before scaling preparation.
Keep observed facts, estimates and hypotheses separate. “Contains linked support cases” is a collection description. “Improves diagnostic reasoning” requires an evaluation.
04 / PLAN THE REVIEW
Use a separate decision gate for each stage.
| Stage | Questions and outputs |
|---|
| Initial assessment | Company profile, retained history, systems and known restrictions. The website returns an initial screen, an on-page summary and a PDF. |
| Scope review | Confirm authority, exclusions and missing information. Determine whether a further buyer conversation is worth pursuing. |
| Buyer review | With permission, discuss the collection against the buyer’s intended use and acceptance criteria. Any sample requires its own agreed scope. |
| Commercial agreement | Address the licensed material, permitted uses, recipients, duration, exclusivity if proposed, preparation duties, fees and payment conditions. |
| Authorized delivery | Use the agreed transfer method and verify what was delivered against the approved scope and acceptance requirements. |
The online assessment completes the first stage only. Further stages depend on human review, buyer interest and agreement. Liquidory does not automatically connect your systems, introduce your company or transfer data.
What your initial result means
The result highlights whether the available answers suggest a review conversation or a need to clarify history or rights. It is not buyer approval, a valuation, a legal determination or a commitment to purchase.
05 / EXPLORE BUYER ROUTES
Public entry points are useful starting points.
Different routes have different requirements. These primary sources explain their own programs; Liquidory is independent of the organizations listed.
Company-data supplier programs
Handshake’s company-data page ↗ publishes program criteria and an application that distinguishes current from peak full-time employees. Its payout range is a program-level statement, not an offer for an individual company.
Direct lab interest
OpenAI’s data partnerships overview ↗ describes interest in non-public collections and public and private dataset collaborations. Its page also identifies sensitive, personal and third-party information as material it is not seeking.
OpenAI’s direct interest form ↗ is a public entry point. Submitting interest is not acceptance and does not establish payment, exclusivity or a commercial relationship.
What affects a commercial conversation?
Ask about the actual scope, intended use, preparation burden, licensing restrictions, acceptance conditions and payment timing. Headcount and storage volume alone do not answer these questions.
Public pages reviewed September 19, 2026. Programs and requirements can change; confirm current terms with the relevant buyer. The OpenAI overview was originally published November 9, 2023.
06 / PREPARE A USEFUL BRIEF
Make the next conversation specific.
For a company considering a partnership
- Describe the business, current team and historical peak.
- List relevant systems and the dates of history still retained.
- Explain a few workflows the records capture, without including confidential examples.
- Identify the decision-maker, restrictions and questions that remain unresolved.
- State whether an administrator could help assess export readiness.
Create your private company assessment ↗
For an AI team seeking data
- Define the task or capability you want to study.
- Describe the domain, record types and temporal coverage you need.
- Specify the intended use and acceptable licensing scope.
- List the evidence needed to assess a sample and the acceptance criteria.
- Provide a timeline and explain any delivery or preparation constraints.
Email Liquidory at ops@avatar33.com ↗. Start with a high-level brief; do not email raw company archives or credentials.