Seller intake

Your contact details

Who we should talk to about this opportunity.

What are you submitting?

Pick one to see what it covers.

Company recordsA datasetAn RL environment

Choose what you're submitting.

Not your company? Refer it instead and we'll take it from there with the owner.

First name

Add your first name.

Last name

Add your last name.

Title or role

Add a title or role.

Email

Add an email address.

Phone number (optional)

Only used if we have questions about your answers.

Are you the decision maker for this opportunity?

YesNo

Choose Yes or No.

How did you hear about us?

Referral partnerProfessional networkFound you myselfOther

Choose how you heard about us.

Who referred you?

Add who referred you.

The company

The business a buyer would license from, and where it's based.

Company name

Add the company name.

Is the legal entity name different from the company name?

YesNo

Choose Yes or No.

Legal entity name

Add the legal entity name.

Which location can you share?

Either one works.

State of incorporationHeadquarters location

Choose which location you're giving.

Location

Add the location.

Country where the company is based

Where it's registered and headquartered.

Choose a country.

Sub-vertical or specialty

Add the sub-vertical or specialty.

Annual revenue, last twelve months (USD)

$

A rounded figure is fine.

Enter annual revenue in US dollars.

The business

A short picture of what the company does, in plain words.

WebsiteWe don't have a website

Add a website, or tick that you don't have one.

LinkedIn company pageWe don't have a LinkedIn page

Add the LinkedIn page, or tick that you don't have one.

What does the business do?

Two or three plain sentences is plenty.

Describe the business.

Who are your customers?

BusinessesConsumersBoth

Choose who your customers are.

Typical job or contract

Size, length or value, whichever fits best.

Describe a typical job or contract.

What does a typical job look like from start to finish?

Walk through a typical job.

Team and history

Who works there, and how far back the records go.

People

Full-time headcount at each office or site

Desk staff work mainly at a computer. Non-desk staff work on the road, in the field or on a floor. Count contractors in whichever column matches their work.

Fill in at least one location: city, desk staff and non-desk staff.

US W-2 employees

Add the W-2 headcount.

Contractors (optional)

Employee email inboxes

Add the number of inboxes.

Peak full-time employees

Add peak headcount.

Year it peaked

Add the year.

History and records

Year founded

Choose the year founded.

Years of data actually retained

From the oldest records that still exist to today, across all systems.

Add how many years of data you keep.

Earliest accessible record

Add the earliest record date.

Latest accessible record

Add the latest record date.

Month and year is enough.

Is the company still operating and generating data?

YesNo

Choose Yes or No.

Systems and data

Where the company's history lives.

Anywhere else the data lives? (optional)

System details

One card per system: what it's used for, what's in it, and how much.

One card per system

Estimates are fine, but every figure needs a value.

No systems selected yet.

Fill in every box on each card. Only notes are optional.

Data and files

The headline numbers, and what's actually in the files.

Headline numbers

Roughly how much data does the company have, all storage combined?

Email, drives, databases and apps together. An estimate is fine, but be specific.

Add a size.

How fast could you provide an export or access?

Ready now1 to 2 weeksAbout a monthLonger or unsure

Choose how fast.

Estimated share of your data in English

Your best estimate is fine.

Choose a share.

What's in the files

What would we find in your files? Describe them in your own words.

What kinds of documents, roughly how many, and anything unusual. The more specific, the better the offer.

Describe what's in the files.

The dataset

What it is, who it's from, and why a buyer would want it.

Dataset name

Add the dataset's name.

Your organization

Or your own name if you're independent.

Add your organization.

Website or link (optional)

What is the dataset?

One to three sentences.

Describe the dataset.

Why would an AI company want it? What could it be used for?

Describe how it could be used.

Scale, coverage and rights

How big it is, what it covers, and who can license it.

Approximate scale

Add the approximate scale.

Date range covered

Add the date range.

Countries, regions and languages covered (optional)

Main file formats

Add the main file formats.

Where did the data come from?

Describe where it came from.

Do you own or control the rights to license or sell it?

YesNoPartlyUnsure

Choose one.

Any restrictions on commercial use, sharing, resale or model training? (optional)

Content and quality

What's inside, and anything a buyer should know about it.

Main fields or content types

Describe the main fields or content.

Does it include labels, annotations, outcomes or useful metadata?

YesNoPartlyUnsure

Choose one.

Does it contain personal, sensitive or confidential data?

NoYesUnsure

Choose one.

If yes, describe it at a high level (optional)

Don't paste any actual records.

Known quality issues, gaps, duplication or bias (optional)

What makes it unusual or hard to reproduce?

Describe what makes it unusual.

Commercial terms and delivery

How a buyer would get it, and when.

Can you provide a small representative sample?

YesNoMaybe, on request

Choose one.

How can it be delivered or accessed?

Add how it can be delivered.

Commercial terms or asking price (optional)

How soon is it available?

Ready now1 to 2 weeksAbout a monthLonger or unsure

Choose how soon.

The environment

What it simulates, who it's for, and why it's hard to rebuild.

Environment or product name

Add the environment's name.

Your organization

Or your own name if you're independent.

Add your organization.

Website or link (optional)

What does the environment simulate or represent?

One to three sentences.

Describe what it simulates.

What kinds of agents or tasks is it intended for?

Describe the intended agents or tasks.

What makes it valuable or hard to reproduce?

Describe what makes it valuable.

Technical setup

What it runs on and how it's accessed.

Primary interface or API

Add the primary interface.

Programming languages

Add the languages.

Supported operating systems (optional)

Required hardware (optional)

Typical setup or install time (optional)

RL specification

Observations, actions, rewards and episodes.

Observation space

Describe the observation space.

Action space

Describe the action space.

Reward signal or objective

Describe the reward or objective.

Episode start and termination conditions (optional)

Is it deterministic or stochastic? (optional)

DeterministicStochasticConfigurableMixed

Single-agent or multi-agent? (optional)

Single-agentMulti-agentBoth

Approximate episode length (optional)

Can task difficulty or parameters be varied? (optional)

Performance and validation

How fast it runs, how it scales, and how it was checked.

Approximate environment steps per second (optional)

Can multiple environments run in parallel? (optional)

YesNoPartly, with limitsUnsure

Typical CPU, GPU and memory usage (optional)

Known bottlenecks or scaling limits (optional)

Does it support headless execution? (optional)

YesNoPartlyUnsure

How was the environment validated?

Describe how it was validated.

If it's based on the real world, what data, models or systems is it derived from? (optional)

Known sim-to-real gaps, simplifications or unrealistic assumptions (optional)

Existing benchmark results or trained-agent performance (optional)

Does it have a baseline agent or reference policy? (optional)

YesNoIn progressUnsure

Rights, delivery and support

What you own, what you'd deliver, and what help comes with it.

Do you own or control the environment and its source and assets?

YesNoPartlyUnsure

Choose one.

Third-party code, assets, models, data or licenses it depends on (optional)

List private APIs, commercial game engines, licensed assets or outside services explicitly.

Any restrictions on redistribution, modification, research or commercial use? (optional)

Paid APIs, proprietary software or outside services needed to run it? (optional)

What exactly would be delivered?

Describe what would be delivered.

Can you provide a demo, video or runnable sample?

YesNoOn request

Choose one.

How is it currently packaged or hosted? (optional)

How quickly could you provide access?

Ready now1 to 2 weeksAbout a monthLonger or unsure

Choose how quickly.

What documentation is included? (optional)

Would you provide setup help, maintenance or updates? (optional)

YesNoLimited or paidTo be discussed

Anything else we should know? (optional)

Review and submit

A person reviews every intake before any offer is made. Change any section before you submit.

Tick the box above to submit.

Your contact details

The company

The business

Team and history

People

History and records

Systems and data

System details

Data and files

Headline numbers

What's in the files

The dataset

Scale, coverage and rights

Content and quality

Commercial terms and delivery

The environment

Technical setup

RL specification

Performance and validation

Rights, delivery and support

Review and submit

Intake received